What "PDF to PNG" Actually Produces
Converting PDF to PNG means rasterizing every page of a PDF inside the browser at a chosen scale and writing each page out as a separate image/png file, so the output is a set of flat PNGs — one per page — that you download individually. Each file represents the visible appearance of the original page: text, vector shapes, embedded images, transparency, fonts, and clipping paths are all painted onto a canvas and then losslessly encoded. The result is a single image per page, not a re-packaged PDF, not a multi-page image, and not an interactive document. Every output is named deterministically from the source filename with a zero-padded page number, so a 12-page report becomes "report-01.png", "report-02.png", and so on through "report-12.png" — sortable in the same order as the original PDF.
Because the rendering happens entirely in the current tab, the source PDF never leaves the browser. No server-side processing, no upload, no account. The trade-off is that what you get is a raster: any text in the PNG cannot be selected, copied, or searched; any link is gone; any form field is gone; and any vector shape is now pixels. For sharing, previews, thumbnails, slides, and design mockups that property is usually fine. For archiving or re-editing, a flat raster is the wrong format and you should keep the original PDF alongside the PNGs.
Where Lossless Page Renders Fit Best
PNG uses lossless compression, which is why page renders saved as PNG stay crisp where JPEG would smear them. Pages with small text, diagrams, screenshots, line art, UI captures, flowcharts, schematics, and signatures all benefit from lossless encoding because any compression artifact becomes a visible blur. A 1-pixel-wide line on a circuit diagram or the dot of an "i" in 9-point body text looks clean in PNG and rough in JPG at the same byte budget. PNG also supports an alpha channel, so transparent regions of a PDF page — for example, a logo placed on a transparent background or an overlapping shape with transparency — survive the conversion instead of being flattened onto a colored background.
Lossless does not mean "identical to the original bytes" or "infinitely detailed". The page is rasterized at the scale you pick, fonts are drawn by the browser's renderer, and the resulting pixels are then encoded with a lossless algorithm. A higher scale produces a denser raster — more pixels per inch — but cannot invent detail that the source PDF never had. A 72 DPI scan saved as PNG will still look like a 72 DPI scan, only larger. The output is faithful to what the page visually shows, not a magical up-res of the source.
Common situations where PDF to PNG is the right tool: extracting a slide as an image for a blog post or social card, capturing a UI mockup that lives inside a PDF spec, attaching a single invoice page to a chat message that does not accept PDFs, sending a diagram to someone who cannot open the original, and producing thumbnails for a catalog. The output is also a clean way to drop a page into a presentation, a design tool, or a knowledge-base article without the recipient needing a PDF reader.
How the Browser Renders a PDF Page into PNG
When you start the conversion, the tool fetches Mozilla's PDF.js and its dedicated worker into the tab — they are not part of the initial page bundle, so the converter itself stays light. PDF.js is the same rendering engine used inside Firefox to display PDFs. For each page, the engine reads the page's content stream — the instructions that combine selectable text, vector geometry, raster images, fonts, transparency, and clipping paths — and computes a viewport at the scale you chose. It then paints the page onto an HTML canvas. Once the canvas holds the complete painted page, the converter calls the canvas's built-in HTMLCanvasElement.toBlob method with the explicit MIME type "image/png" so the browser uses its lossless PNG encoder.
The encoder writes the pixels into a Blob, the Blob is wrapped in an object URL, and that URL becomes the download link for that page. Once you click download, the file is saved with a deterministic name. When you select a new file or change the scale, the previous results, canvases, tasks, and object URLs are released so the tab does not keep dozens of large image buffers in memory. The same worker URL is used across all tools in the PDF image group, which means the worker is cached after the first conversion and the second file you convert loads much faster.
Because the source page may combine vectors, fonts, and transparency, the rendered PNG represents the visible result, not the underlying structure. Selectable text becomes pixel patterns, live links disappear, form fields become static rectangles, and the original compression of any embedded raster image is replaced by PNG's lossless encoding. That is exactly what makes the PNG a faithful visual snapshot and exactly what makes it unusable as a replacement for the source PDF in an editing workflow.
Limits That Can Block the Job
Rendering every page at high resolution can quickly allocate gigabytes of pixel memory per tab, so the converter inspects every planned page viewport before it does any rendering and rejects inputs that exceed its safety limits. Knowing these limits before you start saves a rejected job and a wasted run.
| Limit | Value | Why it exists |
|---|---|---|
| Input file size | 25 MiB | Keeps file reads bounded |
| Page count | 40 | Bounds total work per job |
| Per-side pixels | 12,000 | Caps canvas dimensions per page |
| Per-page megapixels | 40 | Caps pixel memory per page |
| Total megapixels across the job | 100 | Caps aggregate pixel memory |
If your planned scale pushes any page past 12,000 pixels on one side or 40 megapixels, the converter will refuse the job before painting anything. If the input PDF is encrypted, malformed, or otherwise unreadable, you see a visible error instead of a partial output. The tool does not bypass passwords, repair corrupted cross-reference tables, validate signatures, or strip malware — it simply reads the file as given, paints the pages, and writes the PNGs.
Two practical consequences. First, the input must be a PDF you can already open, not a damaged scan wrapped in a PDF container. Second, raising the scale from 1× to 3× multiplies the pixel area of every page by roughly nine, so a 20-page document that fits comfortably at 1× may trip the total-megapixel ceiling at 3×. The rule of thumb: higher scale means larger files and sharper zoom-in behavior, but memory grows with both width and height, not with one of them.
Convert a PDF to PNG Locally
The PDF To PNG tool runs the whole pipeline in your current tab. Use these steps for a clean conversion.
- Pick a PDF no larger than 25 MiB. Encrypted, damaged, and over-limit files are rejected up front, so start with an unprotected, well-formed file you can already open.
- Choose the output scale. A higher value produces larger, denser PNGs and sharper zoom-in behavior; a lower value produces smaller files and is plenty for previews and thumbnails.
- Click Convert to PNG. The tool fetches PDF.js, renders every planned page, runs the lossless PNG encoder, and shows each completed page with its width and height.
- Check each page's dimensions. The displayed numbers come from the actual rendered viewport, so what you see is exactly what you will download.
- Download the PNGs. Each file is named after the source PDF with a zero-padded page number, so the set sorts in the same order as the original.
- If you need a different scale or a different file, change the selection and convert again. Old results are cleared, so the displayed settings never silently disagree with previously generated images.
PNG, JPG, or Long Image — Picking the Right Output
Same source PDF, three different page-as-image tools. Pick by the dominant content of the document and by how the recipient will consume it.
| Output | Compression | Best for | Trade-off |
|---|---|---|---|
| PNG (separate files) | Lossless | Text, diagrams, screenshots, UI captures, anything where crisp edges matter | Files can be large; one PNG per page |
| JPG (separate files) | Lossy | Photo-heavy documents, large reports where smaller files beat perfect edges | JPEG artifacts around text and sharp lines |
| Long Image (single PNG) | Lossless | Mobile-friendly scroll-throughs, comic-style pages, single tall export | One file, not one per page; harder to embed individually |
If the document is a mix, the safest default is to render at a moderate scale as PNG so text stays readable, then drop to JPG only if the resulting file sizes are unmanageable. For an explanation of the stacked variant, see the PDF to Long Image walkthrough. To dial in the scale before you render, the right-scale guide shows the relationship between DPI, viewport, and pixel count.
When a Flat Raster Is the Wrong Choice
The PNG is a faithful visual snapshot, not an editable document. If you need any of the following, keep working with the source PDF instead of relying on the PNG output:
- Selectable, searchable, copy-pasteable text — the PNG contains pixel patterns of letters, not the original glyph instructions.
- Interactive hyperlinks, bookmarks, or a clickable table of contents — annotations are not preserved on a raster page.
- Editable form fields — check boxes, text boxes, and signatures become static rectangles.
- Original vector geometry — shapes become pixels, so the PNG cannot be rescaled cleanly past the chosen scale.
- The original compression of an embedded raster image — PNG's lossless encoding replaces it, which is usually larger but always exact.
For any of those workflows, use the source PDF directly. For sharing a specific page as an image, embedding a page into a design tool, or producing thumbnails, PNG is the right answer and the PDF To PNG tool produces the file without sending the document anywhere.