Guide
PNG vs JPG: Why Your Transparent Background Turns White
You removed the background, then it came back as solid white. Here is exactly why — PNG vs JPG, alpha channels, and how to save a file that actually stays transparent.
TL;DR
- JPG cannot store transparency — it has no alpha channel at all, in every app and every browser, with no exceptions.
- If a transparent image "turned white," it was saved, exported, pasted, or re-opened as a JPG somewhere along the way.
- PNG and WebP both support a full alpha channel — keep transparent images in one of these, always.
- There is no setting that fixes this after the fact — the fix is going back to the original transparent source and re-exporting as PNG, e.g. make any image background transparent again and download as PNG.
- Screenshots, "Save As" dialogs, email attachments, and some upload forms silently convert images to JPG — that is the usual hidden culprit.
You removed a background, downloaded a transparent PNG, and it looked perfect. Then you attached it to an email, pasted it into a document, or uploaded it somewhere — and it came back with a plain white box around the subject, as if the transparency had never existed. This is one of the most common frustrations in image editing, and it almost always comes down to one thing: the file quietly became a JPG somewhere in the chain, and JPG cannot store transparency at all.
What actually stores transparency in an image file
Every pixel in a digital image has colour channels — typically red, green, and blue. Some formats add a fourth channel called alpha, which records how transparent that pixel is, from 0 (fully see-through) to 255 (fully opaque). This RGBA structure is what makes a "transparent background" possible: the pixels around your subject simply have their alpha value set to 0, so anything placed behind the image shows through. A format either has this fourth channel built into its specification, or it does not — there is no in-between and no way to add it after the fact.
Why JPG can never be transparent
JPEG was standardised in 1992 specifically for photographs — continuous-tone images with no hard edges or flat colour fields, where its lossy compression can throw away detail the eye will not miss. Its file structure only ever defines three colour channels; there is no reserved slot for alpha, and adding one would require an entirely different format. This is not a bug or an oversight — JPG was never designed for graphics with cutouts, logos, or overlays, and every version of it since 1992 has the same three-channel limitation. No setting, plugin, or 'export as transparent JPG' option exists anywhere, because the format itself has nowhere to put that information.
Which formats actually support transparency
| Format | Transparency support | Typical use | Notes |
|---|---|---|---|
| PNG | Full alpha channel, lossless | Logos, graphics, general-purpose transparent images | The universal safe default — supported everywhere |
| WebP | Full alpha channel, lossy or lossless | Web images where file size matters | Smaller than PNG at equal quality; less support outside browsers |
| GIF | 1-bit only (fully transparent or fully opaque, no soft edges) | Simple icons, old-web graphics | Produces jagged, hard-edged cutouts — avoid for photos |
| HEIC/HEIF | Alpha supported by the format | iPhone photos | Poor cross-app and cross-platform support for the alpha channel specifically |
| TIFF | Full alpha channel | Print and professional workflows | Large file sizes, rarely used on the web |
| SVG | Transparent by default (vector) | Logos and icons with a vector source | Not applicable to photographs — vector shapes only |
| JPG / JPEG | None — no alpha channel exists in the format | Photographs with no transparency needs | Never use for any image that needs a transparent area |
The five places a transparent image quietly becomes a JPG
- "Save As" or export dialogs that default to JPG unless you manually change the format dropdown — easy to miss if you are moving quickly.
- Pasting into Word, Outlook, or similar apps, which sometimes flatten or re-encode embedded images depending on version and settings.
- Messaging apps — WhatsApp, SMS/MMS, and some chat previews — commonly re-encode images as JPEG to reduce size before sending.
- Upload forms and CMS platforms with an automatic "convert to JPG" or thumbnail-generation step that runs on every uploaded image regardless of its original format.
- Older photo-editing or viewing apps that "flatten" an image on save by default, silently discarding the alpha channel in the process.
How to tell if your file actually has transparency
The file extension alone is not proof — a file can be renamed to .png while still being an opaque, flattened image underneath. The reliable check: open it in something that visually indicates transparency, such as a checkerboard pattern. Most image editors (Photoshop, GIMP, Figma, Preview on Mac) show this automatically. In a browser, open the image file directly in a new tab; browsers render transparent areas as the page's white or grey background, which can look identical to an opaque white image, so this check is not fully reliable on its own — a dedicated editor's checkerboard view is the definitive test.
How to fix it and keep it fixed
- 1
Go back to the original transparent source
Do not try to fix the white-background copy — the transparency data is gone from that specific file and cannot be recovered. If you still have the transparent PNG from before it broke, start from that. If not, make any image background transparent again from the original photo.
- 2
Download and keep it as PNG
Confirm the output is a .png file (WeConvertIt's background removal tools default to PNG for exactly this reason) before doing anything else with it.
- 3
Attach or insert the actual file, not a pasted preview
When emailing, messaging, or uploading, attach the .png file directly rather than copying a rendered thumbnail or screenshot of it — screenshots are always flattened and opaque.
- 4
Convert to WebP only for the final web destination
If file size matters for a website, convert the PNG to WebP using the Image Converter tool as the very last step — WebP keeps full transparency at a smaller size, but do this conversion once you are certain the PNG itself is correct.
- 5
Re-verify after every hand-off
Check the file still ends in .png or .webp — and still shows a checkerboard in an editor — after passing through email, chat, or any CMS upload, since these are the most common places a silent JPG conversion happens.
PNG vs JPG vs WebP vs AVIF beyond transparency
This guide focuses specifically on why transparency breaks — but format choice also affects file size and image quality for non-transparent images. If you are deciding which format to use more broadly (photos, web graphics, general storage), see PNG vs JPG vs WebP vs AVIF: Which Format Should You Use? for the full comparison.
Frequently Asked Questions
Why did my transparent PNG turn white when I opened it?
Somewhere between removing the background and viewing the file again, it was saved, exported, or re-encoded as a JPG. JPG has no alpha channel, so every transparent pixel becomes solid white the instant that conversion happens — and it cannot be undone from that JPG copy. Go back to the original transparent file, or re-run the removal and download as PNG.
Can I make a JPG transparent?
Not directly — a JPG file format has no channel to store transparency in, regardless of what you do to the pixels inside it. You have to convert the subject to a format that supports alpha (PNG or WebP) as part of a background-removal step, which produces a brand new file; you cannot toggle transparency on an existing JPG.
Does WebP support transparency?
Yes. WebP has a full alpha channel, exactly like PNG, and typically produces smaller files. It is a great choice once you know an image is headed for the web. For documents, presentations, and general design software, PNG remains the safer default since support for WebP is less universal outside browsers.
Why does my logo have a white box behind it in Word or PowerPoint?
The image file being inserted is a JPG (or was re-saved as one at some point), even if it looks like a PNG at a glance. Re-export the logo as a genuine PNG from its original transparent source and insert that file instead — see our PowerPoint and Google Slides guide for the exact steps.
I saved as PNG but it is still not transparent — why?
Two common causes: the image never actually had its background removed (it is just a PNG-wrapped photo with an opaque background, which is a valid PNG but was never made transparent), or an intermediate step — a screenshot tool, a chat app preview, a CMS thumbnail generator — flattened it onto white during resizing. Check the file immediately after download from the removal tool, before it passes through anything else.
What is the actual difference between PNG and JPG for transparency?
PNG stores four channels per pixel — red, green, blue, and alpha (transparency) — and is lossless, so nothing is degraded on save. JPG stores only three channels — red, green, blue — with no alpha channel, and uses lossy compression tuned for photographs. The three-channel limitation, not the compression, is why JPG can never hold transparency at any quality setting.
Does converting a transparent PNG to JPG destroy the transparency permanently?
Yes, for that JPG file. The moment the conversion happens, every transparent pixel is filled with a solid colour (almost always white) and that information is gone from the resulting file — there is no hidden data to recover. Keep the original transparent PNG safe, and only ever convert a copy to JPG if you specifically want a flattened, opaque version.