Why your "transparent" PNG keeps showing white

You cut out a logo, saved it as a PNG, and the background is supposed to be gone. Then you drop the file somewhere and a white rectangle appears behind it anyway. Or a black one. The forums are full of half-answers for this, each describing one specific case, so you bounce between threads without knowing which applies to you.

There is no single bug here. “Transparent PNG shows a white background” covers at least five different situations, and the fix depends on which one you actually have. This walks through all of them so you can match the symptom to the cause yourself.

TL;DR: Either the transparency was never saved into the file, or it was saved and the place you are viewing it fills the empty pixels with its own color. Check the file first, then check the viewer.

What “transparent” actually means in a PNG

A PNG can carry an extra channel called alpha. Every pixel stores red, green, and blue values for its color, and the alpha value records how opaque that pixel is, from fully solid to fully see-through. When alpha says a pixel is transparent, there is no color to show. So whatever sits behind the image, a web page, a slide, a chat bubble, shows through.

That last point matters more than it sounds. A transparent pixel has nothing to display, which means something else always decides what fills the gap. On a website that might be the page color. In a document it might be white paper. The PNG itself never contains “white.” It contains “nothing here,” and the gap gets painted by whatever is underneath.

Keep that split in mind: the file either has working transparency or it does not, and even when it does, the background you see is chosen by the viewer. Almost every case below is one of those two problems.

The five common causes

1. The transparency was flattened on export

This is the most frequent one. You deleted the background in your editor, but when you exported you saved a flattened copy that included a solid background layer, or you exported a format that merged every layer into one opaque image. The checkerboard you saw while editing was just the editor’s way of showing emptiness. It does not get saved unless the export keeps the alpha channel.

The tell: the background is a clean, uniform color (usually white) with hard edges that match your canvas exactly, and it looks identical in every app you open it in.

The fix: re-export and make sure transparency is enabled in the export dialog, or that you are not adding a background layer. If the original editable file is gone and all you have is the flattened PNG, you need to remove the background again from the image you have.

2. The file is really a JPG with a .png name

A JPG cannot store transparency at all. There is no alpha channel in the format. If someone renamed photo.jpg to photo.png, or an app exported a JPG but labeled it .png, the file is opaque and will stay opaque. Renaming changes the label, not the pixels.

The tell: there is no way to make it transparent no matter what you try, and the file size is suspiciously small for the detail in the image (JPG compresses hard). You may also notice faint blocky artifacts around sharp edges, which is a JPG signature.

The fix: re-save it as a genuine PNG, then remove the background, because the background pixels are currently solid and baked in.

3. It was saved as PNG-8 with limited or no alpha

PNG comes in a few flavors. PNG-8 uses a small palette of up to 256 colors and, in many tools, only supports on/off transparency or none at all. PNG-24 (often listed as PNG-32 when alpha is included) supports smooth, partial transparency. If your editor saved PNG-8 to shrink the file, you can lose soft edges or transparency entirely.

The tell: the edges of your cutout look jagged or stair-stepped, or there is a faint colored halo around the subject where soft pixels got forced to opaque. Sometimes the transparency works but looks crude.

The fix: re-export as PNG-24/32 with full alpha. If a matte color was baked into the halo during the PNG-8 save, you may need to clean up the edges or redo the cutout.

4. The alpha exists, but the viewer composites it onto white

Here the file is fine. The transparency is real and correct. The place you are looking at it fills the empty pixels with its own background color, and that color happens to be white. This is not a problem with your image; it is just how that destination renders transparency.

The tell: the image looks transparent in one app (your file preview, a browser tab on a colored page) but shows a solid background in another (a document, a slide, a messaging app). Same file, different result depending on where you view it.

The fix: usually nothing is wrong with the PNG, so leave it. If you need it to blend into a specific background, place it on that background deliberately. If a destination refuses to honor transparency, your only option is to design around its background color.

5. A fill or matte was baked in by the editor

Some editors, when you flatten or export, composite your image against a “matte” color to smooth the edges, and that color gets written into the pixels. Background-removal features can also leave a thin rim of the old background, or fill the cleared area with white if the alpha was not written correctly.

The tell: most of the background is gone, but a thin outline or a partial fill remains, often white or a near-match to the original background. It looks like the removal almost worked.

The fix: redo the cutout with the matte turned off, or clean up the leftover edge pixels.

Cause, tell, and fix at a glance

Cause	Tell	Fix
Flattened on export	Uniform background, same in every app	Re-export with transparency on, or remove background again
JPG renamed to .png	Cannot ever go transparent, tiny file, blocky edges	Re-save as real PNG, then remove background
PNG-8, limited alpha	Jagged edges or colored halo	Re-export as PNG-24/32
Viewer composites onto white	Transparent in one app, solid in another	Often nothing; design for the destination
Matte or fill baked in	Thin rim or partial fill remains	Redo cutout with matte off, clean edges

Where transparency tends to “disappear”

A few destinations reliably make people think their PNG broke when it did not.

Pasting into Word or Slides often drops the image onto white. The transparency is intact, but the page behind it is white, so the empty pixels read as white. The same image on a colored slide would show the slide color through.

Some chat and messaging apps render image messages on a fixed bubble color and composite transparent PNGs onto it. Dark-themed apps composite onto black, which is why a “white background” complaint sometimes arrives as a “black background” complaint instead. Same cause, darker canvas.

Printing flattens everything onto paper. Paper is white, so transparent areas print as white by definition. There is nothing to fix in the file; print just has no concept of “see-through.”

In all three, the file is doing exactly what a transparent PNG should. The background you dislike belongs to the destination, not the image.

How to fix it for real

If your problem is in causes 1 through 3 or 5, the file genuinely lacks working transparency and you need to rebuild it. Two free, in-browser options at image.hivly.net handle the common cases: convert an image to a proper PNG with a real alpha channel, or remove a solid background so the subject sits on true transparency. Everything runs locally in your browser, so the file never leaves your machine and you do not need an account.

If your problem is cause 4, the viewer compositing, your PNG is already correct. Open it on a colored or checkered background to confirm the transparency is there, then place it deliberately wherever you need it rather than fighting the destination’s background color.

The quick triage: open the same file in two different apps. If the background changes between them, you have a viewer issue and the file is fine. If the background follows the file everywhere, the transparency was never saved and you need to remake it.