PDF to JPG — every page as an image.

Turning PDF pages into images

A PDF page is a set of drawing instructions, not a picture. To get a picture out you have to render it at a chosen size, and that size is the only decision that really matters. Everything else follows from it.

1. Drop the PDF in. The first page is read immediately and the total page count appears, so you can confirm it is the right file before spending time on a conversion.
2. Choose a format. JPG is smaller and right for photographs and page scans. PNG is lossless and sharper for pages that are mostly text, at roughly three to five times the file size.
3. Choose a resolution. 1× gives one pixel per PDF point (72 dpi), 2× doubles it, 3× triples it. A typical A4 page is 595 × 842 points, so the three settings produce roughly 595, 1190 and 1785 pixels across.
4. Narrow the pages if you want. Leave the field empty for the whole document, or type 1-3, 7 to render four pages out of a hundred.

When this comes up

• Putting a PDF page into a slide deck. Slides accept images, not PDFs. Rendering at 2× gives a page that stays sharp when projected.
• Sending one page in a chat. Nobody opens a 40-page attachment to read page 3. Convert just that page and paste the image.
• Building a thumbnail or preview. A 1× render of page one is a few tens of kilobytes and good enough for a card, a listing or an email preview.
• Feeding a page to a tool that only takes images. OCR, image editors, design mockups and some upload forms accept JPG and nothing else.

A worked example: twelve pages at three sizes

A twelve-page A4 contract, mostly text with rules and a signature block, rendered as JPG at each of the three settings on an ordinary laptop:

The jump from 2× to 3× costs twice the file size for 50% more pixels, which is why 3× is worth it only for pages that will be printed. Notice too that rendering time barely moves between 1× and 2× — the page has to be parsed and drawn either way, and the pixel count is not the bottleneck at these sizes.

PNG behaves differently, and not the way the usual advice suggests. On this document a single page at 1× is 18 KB in PNG against 23 KB in JPG, because large flat areas of white compress well without loss. At 3× the order reverses: 111 KB in PNG against 87 KB in JPG. PNG wins on simple, sparse pages; JPG wins as resolution rises and the page gets busy. On a scanned photo page PNG loses badly at every size.

There is a second cost people forget. Fifty pages at 3× is fifty canvases of roughly 1785 × 2526 pixels held in memory at once, which is close to a gigabyte. On a phone that fails quietly. Converting in batches of ten pages and merging the ZIPs afterwards works fine, and the page range field exists for exactly that.

Where PDF-to-image goes wrong

• Rendering at 1× and then zooming. This is the most common disappointment. The image is exactly as sharp as it was rendered and no sharper; zooming in a viewer shows the pixels, not the text.
• Choosing PNG for a photographic page. A scanned photo page in PNG can be ten times the size of the JPG with no visible gain. PNG wins on text and line art, JPG wins on photographs.
• Assuming the page numbers match. A document with a cover page often has printed numbers that are one or two behind the actual PDF page index. Check page one before converting a range.
• Losing what made the PDF useful. Links, form fields, selectable text and bookmarks all disappear. If the recipient needs to search or fill the document, send the PDF.

Questions