Skip to content
Lizely

PDF To PNG

Render each PDF page as a lossless PNG locally, with exact output dimensions and no upload.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Choose a PDF no larger than 25 MiB; encrypted, damaged, and over-limit files are rejected.
  2. 2.Choose the output scale and click Convert to PNG to render every planned page.
  3. 3.Check each page's dimensions, then download the individual zero-padded PNG files.

About PDF To PNG

PDF to PNG converts every visible page in one PDF into a separate PNG image without sending the document to Lizely. Select a local file, choose a rendering scale, and start the job. The tool displays each completed page with its width and height and provides an individual download. All parsing, rendering, encoding, and object URL creation happen in the current browser tab.

This is a page renderer, not an embedded-image extractor. PDF pages may combine selectable text, vector shapes, raster images, clipping paths, fonts, and transparency. PDF.js interprets those instructions and paints the complete page onto a canvas. The PNG therefore represents the visible result. It does not keep editable text, live links, form fields, vector geometry, layers, metadata, or the original compression of images stored inside the PDF.

PNG uses lossless compression, which is useful for diagrams, user-interface captures, line art, documents with small text, and pages that would show JPEG artifacts. Lossless does not mean the output is identical to the source bytes or infinitely detailed. The page is rasterized at the chosen scale, fonts and colors follow the browser renderer, and a higher scale only creates a denser raster representation. It cannot recreate information missing from a low-resolution scan.

Scale changes the pixel dimensions of every page. A larger value can improve readability when zooming into the resulting image, but memory and file size grow quickly because pixel area grows with both width and height. Before creating downloads, the converter inspects every planned page viewport. It rejects any page above 12,000 pixels on one side or 40 megapixels, any PDF above 40 pages, any input above 25 MiB, and any job whose planned pages exceed 100 megapixels in total.

The converter uses explicit image/png encoding. Output names remove an existing .pdf suffix, replace characters that are unsafe in common desktop filenames, and add zero-padded page numbers. This makes a set of downloads sort in the same order as the PDF. Selecting another file or changing scale clears old results, so the displayed settings never silently disagree with previously generated images.

PDF.js and its dedicated worker are fetched only when conversion begins. They are not loaded into the initial page bundle, and all tools in this PDF image group use the same worker URL for browser caching. Starting again cancels the earlier job. Render tasks, page resources, canvases, and temporary download URLs are cleaned up during cancellation, replacement, and unmounting to avoid retaining large image buffers longer than necessary.

Encrypted PDFs, malformed cross-reference tables, unsupported content, or documents that exceed a safety limit return a visible error. The tool does not bypass a password, repair corruption, validate signatures, remove malware, or make claims about the source document's trustworthiness. Keep the original file and inspect important output before relying on it.

Choose PNG when you need a lossless page image or crisp text and graphics. Choose PDF to JPG when smaller lossy images are preferred. Choose PDF to Long Image when every page should be stacked into one tall PNG. None of these operations modifies the source PDF.

Methodology & sources

Validate and load one bounded PDF after explicit user action, preflight every scaled page viewport before encoding, render the visible page through PDF.js, encode explicitly as image/png, name outputs deterministically, and cancel and release all page, canvas, task, and object URL resources when work is replaced.

Frequently asked questions

Are the PNG images created on a server?
No. The PDF worker, canvas rendering, PNG encoding, and downloads all run in your browser.
Is PNG always better than JPG?
No. PNG is lossless and often better for text or diagrams, while JPG can be smaller for photographic pages.
Will links and selectable text remain interactive?
No. Each output is a flat raster image of the visible page.
Why can a large PDF be rejected?
Page, dimension, file-size, and aggregate-pixel limits prevent one tab from allocating unbounded memory.

Related tools

PDF Tools guides

View all