Why Did My Transparent PNG Turn Black?

You have a logo on a transparent background. You upload it, or convert it, or drop it into a document, and the transparency becomes a solid black rectangle. The file was fine a moment ago.

Nothing is corrupt. Something along the way had to decide what to put where the transparency was, and it chose black.

The Alpha Channel, and Formats That Lack It

A transparent PNG stores four values per pixel: red, green, blue, and alpha — how opaque that pixel is. Alpha at zero means fully transparent, and the colour values there are typically meaningless, often left as zero. Zero red, zero green, zero blue is black.

JPEG has no alpha channel at all. It cannot represent “nothing here”. So converting a transparent PNG to JPEG forces a decision: every transparent pixel must become some actual colour.

A careful converter asks you, or defaults to white. A careless one simply drops the alpha channel and keeps whatever colour values were sitting underneath — which, as above, are usually zero. That is where the black comes from. It is not a deliberate choice of black; it is the absence of a choice.

Where This Bites

• Link preview images. Most preview renderers do not support transparency, and an Open Graph image with a transparent background commonly shows as a black card.
• iOS app icons. Apple requires no alpha channel at all. A transparent icon is either rejected or filled black — which is why so many submitted app icons look like a logo floating on a dark tile.
• Email. Several mail clients flatten images onto a background of their own choosing, and in dark mode that choice can be black.
• Office documents and printing. Transparency usually survives into PowerPoint and Word, but exporting to some formats, and most printing paths, flattens it.
• Older image viewers. Some display transparency as black rather than the chequerboard pattern you are used to — in which case the file is fine and only the preview is misleading.

The Fix: Flatten Deliberately

The reliable approach is to make the decision yourself rather than leaving it to whatever software touches the file next.

Before converting, place the image on a solid background of the colour you want and flatten it. Then convert. Now there is no transparency to lose, and no tool downstream has a choice to make.

Which colour depends on where it is going. White for most documents and light pages, your brand colour for a preview card, the actual page background if you know it. The point is that you pick it, once, knowingly.

And where transparency is genuinely supported — a website, an app interface — keep the PNG and do not convert at all. The problem only exists at the boundary where a format with alpha meets one without.

Which Formats Support Transparency

• PNG — full 256-level alpha. The standard choice.
• WebP — full alpha, and smaller files than PNG.
• AVIF — full alpha, smaller again.
• SVG — transparency is native; it is not a pixel format at all.
• GIF — only one bit. See below.
• PDF — supported, though printing may flatten it.
• JPEG — none. This is the one everyone trips over.
• BMP — technically possible, poorly supported in practice.

GIF’s One-Bit Transparency and the Ugly Halo

GIF supports transparency, but only as a switch: each pixel is either fully transparent or fully opaque. There is no partial.

This matters because smooth edges depend on partial transparency. A curved logo edge is drawn with pixels that are 30% opaque, 60% opaque, and so on, blending into whatever is behind. GIF cannot store those, so each one becomes either solid or gone.

The result is the jagged, hard-edged look of GIF logos, and the notorious white halo: if the image was made against white, the semi-transparent edge pixels get rounded to opaque white, and the logo arrives on a dark page wearing a pale fringe.

There is no setting that fixes this. It is the format. Use PNG or WebP.

The Same Problem in Reverse: the Pale Fringe

Occasionally a PNG with proper alpha still shows a light outline on a dark background. This is a related defect: the edge pixels were blended against white when the image was produced, and that white is baked into the colour values of the semi-transparent pixels.

The fix is upstream — export the image again from the original artwork against a transparent or similarly-dark background. Once the fringe is in the pixels, no conversion removes it.

Checking Before You Send

Two quick tests that catch almost all of this:

• Put it on black and on white. A logo that only looks right on one of them has a fringe problem. One that disappears on one of them needs a defined background.
• Check whether the destination supports alpha at all. If it does not — a preview card, an app icon, a print job — flatten it yourself before handing it over.

Quick Reference

• JPEG has no alpha channel; conversion must fill the transparent area
• Black appears because the discarded colour values under full transparency are usually zero
• Flatten onto a chosen colour yourself before converting
• Keep PNG or WebP wherever transparency is actually supported
• GIF has one-bit transparency — jagged edges and white halos, unavoidable
• A pale fringe means white was baked into the edge pixels; re-export from the original
• Test every transparent image on both black and white