Guide
How to convert a PDF to PNG without losing quality — using the PDF Pro lossless PNG converter.
This guide is for designers placing a contract page into a Figma frame, marketers pulling a hero shot out of a brand PDF, and developers needing a transparent overlay rendered from a vector source. PNG is the right format when you can't afford the JPEG smear and you might need a transparent background. Five steps, the right encoder choice, and the gotchas.
What you'll need
- A modern browser (Chrome, Edge, Firefox, or Safari from the last two years)
- The PDF you want to rasterize, on your device
- A decision: truecolor (photos, gradients) or palette (logos, line art)
- About two minutes — including a 100% zoom check
The five steps
Open the lossless PNG converter
Head to the PDF Pro PDF-to-PNG tool. The page is a single static document plus a WebAssembly renderer — no signup, no upload, no queue. Because PNG encoding is deterministic, the output you get from this in-browser converter is byte-equivalent to what a server would produce given the same renderer settings.
Drop the PDF onto the page
Drag the file in. The renderer parses it locally and surfaces two facts you'll want to know up front: how many pages it has, and whether any of them use transparency. PDFs that came out of Illustrator, Sketch, or Figma usually do; PDFs that came out of Word usually don't.
If the page background is opaque white, you don't need alpha — and turning it off makes the resulting PNGs noticeably smaller. The tool detects this and suggests a sensible default.
Pick truecolor or palette, enable alpha
Two encoder choices matter for PNG output. Truecolor (24-bit RGB or 32-bit RGBA) stores every pixel exactly and is the right choice for anything with photographs, gradients, or anti-aliased text on a colored background. Palette (PNG-8) quantizes to 256 colors and produces dramatically smaller files for logos, icons, screenshots of UI with flat fills, and line art — with no visible quality loss when the source has fewer than 256 distinct colors.
Enable the alpha channel if you need the PDF's transparent background to come through. Disable it for opaque pages to save 25% on file size.
Render and inspect at 100% zoom
Hit Render. Each page is rasterized in a Web Worker, then PNG-encoded with zlib compression level 9 (the slowest, smallest setting — but PNG compression is lossless either way). Open the first thumbnail at full size: PNG is lossless, so anything that looks soft is a DPI problem, not a compression problem. If text edges look fuzzy, re-render at a higher DPI.
Save the PNGs
Download single PNGs from the thumbnails or hit "Download all" to get a zip. Filenames follow originalname-page-001.png for clean sorting. Drop one into Photoshop, Figma, or your favorite viewer and confirm the transparency is intact — the checkerboard background pattern will tell you instantly. The file lives entirely on your machine; the PNG converter never sent it anywhere.
Common mistakes & gotchas
- Choosing truecolor for a logo. A two-color logo as 32-bit RGBA is enormous compared to the same logo as PNG-8 with one transparent index. Use palette for line art and you'll cut the file size by 80% with zero visible difference.
- Forgetting to enable alpha. Opaque PNGs flatten the PDF page background to white. If you need to overlay the result on a colored canvas later, you have to re-render with alpha on — it's not recoverable in Photoshop.
- Believing "lossless" fixes a low DPI. PNG losslessly stores whatever the renderer produced. If you rendered at 72 DPI, your PNG is a perfect copy of a fuzzy bitmap. DPI is the quality knob, not the encoder.
- Saving a 600-DPI PNG of a photograph. JPG-tier photos belong in JPG. A 600-DPI lossless PNG of a magazine ad can hit 50 MB per page. Use the JPG converter for that.
- Skipping the 100% zoom check. Designers see PNG output at fit-to-screen and assume it's good. Always inspect at 100% — that's where a wrong DPI choice becomes obvious.
Troubleshooting
The PNG has a white background instead of being transparent.
The alpha channel was disabled at render time, or the source PDF page has an opaque white background drawn on it. Re-render with alpha on; if the result is still white, the white is part of the page content, not the background — open the PDF in a vector editor to remove it before converting.
My PNG files are massive — much bigger than the JPGs.
Expected. PNG is lossless and stores every pixel; JPG throws away high-frequency detail to shrink. For photographic content where some loss is fine, switch to the JPG converter. For line art and screenshots, try the palette mode — it cuts file size dramatically without quality loss.
Text is fuzzy in the PNG even at 300 DPI.
Two likely causes. First, the PDF may contain text rendered as a low-resolution image rather than vector — in that case the source is the limit, not the renderer. Second, anti-aliasing may be off; toggle "subpixel rendering" in the converter options and the edges will smooth out.
Colors look slightly different from the PDF.
PDFs can carry ICC color profiles (often CMYK for print). The PNG output is sRGB. The converter applies a perceptual color match by default; if you need exact color fidelity, render with the "embed source profile" option enabled and your image editor will honor the original colors.
Can I get one PNG that contains all pages stacked vertically?
Yes — enable the "stitch pages" option before rendering. The output is a single tall PNG with each page stacked top-to-bottom. Useful for long-form previews and screenshot-style sharing. Be aware: a 30-page stitched PNG at 300 DPI will be very tall and may exceed some viewers' max image dimensions.
Ready to convert?
Open the lossless PNG converter and run your PDF through the five steps above.