PDF to JPG vs PDF to PNG: Which to Choose (2026 Decision Guide)
Quick decision guide on whether to convert PDF to JPG or PNG. Resolution, quality, file size, transparency, every trade-off explained with real benchmarks.
If you’ve ever converted a PDF to images, you’ve faced the choice: JPG or PNG? Both work. Both are universal. But picking the wrong one means either fuzzy text edges or files 4× bigger than necessary. This guide gives you a clean rule and the trade-offs behind it.
The 5-second answer
Pick JPG when…
- Page contains photos or color gradients
- It's a scanned document (mostly bitmap content)
- You'll send by email (file size matters)
- You won't zoom past 200%
- You don't need transparency
Pick PNG when…
- Page is mostly text (sharp edges critical)
- It's a diagram, chart, or screenshot
- You'll re-edit or zoom heavily
- You need transparency (rare for PDFs)
- File size doesn't matter
If you’re not sure, default to JPG at quality 90, 150 DPI, works for 80% of cases.
What’s actually different
JPG (JPEG) and PNG are both lossless containers in the sense that “what gets saved” is what was rendered, but JPG applies lossy compression to the pixel data. PNG uses lossless compression, every pixel is preserved exactly.
| Property | JPG | PNG |
|---|---|---|
| Compression type | Lossy (DCT-based) | Lossless (DEFLATE) |
| Best for | Photos, gradients, natural scenes | Text, line art, diagrams, screenshots |
| Max colors | 16.7M (24-bit) | 16.7M (24-bit) or more |
| Transparency | No | Yes (alpha channel) |
| File size (A4 @ 150 DPI) | ~150–250 KB | ~600 KB – 1.5 MB |
| Quality knob | 1–100 (use 85–95) | None (always perfect) |
| Re-edit cycles | Each save loses quality | Infinite (lossless) |
| Browser support | Universal (1992) | Universal (1996) |
The text-edge problem
JPG's lossy compression operates in 8×8 pixel blocks (DCT). On smooth photo content this is invisible. On sharp text edges it produces "ringing" artefacts, faint halos around letters. PNG has no blocks, so text stays razor-sharp at any zoom level.
Real benchmarks: same page, both formats
Rendering a typical A4 page at 150 DPI (1240 × 1754 pixels):
| Page content | JPG @ 90 | PNG | Ratio |
|---|---|---|---|
| Pure text (legal contract) | 195 KB | 580 KB | 1:3 |
| Scientific paper (mixed text + figures) | 280 KB | 1.1 MB | 1:4 |
| Magazine spread (photo-heavy) | 410 KB | 2.4 MB | 1:6 |
| Engineering diagram (CAD lines) | 240 KB | 460 KB | 1:2 |
| Screenshot (UI mockup) | 320 KB | 890 KB | 1:3 |
For a 50-page PDF, that’s the difference between a 12 MB attachment (JPG) and a 38 MB ZIP (PNG), Gmail’s 25 MB limit kills the PNG option entirely.
Resolution (DPI) explained
DPI = dots per inch = how many pixels each inch of the original PDF gets rendered into. Higher DPI = sharper output but bigger files.
| DPI | Use case | A4 pixel dimensions | JPG size | Quality |
|---|---|---|---|---|
| 72 | Email previews, thumbnails | 595 × 842 | ~50 KB | Low, text fuzzy |
| 96 | Web embeds, casual viewing | 794 × 1123 | ~80 KB | Acceptable |
| 150 | Standard screen viewing | 1240 × 1754 | ~250 KB | Good, sharp text |
| 200 | Mobile zoom, basic printing | 1654 × 2339 | ~450 KB | Excellent |
| 300 | Print, archival, heavy zoom | 2480 × 3508 | ~900 KB | Print-grade |
| 600+ | Forensic / scanning | 4960 × 7016 | ~3 MB | Overkill for most |
The 150 DPI sweet spot
For 90% of digital use cases, 150 DPI is the right answer. It looks crisp on Retina displays at 100% zoom, files stay under 500 KB per page, and you can zoom to ~200% before pixelation appears. Only push to 200–300 DPI when you'll print or zoom heavily.
When to pick JPG
JPG wins when: (a) the page is photo-heavy or visually rich, (b) you’re sharing/emailing/uploading where size matters, (c) the user will view at normal zoom levels. Practical examples:
- Scanned receipts and invoices → JPG. Photos of paper, text recognition still works.
- Real estate photos in a brochure PDF → JPG. Photo content, large file otherwise.
- Magazine pages → JPG. Photo-heavy, JPG built for this.
- Social media uploads → JPG. Platforms re-compress anyway.
- Email attachments → JPG. 4× smaller fits Gmail 25 MB limit.
When to pick PNG
PNG wins when: (a) the page has lots of fine text/lines, (b) sharp pixel edges matter, (c) the user might zoom in heavily, (d) file size is irrelevant. Examples:
- Screenshots of UIs → PNG. Single-pixel borders, sharp text.
- Engineering or CAD diagrams → PNG. Lines must be crisp.
- Code snippets / terminal output → PNG. Monospace fonts shrink readably.
- Charts and graphs → PNG. Anti-aliasing on edges renders better.
- Pages you’ll re-edit → PNG. No quality loss on re-save.
How to convert without losing quality
The rendering engine matters as much as the format choice. Browser-based PDF→image converters (using PDF.js + canvas) are nearly indistinguishable from desktop tools, same pixels, same quality.
- Open PDF to JPG (or pick PNG mode if your content matches the PNG list above).
- Drop your PDF, it never uploads, processing happens in your browser via WASM.
- Pick DPI: 150 for screen, 200 for print, 300 for archival.
- For JPG: set quality 85–95. For PNG: no quality knob, always lossless.
- Download as a ZIP if multi-page, or single image if 1 page.
Avoiding the "scanned look"
If your output looks fuzzy or scanned, you probably picked too low a DPI. Bump from 96 → 150, almost always solves it. Bumping JPG quality from 80 → 95 helps less than DPI does.
Summary
| Your situation | Format | DPI | Quality |
|---|---|---|---|
| Email scanned receipt | JPG | 150 | 85 |
| Embed page in blog post | JPG | 150 | 90 |
| Save magazine spread | JPG | 200 | 92 |
| Document UI screenshot | PNG | 150 | n/a |
| Save engineering diagram | PNG | 200 | n/a |
| Archive entire scanned book | JPG | 200 | 95 |
| Print preview | PNG | 200 | n/a |
| Print ready | JPG or PNG | 300 | 95 |
When in doubt, JPG at 150 DPI quality 90. Use PNG when text/lines matter or files need to survive future editing without degradation.