Pdf to images

This PDF to Images tool does two distinct jobs. It can render each page of a PDF as a picture, letting you choose PNG or JPG, a render scale from 0.5x to 4x, which maps to 36 to 288 DPI, and a JPG quality level. It can also scan the document for images that were embedded when the PDF was created and pull those out at their original pixel dimensions. Results appear as a grid of thumbnails you can download individually, or all at once as a ZIP archive. It suits anyone who needs a slide as a picture for a presentation, a scanned page to attach to a form, or the photographs from a brochure without asking the designer for the source files. Files up to 100 MB are supported, and rendering is done in the browser with PDF.js, so the document is never uploaded.

Page rendering draws the whole page. PDF.js opens the document, and for each page the tool requests a viewport at your chosen scale, renders the page onto an HTML canvas, then reads the canvas back as a PNG or JPG data URL. The output is a picture of everything on the page, flattened into pixels.

Scale is a multiplier applied to the PDF's native 72 points per inch, which is why the interface shows the resulting DPI beside it. A scale of 1 gives 72 DPI, 2 gives 144, 3 gives 216 and the maximum of 4 gives 288. Pixel dimensions are the page size in points times the scale. When JPG is selected, a quality slider controls the compression level; PNG is lossless and ignores it.

Image extraction works differently. Instead of drawing the page, the tool walks its resources to find embedded image objects, normalises the pixel data to RGBA and exports it from a canvas. You get the picture at the resolution it was stored at, without surrounding text. If the PDF holds no embedded images, the tool reports that none were found.

Downloading everything at once loads JSZip on demand and builds an archive.

A PDF measures pages in points, where one point is one seventy-second of an inch. A4 is 210 by 297 millimetres, which comes out as 595 by 842 points.

Render that page at a scale of 1 and you get 595 by 842 pixels at 72 DPI, which is too coarse for anything but a thumbnail. At the default-friendly scale of 2 the maths is 595 times 2 by 842 times 2, giving 1190 by 1684 pixels at 144 DPI. That suits web use and most screens, at roughly two megapixels.

Push to a scale of 3 and you get 1785 by 2526 pixels at 216 DPI, which is around 4.5 megapixels and suitable for printing at a modest size. The maximum scale of 4 gives 2380 by 3368 pixels at 288 DPI, just over 8 megapixels.

File size grows roughly with the pixel count, so quadrupling the pixels between 2x and 4x quadruples the output too. For a text-heavy page saved as PNG, a 144 DPI render might be a few hundred kilobytes while the same page at 288 DPI runs into several megabytes. Render a single page first to check before processing a long document.

Choose PNG when the page is mostly text, line art, tables or screenshots, because lossless compression keeps edges crisp and PNG supports transparency. Choose JPG when the page is dominated by photographs, where its compression produces far smaller files, and lower the quality slider if size matters more than fine detail. Never use JPG for small text at low quality: the artefacts cluster around letterforms and make the result harder to read than the original.

Decide which of the two modes you actually need. If you want the photographs from a brochure at their original resolution, use image extraction, because rendering the page would give you a flattened picture including the text. If you want the page as it appears, including layout and typography, render the page.

A rendered page is pixels, so the text in it is no longer selectable or searchable. Anyone needing to copy text from the result would have to run optical character recognition afterwards, which is a good reason to keep the original PDF alongside the images.

Two final limits: the 100 MB ceiling exists because the document is processed in memory, and encrypted or password-protected PDFs cannot be opened for rendering.