PDF to PNG online — lossless image export
Turn each page of a PDF into a crisp, lossless PNG in seconds. All processing happens locally in your browser — no uploads, no signup, no watermark.
How to convert a PDF to PNG
Converting a PDF to PNG images with PDFluna takes one click and happens entirely in your browser. There is nothing to install, no account to create, and no files are sent to a remote server. Here is the full process, step by step:
- Upload your PDF. Drop your PDF onto the upload area, or click Choose file. Files up to 100 MB are supported. Nothing is sent to a server — the PDF stays on your device.
- Preview every page. PDFluna renders a thumbnail of each page so you can confirm the file before exporting. The preview is scroll-locked to the viewport, so it stays visible while you tune the settings.
- Pick a quality preset. Choose Small (72 DPI, smallest files), Medium (150 DPI, balanced) or Large (300 DPI, print quality). PNG is lossless, so DPI is the only knob that matters — there is no quality slider.
- Click Convert to PNG. Each page is rendered to an image in your browser, encoded as PNG, and streamed into a single ZIP archive. A single-page PDF produces one .png file instead of an archive.
- Download the images. When the conversion finishes you get a download link. Multi-page PDFs come back as a ZIP; single-page PDFs come back as a single .png. Your original PDF is never modified.
Why convert a PDF to PNG?
- Lossless detail. Every pixel of the rendered page is preserved exactly. There is no JPEG ringing around the edges of text, no chroma subsampling smearing fine lines — the PNG is a perfect raster of what the page looks like in a viewer.
- Sharp text and line art. Pages dominated by typography, code, charts, schematics or diagrams compress particularly well as PNG. The format was designed for this content and often produces smaller files than JPG for non-photographic material.
- Documentation and slide decks. Embed individual pages of a PDF into Notion, Confluence, Figma, Keynote or PowerPoint without rendering quality loss. Cleaner than embedding a whole PDF and crisper than a JPG.
- Archival snapshots. PNG is a stable, universally readable format with no generational quality loss. Useful when you want to keep the visual content of a document forever without depending on a PDF reader.
How PDFluna processes your files
Under the hood, PDFluna uses PDF.js (Mozilla’s open-source PDF renderer) and fflate (a tiny, fast ZIP library). Both load from a public CDN the first time you use the tool and are then cached by your browser. The actual processing never touches a server:
- Render. Each page is drawn onto an in-memory
<canvas>at the DPI you chose. PDF.js runs entirely in WebAssembly / JavaScript; no external service is consulted. - Encode. The canvas is handed to
canvas.toBlob('image/png')— the browser’s native PNG encoder. PNG output is lossless by definition; there is no quality argument because the spec doesn’t define one. - Pack. For multi-page PDFs, every PNG is streamed into a ZIP archive using fflate’s “store” mode. We never hold more than one decoded page in memory at a time, which keeps the tool usable on mid-range phones even for hundred-page documents.
- Deliver. The finished file is turned into a
blob:URL and attached to the download button. Clicking it triggers a standard browser download — nothing is uploaded anywhere.
PNG vs JPG — which one should you pick?
Both PDF to PNG and PDF to JPG use the same browser-side rendering pipeline. The only difference is the encoder applied to the canvas. The right choice depends on what your PDF actually contains:
- PNG wins for crisp text, screenshots, code listings, line art, technical drawings and pages with large flat-colour backgrounds. The lossless compression keeps edges sharp and the file size stays modest because PNG’s deflate stage compresses repetitive pixels well.
- JPG wins for scanned documents, phone-camera captures, pages with large photographs or rich gradients. JPG can produce files 3–5× smaller than PNG for the same visual content because it tolerates losing imperceptible detail.
- If in doubt, try both. Both tools are free and instant. Convert one page each way and compare file sizes — the smaller file at acceptable quality wins.
Frequently asked questions
Is my PDF uploaded to your servers?
No. Everything happens in your browser — we use PDF.js to render each page onto a canvas, then encode that canvas to PNG and pack the result into a ZIP. You can verify this yourself by opening browser DevTools → Network while the tool runs: no file uploads are made. Your PDF never leaves your device.
What is the difference between PDF to PNG and PDF to JPG?
PNG is lossless — every pixel of the rendered page is preserved exactly, with no compression artefacts. That makes it the right choice for pages with crisp text, screenshots, line art, charts and diagrams. JPG is lossy and produces smaller files but adds subtle ringing around sharp edges, so it’s better suited to photographic content like scans or phone pictures. Pick PNG when sharpness matters, JPG when file size matters and the content is photographic.
Why is there no quality slider?
PNG is a lossless format. The HTML specification defines no quality argument for PNG output — passing one has no effect in any browser. The only knob that controls PNG file size is the rendering DPI: more pixels means a bigger file, but with all detail preserved. If you need smaller files, lower the DPI; if you need much smaller files for photographic content, use our PDF to JPG tool instead.
What is the maximum file size and page count?
The tool accepts PDFs up to 100 MB. There is no hard page limit, but conversion time scales with page count and DPI: PNG encoding is slower than JPEG, so expect roughly 100 pages in 30–60 seconds on a mid-range laptop at 150 DPI. PNG output is also typically 2–4× larger than JPG for the same page, so a 200-page document at 300 DPI may produce a multi-hundred-MB ZIP. For very long scans, split the document first with our free Split PDF tool and convert each part.
Which DPI should I pick?
For on-screen use (web embeds, slide decks, documentation) 150 DPI is usually sharp enough on retina displays and keeps file sizes reasonable. 72 DPI is fine for thumbnails and small inline previews. 300 DPI is print quality; only pick it if you actually plan to print the images, otherwise file sizes grow roughly 4× for no visible benefit on screens.
Why do I get a ZIP instead of separate PNGs?
Browsers can only download one file at a time without the user clicking repeatedly. Packaging the pages into a single ZIP is the standard, friction-free way to deliver multi-page conversions. The ZIP uses “store” mode (no deflate compression) because PNG is already compressed internally — deflating it again would cost CPU time and barely shrinks the archive. A single-page PDF returns a single .png directly, no ZIP.
Are the PNGs transparent or do they have a white background?
The rendered PNGs are flattened against a white background, matching how Adobe Acrobat, macOS Preview and every other PDF viewer display pages. PDF pages are conceptually transparent in places (text on a blank page is just glyphs over no background), but viewers all flatten to white, and we follow the same convention so the exported image matches what you see on screen. If you specifically need transparent backgrounds for compositing, this tool isn’t the right fit — that requires per-object extraction, not page rendering.
Do the output images keep the original page order?
Yes. Files inside the ZIP are named yourname-page-01.png, yourname-page-02.png, and so on, with the page number zero-padded so they sort naturally in Windows Explorer and macOS Finder. Extracting the ZIP anywhere preserves the order.