Transparent Image Turns Black or White
Last reviewed:
A black or white background can come from four different places: the file never contained alpha, conversion removed it, an application flattened it, or the viewer is merely showing transparency over its own background. Identify which one happened before editing the image.
Quick diagnosis
| What you see | Likely explanation | Best test |
|---|---|---|
| Solid white rectangle everywhere | White pixels are baked in or alpha was flattened | Inspect alpha in an editor |
| Black only in one viewer | Viewer background or unsupported alpha | Open over a colored layer elsewhere |
| Background changed after JPEG export | JPEG cannot store alpha | Check output format |
| White/dark outline around subject | Matte contamination or alpha interpretation | Test on opposite-color backgrounds |
| Checkerboard visible in final image | Checkerboard was baked into pixels | Zoom and inspect color channels |
Step 1: prove whether alpha exists
Do not infer transparency from an editor’s checkerboard, filename, or product-page preview. Open the file in an application that can display channels, then place it above a bright color that does not appear in the image. If the new color shows through cleanly, alpha exists. If white or black remains, those areas are probably opaque pixels.
A PNG can be fully opaque; PNG support for alpha does not mean every PNG uses it. A JPEG is always opaque in this context.
Step 2: compare source and output formats
If the source has alpha and the result does not, confirm whether the destination supports transparency. PNG, WebP, AVIF, and suitable SVG workflows can represent useful alpha. JPEG cannot. ForgeConvert BMP output is 24-bit and removes alpha; static GIF has much more limited transparency than full-alpha formats.
When an opaque output is required, choose the matte intentionally. White fits a white document; black may fit dark artwork; a brand color can avoid a visible rectangle in a fixed layout. There is no universal matte for content that will appear on multiple backgrounds.
Step 3: determine whether the problem is display-only
Some viewers show transparent pixels over black, white, or a checkerboard but do not bake that surface into the file. Exporting a screenshot of the viewer does bake it in. Test the original in a browser and a channel-aware editor, and inspect the page or app background separately.
On the web, transparent images reveal the CSS background of their element or ancestors. A theme switch can therefore change the apparent background while the image bytes remain identical.
Step 4: diagnose edge halos
A halo is different from a completely lost background. Partly transparent edge pixels have both color and opacity. If their color was prepared against white, they can look pale over black. Resampling, sharpening, or converting between straight and premultiplied alpha incorrectly can spread the matte into visible pixels.
- Return to the cleanest alpha-bearing master.
- Remove any old matte contamination before resizing.
- Resize color and alpha with an alpha-aware tool.
- Export once to the target format.
- Inspect the result at 100% over white, black, and saturated backgrounds.
Cause-specific fixes
The output is JPEG
JPEG cannot preserve alpha. Re-export to PNG, WebP, or AVIF when the receiving environment supports it. If JPEG is mandatory, flatten onto the exact intended background and keep the transparent master separately.
The original is an opaque JPEG
JPG to PNG changes the encoding but does not isolate the subject. Background removal requires a mask, selection, clipping path, or segmentation workflow—not ordinary format conversion.
A transparent PNG fails in one application
Confirm that the application supports full alpha rather than only binary transparency. Test a current version and a minimal known-good PNG. If the application requires another supported format, a route such as PNG to WebP may help only when that application supports WebP alpha.
An SVG becomes opaque after rasterization
Check the selected raster destination and the SVG’s own background objects. SVG to PNG can create transparent raster output when the trusted source has no opaque background and the renderer preserves alpha.
BMP output loses transparency
ForgeConvert writes 24-bit BMP output, so select an alpha-capable destination instead when transparency is a requirement.
A controlled recovery workflow
- Preserve the source and identify its real format.
- Verify alpha in a channel-aware editor.
- Check whether transparency is full, partial, or absent.
- Choose a destination that supports the required model.
- Convert a single edge-sensitive sample.
- Test it in the real destination on multiple backgrounds.
- Only then process the rest of the assets.
Common mistakes
- Converting JPEG to PNG and expecting automatic background removal.
- Using a screenshot of a checkerboard preview as the source.
- Testing only on a white canvas.
- Flattening before the final background is known.
- Assuming every application interprets alpha the same way.
- Repeatedly resizing an already matted derivative.
- Deleting the layered, vector, or transparent master.
Prevent the problem
Keep one clean alpha-bearing master, document the approved opaque matte, export named derivatives for each destination, and include a light/dark background check in quality control. For teams, store transparency requirements alongside dimensions and byte limits so a smaller opaque file is not mistakenly accepted as a successful result.
Frequently asked questions
Why does my transparent PNG have a black background?
The viewer may display transparency over black, the alpha channel may have been lost or misinterpreted, or transparent pixels may carry dark matte colors.
Why does transparency turn white in JPEG?
JPEG has no alpha channel. A converter or editor must replace transparency with an opaque matte, often white by default.
Can converting JPEG to PNG restore transparency?
No. Converting creates a PNG container but cannot know which opaque JPEG pixels should be removed.