PDF to PNG: when lossless image extraction is the right call

"PDF to image" usually means PDF to JPG — it's the default in most converters and the file sizes are smaller. But for a significant share of use cases, PNG is the right output format and the choice deserves more thought than it gets.

The deciding factor is what's on the page. PDFs with photos compress beautifully as JPG. PDFs with text, diagrams, screenshots, or charts often look noticeably worse as JPG than as PNG — and at typical render scales the file-size difference isn't dramatic enough to justify the visual hit.

When PDF to PNG beats PDF to JPG

• Pages with text. JPG's lossy compression creates "ringing" artifacts around sharp edges. Text is all sharp edges. Even at quality 92, you can sometimes see faint halos around characters when you zoom in. PNG keeps every pixel exact.
• Charts and diagrams. Crisp lines, solid colour fills, and tight gradients are exactly where JPG struggles. PNG preserves them perfectly.
• Screenshots. If your PDF contains screenshots of UIs, web pages, or apps, those snippets already have the sharp-edge problem twice over. PNG is the only reasonable choice.
• Documentation and READMEs. Page images embedded in documentation get viewed at various zooms. PNG stays sharp regardless.

When PDF to JPG is still better

• Pages dominated by photos. A travel-magazine PDF where each page is a full-bleed photo. JPG at 92% quality is visually indistinguishable and 3-5× smaller than PNG.
• Storage-constrained use cases. Embedding many PDF pages in a slideshow or website where total page weight matters.
• Social sharing. Social platforms re-compress to JPG anyway; starting with JPG removes one round of lossy re-encoding.

Scale matters more than format choice

Both PNG and JPG are raster formats — they have a fixed pixel resolution baked in. A PDF page rendered at 1× scale is ~72 DPI: fine for thumbnails, blurry when zoomed. Render at 2× and you get screen-sharp output at standard viewing zoom. Render at 3-4× and you get print-quality images.

Higher scale means bigger files in either format. A PDF page at 1× as PNG might be 200 KB; at 4× it's often 4-8 MB. Pick the scale that matches your use case:

• 1× — thumbnail previews, small social posts
• 2× — standard quality, most documentation use cases (default)
• 3× — high-quality print or zoom-in scenarios
• 4× — archival or pixel-peep print

How to convert PDF to PNG in your browser

Drop your PDF into our Universal Converter and pick PNG as the target. Each page becomes a separate PNG file with a zero-padded suffix in the filename (so they sort correctly in any folder view). The Universal Converter uses pdf.js — the same rendering engine that ships in Firefox — for accurate output that matches what a PDF reader would show.

For more dedicated workflow with quality settings and batch operations, the PDF to PNG tool is coming next. In the meantime, /convert handles the same task with sensible defaults.

Multi-page handling

A 50-page PDF becomes 50 PNG files. Browsers download them sequentially when you click convert. Most browsers ask for permission once for multiple downloads, then proceed — say yes and you'll get the whole batch.

For workflows where you want all pages in a single combined image (a tall vertical strip for documentation), we're shipping a "combine output" toggle in the next release. Until then, the simplest workaround is to extract individual PNGs and stack them in any image editor or with ImageMagick (convert page-*.png -append all-pages.png).

The privacy angle

PDF-to-image conversion in our tools runs entirely in your browser using pdf.js. Your PDF is read from your disk, rendered to a canvas, exported as a PNG blob, and downloaded — never uploaded anywhere. For confidential PDFs (contracts, financial statements, HR documents), this is the only safe way to extract page images.