PNG vs JPG for PDF Pages: Which Format Actually Makes Sense?

When you render a PDF page into an image, the first decision that trips people up is deceptively simple: PNG or JPG? Most guides just say "PNG is better quality" and leave it there. That's technically true in a narrow sense, but it misses the actual trade-offs you'll face when converting real documents — legal contracts, architectural drawings, scanned invoices, product brochures, academic papers.

PNG uses lossless compression. Every pixel you get back is exactly what the PDF renderer produced. That matters enormously for text-heavy pages where a JPG's compression artifacts can smear fine letterforms and make thin horizontal rules look like they're vibrating. If you're converting a contract or a technical specification where every character needs to be legible and unambiguous, PNG is not just "better" — it's the correct choice. The trade-off is file size. A single A4 page rendered at 150 DPI as PNG typically lands between 500 KB and 2 MB depending on content density. At 300 DPI, you're looking at 2–8 MB per page.

JPG, on the other hand, excels where photographs and gradients live. If your PDF contains full-bleed marketing imagery, scanned photographs, or richly coloured illustrations, a JPG at 90–95% quality will look visually identical to PNG at roughly a quarter of the file size. The artifacts JPG introduces happen in smooth gradient regions and fine diagonal lines — not in the flat colour blocks of most photos. So for a product catalogue where images dominate and you need a manageable file size, JPG at 92% quality is a genuinely sensible choice, not a compromise.

DPI: The Number Everyone Gets Wrong

DPI (dots per inch) is where most people make costly mistakes. The confusion comes from mixing up screen viewing and physical printing. On a standard 96 DPI monitor, a PDF rendered at 96 DPI will appear at "actual size." But PDFs are designed for print, where 300 DPI is the baseline for professional quality.

Here's a practical breakdown:

72–96 DPI — Thumbnail previews, website thumbnails, quick email previews. Pages look fine on screen at small sizes but will appear soft and pixelated if you zoom in or print them. File sizes are small, which makes this useful for automated pipelines that need fast previews.

150 DPI — The sweet spot for screen display. A full A4 page at 150 DPI is 1240 × 1754 pixels — large enough to read comfortably on any monitor without being unnecessarily heavy. This is what most people need for sharing documents as images over email or Slack.

200–250 DPI — Good middle ground when you want to share something that can also be printed on a home printer without looking muddy. Design proofs, presentation slides, and educational materials work well here.

300 DPI — Professional print quality. A4 at 300 DPI is 2480 × 3508 pixels. Use this when the images will be printed, submitted to a publisher, or used in a design workflow where quality is non-negotiable. File sizes are substantial — plan accordingly if you have many pages.

600 DPI — Archival and prepress. You'll need this for high-resolution scans, medical imaging output, or engineering drawings where you need to measure fine details. An A4 page at 600 DPI is 4960 × 7016 pixels. A 50-page PDF at this resolution can easily consume several gigabytes of storage.

What Happens Inside the Renderer

When a browser-based tool converts a PDF page to an image, it's doing something surprisingly sophisticated. PDF is a vector format — it describes content in terms of paths, text glyphs, and embedded images, not pixels. The renderer has to interpret those descriptions and rasterize them onto a pixel grid at whatever scale you specify.

The scale factor relates directly to DPI through a simple formula: scale = DPI / 72. PDF.js, the de facto standard for in-browser PDF rendering, uses 72 as its base unit (matching the PDF specification's "user space" unit where 1 point = 1/72 inch). So 150 DPI means a scale of 2.08×, and 300 DPI means a scale of 4.17×. The renderer then draws each page element onto an HTML5 canvas at that magnification.

Text rendering is particularly interesting here. Fonts embedded in a PDF are used directly by the renderer, which means text edges are sharp and anti-aliased correctly at any scale. This is very different from photographing a printed page, where you get optical distortion and paper texture. A PDF-to-image conversion at 150 DPI will generally produce sharper text than scanning the printed equivalent at the same DPI.

Where This Matters in Real Workflows

The use cases for PDF-to-image conversion are more varied than they first appear. Some common ones worth thinking through:

Social media and presentations. LinkedIn, Twitter, and Instagram don't accept PDFs natively. Turning slides or infographics into individual images is the standard workaround. 150 DPI PNG is usually perfect — high enough quality for retina screens, small enough to upload without hitting size limits.

Optical character recognition (OCR) preprocessing. Many OCR engines work better with image input than PDF. The recommended DPI for OCR is generally 300–400. Below 200 DPI, character recognition accuracy drops noticeably, especially for smaller font sizes.

Document archiving. Some archival workflows require TIFF format (not covered here) but PNG at 300 DPI is an acceptable lossless alternative for long-term storage of important documents without worrying about format obsolescence.

Legal and compliance contexts. Converting specific pages of a contract to images for embedding in a report or email is a common task. PNG is strongly preferred here since compression artifacts on numbers or signatures could theoretically create ambiguity — unlikely but undesirable in legal contexts.

Thumbnail generation for document management systems. 96–150 DPI JPG at 80% quality is standard for this — fast to generate, small to store, adequate for identification purposes.

Batch Downloading: Why ZIP Beats Downloading One-by-One

For documents beyond four or five pages, downloading images one at a time becomes genuinely painful. A 20-page report would mean 20 separate save dialogs. Batch downloading as a ZIP file solves this neatly — all pages in a single archive, named sequentially so they sort correctly in any file manager.

The trade-off to understand is that ZIP generation happens in your browser's memory. A 50-page PDF rendered at 300 DPI as PNG can produce images totalling 200+ MB. Most modern laptops handle this fine, but older machines with limited RAM (under 4 GB available) can struggle. If you're converting a very long, high-resolution document, consider either reducing the DPI or processing it in sections.

One practical tip: if you need images for web use, always do a final check of the file sizes after conversion. A 300 DPI PNG of a text-heavy page might be 3 MB — completely fine for print, but unacceptably heavy for web embedding where you'd want under 200 KB. In those cases, running the images through additional compression afterward (or simply using a lower DPI from the start) is the right move.