PDF to Image Converter: Practical Tips and Common Mistakes
Reviewed by the FreeOnline.fyi team · Updated 2026-09-14
What actually happens when you press Convert
We built this converter because almost every "PDF to JPG" site asks you to hand over the file first. Ours doesn't. When you drop a PDF into the box at PDF to Image Converter, the browser reads it as an ArrayBuffer and passes it straight to PDF.js, which ships with the page rather than loading from a CDN. Nothing is uploaded, there is no queue, and no account is involved.
Pages render one at a time: draw page 1 onto a canvas, export it as an image blob, shrink the canvas to 1×1 to release memory, then move to page 2. That serial loop is deliberate. If we rendered in parallel, a 60-page report at 300 DPI would hold sixty full-size canvases in memory at once and likely crash the tab.
The result area shows a thumbnail grid named page-1.png, page-2.png and so on. Clicking any thumbnail downloads the full-resolution blob — the preview you see is a scaled-down copy, not the file. When the document has two or more pages, a "Download all as ZIP" button appears and packs everything into pdf-images.zip. A one-page PDF gets no ZIP button, because a single file doesn't need an archive.
PNG or JPG: choose by page content, not habit
PNG is the default and it earns that spot. It is lossless, which matters for text. A 300 DPI page of black type on white often lands around 200–400 KB as PNG, because long uniform runs of white compress well. The same page as JPG is frequently smaller, but JPEG's block compression leaves faint halos around thin strokes — visible when someone zooms in, and genuinely harmful if you plan to run the image through OCR later.
Flip the reasoning for photographed or scanned pages. A scanned contract with a stamp, a photo-heavy product sheet, or a chapter of images will produce PNGs that can be many times larger than the JPG equivalent, with no visible benefit. JPG in this tool uses a fixed quality of 0.92 and there is no slider to fiddle with; 0.92 is high enough that artifacts stay invisible at normal viewing sizes.
A practical rule: if the page is mostly text, lines, charts, or screenshots, take PNG. If the page is mostly continuous-tone imagery, take JPG. Mixed documents are common, so if you only want one pass, PNG is the safer default and you can always convert again — the work is local and costs nothing but time.
Picking a DPI that survives your workflow
Resolution is converted internally to a scale factor of DPI ÷ 72. At 72 DPI you get the PDF's own coordinate space rendered one-to-one: an A4 page becomes roughly 595 × 842 pixels. At 150 DPI that becomes about 1240 × 1754; at 300 DPI, about 2480 × 3508; at 600 DPI, about 4960 × 7016 — nearly 35 megapixels for a single page.
Match the number to the destination rather than to a vague idea of "higher is better". 150 DPI is right for slides, chat previews, note apps, and web images. 300 DPI is what you want when the image will be printed, inserted into a Word or PowerPoint document, or submitted as part of an application that expects "print quality". 600 DPI is worth it mainly when you need to crop into a small region afterwards, or when you are archiving fine line art such as engineering drawings and signatures.
One thing worth internalising: the DPI setting here is a rendering decision, not metadata written into the file. Print shops and submission portals generally care about pixel dimensions relative to the size the image will be placed at, so a 300 DPI render placed at double size behaves like 150 DPI. Check the destination's requirement before converting a whole document at 600 DPI out of habit.
The mistakes we see most often
The first is expecting selectable text. A converted page is a picture — the text layer is gone. If you need searchable or copyable text, a PDF-to-image conversion is the wrong step and you want OCR instead. We mention this up front because it is the single most common disappointment.
Second, closing or reloading the tab mid-run. Because there is no server, there is no copy anywhere but your browser's memory. Reload, navigate away, or let a phone browser discard a backgrounded tab, and the finished pages are gone — you convert again from scratch. Keep the tab in the foreground, especially on mobile, and download the ZIP before you do anything else.
Third, misreading the ZIP. Archived PNGs and JPEGs are already compressed, so zipping them barely shrinks anything. The ZIP exists to save you dozens of individual clicks, not to save space. Fourth, building a workflow around a 600 DPI batch conversion when 150 DPI would do; pixel count scales with the square of DPI, so a 600 DPI run processes roughly sixteen times the pixels of a 150 DPI run of the same document. And finally, encrypted PDFs: if a file is password-protected, PDF.js cannot render it until it has been unlocked in a PDF reader first.
Large files and the limits we're honest about
The interface suggests a ceiling of about 100 MB and 200 pages. Exceed it and you get a warning, but the tool still lets you try — on a modern desktop, a 150-page text PDF at 150 DPI usually finishes fine, while a 150-page scan at 600 DPI will not. Time scales with both page count and pixel count, so plan around the total rather than the page count alone.
Canvas limits are the hard wall on some platforms. Mobile Safari and other browsers cap canvas dimensions and total canvas area; a 4960 × 7016 render can exceed those caps and fail even though memory looks available on paper. For big documents at high DPI, use a desktop browser and watch the progress readout ("processing page 7 of 24") to confirm it is advancing.
We are not going to pretend this is a print-production pipeline. It renders pages reliably and it never touches your file, but it does not rotate, crop, choose page ranges, or output WebP — those were left out on purpose to keep the page a single screen. If a converted page is going into something important, verify it: open the finished image, check the dimensions, and confirm the page count matches the original before you send it anywhere.
A short pre-flight checklist
Before you start: confirm it is the right PDF (page count shown after you drop the file), decide PNG or JPG based on page content, and pick the lowest DPI your destination will accept. Drop, convert, then download the ZIP in one sitting with the tab kept open.
Afterwards, spot-check one or two pages at full size rather than trusting the thumbnails alone, and keep the original PDF until the images have been accepted wherever they are going. If a run fails partway through, the usual culprits are DPI that is too high for the device, an encrypted file, or a tab that lost focus.
The no-upload approach is the whole point of this tool, and it runs through everything else on FreeOnline.fyi — the Video Highlight Finder works on the same principle for media files. Local processing is a privacy win, but it also means the browser is doing all the work, so give it the conditions to succeed.