PDF to Images Converter
Convert every page of a PDF into PNG images right in your browser. Choose the output scale and download individual pages or the whole set. 100% client-side — your PDF never leaves your device.
How do you convert a PDF page into an image? A rendering engine reads the page's drawing instructions and paints them onto a raster surface at a chosen resolution. This tool uses pdf.js, the engine behind Firefox's built-in PDF viewer, to draw each page onto a canvas and export it as a PNG. Scale 1 gives 72 pixels per inch, matching the point grid PDF uses internally; scale 4 gives 288.
How to Convert a PDF to Images
-
Load your PDF — Drop a file on the zone or click to browse. The file is read with
FileReaderand parsed by pdf.js in the page — nothing is sent anywhere. - Choose an output scale — The slider runs from 1x to 4x. Each step multiplies the page's point dimensions, so 1x renders an A4 page at about 595 by 842 pixels and 4x at about 2381 by 3368.
- Convert the document — Click Convert to Images. Every page is rendered to its own canvas and exported as a lossless PNG, with the progress bar reporting which page is in flight.
- Review the gallery — Rendered pages appear as a thumbnail grid in document order. Check a page with fine print or a hairline rule to confirm the scale you chose is sharp enough.
- Download what you need — Each tile has its own Download PNG button for a single page, or use Download All to get every page as one ZIP archive built in the browser.
How PDF to Image Conversion Works
A PDF page is a program, not a picture. It holds a sequence of drawing operators: move to this coordinate, set this font, show this string, fill this path with that colour, paint this image stream into that rectangle. Nothing in the file says how many pixels a page is, because a page has no pixels — it has a size in points, and points are a physical unit at 72 to the inch. Converting to an image means executing those instructions against a raster grid and deciding how fine that grid should be.
That decision is exactly what the scale control makes. pdf.js builds a viewport
for each page by multiplying its point dimensions by your scale factor, and the tool sizes a
canvas to match before rendering. Because one point maps to one pixel at scale 1, the scale
factor is effectively a multiplier on 72 DPI. The finished canvas is exported with
toDataURL as a PNG, which is lossless: no compression artefacts appear around
text edges or thin lines, which is the reason PNG rather than JPEG is used for pages of type.
The important trade is that rasterising is one-way. The text on a rendered page is no longer text — it is an arrangement of dark pixels. It cannot be selected, searched, copied, read by a screen reader or reflowed, and returning the image to a PDF later gives you a picture of a document rather than a document. Convert to images when you need a picture of a page; keep the PDF when the content still needs to behave like content.
Scale, Resolution and Output Size
| Scale | Effective resolution | An A4 page becomes about | Suited to |
|---|---|---|---|
| 1x | 72 DPI | 595 × 842 px | Thumbnails, contact sheets, quick previews |
| 2x | 144 DPI | 1190 × 1684 px | Screen use, slides, documentation figures |
| 3x | 216 DPI | 1786 × 2526 px | Readable small print, high-density displays |
| 4x | 288 DPI | 2381 × 3368 px | Print reference and archival captures |
Pixel counts grow with the square of the scale, so a 4x render is roughly sixteen times the data of a 1x render of the same page. Pick the smallest scale that keeps your smallest type legible; going higher costs memory and download size without adding detail the source page never had. A page that is itself a 150 DPI scan gains nothing from a 4x render, because the missing detail is absent from the original.
What Happens to Each Kind of Content
| In the PDF | In the PNG |
|---|---|
| Text with embedded fonts | Pixels — sharp, but no longer selectable or searchable |
| Vector artwork and charts | Rasterised at the chosen scale; re-scaling later softens it |
| Embedded photographs | Resampled to the render grid, up or down |
| Page rotation | Applied — the image comes out the way the page displays |
| Transparency | Composited against the page background |
| Annotations, links, form fields | Interactivity is lost; only their drawn appearance remains |
Long documents at high scale use a lot of memory. Every page is rendered and held in the tab at once, so a 200-page file at 4x can exhaust the browser before it finishes. If conversion stalls or the tab becomes unresponsive, drop to 2x, or split the document with PDF Split and convert the parts separately.
Frequently Asked Questions
Load the PDF, pick a scale, and press Convert to Images. Each page is drawn onto a canvas at the resolution your scale implies and exported as a PNG, which you can then download individually or all at once as a ZIP. There is nothing to install and no account to create.
PNG only. PNG is lossless, so the sharp edges of text and hairline rules survive intact, where JPEG would surround them with compression halos. If you need JPEG for a size-sensitive upload, convert here first and then re-encode the PNGs with an image compression tool.
Scale 1 is 72 DPI, and every step adds another 72, so 2x is 144 DPI and 4x is 288. Use 1x for thumbnails, 2x for anything read on a screen, and 3x or 4x when small print has to stay legible or the image is going to paper. Higher is not automatically better: the render cannot invent detail the source page does not contain.
No. Rendering converts glyphs into pixels, so the words become part of the picture. You cannot select, copy or search them, and assistive technology has nothing to read. Keep the PDF alongside the images if the text still matters, or run the images through OCR to rebuild a text layer.
No. The file is read by your browser and rendered by pdf.js inside this page, so the document never travels over the network. Even the ZIP is assembled locally rather than by a service. Closing the tab discards everything, which makes the tool safe for confidential documents.
Not directly. A document that needs a password to open cannot be parsed without it, so conversion fails rather than producing blank pages. Open the file in a reader with the password, save an unprotected copy, and convert that copy instead.
Every page is rendered and kept in the tab at the same time, so total memory grows with page count multiplied by the square of the scale. A long document at 4x is the usual culprit. Drop to 2x, close other heavy tabs, or split the PDF into shorter files and convert them one at a time.
A single page download uses your original filename with the page number appended, so report.pdf page 3 becomes report-page-3.png. The ZIP takes the same base name with -images.zip, and the pages inside it are numbered page-1.png upwards in document order.
Use Cases
Slides from a Report
A presenter drops rendered pages straight into a slide deck, so a chart from a PDF appears exactly as designed instead of being rebuilt by hand.
Web and Social Previews
A marketer publishes the first page of a whitepaper as an image on a landing page, because visitors will not click through to a PDF to see what it looks like.
Attaching Pages to a Ticket
A support agent pastes the single page showing an error into a ticket, giving the engineer the evidence without circulating the whole customer document.
OCR Input
A researcher renders a scanned book at 3x to feed an OCR engine, since recognition accuracy depends heavily on the resolution it is given.
Design and Print Proofing
A designer exports every page at 4x to check bleed and small type at close zoom before a layout goes to the printer.