PDF to Image Converter: No-Upload Conversion, Compared to the Alternatives
Reviewed by the FreeOnline.fyi team · Updated 2026-09-14
Why we built a converter that never uploads your file
Search for "PDF to PNG" and almost every result asks you to upload the document first. That's fine for a public flyer. It's a bad idea for a signed contract, a payslip, an invoice with bank details on it, or a scanned ID — which, in our experience, are exactly the files people convert most often. Once a file lands on someone else's server, you're trusting their retention policy, their queue, and whatever their "files are deleted after one hour" promise happens to say.
So we built PDF to Image Converter the other way round. You drag a PDF onto the page, the browser reads it as an ArrayBuffer, and PDF.js — shipped with the tool rather than pulled from a CDN — renders each page inside your own tab. Nothing is posted anywhere. No account, no queue, no daily limit, no watermark. Close the tab and the document is simply gone from memory.
The trade-offs cut both ways. Conversion speed depends on your machine rather than our bandwidth, and a conversion in progress doesn't care if your Wi-Fi drops. But there's no server-side muscle to fall back on either, which is why a 200-page document at 600 DPI is a genuinely heavy thing to ask of a laptop. We'd rather tell you that up front than have you find out at page 140.
What happens between the drop zone and the ZIP file
The interface is deliberately small: one drop zone, two pill selectors (PNG or JPG, and 72 / 150 / 300 / 600 DPI), one button. Defaults are PNG plus 150 DPI, so you can convert without touching a setting. Internally the DPI choice is just a scale factor — scale = DPI ÷ 72. At 300 DPI every page renders at about 4.17× its native PDF size. For A4 that works out to roughly 595 × 842 px at 72 DPI, 1240 × 1754 px at 150, 2480 × 3508 px at 300, and about 4961 × 7016 px at 600.
Rendering is strictly one page at a time: render, export to an image blob, reset the canvas to 1 × 1 to free memory, move to the next page. That's why the progress bar reads "processing page 3 of 12" instead of jumping unpredictably. Ten pages rendered in parallel at 300 DPI would be roughly 350 MB of raw pixel data — a single A4 canvas is around 35 MB before compression — and that is exactly how browser tabs die. Serial rendering looks slower on paper and behaves far better in practice.
PNG is the honest default. The PNG specification defines it as lossless, so small text, tables, thin rules and screenshots stay crisp, and flat white pages compress well. JPG is fixed at quality 0.92 with no slider, which makes it the better choice for photo-heavy scanned pages where PNG would balloon. When a document has more than one page, a ZIP button appears and packs everything as pdf-images.zip containing page-1.png, page-2.png and so on, assembled locally. One honest caveat: zipping already-compressed images barely shrinks them, so the archive is roughly the sum of the individual files.
How it stacks up against the other ways to do this
Screenshotting a page is the most common alternative and the weakest one. You get whatever resolution your screen happens to have, you can't choose DPI, and a 12-page document means 12 careful crops with the window scrolled to exactly the right place. Browser zoom plus print-to-image tricks are only marginally better, because output size ends up tied to window width and is never reproducible.
Desktop software is genuinely good at this job. Adobe Acrobat exports images with fine control, macOS Preview handles single pages competently, and LibreOffice Draw can export multi-page documents. The catch is installation, licensing, and locked-down work laptops that won't let you install anything at all. Command-line tools like pdftoppm from Poppler, or ImageMagick, are the best option if you're converting hundreds of files on a schedule — scriptable, fast, batch-friendly. Our tool is built for the other case: a handful of files, a one-off task, on a machine you don't control.
Upload-based converters sit in the middle — zero install, works on any device, but the file leaves your machine and you're usually paying for the convenience with a size cap, a queue or a watermark. That's the one trade we refused to make. If the PDF is genuinely public and you need 500 pages converted overnight, a server will beat a browser tab. If it's your lease agreement, keep it local.
Picking settings for real jobs
Contracts and invoices you're sending a colleague as a visual preview: JPG at 150 DPI. It's legible on a phone, a three-page document stays comfortably small, and email clients won't complain. PNG at the same DPI is crisper for text but often several times larger, which matters when the file is an attachment.
Pages you're dropping into slides, a CMS, an e-commerce listing or a chat thread: PNG at 150 DPI. Text and interface screenshots stay clean, and roughly 1240 px of width for A4 is already more than most templates need. Jumping to 300 DPI for on-screen use makes each image about four times heavier with essentially no visible gain at typical display sizes.
Print or print-adjacent work: start at 300 DPI — 2480 × 3508 px for A4 is the ballpark most print shops ask for. Reserve 600 DPI for fine line art, embossed stamps or archival copies where someone will zoom in later, and expect individual pages to run tens of megabytes and the whole job to take a while. Photo-heavy scans and magazine-style layouts: JPG at 300 DPI. Mostly-text vector pages: PNG at whatever DPI the destination needs.
If the exported images are headed for a web page as a link preview, pair the export with our Free Meta Tag Generator so the og:image you point at is actually sized for the card it will appear in.
What it deliberately doesn't do (and how to work around it)
There's no page range selector — it converts the whole document, every time. That keeps the whole tool on one screen, but it's the limitation people hit first. If you need pages 7 to 9 of a 300-page report at 600 DPI, this isn't the right tool for that pass; convert the document at 150 DPI, or reach for a desktop or command-line converter when only a few pages matter.
There's no WebP output (Safari's support has been inconsistent historically), no rotation, no cropping, no JPG quality slider, and no multi-file batch queue. One PDF at a time. Password-protected PDFs may simply fail to open: because the file is never transmitted, there's nothing on our side that could attempt to unlock it. If it's your document, unlock it locally first.
The output is pixels only. There's no OCR, so text in the resulting PNG or JPG can't be selected, copied or searched. If you need searchable output, you want a text-extraction or OCR tool rather than a renderer. And since PDF is defined by an ISO standard that permits a lot of variation, odd files exist: embedded images that are already low-resolution, where no DPI setting can invent detail that was never scanned in; unusual colour spaces; pages that rely on transparency, which JPG flattens because it has no alpha channel.
Treat every number here as an expectation rather than a guarantee. Check the actual pixel dimensions of your exported images against the spec you're working to — a print shop's requirement, a platform's upload limit, a template's aspect ratio — before sending anything important. And if you need a companion step like resizing, compressing or checking a file, there's a full set of free online tools to pick from.