To convert a PDF into PNG images, open the PDF To PNG tool in your browser, pick a local file up to 25 MiB, choose an output scale, and click Convert to PNG. Each page is rendered individually as a lossless PNG, with the exact width and height shown before you download. All parsing, rendering, encoding, and download creation happens inside your current browser tab, so the original document never leaves your computer. PNG uses lossless compression, which means the page image keeps every pixel the canvas produced at your chosen scale, with no JPEG-style artifacts around text, edges, or diagrams. The output is a flat raster representation of the visible page, so selectable text becomes image pixels and clickable links no longer respond to clicks. You end up with one zero-padded PNG file per page, named to sort in the same order as the PDF, and every PNG is a true rasterization at the scale you chose rather than a fuzzy screen capture.
The reason most people search for a way to put a PDF to PNG is that screenshots never look right. A screenshot of a PDF page is a screen-resolution rasterization of whatever your monitor is showing, which often means blurry text and washed-out diagrams. PNG is the standard lossless image format on the web, so a properly rendered PNG page can be dropped into a slide deck, pasted into a documentation screenshot, attached to a chat message, or uploaded to a CMS without any visible quality loss compared to the source. If you need a single page from a manual, a clean diagram from a report, or a sharable image of a contract page, converting the PDF directly to PNG gives you a result with the same sharpness as the PDF's own render.
What a PNG keeps (and what gets dropped)
A PDF page is a stack of drawing instructions: vector paths, text runs, embedded raster images, fonts, transparency, and clipping rules. The tool feeds that page to PDF.js, the open-source PDF renderer maintained by Mozilla, and asks it to paint the visible result onto a canvas. The canvas is then encoded with the explicit image/png encoding, which produces a true PNG with lossless compression.
Because the canvas is just a grid of pixels, every editable element in the PDF flattens into the image. Selectable text is no longer selectable, live links no longer navigate, form fields become inert boxes, vector geometry becomes colored pixels, and any metadata or compression of the original embedded images is not preserved. What you keep is a faithful visual snapshot of the page at the scale you chose. Lossless means the PNG encodes every pixel that the renderer produced without throwing information away, but it does not mean the output is identical to the original PDF bytes — those were never a raster format to begin with.
PNG also cannot invent detail that is not in the source. If the PDF contains a low-resolution scan, the rendered PNG reflects that scan's resolution multiplied by your scale factor; it cannot recreate information that was never captured. A higher scale only produces a denser raster representation of whatever is already in the page, following the colors and fonts the browser renderer applies.
Picking the right scale for the page
Scale is the multiplier that turns each PDF point into a fixed number of pixels. A PDF point is exactly 1/72 of an inch, so a standard US Letter page is 612 by 792 PDF points. At scale 1 the output is 612 by 792 pixels, at scale 2 it becomes 1224 by 1584 pixels, and at scale 3 it is 1836 by 2376 pixels. To see exactly how scale changes a page, take the US Letter page and work out scale 2 step by step: multiply each side by 2 (612 × 2 = 1224 pixels wide, 792 × 2 = 1584 pixels tall), then multiply width by height to get the total pixel count (1224 × 1584 = 1,938,816 pixels, or roughly 1.94 megapixels for that one page).
Because pixel count grows with the square of the scale factor, doubling the scale quadruples the pixels for every page, and tripling it multiplies them by nine. File size grows along roughly the same line, which is why a 40-page PDF at scale 3 produces noticeably larger downloads than the same PDF at scale 1.
A practical rule:
- Scale 1 is fine for thumbnails, quick previews, or pages you will not zoom into.
- Scale 2 is the most common sweet spot for slides, documentation, and chat attachments — readable text and clean lines without massive files.
- Scale 3 or higher is justified for pages with very small text, dense UI captures, or images you intend to crop tightly and inspect at native pixel density.
The tool preflights every planned page viewport before encoding and rejects any single page over 12,000 pixels on one side or over 40 megapixels, so very high scales on very large pages can be refused even when the source PDF itself would be accepted.
How to put a PDF to PNG in your browser
- Open the tool and select a local PDF. The file must be 25 MiB or smaller. Encrypted PDFs, damaged files, and documents over the safety limits are rejected with a visible message; nothing is uploaded, so the rejection happens locally in your tab.
- Choose the output scale. Pick the multiplier that matches how you intend to use the images — scale 1 for compact previews, scale 2 for general-purpose sharing, scale 3 or more when you need to zoom or crop tightly. After a scale change, the previous results are cleared so the displayed settings never silently disagree with what was generated.
- Click Convert to PNG. PDF.js and its dedicated worker are fetched on demand, each planned page is rendered through the renderer, and the canvas is encoded explicitly as image/png. The tool shows every completed page with its width and height in pixels.
- Verify the dimensions and download. For each page, confirm that the width and height match what you expect, then download the individual PNG. Output names strip any existing .pdf suffix, replace characters that are unsafe in common desktop filenames, and add zero-padded page numbers so the set sorts in the same order as the PDF.
- Re-run if you change anything. Choosing a new file or a new scale cancels the earlier job. Cancelling, replacing, and unmounting all release page resources, canvases, render tasks, and temporary download URLs, so large image buffers are not retained longer than necessary.
Limits that can stop a conversion
The tool runs entirely in one browser tab, and a tab cannot safely allocate unbounded memory for a single conversion. Before any PNG is encoded, every planned page viewport is checked. A conversion will be rejected if any of the following limits are exceeded:
| Limit | Threshold |
|---|---|
| Input file size | 25 MiB maximum |
| Page count | 40 pages maximum |
| Single page width or height | 12,000 pixels maximum on either side |
| Single page total pixels | 40 megapixels maximum |
| Aggregate planned pixels across all pages | 100 megapixels maximum |
If your PDF trips one of these checks, the conversion stops before any download is created. Common culprits are scanned PDFs at very high DPI (each page is already huge), reports with dozens of pages rendered at scale 3 or higher, or encrypted PDFs that the renderer cannot parse. The tool does not bypass a password, repair corruption, validate signatures, or remove malware; it simply refuses the file and shows the reason.
If the rejection is about scale, dropping one step usually fixes it. If the rejection is about page count or input size, splitting the PDF first with Split PDF or trimming it with Delete PDF Pages lets you process the document in two passes.
PNG, JPG, or a long image — picking the right output
The PDF To PNG tool is one of three image outputs available for a PDF. Each is suited to a different job, and the choice usually comes down to whether you need lossless quality or the smallest file size, and whether the pages should stay as separate files or stack into one image.
| Use case | Best output | Reason |
|---|---|---|
| Pages with text, diagrams, UI captures, line art, or small fonts | PNG (lossless) | No JPEG artifacts around edges; readable at any zoom level |
| Photographic pages where small file size matters more than perfect text | JPG (lossy) | Often smaller files; JPEG artifacts acceptable for photos |
| Long scrolling reference where every page should be in one image | Long image (PNG) | One tall image instead of many separate files |
The underlying renderer is the same in each case — PDF.js paints the visible page onto a canvas — but the encoding and packaging differ. PNG keeps every pixel exactly as rendered, JPG trades some fidelity for smaller files, and the long image variant stitches every page vertically with adjustable spacing. If you are unsure, render one page at your chosen scale in each format and pick the one that looks right at the file size you can live with.
None of these operations modifies the source PDF; the original stays on your computer exactly as you loaded it.