How do I turn a PDF page into a JPG or PNG?

Turning a PDF page into an image is one of the few PDF jobs with no hidden traps, but there are two decisions that determine whether the result is crisp or disappointing, and both are made before you convert, not after.

The two decisions

Which format, and at what resolution. Get those right and there is nothing else to think about.

PNG or JPG

They compress differently, and the difference is not subtle when the page is text.

PNG is lossless. Every pixel comes out exactly as it was drawn. Text edges stay hard, thin rules stay thin, and a screenshot of the image is identical to the page. The cost is file size: a text-heavy A4 page at 150 DPI might be 300 KB.

JPG is lossy. It discards detail the eye is unlikely to miss, which works brilliantly on photographs and badly on text. Around every sharp black-on-white edge JPG leaves a faint grey halo. The artefact everyone recognises without being able to name. The same page might be 80 KB.

The rule that follows:

If you are unsure, choose PNG. A file that is too big can be compressed later; detail that has been thrown away cannot be recovered.

Resolution, in terms that mean something

A PDF page has no resolution. It is a set of drawing instructions that can be rendered at any size, which is why a PDF stays sharp when you zoom in and a photograph does not. Rendering it to an image is the moment you choose how much detail to keep.

DPI (dots per inch) is that choice. An A4 page is 8.27 inches wide, so:

• 72 DPI gives about 595 pixels wide. Fine for a small thumbnail. Text becomes unreadable.
• 150 DPI gives about 1,240 pixels. Comfortable on screen, readable, sensible file size. This is the default here, and it is right for most uses.
• 300 DPI gives about 2,480 pixels. The standard for printing. Overkill for anything that stays on a screen.
• 600 DPI gives about 4,960 pixels. Only worth it for archival scanning or when someone will zoom deeply into fine detail.

The common mistake is choosing 72 because the image is "for the web" and then discovering nobody can read the text. Screens have moved on; 150 is the modern floor for anything with words on it.

Doing it

PDF to Image renders at 150 DPI and lets you choose PNG or JPG and which pages to convert. One page comes back as an image; several come back as a ZIP, because a browser can only save one file at a time.

If you only want one page out of a long document, say so in the page box rather than converting all forty and deleting thirty-nine.

Why the result sometimes looks soft

Three causes, in order of likelihood.

The page was a scan to begin with. Rendering does not add detail that was never captured. If the PDF holds a 100 DPI scan, rendering at 300 DPI gives you a larger blurry image, not a sharper one. Enhance can help with contrast and speckle, but it cannot invent resolution.

You rendered too low and then enlarged. Same problem from the other end. Render at the size you need.

You chose JPG for a text page. The halos read as softness. Convert again as PNG and compare.

Where people actually use this

Putting a certificate or a diagram into a slide deck or a document, where an embedded PDF would be awkward. Making a thumbnail of a report's cover. Getting one chart out of a long PDF without extracting the page. Posting a page where the reader should not need a PDF viewer.

Going back the other way

If you end up with a folder of images and need one document again, Image to PDF puts them back together in the order you set, one image per page. Note that this round trip is lossy: the text became pixels on the way out and does not become text again on the way back. If you need the words back, PDF to Text works on the original, not on the images.

Transparency, and the white you might not get

A PNG can have a transparent background. A JPG cannot: the format has no concept of it.

That matters less than people expect here, because a PDF page nearly always has an opaque white background of its own. Rendering it gives you white pixels, not transparency, in either format.

So if you were hoping to get a logo or a diagram out of a PDF with a transparent background, rendering the page will not do it. What you get is the artwork on a white square. Cutting the background out afterwards is an image-editing job, and it is only clean when the artwork has hard edges.

Colour, and why a print PDF can look different on screen

PDFs made for professional printing sometimes use CMYK colour. The four inks a press lays down. Screens use RGB. The two do not cover the same range of colours, and converting between them shifts some of them.

The most visible cases are deep, saturated colours: a rich navy or a strong red can come out slightly duller after rendering. Nothing has gone wrong; there is simply no exact RGB equivalent of the ink.

If colour accuracy genuinely matters. A brand colour on a certificate, a chart where two shades must stay distinguishable. Check the rendered image against the PDF on the same screen before using it.

A note on file sizes

A rendered page is usually larger than the PDF page it came from, and often much larger. A page of text is a few kilobytes of drawing instructions and a few hundred kilobytes of pixels.

That surprises people converting a PDF to images in order to make it smaller. It goes the other way. If size is the goal, Compress PDF is the tool, and rendering to images is the opposite of what you want.