PDF to PNG

PNG exports keep transparency wherever the PDF page itself paints nothing. The exporter renders onto a fresh canvas and never fills it with white first, so if a page has no background rectangle those pixels come out with an alpha value of zero and PNG stores them that way. In practice most PDFs produced by word processors and print workflows do paint a white background box, and those export as solid white — the transparency you get depends on how the page was authored, not on a setting here. A quick way to check is to open the PNG over a dark background; genuine transparency shows through. If you want a guaranteed white page regardless of authoring, PDF to JPG always fills white before rendering.

PNG files are larger because PNG is lossless: it stores every pixel exactly and has no quality dial to trade detail for size, which is the whole reason this tool has no slider. A 300 DPI page of dense text can easily land in the several-megabyte range, where the same page as JPEG at 90 % would be a fraction of that. The only size lever here is the DPI chip — dropping from 300 to 150 cuts the pixel count to a quarter and shrinks the file roughly in proportion. PNG's compression favours flat colour, so diagrams, charts and screenshots compress well while scanned photographic pages compress badly. If size matters more than fidelity, PDF to JPG or PDF to WebP produce far smaller files.

In PDF to PNG the export button stays disabled until the document has actually parsed. PDF to PNG tracks the state of the PDF rather than the state of the file input, so a file pdf.js cannot open — encrypted, truncated, or not a PDF at all — leaves the button inert and shows "Could not read this PDF — make sure it is a valid file" instead of letting you start a run that would fail halfway. The same guard catches a document that reports zero pages. If you swap files quickly, only the newest pick may write to the screen, so a slow parse of the file you abandoned cannot overwrite the one you want. Clear it with Reset, then try the unlocked or re-exported file.

Exporting a single page is not possible from this tool — PDF to PNG always renders every page in the document and fires one download per page. The preview lets you look at any page, but the selection there is a preview, not an export filter. To get one page as a PNG, isolate it first with Extract PDF pages or Split PDF, then run the resulting one-page file through here; it saves as name.png with no page suffix. That two-step route is also the sane way to handle a 400-page document when you only need the cover, since it avoids firing hundreds of downloads and rendering pages you will throw away immediately.

No — every page comes out as a flat grid of pixels, with no selectable text, no fonts and no vector paths. Rasterising is the point of this tool, and it is why a PNG export is a reasonable way to hand someone a page they should not casually copy-paste or reflow. It is not a security control, though: anyone can run character recognition on the image, so treat it as a convenience rather than as protection. If you need the words rather than the picture, PDF to text pulls the text layer straight out of the document. If you need the embedded photographs rather than a snapshot of the whole page, Extract PDF images is the tool that does that.

There is no account, no page cap and no watermark on a PDF to PNG export. Nothing in the tool counts your usage, because there is nothing server-side to count — the file is read from disk by your browser, rendered by pdf.js on your device and encoded by that same browser's canvas. A very long document is limited only by your own memory: each page is rendered into a full-size canvas before it is encoded, so 300 DPI on a phone is where you will feel it first. Press Reset between documents to release the previews the tool is holding. The one thing that does travel over the network is the pdf.js code chunk itself, fetched the first time you open a document.