Why transparent PNGs cause trouble on marketplaces
Cutting a product out and saving it with a transparent background feels like the professional move. One file, drop it on any colour, done.
On marketplaces it is the format most likely to produce a listing that looks broken, and the reasons are worth understanding before you commit a catalogue to it.
What transparency actually is
A normal pixel has three numbers: red, green and blue. A transparent-capable image has a fourth, alpha, running from 0 (fully see-through) to 255 (fully opaque).
The important part is what happens at the edges. A product edge is not a clean boundary: a pixel that is half product and half background gets an alpha of about 128, meaning "blend me halfway with whatever is behind". That partial transparency is what makes a cutout look natural instead of jagged.
It also means the file does not contain a finished image. It contains an image plus instructions for combining it with something else. What the shopper sees depends entirely on what that something else turns out to be.
The four ways it breaks
The background is not white. Marketplaces composite transparent images onto their own background. Usually white, sometimes not, and sometimes black, which turns a cut-out product into a silhouette on a black card. You have no control over this and no warning when it changes.
Dark fringing. If the cutout was composited against a dark background at some point, or if the alpha and colour channels get combined in the wrong order, semi-transparent edge pixels carry a dark tint. On white, that reads as a grey halo around the product. It is the commonest visible symptom of a transparency problem and it is not always obvious at thumbnail size.
File size. PNG is lossless, so a photograph saved as PNG is often five to ten times a comparable JPEG. On a marketplace with a file size cap, transparency can put you over it by itself.
JPEG has no alpha channel at all. So the moment anything in the chain converts to JPEG, and marketplaces re-encode routinely, the transparency has to be flattened onto something. If nobody chose what, you get the default.
The rule for marketplace listings
Flatten to white yourself, and upload a JPEG.
You then know exactly what the shopper sees, because you decided it. The corners are literally 255,255,255, the file is small, and there is no compositing step where something else can choose a colour for you.
This is not a workaround. For a listing image, an opaque white background is what you actually want; transparency offers flexibility you cannot use.
When transparency is right
Your own website, where you control the page and might place a product over a coloured band or a photograph.
Overlays and lifestyle composites, where the product is placed into another scene.
Logos and marks, which are graphics rather than photographs. PNG handles hard edges well and the file will be small.
Your masters. Keep a transparent version archived and export flattened copies from it. That way a redesign does not mean re-cutting four hundred products.
Two technical traps worth knowing
Premultiplied versus straight alpha. In premultiplied alpha, the colour channels are already multiplied by the alpha value; in straight alpha they are not. Combining files that use different conventions produces either dark fringes or bright ones. Most tools handle this correctly, but it is the underlying cause when a cutout has an inexplicable halo.
Indexed PNGs only have binary transparency. PNG-8 stores one fully-transparent colour rather than a per-pixel alpha, so edges are hard and jagged with no partial blending. If your cutout looks like it was cut with scissors, check whether something downgraded it to 8-bit.
A practical workflow
- Cut the product out once, at full resolution, and keep that as a transparent master.
- For marketplace listings, flatten onto white and export JPEG.
- For your own store, export WebP with transparency where you need it.
- Never upload a transparent file to a marketplace unless their documentation explicitly says it is supported and states what it composites onto.
The one-file-fits-everywhere instinct is the problem. Two exports from one master is less work than one file that behaves differently on every platform.