Why Does My PNG Turn White in a PDF?

Seeing white where your PNG had a transparent background almost always means one of two things: either the converter flattened your PNG to JPEG before putting it in the PDF (JPEG has no alpha channel, so the transparency was destroyed permanently), or the transparency actually survived just fine and you're looking at your PDF viewer's default white page canvas painted underneath it. Both produce the exact same visual result, which is why this is so confusing. The first is a real data loss you can't undo after the fact. The second is completely normal PDF viewer behavior and isn't a bug in your file at all. Telling them apart requires knowing what your specific converter did internally, which most tools never tell you — so the rest of this article walks through how to check, rather than asking you to just trust either explanation.

A lot of PNG-to-PDF tools, including several built into design and document software, take a shortcut: they draw your image onto a canvas and re-encode it as a JPEG before embedding it in the PDF page. JPEG is a format that was never built to store an alpha (transparency) channel — it only knows about red, green, and blue pixel values. So any tool that runs your PNG through a JPEG step, even briefly, silently throws away the transparency before the PDF file even exists. There's no error, no warning; the resulting PDF just has a solid image where the transparent area used to be. This is a real, permanent loss, and no PDF viewer setting or export option can bring it back afterward — the only fix is re-converting from the original PNG through a tool that skips the JPEG step entirely.

A converter that does this correctly checks your file's real MIME type, and when it's genuinely `image/png`, it embeds the PNG's own bytes — alpha channel included — directly into the PDF using a native PNG-embed operation, never re-encoding it as anything else. Pixeltools' own /image-to-pdf tool works exactly this way: files that report as `image/png` are embedded with a direct PNG embed that carries the alpha channel through untouched, and only non-PNG images get drawn to a canvas and saved as JPEG (where there was no transparency to begin with anyway, since JPEG doesn't support it). Nothing is drawn behind the image on the page itself — no white or colored rectangle is added — so whatever alpha values were in your original PNG are exactly what end up in the saved PDF.

Here's the part almost nobody explains: even when a PDF correctly contains your image with its alpha channel fully intact, opening that PDF in Acrobat, macOS Preview, or Chrome's built-in viewer will usually still show white where the transparency is. That's because a PDF page isn't a transparent canvas the way a PNG file is — most viewers paint the page background as solid white by default before drawing anything on top of it, and there's no viewer-standard notion of a PDF page that renders as "see-through." So a white square is not evidence your transparency was lost. It's simply the viewer's default page fill showing through, which is expected and correct behavior, not an error in your file or your converter.

Since a white page tells you nothing either way, you need a test that doesn't rely on how a PDF viewer paints its background. The most reliable way is to convert the PDF back into an image using a tool that itself preserves alpha (a PDF-to-PNG conversion that keeps transparency), and see whether the transparent area comes back as transparent rather than white. Alternatively, place the PDF page as an image inside an image editor that respects alpha channels — if the editor shows a checkerboard pattern in that area instead of solid color, the transparency made it through. If both of those show solid white or black with no checkerboard, transparency was actually lost somewhere in the pipeline, most likely a JPEG re-encode step.

If your goal isn't "don't lose transparency" but "I want a specific color or dark background to actually be visible behind my image in the PDF," true transparency won't get you there, because a normal PDF viewer's white canvas will win regardless of what's in the file. The only reliable fix is to add that background color to the image yourself before converting — for example, placing a colored rectangle behind your artwork in an image editor and flattening it, so the color becomes part of the actual pixel data rather than depending on transparency you can't control how a viewer renders. This is the honest fix graphic designers use when a client insists a PDF "needs" a dark background: bake it in, don't rely on alpha.