Print & Web2026-04-15

High-Resolution PDF to PNG: Print vs Web Output Settings

The same PDF needs very different PNG settings depending on where the output is going. For a print proof, a color shift is unforgivable. On a marketing page, one extra megabyte costs you a visitor. This guide separates the two scenarios end to end — DPI, color space, pixel size, compression — with the exact numbers you should reach for in each case.

Start with DPI: pixel density = print sharpness

DPI (dots per inch) is just how many pixels live in one inch. Monitors are 72–110 ppi. Home inkjets aim for 300 dpi. Commercial printers run 300–600 dpi. Converting the same A4 page at different DPI values gives very different pixel sizes:

DPIA4 pixel sizeApprox. file sizeUse case
72595 × 842100–300 KBWeb thumbnail, preview
1501240 × 1754400 KB–1 MBFull-width web, mobile
3002480 × 35082–6 MBPrint proof, home printer
6004961 × 70168–20 MBCommercial press

Memorize this table and you're halfway home. Pick the destination first; the DPI follows.

Web output: fast and lean wins

For embedding a PDF page on a webpage, the target is "sharp enough that nobody zooms in." Desktops sit near 110 ppi, mobile Retina at most 220 ppi — so 150 DPI is plenty in practice. A 1200–1600px long edge covers nearly every device.

Recommended web settings

  • DPI: 150 (going past 200 is wasted for almost everyone)
  • Long edge: 1200–1600px
  • Color space: sRGB (browser default)
  • Compression: PNG-8 (256 colors) cuts size 50%+ on text-heavy pages

Our web converter renders at 2000px (long edge) by default — for web use, downscale after the fact with sips (macOS) or ImageMagick:

# Downscale to 1600px wide (macOS)
sips -Z 1600 page-001.png --out web/page-001.png

# ImageMagick with high-quality Lanczos resampling
magick page-001.png -resize 1600x -strip web/page-001.png

Print output: DPI and color space both matter

Two extra concerns appear when print is the destination. First, DPI of 300 or higher — that's the threshold below which ink dots start to look ragged. Second, color space — handing the printer an sRGB PNG straight off your monitor often loses saturation in the CMYK conversion.

Recommended print settings

  • DPI: 300 (home, proofing), 600 (magazines, books)
  • Color space: ship AdobeRGB or ProPhoto RGB PNGs and provide the source PDF in parallel
  • Bit depth: 16-bit PNG prevents gradient banding (matters for photo pages)
  • Final check: zoom to 200% and look at text edges before sending to print

A footnote: PNG itself doesn't support CMYK by spec. Standard practice is to send sRGB or AdobeRGB PNGs, trust the press to do the CMYK conversion, and proof on a calibrated monitor. For high-end print, skip PNG and go to PDF/X-1a or TIFF.

Three real scenarios

A. One report page embedded in a blog post
150 DPI, 1200px wide, sRGB → ~400 KB. Won't move mobile LCP.
B. Office printer for proofing
300 DPI, A4 (2480×3508), sRGB → 2–4 MB per page. Bundle as a ZIP.
C. Magazine page sent to a press
600 DPI, AdobeRGB, 16-bit → 10–20 MB per page. Prefer PDF/X-1a over PNG when possible.

Common mistakes

  • Converting at 72 DPI for the web, then discovering it breaks at print — keep a separate 300 DPI master.
  • Shipping 300 DPI assets to the web, blowing LCP to 4 seconds — always downscale for web display.
  • Compressing text pages to JPG and getting ringing around letterforms — text pages belong in PNG. See the PNG vs JPG guide for the exact breakpoint.

Convert now

Start from a 2000px master and downscale per use case. ZIP download for batches.

Convert Now
High-Resolution PDF to PNG: Print vs Web Output Settings | PDF to PNG Converter