PDF to Images

When a PDF page needs to be an image

A PDF is great until the moment you need to put a page somewhere that only takes images. Slack previews, an Instagram carousel, a slide you're building in Keynote, a forum post, a product listing, a documentation screenshot — none of them embed a PDF nicely. You end up screenshotting a page, cropping the browser chrome, and settling for whatever resolution your monitor happened to be. This tool does that job properly: it renders every page of a PDF to a clean PNG or JPG at the size you choose, with no window edges, no cropping, and no guesswork about quality.

Under the hood it uses Mozilla's pdf.js — the same engine Firefox uses to display PDFs — running entirely in your browser. It reads the actual page geometry and re-rasterises each page at your chosen resolution, so a diagram or a chart comes out sharp rather than blurry the way a screenshot of a zoomed-out page would. You get a single image if the PDF is one page, or a numbered ZIP of every page for a longer document.

PNG or JPG, and what resolution

Two choices decide how your images look and how big the files are.

Format. PNG is lossless — every pixel is exact, edges stay crisp, and there's no compression fuzz around text and lines. It's the right pick for slides, diagrams, screenshots, or anything with sharp type. JPG trades a little of that sharpness for much smaller files, which suits photo-heavy pages or when you need to keep the total download light. One honest detail: PDF pages can be transparent, but JPG can't hold transparency, so JPG pages are given a flat white background. PNG keeps whatever the page had.

Resolution. Three presets cover most needs:

• Screen (~108 dpi) — light files for web previews, chat, and social, where the image will be viewed on a display anyway.
• High (~144 dpi) — a good default: crisp on high-density phone and laptop screens without ballooning the file size.
• Print (~216 dpi) — dense enough to look clean on paper or when someone will zoom in. Files get noticeably larger; use it when you actually need the detail.

The trade-off worth knowing

An image is pixels, not a document. Once a page becomes a PNG or JPG, the text in it is no longer selectable, searchable, or editable — it's a picture of text. That's exactly what you want when the goal is to show a page somewhere that won't take a PDF, or to stop someone easily copying the text out. It's the wrong tool if you actually need an editable or searchable file — in that case keep the PDF, or use the merge/split PDF tools to rearrange pages while they stay real PDFs. This tool converts to images on purpose; it doesn't pretend the result is still a document.

It runs on your device, and stays there

The files people convert are rarely just brochures. They're contracts, bank statements, medical results, signed forms, internal decks — pages you might want as images to paste into an email or a chat, but definitely don't want sitting on a stranger's server first. Because pdf.js renders everything locally, your PDF is never uploaded. There's no account, no queue, no daily cap, and once the page has loaded it keeps working with the network switched off — which is also the simplest proof that nothing is being sent anywhere.

A practical note on big files: since the work happens on your own hardware, a very long or image-heavy PDF at print resolution leans on your device's memory. Most documents convert in a moment; a few-hundred-page scan at 216 dpi is where an older phone might struggle. If it feels slow, drop the resolution a notch or convert in smaller batches. For the everyday case — turning a handful of pages into images you can actually use, without handing the file to anyone — it's fast, private, and does exactly one thing well.