PDF to PNG: Choosing the Right DPI
Use page dimensions and the destination to choose 100, 150, 200, or 300 DPI without creating needlessly large PNG files.
Published and reviewed July 18, 2026 by the PDFMK Editorial Team
DPI controls raster dimensions
A PDF page does not have one mandatory pixel size. It has physical page dimensions, usually expressed internally in points, and it may contain vector paths, text, and images. Rendering converts that page into a pixel grid. DPI—dots per inch in common interface language—sets how many output pixels represent one inch of the page.
The calculation is straightforward: page width in inches multiplied by DPI equals pixel width, and page height in inches multiplied by DPI equals pixel height. PDF coordinates commonly use 72 points per inch, so a 612 by 792 point US Letter page is 8.5 by 11 inches. Increasing DPI makes text edges and line art sharper, but also increases pixel count, memory use, conversion time, and ZIP size.
Pixel dimensions for a Letter page
An A4 page has slightly different proportions, about 8.27 by 11.69 inches, so its pixel dimensions differ. Landscape pages swap width and height. Oversized drawings can become extremely large at 300 DPI; a page twice as wide and twice as tall produces four times as many pixels.
| Setting | Approximate pixels | Typical use |
|---|---|---|
| 100 DPI | 850 × 1,100 | Thumbnails, quick review, small on-screen previews |
| 150 DPI | 1,275 × 1,650 | General web use and readable full-page reference |
| 200 DPI | 1,700 × 2,200 | Small text on screen; PDFMK’s balanced default |
| 300 DPI | 2,550 × 3,300 | Detailed line work, OCR input, or print-oriented inspection |
Choose based on the final use
For a card-sized preview, 100 DPI is often enough because the browser will display the image smaller than its native dimensions. For an article where readers may zoom into a full page, 150 or 200 DPI is a better starting point. Use 300 DPI when small type, fine diagrams, or downstream OCR genuinely needs it—not simply because 300 is the largest button.
Rendering at high DPI cannot recover detail missing from the source. If a scan was captured at low resolution, enlarging it creates more pixels but not new characters or line detail. Conversely, a vector PDF can remain crisp at many scales inside a PDF viewer, but the PNG export becomes fixed-resolution as soon as it is rendered.
Why PNG files can be surprisingly large
PNG uses lossless compression and is well suited to text, diagrams, flat colors, and interface captures. It can be inefficient for full-page photographs or heavily textured scans compared with JPEG. PDFMK exports PNG only, so lowering DPI is the available way to reduce raster dimensions before download.
Pixel count grows with the square of the scale. Moving from 150 to 300 DPI doubles width and height, creating four times the pixels before compression. The actual file may not be exactly four times larger because blank areas and repeated colors compress well, but memory demand during rendering still rises sharply. For a multi-hundred-page PDF, that difference is operationally important.
Use batch and ZIP inputs deliberately
PDFMK accepts multiple standalone PDFs, ZIP archives containing PDFs, or a mixture. Each page becomes a PNG, and the download is a ZIP. Names derive from the source PDF plus a zero-padded page number; name collisions receive a short suffix. That makes batches easier to trace back to their source.
Before uploading a ZIP, remove unrelated or sensitive files even though the converter ignores non-PDF entries. After download, compare the number of PNG files with the total pages you expected, inspect the first and last image from each source, and zoom to 100 percent. If text is soft, rerun at the next DPI level rather than applying artificial sharpening to an undersized render.
Apply the guide
Keep your source file and verify the result after processing.