Why convert a PDF to PNG instead of JPG for sharp text and line art?
PNG encodes every rendered pixel without discarding high-frequency detail, so thin typography, table borders, and vector curves stay razor-sharp. Under the W3C Portable Network Graphics (PNG) Third Edition Specification, the format pairs scanline prediction filters with lossless Deflate compression, eliminating the blurry ringing halos that JPEG introduces around high-contrast edges.
Lossless Deflate filtering versus JPEG block artifacts
JPEG divides an image into 8-by-8 pixel blocks and discards subtle frequency data to shrink file size. On continuous-tone photographs, that trade-off is nearly invisible, but around black 10-point text on white paper it creates faint gray smudges.
PNG preserves every pixel value exactly as pdf.js draws it onto the canvas. Flat white margins, solid chart fills, and crisp gridlines compress efficiently with Deflate while remaining mathematically identical to the rendered frame.
Because no pixel data is thrown away, PNG files containing full-page photographs or dense scans are noticeably larger than JPEGs. When your document consists mostly of camera photos rather than diagrams, you can switch to smaller JPEG files for photo-heavy pages.
Why there is no quality slider for PNG
You will notice that PDF to PNG shows Resolution and Pages controls without a Quality dropdown. That is intentional because the PNG specification has no lossy quality parameter.
Adjusting sharpness and file weight in PNG happens strictly through the Resolution selector. Choosing 150 DPI instead of 300 DPI cuts total pixel count by 75% while keeping every remaining pixel 100% lossless.
If you need to inspect fine print on engineering schematics or densely packed financial tables, higher DPI values add real pixel detail without introducing compression noise. That predictable scaling behavior makes PNG ideal for technical documentation.
Resolution presets from 72 DPI to 600 DPI and canvas limits
Each PDF page is measured in typographic points, with 72 points per inch, and rendered locally onto an HTML canvas before encoding through the MDN Web Docs HTMLCanvasElement.toBlob() API using image/png. Nothing leaves your device, so 0 bytes cross the network and your converted images are never stored on cloud servers.
| Preset | DPI value | Pixel dimensions (8.5 x 11 in) | Recommended use case |
|---|---|---|---|
| Screen | 72 DPI | 612 x 792 px | Compact thumbnails and layout checks |
| Standard | 150 DPI | 1,275 x 1,650 px | Documentation, slides, and web embeds |
| 300 DPI | 2,550 x 3,300 px | Print proofing and OCR pipelines | |
| High | 600 DPI | 5,100 x 6,600 px | Dense technical CAD and fine charts |
Standard (150 DPI) is selected by default because it balances crisp on-screen legibility against reasonable browser memory usage. At 600 DPI, a single US Letter sheet reaches 33,660,000 pixels, which demands substantial RAM across multi-page exports.
To protect your browser tab from crashing on oversized architectural drawings or banners, the renderer enforces a ceiling of 60,000,000 pixels per page. Any sheet exceeding that threshold scales down its effective DPI automatically so the conversion still completes.
Browser engines also cap individual canvas sides near 16,384 pixels, so keeping total pixel area bounded prevents silent blank-canvas exports on wide posters. For multi-page archival workflows that specifically require TIFF containers, use a multi-page TIFF archival export.
Page selection, multi-page ZIP output, and local memory
Converting a 200-page manual to 300 DPI PNGs creates hundreds of megabytes of uncompressed image buffers in memory. Filtering down to just the pages you need keeps the export fast and lightweight.
Using comma and range syntax in Pages
The Pages input accepts individual numbers, hyphenated ranges, or combinations such as 1-3, 7. Leaving the field blank processes every page from start to finish in document order.
Entering a short test range first lets you inspect text legibility at 150 DPI or 300 DPI before committing to a large batch. You can adjust the resolution and re-run immediately without re-selecting your source file.
Single PNG files versus numbered ZIP archives
When you convert a single page, clicking Convert to PNG downloads one .png file named after your source PDF with -page-N.png appended. Converting multiple pages downloads all images inside a single -png.zip bundle following the Library of Congress ZIP File Format Specification.
Page numbers inside the ZIP are zero-padded so file managers sort page 2 before page 10 automatically. After annotating or cropping those screenshots, you can merge edited PNG screenshots into a PDF with custom page margins.
Tip: On documents with more than 20 pages, convert at 150 DPI first or split exports into 25-page ranges in the Pages box to keep browser memory usage comfortable.
When to render pages as PNG versus extracting embedded images
Rendering a PDF page to PNG captures the entire visual composition: headings, body text, vector borders, drop shadows, and placed artwork flattened together. That is the right workflow when you want an exact visual snapshot of a slide, invoice, or technical diagram to drop into documentation or a design mockup.
Unlike JPEG, the PNG format supports an alpha transparency channel, though standard PDF pages with a paper background render onto white unless the page itself uses transparent layers. Keeping lossless pixel fidelity also helps when feeding rendered pages into downstream optical character recognition or layout inspection pipelines.
If your goal is to recover an original uncropped photograph or logo that was placed inside the PDF, full-page rasterization resamples that asset at the chosen page DPI. In that case, you should save original embedded images from a PDF so each embedded picture exports at its native resolution without surrounding page text.