How to convert PDF to PNG
- Drop your PDF onto the box above, or press Browse files to select it.
- Choose the render scale. 2× suits screens; go higher only if the images will be printed.
- Optionally list the pages you need, to avoid rendering a long document you do not want.
- Press Convert to PNG and wait for the pages to render.
- Download the images one by one, or take them all as a single ZIP archive.
Why PNG for pages
- Completely lossless, so there is no shimmer or halo around text and line work.
- Often produces smaller files than JPEG for pages of flat colour and type.
- Renders at up to 5× for print-ready resolution.
- Exports selected pages only, which keeps long documents manageable.
- Shows the pixel dimensions of each rendered page so you can check before downloading.
- Runs on the same engine your browser uses to display PDFs, so nothing looks different.
The case for lossless page images
Rendering a page to an image is a compromise no matter which format you pick, the text stops being text. What you can control is whether the picture itself is faithful. PNG stores exactly what was rendered, so a black letter on a white background stays a black letter on a white background, with no grey fringing and no blocky patches in the whitespace.
JPEG cannot make that promise. Its compression works by simplifying high-frequency detail, and the boundary between black text and white paper is the highest-frequency detail there is. That is why a JPEG of a text page always has a faint haze around the letters, visible the moment you zoom in.
When PNG is clearly right
- Pages of body text, tables or code, where every edge is high contrast.
- Technical drawings, wireframes, org charts and schematics.
- Logos and brand artwork that will be reused elsewhere.
- Anything going into documentation, where readers zoom in.
- Screenshots of a PDF that must match the original exactly for a bug report or an audit.
The exception is a page dominated by photographs. There PNG has to record every subtly different pixel losslessly and the file balloons, while JPEG handles the same content beautifully. For those pages, PDF to JPG is the better tool.
Picking a scale without exhausting the browser
Scale multiplies both dimensions, so the pixel count, and the memory required, grows with its square. Rendering A4 at 2× produces about 1190 × 1684 pixels, which is comfortable. At 5× the same page is roughly 2975 × 4210, some twenty-five times the data of a 1× render.
A thirty-page document at 5× is therefore a serious job, and everything runs on the main thread. If you need high-resolution output from a long document, work in batches using the page range field rather than asking for all of it at once. Render two pages first and check they look right before committing.
Making the files smaller afterwards
Lossless output is not always small output. A rendered page at 4× can easily exceed five megabytes. Two things help without touching the format: reducing the scale, which is by far the biggest lever, and running the results through the PNG compressor, which reduces the colour palette. Page renders respond unusually well to palette reduction, because a text page genuinely contains very few distinct colours.
What is lost, and what is not
The visual result is exact; everything else is gone. No selectable text, no working links, no form fields, no bookmarks. If you want those, do not rasterise at all, use the text extractor for the words, or the page extractor to keep a section as a proper PDF.
Rendering happens entirely inside your browser, so the document is never uploaded and no server holds a copy. Rebuilding a PDF from the images afterwards is handled by PNG to PDF.