How to convert PDF to JPG — sharp pages at the right resolution

The reasons to turn PDF pages into images keep piling up: a slide for software that only accepts pictures, a page mockup for a website build, receipts for an expense app, a proof for someone with no PDF reader at hand. The first instinct is a screenshot — wrong resolution, cropped edges, text that blurs the moment anyone zooms. The second is an online converter, which quietly uploads the entire document to a server. There is a third way: render each page from the PDF’s own vector data, in your browser, with nothing uploaded. This guide covers that method, then the decisions around it — which resolution matches which destination, why a real render beats a screenshot, and how to convert only the pages you need.

Convert PDF to JPG in your browser, step by step

The fastest path is the PDF to JPG tool on this site. The rendering happens entirely on your device.

1. Open the converter and drop your PDF anywhere on the page, click to browse, or paste it from the clipboard. It opens locally — nothing is sent anywhere.
2. Pick the resolution: 96, 150 or 300 DPI.
3. Click Convert to JPG. Each page is rendered at full quality by the same engine that powers the page previews, then encoded as a JPG on your device. A progress bar follows, page by page.
4. Download the ZIP. All images arrive in a single archive named after your document — “report-page-1.jpg”, “report-page-2.jpg” and so on.
5. Unzip and use them anywhere: the JPGs are ordinary image files with no strings attached.

96, 150 or 300 DPI — match the resolution to the destination

DPI — dots per inch — decides how many pixels each page becomes, and the right answer depends on where the image is going, not on how big you can make it.

96 DPI keeps files light. Chat apps, quick reads, screen-first destinations — at 96 DPI a forty-page document still arrives as an archive small enough to send on the first try.

150 DPI is the balanced default for sharing and viewing: sharp on any modern screen, without paying for print density nobody will use.

300 DPI is the print-grade choice — genuinely crisp type at the cost of noticeably larger files. Choose it when the images will end up on paper.

One limit worth respecting: scanned PDFs are already images. Rendering them above the resolution of the original scan adds size, not detail — a 200-DPI scan converted at 300 DPI just makes heavier files.

Why a real render beats a screenshot

Pages are rasterized from their original vector data: lines come out clean, text edges precise. At 300 DPI the output is real typographic sharpness, not an upscaled screenshot — visibly better than photographing a screen, and better than printing the page and scanning it back.

The trade is inherent to the format: text stops being selectable. A JPG is a picture of the page; no converter on any platform keeps the words underneath. If the recipient needs to copy text, send the PDF — convert when they need to see the page.

One ZIP, numbered and ready to use

Why an archive instead of individual downloads? Browsers either sprinkle dozens of files through the downloads bar or block them outright. A single ZIP guarantees every page arrives together, in order, with predictable names — the page order is baked into the file names, which makes the set ready for scripts, bulk uploads and drag-and-drop.

The packaging also solves the email problem: at 96 or 150 DPI, the whole archive usually clears attachment limits on the first attempt, no second pass needed.

Convert only what you need — and the way back

Two workflow refinements save real time. If you need a handful of pages from a long document, extract them first and convert that small file — the output matches its input exactly, the run is faster, and you are not deleting forty unwanted images afterwards. And if the images must come back together — a set of scans to deliver as one document — the reverse trip turns JPGs into a PDF in one step.

One prerequisite, shared with every tool in this family: encrypted files must be unlocked before rendering, because the engine cannot draw pages it cannot read.