The short answer: if you need pictures out of a PDF, the realistic browser workflow is to render the pages as high-resolution images and crop what you need. PDFEdit's PDF to Images tool renders each page at up to 216 DPI as PNG or JPG. What it does not do is pull the original embedded photo files out of the PDF — and understanding that distinction will save you confusion.
Rendering vs. extracting: the distinction that matters
A PDF can contain original image files embedded inside it — say, a 5-megapixel product photo placed on page 3. There are two completely different ways to "get the image out":
- Extracting — pulling the original embedded file out of the PDF, byte for byte, at its native resolution. This needs desktop software (and the PDF has to actually contain the original).
- Rendering — drawing the whole page as a brand-new image at a chosen DPI. You get a picture of the page, including its text, layout, and background.
Browser-based tools, including PDFEdit's, do #2. For most real-world needs — grabbing a chart for a slide, saving a diagram, sharing a page as an image — the render is exactly what you want. But if you're hoping to recover the original 5-megapixel photo file, a render won't give you that.
The practical workflow
Getting a whole page as an image
- Open PDF to Images.
- Drop in the PDF and choose PNG (lossless — best for cropping later).
- Pick 3x Ultra (216 DPI) for maximum pixels.
- Download the page you need.
Getting one picture off a page
- Render the page as above at 216 DPI PNG.
- Open it in any photo editor (even your phone's built-in editor).
- Crop to the image. Done.
Two steps, no special software, and at 216 DPI the cropped result is sharp enough for slides, documents, and web use.
Getting all pages as images
The tool converts every page and offers a ZIP download of the lot — useful when you're archiving a visual document or processing a whole catalog.
Choosing format and resolution
- PNG at 216 DPI — when you'll crop, zoom, or print. Maximum quality, bigger files.
- PNG at 144 DPI — whole pages for screens and slides. The sweet spot.
- JPG at 144+ DPI — photo-heavy pages where file size matters; use the quality slider (default 92%) to balance size and sharpness.
- 72 DPI — thumbnails and previews only. Don't crop from these.
What about the original embedded images?
If you genuinely need the source files — say, recovering photos from a PDF someone sent you when the originals are lost — honest options:
- Desktop PDF editors (Adobe Acrobat, etc.) can sometimes export embedded images at native resolution via their export functions.
- What browser tools can't do: reach inside the PDF's object structure and hand you the original file. Any online tool claiming "extraction" is almost certainly rendering pages, same as ours — we're just upfront about it.
In practice, a 216-DPI render cropped tightly is visually indistinguishable from the embedded original for screen and print-at-normal-size purposes. The gap only matters for large-format printing or pixel-peeping.
The copyright note (important)
Just because you can get images out of a PDF doesn't mean you should reuse them freely. Extracting images from your own documents, or from PDFs you have rights to, is fine. Pulling photos, illustrations, charts, or logos out of someone else's PDF to reuse in your own work can infringe copyright. When in doubt, check the source's license — or ask.
Common mistakes
Rendering at 72 DPI then cropping. You'll get a mushy crop. Always render at the highest DPI when you plan to crop.
Using JPG for a diagram. Text and line art in a cropped JPG look fuzzy. PNG for anything with sharp edges.
Assuming the render IS the original. It's a picture of the page. Great for most uses — just don't expect the embedded file's native resolution.
Forgetting you can't go backward losslessly. A render of a render loses quality each generation. Work from the highest-DPI render you have.
Best render settings by use case
| You need | Format | DPI | Why |
|---|---|---|---|
| Slide images | PNG | 144–216 | Crisp text on projectors; 216 if you'll crop |
| Social post | JPG | 144 | Small file, looks great at feed sizes |
| Print a page | PNG | 216 | Maximum real pixels for paper |
| Thumbnail/preview | JPG | 72 | Tiny file, just needs to be recognizable |
| Image you'll edit further | PNG | 216 | Lossless + headroom for cropping |
| Archive the visuals | PNG | 216 | Render once, keep the best version |
When in doubt: PNG at 216 DPI. Storage is cheap, and you can always downscale later — you can't upscale later.
Reuse rights: a quick primer
Since extraction makes reuse easy, a quick word on what's actually reusable:
- Your own documents: obviously fine.
- Public domain / CC0 images: fine, no restrictions.
- Creative Commons licensed: check the variant — some require attribution, some forbid commercial use.
- Stock photos in a PDF someone sent you: the license belongs to whoever bought it, not to you because you can see it.
- Logos and trademarks: extracting a company's logo from their PDF doesn't grant you the right to use it.
When reusing an extracted image publicly, note where it came from. It's both legally safer and professionally decent.
Do it with PDFEdit
- Convert PDF pages to images — PNG or JPG, 72/144/216 DPI, per-page or ZIP, all in-browser
- Convert PDF to JPG — the JPEG-only variant with quality control
- Convert PDF to PNG — format choice deep-dive
Render the page, crop the picture. For everything short of recovering original print assets, that's the whole job.
