Sometimes you don't need the PDF — you need the pictures inside it. Pulling a diagram out of a report to drop into a slide deck, grabbing a scanned photo out of an old document, or turning a one-page flyer into an image for social media are all the same underlying job: render each PDF page as an image. PDF to JPG does this locally, without uploading your file.
This guide covers the conversion itself, the quality setting that determines how the images turn out, and how to decide between JPG and PNG when you have the choice.
How to convert a PDF to JPG
- Open PDF to JPG and drop in your file.
- Choose a quality — Low, Medium, or High. Higher quality means larger, sharper images.
- Convert. Every page becomes its own JPG, bundled together into one .zip file.
- Extract the .zip to get the individual page images.
The conversion is purely visual: each page is rendered exactly as a PDF reader would display it, then captured as an image. What you see on the page is what you get in the file — layout, fonts, graphics, stamps, everything.
Why turn pages into images?
A PDF page and an image of that page sound interchangeable, but they behave very differently once they leave your desk. Images are the lingua franca of computing — every app, chat tool, and platform knows what to do with a JPG, while PDF support is patchier in exactly the places you often need it:
- Slide decks and documents — dropping a page into PowerPoint, Word, or Google Slides as an image is often cleaner than embedding a PDF, which may display inconsistently (or not at all) on the recipient's machine.
- Chat and messaging apps — many preview images inline instantly but treat PDFs as clunky file attachments, when they accept them at all.
- Social media and web content — platforms want images, not documents. A flyer, certificate, or infographic page becomes postable the moment it's a JPG.
- Design tools — pulling a page into Figma, Canva, or an image editor to annotate or restyle it means having it as an image first.
- Proof and record-keeping — capturing exactly what a page looked like, fixed and unchangeable, for documentation or comparison.
There's also a practical size argument: for a single page someone needs to glance at, a JPG often beats a multi-megabyte PDF attached in full.
Choosing a quality level
Low, Medium, and High aren't marketing labels — they map directly onto the trade-off every raster format makes between detail and file size. JPG is a lossy format: it stores an approximation of the image, and the quality setting decides how faithful that approximation is.
Medium is a solid default for most uses — sharing on a slide, embedding in a document, posting online. At typical viewing sizes it's visually indistinguishable from the higher setting while producing sensibly sized files.
High is worth reaching for when fine detail matters: a diagram with small labels, a scanned document you'll re-read closely, a page someone will zoom into. Small text is where low-quality JPG suffers first — edges soften and letters smear long before anything else visibly degrades.
Low fits when size outranks sharpness — a large batch you're archiving as thumbnails, pages destined for a quick glance, or images going somewhere with tight size limits.
A practical rule of thumb: convert one page at each level and look at the result. It takes ten seconds and removes all guesswork about where the sweet spot is for your document.
How the rendering works — and why scans aren't a problem
The tool renders each page visually rather than trying to read text out of it. That has a useful consequence: it doesn't matter whether the PDF is text-based or a scan. A scanned page converts to JPG just as cleanly as a typed one, since either way the job is capturing what the page looks like.
The same logic means pages with unusual fonts, vector graphics, watermarks, or stamps render correctly — anything a PDF reader can display, the image captures. The flip side is worth knowing: after conversion, text on the page is pixels, not characters. You can't select or search it in the image. If your goal is editable text rather than a picture of text, converting to an image is the wrong direction — PDF to Word or OCR PDF is the tool for that job.
JPG or PNG?
JPG is the right default for pages-as-pictures: it's universally supported and keeps file sizes sane for photographic or complex content. But JPG compression is lossy, and pages that are mostly sharp text, lines, and flat colors are exactly the content where its artifacts show first.
If you need a pixel-perfect, lossless capture — evidence screenshots, archival copies, or images that will be edited and re-saved downstream — PDF to PNG produces exactly that, with a resolution selector instead of a quality selector. As a general rule: photos and mixed-content pages → JPG; text and line art where crispness is paramount → PNG.
Why a .zip?
A ten-page PDF converted to ten separate JPGs is ten downloads — awkward in any browser. Bundling the pages into a single .zip keeps it to one download, and the images inside are named page by page (document-page-1.jpg, document-page-2.jpg, …) so the page order survives extraction. Double-click the zip on Windows or macOS, or use any archive tool, and you have a folder of images in reading order.
Private by default
The rendering happens in your browser — the PDF is parsed and drawn by your own machine, and the images are saved straight back to you. The file never uploads, which matters most for the documents this conversion is often wanted for: contracts, IDs, medical records, statements. No server copy, no retention window, nothing to trust beyond the tab you have open.
Going the other direction
If you're starting from images and want them combined into a single PDF instead, that's the reverse job — see JPG to PDF.