Export PDF pages as images at the resolution you need

Turning a PDF page into a picture sounds trivial until the result is either unreadably fuzzy or a 40 MB file. Both outcomes come from the same two settings, and both are easy to get right once you know what they control.

Choose the format by what is on the page

The page-to-image tool can write JPG or PNG. They are not interchangeable, and the correct choice depends entirely on the page content.

JPG uses lossy compression tuned for photographs. It handles smooth gradients and natural detail extremely well and produces small files. What it handles badly is hard edges: the boundary between black text and white paper is exactly the pattern that produces visible ringing artefacts. A page of body text exported as a mid-quality JPG looks slightly dirty, and the dirt gets worse every time it is re-saved.

PNG uses lossless compression. Every pixel survives exactly, so text stays sharp, screenshots stay clean, and diagrams keep their crisp lines. The cost is file size, which for a photographic page can be several times larger than the equivalent JPG.

The practical rule: if the page is mostly a photograph, use JPG. If it contains text, tables, charts, logos, or line drawings — which is most PDF pages — use PNG.

Resolution is the quality setting

A PDF page has no inherent pixel dimensions. It is defined in points, and the renderer decides how many pixels to produce per inch. That number, not the format, is what determines whether the result looks good.

Target	Resolution	Why
Web page or slide	96–150 dpi	Matches typical screen density without waste
Detailed on-screen review	200 dpi	Small type stays legible when zoomed
Printing	300 dpi	The standard threshold for photographic print quality
Archival or reprocessing	400–600 dpi	Only when the image will be re-scaled or recognised later

Rendering at 600 dpi "to be safe" quadruples the pixel count of a 300 dpi export for no visible benefit on paper, and it is the single most common reason an image export becomes unmanageably large.

Export only the pages you need

A 200-page report rendered in full produces 200 images and a very long wait. Most of the time the actual requirement is one figure on page 47.

Select the specific pages before exporting. If the range you need is contiguous and you would rather work with a smaller document throughout, extract it first with the split tool and render from that. Both approaches avoid the render-everything-then-delete cycle.

Understand what you lose

Exporting a page as an image discards the structure that made it a PDF:

• Text becomes pixels. The result cannot be searched, selected, copied, or read aloud by a screen reader.
• Vector artwork becomes fixed. Logos and charts that were resolution independent are now locked to the resolution you chose, and enlarging them reveals the pixels.
• Links, bookmarks, and form fields disappear. There is nowhere for them to live in an image.
• Accessibility drops sharply. An image of text is inaccessible unless recognition is applied afterwards.

So treat the export as a derived artefact, not a replacement. Keep the original PDF. If someone later needs to search the content, you still can.

When an image export is the right answer

Despite those losses, there are cases where images are genuinely the correct output:

• Placing a page into a slide deck, a document, or a web page.
• Sending a preview to someone who should look but not extract.
• Attaching a figure to a support ticket or a chat message.
• Producing a thumbnail or a cover image.
• Feeding a page into image-based tooling that cannot parse PDF.

If the resulting images are larger than you want, reduce the render resolution rather than compressing hard afterwards — resampling at export time produces a cleaner result than crushing a high-resolution JPG. And if the goal was simply a smaller document rather than pictures, the compression tool is a better fit than converting the whole thing to images.