PDF to Image — Free Online Tool on Toolpile
Every tool you need, one place
PDF, Image, AI, Dev, and Business tools — free, private, no signup.
Toolpile uses cookies for analytics and ads. The tools themselves keep your files in the browser — that doesn't change. Read the full policy
PDF, Image, AI, Dev, and Business tools — free, private, no signup.
About PDF to Image
Converting a PDF to images is the inverse of Image-to-PDF, and the use cases are different: extracting a thumbnail of page 1 for a preview, pulling diagrams out as PNGs for a slide deck, sending a single page to someone whose phone can't open PDFs reliably. The tool produces one image per PDF page; what follows are the choices — DPI, format, page selection — that decide whether the output is sharp enough for what you'll do with it.
PDF is a vector format (mostly) — text and shapes are described mathematically, so they can render at any resolution. When you convert to a raster image (PNG, JPEG, WebP), you have to pick how many pixels per inch the output should have. That single number determines file size and visual quality.
Practical thresholds: 72 DPI = screen-only thumbnail, smallest file (a US Letter page at 72 DPI is 612 × 792 px, ~50 KB PNG). 150 DPI = good for screen viewing at full size, acceptable for laser-print quick reference (1275 × 1650 px, ~300 KB PNG). 300 DPI = print-ready, sharp on retina displays, the publishing default (2550 × 3300 px, ~1.5 MB PNG). 600 DPI = high-resolution archival or fine print, rarely necessary, file sizes 4× a 300 DPI version.
The trap: choosing 600 DPI "to be safe" produces 5-10 MB image files for what could be a 200 KB output at 150 DPI. Match the DPI to the destination — screen displays only render ~120-220 effective DPI, so anything you generate above 300 DPI is invisible quality on screen. Pick the lowest DPI that passes your quality test, not the highest possible.
PNG is lossless and the safest default for converted PDF pages. Text edges stay sharp, diagrams retain crisp lines, and there's no compression artefact regardless of DPI. The cost is file size — a 300 DPI PNG of a US Letter page is typically 1-3 MB.
JPEG is smaller (300-600 KB at the same DPI) but introduces subtle ringing around text edges. For pages dominated by photographs (a photo magazine, a scanned image-heavy report), JPEG output is fine and the size saving matters. For pages with body text, equations, or technical diagrams, JPEG output looks visibly degraded around every letter — stick with PNG.
WebP is the modern compromise: lossless or lossy, 25-35% smaller than equivalent PNG/JPEG, supported in every browser since Safari 14 (2020). For 2026, WebP is a strong default if you control where the images will be used. Avoid it only if the destination is something legacy (older email clients, certain CMS uploads, print pipelines) that still doesn't decode WebP.
For OCR (running an image through text-recognition afterward), PNG at 300 DPI is the gold standard — Tesseract and other OCR engines specifically prefer lossless input at that resolution. JPEG artefacts confuse the recognition engine even when invisible to humans.
Most use cases want one or two specific pages, not every page of a 200-page PDF. The tool lets you specify page ranges (`1-5`, `7`, `10-12`) — pick before converting, because converting all pages of a long document produces dozens or hundreds of files (a 200-page PDF at 300 DPI PNG = ~600 MB total).
First-page-only is the most common ask — generating a thumbnail for a document preview, capturing a cover page for sharing on social, pulling the title page of a paper. The tool defaults to all pages but accepts `1` as the explicit single-page case. The output is one file (`page-1.png`), not a zip.
Multi-page output downloads as a zip. The naming convention is `page-1.png, page-2.png, page-3.png…` — sortable, consistent, predictable. Some tools number from 0 (`page-0.png`); this one starts at 1 to match how humans count pages.
Why are my converted images blurry?
Almost always the DPI is too low for the destination. A 72 DPI image looks fine as a small thumbnail but pixelates if you display it full-screen on a retina monitor. Re-run at 300 DPI and compare. If the source PDF itself is a low-resolution scan, the conversion can't add detail that wasn't there — you'll get back what was originally captured.
Can I extract just images from a PDF (not full pages)?
No — this tool rasterises whole pages. To pull individual embedded images out (the photos and diagrams as separate files, not the full page rendered around them), use the PDF Extract Images tool on this site, which reads the PDF's image objects directly without re-rendering.
Does it preserve text searchability?
No — once you convert to an image, the text becomes pixels. PNG and JPEG don't carry text content. If you need a searchable image-PDF, run the converted images back through OCR (PDF to Text or a dedicated OCR step). The original PDF is always the better source for searchable content.
Will it work on a password-protected PDF?
No — encrypted PDFs need decryption first. Run through PDF Unlock (browser-local) and then convert the unlocked output.
What's the maximum PDF size I can convert?
Browser memory limits this. A 50 MB PDF at 300 DPI typically converts fine; a 500 MB scanned document risks running Chrome out of per-tab memory mid-process. For massive PDFs, split first (PDF Split), convert chunks separately.