Guide
PNG With Transparent Background
Short answer: when someone asks for “a PNG with a transparent background”, they are naming four properties at once — the container (PNG, not JPEG), a populated alpha channel, an edge that was rebuilt rather than sliced, and a canvas whose pixel size they can use. A file can satisfy some of those and fail the rest, which is why cut-outs that look perfect on your screen come back with “this is on a white box” or “this is the wrong size”. The seven checks below take about a minute and catch every one of them before you send the file.
What the request actually asks for
The phrase is a specification, not a format. Each part of it fails in a different way, and the failure that gets reported back is almost never the one you would guess.
| What was asked for | How it fails silently | How to check it |
|---|---|---|
| PNG | Saved as JPEG by an export preset, a messaging app or an upload pipeline. The name still ends in .png on some sites. | Open the delivered file, not your original. Any JPEG conversion leaves no alpha at all. |
| A transparent background | The empty area is plain white pixels. It looks empty because the page behind it is also white. | Place the image over a strong colour. If the background turns that colour, it is transparent. If it stays white, it is not. |
| A usable edge | The cut was hard, so the boundary pixels are a mixture of subject and old background. On a new background they read as a pale or dark ring. | Composite the result over black and over white. A ring that appears on one and not the other is baked into the edge. |
| A usable canvas | The background was removed but the original margins stayed, so the subject occupies a fraction of the stated size. | Compare the visible bounding box to the image dimensions before sending. |
Check one: the alpha is populated, not implied
Transparency in PNG lives in an alpha channel, or in a transparency chunk attached to an indexed image. Both are real; what is not real is a file whose “empty” area consists of white pixels that nobody has told it to hide.
The quickest test needs nothing installed. Put the image on a saturated background — magenta, lime, pure red — in whatever editor you already have. A real alpha lets that colour through. An image that stubbornly shows white in the middle of your magenta canvas has no transparency, and no amount of re-saving will give it one.
If you want to read the file rather than test it, the colour type is decisive. Types 4 and 6 carry an alpha channel for every pixel. Types 0, 2 and 3 can still be transparent, but only through a transparency chunk that marks particular values or palette entries as invisible. Everything else is opaque by construction.
Check two: the edge holds on both backgrounds
This is the check most people skip, and it is the one that produces the complaint that sounds like a colour problem but is not.
Composite the cut-out over white, then over black. On white, leftover old background shows as a pale halo. On black, the same leftover shows as a bright fringe. A clean edge looks acceptable on both, because its semi-transparent pixels carry the subject’s colour rather than a mixture with the background you removed.
If the fringe appears on only one background, the edge was cut with a hard threshold and never rebuilt. If it appears on both, the removal took too much of the subject in the transition zone. Either way the fix is at the edge, not in the colour settings, and the file is not ready to hand over.
Check three: the canvas in pixels
Send the number the recipient will type into their layout: the pixel width and height of the file. Not the dpi.
PNG can carry a physical-resolution chunk, and some editors display it, but almost nothing that will place your image actually reads it. A browser, a slide, a web form and a design tool all position the image by its pixel dimensions. A file described as “300 dpi” that is 400 pixels wide will be 400 pixels wide in every one of them.
Two numbers are worth writing down with the file: the canvas size, and the size of the subject inside it. If the second is much smaller than the first, the recipient will place the file at the size you gave them and get a subject far smaller than they expected — and the transparent margin will be doing the damage, invisibly.
Check four: colour space
PNG is an RGB format. There is no CMYK PNG, which matters the moment the file is headed for print rather than a screen. A print-bound request that asks for transparency usually means a PSD or a TIFF with an alpha channel, not a PNG, and converting a CMYK document to PNG will shift the colours as well as change the file type.
For screen work, an untagged PNG is usually interpreted as sRGB, and that is normally what you want. Tagging it explicitly costs nothing and removes one variable when the recipient says the colours look off.
Check five: the filename and the metadata
Two small things that cause a surprising number of round trips. A filename containing spaces, brackets or the word “copy” breaks uploads and links often enough to be worth avoiding; lowercase with hyphens is safe everywhere.
And strip what does not need to travel. Camera metadata, location, editing history and embedded thumbnails can all sit inside a PNG, and none of them help the person receiving a cut-out. Modern editors expose this as “export” rather than “save”, which usually drops the extras.
Check six: the delivered copy, not your copy
Almost every failure in this list is a failure of the copy in transit rather than the file on your disk. Upload pipelines re-encode. Some turn PNGs into JPEGs for thumbnails. Some resize to a maximum width and drop the alpha in the process. Some serve an older cached version of the same filename.
So the last check is the only one that counts: download or open the asset from the place the recipient will actually get it, and run the colour test on that file. If the background survives there, it will survive for them.
The seven checks, in order
- Open the delivered file, not the original.
- Place it on a strong colour. Background turns the colour, or it does not.
- Composite over black and white. A fringe on one is a cut edge; on both, it is over-removal.
- Read the pixel dimensions and compare them to the visible subject.
- Confirm RGB if the destination is a screen; look for PSD or TIFF if it is print.
- Rename it to something plain, and export rather than save.
- Re-test the copy from the destination before calling it done.
This site’s tool, honestly
The remover here produces a PNG with a real alpha channel at the exact pixel size of the image you loaded, and the processing happens in your browser, so the file never leaves your device. It does not trim, pad or rename — those are separate edits, and they are exactly the ones the checks above are looking for.
What it cannot do is fix a file that never had a transparent background to begin with, or rebuild an edge that was already destroyed by an earlier export. For those, start from the original image. Open the green screen remover if you have the original; this page covers the case where the file you were given has no transparency at all.
Questions
How can I tell if a PNG really has a transparent background?
Place it over a saturated colour in any editor. If the empty area takes that colour, the file has transparency. If it stays white, the background is made of white pixels and the PNG simply has nothing to hide. Reading the file’s colour type works too: types 4 and 6 carry alpha for every pixel.
Why does my PNG look transparent in one app and white in another?
Because each app chooses what to draw behind an image that has no colour in that area. Some draw a checkerboard, some draw white, some draw the document background. The file did not change; the backdrop the app picked did. A saturated colour test removes the ambiguity.
Is a transparent PNG always RGBA?
No. RGBA is one way to store it. An indexed PNG can mark palette entries as transparent, and a greyscale PNG can carry a transparency value. What matters is that some part of the file declares those pixels invisible — not which colour type was used to do it.
Does resizing a PNG remove its transparency?
Not by itself. A resize that keeps the alpha channel keeps the transparency, though very small resizes can thin or lose a soft edge. What removes transparency is an export that changes the format — to JPEG, most commonly — or an upload pipeline that flattens the image onto a background.
Why do I get a pale ring around the subject after removing the background?
The boundary pixels were a blend of subject and old background, and the removal kept the blend. On white that reads as a pale halo; on black, as a bright fringe. Check both backgrounds to tell a hard cut from over-removal, then fix the edge rather than the colour settings.
Can I just rename a JPEG to .png?
No. The extension is a label, not a conversion. The file still holds JPEG data with no alpha channel, and most tools will either refuse it or quietly treat it as opaque. Convert properly by opening it and exporting as PNG, but remember that the white background is still part of the picture and has to be removed separately.
Does this site upload my image?
No. The removal runs in your browser and the image stays on your device. The checks on this page are things you can do in any editor you already have; none of them requires sending the file anywhere.
Open the green screen remover — free, no account, and it writes a PNG with a real empty background at the exact pixel size you loaded. If the file also has to land in a layout at the right size, this page covers the canvas question that comes next.