Initializing... drag & drop files here
Supports: PDF
To convert PDF to PNG, upload your PDF, pick a DPI (300 for print, 150 for screen), and click Convert. Each PDF page becomes one PNG image. PNG uses lossless compression, so text and line art stay perfectly sharp, and it preserves any transparency the page already has — the key advantage over PDF to JPG.
Real result: a 10-page PDF rendered at 300 DPI produces 10 numbered PNGs (page-1.png, page-2.png, ...), delivered individually or as one ZIP. Need smaller, photo-friendly files instead? Use PDF to JPG.
PNG is the right output when you need pixel-perfect rasters of PDF pages — text stays sharp, line art stays clean, and transparency is preserved. Unlike JPG, PNG uses lossless compression, so a 300 DPI PNG of a contract page is mathematically identical to what the PDF renderer produced. That matters whenever the page will be re-edited, posted to the web at native resolution, or printed.
| Property | PNG | JPG | WebP |
|---|---|---|---|
| Compression | Lossless | Lossy | Lossy or lossless |
| Alpha transparency | Yes (full alpha channel) | No | Yes |
| Sharp text and line art | Excellent | Visible artifacts at sharp edges | Excellent (lossless mode) |
| File size for text page | Medium | Smallest (lossy) | ~26% smaller than PNG (lossless) |
| Browser & app support | Universal | Universal | Chrome, Firefox, Edge, Safari 16+ (~96%) |
| Best for | Documents, diagrams, screenshots, design assets | Photo-heavy magazine PDFs | Modern web pages where size matters |
For text-heavy PDFs and anything with sharp edges, PNG is the safe default. Pick PDF to JPG for photo-heavy PDFs where 30-50% smaller files matter more than perfect sharpness, or PDF to WebP when the destination is a modern web page and you control the rendering surface.
| DPI | Pixel dimensions | Typical PNG size | Best for |
|---|---|---|---|
| 72 DPI | 612 x 792 px | ~80-150 KB | Web thumbnails, contact-sheet previews |
| 96 DPI | 816 x 1056 px | ~150-250 KB | Default Windows / screen resolution |
| 150 DPI | 1275 x 1650 px | ~300-500 KB | Screen viewing, email attachments, slide decks |
| 200 DPI | 1700 x 2200 px | ~500-800 KB | Everyday documents, readable body text |
| 300 DPI | 2550 x 3300 px | ~1-2 MB | Print production, OCR, archival |
| 600 DPI | 5100 x 6600 px | ~3-6 MB | Fine-detail archival, prepress, halftone source |
| 1200 DPI | 10200 x 13200 px | ~10-25 MB | Specialty prepress, microform substitute |
Sizes are typical for mixed text-and-graphics pages and grow with the amount of image content on the page. A pure-text page compresses much smaller than a page with photographs.
PDF pages can carry transparent elements — overlay logos, watermarks on a clear background, design layers without a fill. The xconvert Image Transparency control lets you choose: keep transparency (alpha channel) or flatten to a solid color (the default is white, but you can pick any of the named palette colors).
Yes. A 10-page PDF produces 10 numbered PNGs (page-1.png through page-10.png). They're delivered as individual downloads or bundled into a single ZIP archive. PNG itself has no multi-page container — that's a feature of formats like TIFF or PDF, not PNG.
150 DPI for screen viewing, slide decks, and email attachments. 200 DPI for everyday document sharing where text needs to remain comfortably readable when zoomed. 300 DPI for printing, OCR, and any case where you might later re-export or crop. 72 DPI only for tiny web thumbnails. Doubling the DPI roughly quadruples the pixel count and file size, so don't pay for resolution you won't use.
Only if the source PDF page itself contains transparent elements. PDFs authored for print typically have a white page background — converting those produces a PNG with white pixels, not transparency. PDFs authored as design assets, single-element exports, or with a transparent page color produce PNGs with a real alpha channel. Use the Image Transparency control to flatten to a chosen background color when you don't want alpha.
PDF stores text as glyphs (a few bytes each) and vectors as math; PNG stores rasterized pixels. A 50 KB PDF page rendered at 300 DPI can easily produce a 1.5 MB PNG because you're now storing every pixel of every letter. That's expected — drop the DPI to 150 if file size matters more than print sharpness, or convert to WebP for roughly 26% smaller lossless files at the same visual quality.
Yes. PNG uses DEFLATE compression (the same algorithm as ZIP), which is mathematically reversible — no pixel data is discarded. JPG uses DCT-based lossy compression and discards high-frequency detail, which is what produces the "fuzzy text" artifacts around sharp edges in document conversions. For any PDF with text, diagrams, or screenshots, PNG keeps things crisp where JPG smears them.
Use Split PDF first to extract the page range you want, then convert the resulting PDF to PNG. That keeps the workflow simple and avoids re-uploading the whole document just to throw most pages away.
There is no fixed page-count cap. Very large PDFs (hundreds of pages at 300 DPI) will produce hundreds of megabytes of PNG output — upload size and your connection speed will be the practical limit, since the file is uploaded to our servers for rendering. For large jobs, drop to 150 DPI, split the file into smaller chunks via Split PDF, or export every page at once with PDF to Images.
Yes — use PNG to PDF for a single image or Merge images to PDF when you have many. Round-tripping is lossless on the PNG side, so re-merged PDFs preserve everything except text searchability (since the PDF now contains rasters, not glyphs — run OCR if you need search).
Run the output through Compress PNG after conversion. PNG compression is lossless by spec, but smart re-encoding (palette reduction, filter optimization, removing metadata) typically saves 20-50% on document-rendered PNGs without any visible quality loss.