PDF to PNG — when lossless beats small, and how to pick the right scale
PDF-to-PNG is the right export when you need every pixel preserved exactly — typically for text-heavy pages, screenshots, line art, or anything where JPG's compression artifacts would show up as ringing around character edges. The trade-off is file size: PNG files are typically 3–5× larger than the equivalent JPG. Here is how to think about that trade-off, what scale to pick for which use case, and the two patterns that catch users off-guard.
PNG vs JPG — pick by content type
The simplest decision rule: PNG when the page is mostly text or vector graphics, JPG when the page is mostly photographs. The reason is how each format compresses. PNG uses lossless DEFLATE compression — exactly reconstructs the input — which means hard edges (the side of a letter, the boundary of a logo) stay sharp at any zoom level. JPG uses lossy frequency-domain compression that produces small files for photographic content but adds visible ringing around hard edges in text or line art.
If you cannot decide, run a one-page test export at both formats at the same scale and look at the output. Open both at 100% and at 200%. The right choice is usually obvious — JPG looks fuzzy around letters, PNG looks crisp; or both look fine and you pick the smaller file.
Picking the right scale
The scale multiplier (1×, 2×, 3×) tells the rasterizer how many pixels per PDF point to render. Each step up multiplies the pixel count by 4×, which means the file size also roughly 4×s. Picking the right scale for your end use saves a lot of bytes:
- 1× — screen preview at native size. Use when the image will only ever be viewed at its natural page size on a standard-DPI screen. The thumbnail panel in your gallery app, a low-res email preview, a quick check on a phone.
- 2× — retina screens and print at 144 DPI. The most common pick. Modern phones, tablets, and laptops all have hi-DPI displays where 2× looks crisp. Also matches typical office-printer resolution — print quality is good without going overboard on file size.
- 3× — archival, hi-res print, marketing assets. Use when the image will be printed at large physical sizes, used as a hero asset for marketing, or needs to scale beyond its natural size without softening. The file size is 9× the 1× version, which is significant for multi-page exports — only use 3× when you actually need it.
When PDF-to-PNG is the right tool
Cases where you genuinely want PNG output rather than another conversion:
- Embedding a page as an image in a slide deck. PNGs render losslessly inside PowerPoint or Keynote. The page's text stays crisp at any slide zoom.
- Generating thumbnails for a gallery. Convert every page at 1× scale; use the resulting PNGs as previews in a document library or CMS.
- Building a long social-media carousel from a deck or report. LinkedIn, X, and Instagram all want individual images per slide. Export each page as PNG and upload as a carousel.
- Archiving a one-pager for environments that don't render PDF. Some legacy systems display images but not PDFs. Convert to PNG and embed.
- Pre-processing for a different image pipeline. Need to run each page through a custom image-filter chain, OCR engine, or AI image model? Export to PNG first; downstream tools handle PNG more universally than PDF.
Two patterns that catch people out
The friction points that show up in support tickets:
- Files larger than expected. A 50-page PDF exported at 3× PNG can easily be 200+ MB. If you're going to publish, archive, or share at that scale, run a separate compression pass on the PNGs (oxipng, pngquant) afterward — those tools can typically reduce PNG size by 30-60% with no visible quality loss. Or drop to 2× scale, which is almost always sufficient.
- PNG transparency is preserved, even for white backgrounds. If your PDF page has a transparent background (rare, but it happens with some printer outputs), the resulting PNG will be transparent too. That looks weird in viewers that expect a white background. If you need a guaranteed white background, flatten the PDF before rasterizing — our Compress tool with the Smaller preset flattens transparency as part of its pass.
Limits and compatibility
On the free web tool, PDF-to-PNG handles files up to 100 MB with no page-count cap. PDFium runs in WebAssembly in your browser; nothing is uploaded. Output PNGs are plain RGBA images compatible with every viewer, every editor, every CMS, every social platform.
Download individual pages or use the Download All option to save every page at once. Zipping the output is on the roadmap; for now the per-page downloads land in your default browser-downloads folder with predictable filenames.