You download a PNG that a search result promised was transparent. You place it on a coloured background, and there it is: a grey-and-white chequered pattern where the transparency should be. The file is not broken, and neither is your software. You are looking at a picture of transparency.
Why does this happen at all?
Every design program draws transparent areas as a grey-and-white grid so you can see them. When somebody screenshots that program, or exports on a flattened background, the grid stops being a visual aid and becomes part of the picture: ordinary, solid, fully opaque pixels, arranged in squares. Those pixels print. They cut. They sit behind your artwork forever.
Image search is full of these, because the grid is what "transparent" looks like in a thumbnail, and a scraped copy of a screenshot looks identical to the real thing until you use it.
How can I tell in one second?
Drop the file into the transparent PNG checker, or right-click it on the page with the extension. It reads the file's own header, which says whether the format can hold transparency at all, then counts the see-through pixels. Real transparency and a painted grid are not remotely the same to a computer, even though they are identical to the eye.
By hand, there are two quick tells. Drag the file onto a dark background: a painted grid stays visible. Or zoom in on the squares — a real checkerboard drawn by software is always perfectly aligned to the same size, while a resized screenshot has soft, blurred edges between the squares.
Can it be fixed, or do I need a new file?
It can usually be fixed, and this is the part most tools get wrong. A background remover looks at colour, so when it removes "white and light grey" it also removes the white parts of your design: the highlight in an eye, a white outline, the snow, the teeth.
The checker takes a different route. It works out the grid itself — the size of the squares and where they start — then removes only pixels that are the colour their square in the grid should be, and only where those form a run longer than a single square. White artwork never matches that pattern, because it sits in every square regardless. So the grid goes and the design stays.
The one place to look closely is where white artwork touches the checkerboard directly. The squares that straddle that border can be taken with the background. Zoom in on those edges before you cut a hundred of them.
Why does it still look wrong after I removed it?
Three usual suspects, all of which the checker names:
- The file has no alpha channel. A JPG cannot store transparency, and neither can a PNG saved as plain colour. Renaming it changes nothing. It has to be re-saved as a PNG with alpha, which is what the background remover gives you.
- Invisible pixels are still there. Pixels at one or two percent opacity are invisible on screen but not empty, so anything that measures your design by its non-empty pixels — a print-then-cut border, an auto-trim — includes them. Your design "mysteriously" measures bigger than it looks.
- A pale rim survives. The half-transparent edge pixels still carry the old background's colour. On a white shirt nobody notices. On a black one it is a halo around everything.
How do I avoid it next time?
Judge a file before you build on it, not after. Check the source: artwork you bought with a licence, made yourself, or downloaded from somewhere that publishes real files rather than screenshots of them. And put any file through the checker once, at the start, where fixing it costs a minute instead of a run of materials.
Next: check it is big enough to print, then trace it into a cut file.
Everything linked here is free to use, runs in your browser, and needs no account. If something in this post is wrong or out of date, it is worth telling us — the date at the top is the last time it was checked.