Someone sends you a PDF — a brochure, a research paper, a slide deck — and there's a figure inside it you genuinely need: a chart for your notes, a product photo for a mockup, a diagram for your own document. Right-clicking the image does nothing. Photoshop's "Placed" extraction is overkill. So you take a screenshot... and end up with a blurry 72-DPI grab that includes the scrollbar and a chunk of the white margin. There's a better way.
This guide explains how to pull images out of a PDF cleanly, why the screenshot method is the wrong tool, how local rendering actually preserves quality, and exactly which DPI to choose depending on whether you're viewing on screen or sending something to print.
What's actually inside a PDF?
A PDF isn't one flat picture — it's a structured document that holds text, vector shapes, and embedded raster images as separate objects. When a figure sits on a page, it's usually embedded at its original resolution (often 200–400 DPI), which is far higher than what your screen shows. The trick is to render that page out at a resolution you choose, rather than screenshotting the already-downscaled view your browser displays.
Why the screenshot approach fails
A screenshot captures exactly what's on your monitor — typically 72–96 DPI. It also captures whatever else is on screen: browser chrome, the cursor, shadows, and misalignment. Zoom into a screenshot of a chart and the text is fuzzy because you only ever recorded 72 DPI of detail. Rendering the PDF page itself lets you choose 150 or 300 DPI, giving you a crisp image that matches the original, with none of the screen furniture.
| Method | Effective resolution | Quality | Clean edges? |
|---|---|---|---|
| Screenshot of screen | ~72–96 DPI | Blurry when zoomed | No — includes UI |
| Render at 150 DPI | 150 DPI | Crisp for screen use | Yes |
| Render at 300 DPI | 300 DPI | Print-quality | Yes |
How local rendering keeps the quality intact
The good tools decode the PDF with pdf.js (the same engine Firefox uses internally) and paint each page onto a canvas at a resolution you control. Because this runs in your browser, the PDF never uploads — important if it's a confidential contract or internal report. You pick which pages to export, choose the DPI, and get back a JPG or PNG per page.
Our PDF to JPG converter works exactly this way: drop in the PDF, wait for the page thumbnails to render, select the pages you want, set DPI, and download them individually or as one ZIP. It's the same engine the tooling industry uses, just wrapped in a no-upload interface.
Which DPI should you pick?
This is the single most common question, and the answer depends entirely on the destination:
- 72 DPI — only for quick thumbnails or previews. Don't use this for anything you'll reuse.
- 150 DPI — the sweet spot for on-screen use: slides, notes, web images, embedding in docs. Crisp, and the files stay reasonable (a page lands around 200–500 KB).
- 300 DPI — print quality. Choose this if you're sending the image to a printer or publishing it. Expect much larger files (1–3 MB per page), so don't default to this for screen-only work.
Rule of thumb: if it lives on a screen, 150 is plenty; if it touches paper, go 300.
Batch extracting a whole deck
When the image you need is actually every page — a slide deck you want as a set of JPGs, or a scanned report you want to turn back into photos — select all pages and use the ZIP download. There's no point exporting 40 pages one at a time; the bundle puts them in a single archive named in page order. Conversely, if you only need page 7, just tick that one checkbox instead of rendering the whole document.
JPG or PNG for the output?
For pages that are mostly photos or a mix of text and imagery, JPG at high quality is smaller and perfectly readable. For pages that are pure vector diagrams, sharp line art, or slides with solid color blocks, PNG avoids JPEG's softening around edges. When in doubt, JPG at 90% is the safe default; switch to PNG if text looks fuzzy after export.
What if you want to go the other direction?
Once you've extracted pages as images, you might want to recombine a selection into a new PDF — for example, taking the relevant figures from a long report into a short handout. That's the reverse operation, and the images-to-PDF tool does exactly that: drag in the exported JPGs, order them, and export a fresh multi-page PDF.
Extract every page of a PDF as a crisp image — choose DPI, pick pages, download as ZIP. Runs locally.
Open the PDF to JPG converterFrequently asked questions
Does extracting pages from a PDF lose quality?
Not if you render at sufficient DPI. At 150 DPI for screen use or 300 DPI for print, the output matches the original. A screenshot at 72 DPI is what loses quality — the render method is the fix, not the problem.
Can I pull out just one embedded image, not the whole page?
Rendering exports a full page as an image, which is the most reliable method and works on every PDF. True "extract the embedded object" extraction varies by PDF structure and often fails; page rendering always works and you can crop afterward.
Why is my 300 DPI export so large?
Because a 300 DPI A4 page has roughly 4× the pixels of a 150 DPI one. That's expected. If the images are only for screen viewing, 150 DPI keeps the files small with no visible difference.
Is it safe to process a confidential PDF here?
Yes. The PDF is decoded by your browser with pdf.js and never uploaded. Disconnect the network after the page loads and it still renders and exports — that's how you can verify no file leaves your machine.
My PDF is scanned (an image itself). Does this still work?
Yes. A scanned PDF is just a page-sized image, so rendering it out at 150–300 DPI gives you back that image at good quality — useful if you need to OCR, crop, or reuse a scan elsewhere.
