PDF to JPEG: Best Resolution by Destination
Quick answer
This tool has two settings, and one of them matters most: resolution. Use 150 dpi for a screen preview, 96 to 110 dpi for a marketplace thumbnail or a chat image, 200 dpi for a printed handout, and 300 dpi only when the image will be zoomed or printed large. Then choose pages deliberately — all is rarely what a delivery needs.
What this article covers
Resolution by destination, how page selection interacts with render time, and the two preparation steps that make the ZIP easier to use. There is no quality slider on this tool, and this article does not pretend there is one. For the mechanism, read the beginner's guide.
What it actually does
Resolution is the only image control. The page is drawn at the dpi you choose, so the pixel dimensions of the JPEG are the page's physical size times that number, divided by 25.4. A4 at 150 dpi is about 1240 by 1754 pixels. The same page at 300 dpi is about 2480 by 3508.
That is worth checking against the destination before you render, because the destination's limit is almost always expressed as a maximum width in pixels. A listing that shows images at 1200 pixels wide does not benefit from a 2480-pixel render; it will downscale it and the upload will take four times as long for nothing.
That multiplication is the whole trade-off. More pixels means more detail and a bigger file, and the cost is roughly quadratic: doubling dpi quadruples the pixels before JPEG compression. There is no quality field, because there is no second encoder decision to make — the page is drawn once at that resolution and encoded.
Page selection is the other control, and it is a cost control as much as an editorial one. Each page is a canvas draw, so rendering fifty pages takes far longer than rendering five. The run is capped at 50 pages for exactly that reason.
Step by step
- Ask what the destination is: a screen, a print, a thumbnail, a large format.
- Pick the dpi from the table below.
- Choose the pages, using
1,2-6,last,oddorall. - Run and unzip into a folder named after the document.
- Compare the image's pixel dimensions with the destination's stated limit.
- If it is too large, lower the dpi and re-render rather than resize afterwards — re-rendering keeps the page sharp.
| Destination | Resolution | Notes |
|---|---|---|
| Chat or email preview | 96–110 dpi | small file, readable on a phone |
| Marketplace listing image | 110–150 dpi | check the site's maximum dimension |
| Slide or document insert | 150 dpi | default; fits a full-width slide |
| Printed handout | 200 dpi | readable at arm's length |
| Print or deep zoom | 300 dpi | large files; render only the pages needed |
| Thumbnail | 72–96 dpi | the destination will scale it down anyway |
What to check after download
- Pixel dimensions against the destination's limit, in pixels rather than megabytes.
- Smallest text at 100 per cent, on the busiest page.
- Thin rules and table borders, the first things to disappear.
- Aspect ratio, which should match the page — a stretched image means the source page had an unusual size.
- File count, matching the pages you selected.
- Names, so the images sort into page order in a folder.
- The destination's own preview, if it has one, because that is the copy a customer will see, and it may crop what you upload.
- Whether the page is the one the destination expects first, since some listings use the first upload as the thumbnail.
Common beginner mistakes
Choosing dpi by the file size you want rather than the destination you have. The destination's pixel limit is the useful number.
Rendering at 300 dpi for a listing that will downscale to 1000 pixels wide. The extra detail is discarded by the site and paid for twice, once on render and once on upload.
Rendering all for a twenty-page report when the deliverable is the cover and the price table.
Resizing the JPEG afterwards to hit a limit. Rendering at the right dpi produces a sharper image than rendering large and shrinking it.
Treating one good render as a template for every document. The dpi that suits a text page is often too much for a photo-heavy brochure, because the file size follows the detail in the page rather than the page count.
Rendering the whole document to test one page. Render just the cover or the price table, check it, and then render the rest with the settings you proved.
When this tool is the right choice
When the destination is measured in pixels. If it is measured in pages or megabytes of document, a PDF tool is the right family and this one is not. If the task is to edit the text, no render will help.
Related tools
Resize an Image is the follow-up when the rendered image needs an exact width, a different format such as WebP, or a smaller file at a fixed size. It works on the JPEG this tool produced, so render slightly larger than you need and let the resize step land exactly on the limit.
Use this tool
Render to the destination's number on PDF Converter: the table above is the starting point, and the pixel dimensions after the first render tell you whether it was right.
Next step
Read business use cases for the workflows where a folder of page images is the deliverable rather than a stop on the way to one.
Continue Exploring
Browse more release notes and the tools they reference.