PDF to PNG Without Uploading Anything

When you drop a file onto the upload area, your browser gives the page a reference to it — not the contents, just a handle. Nothing has been read at that point, and certainly nothing sent.

When you press the action button, the page reads the bytes of that file into memory using the browser's File API. This is a local disk read, the same kind any application on your device performs, and it never touches the network.

The processing runs against those bytes inside the tab. Depending on the tool, that means parsing the PDF structure with pdf-lib or rendering pages with pdf.js — both are JavaScript libraries that were downloaded once as part of the page and run entirely on your processor.

The result is assembled in memory as a Blob and given a temporary local address that only your browser knows about. Pressing download copies it from memory to your disk. At no stage in this sequence does your document, or any part of it, travel over the network.

Pages are rendered with pdf.js onto an HTML canvas at the scale you chose, where a scale of 1 equals the PDF's native 72 dpi. The canvas is pre-filled with white before rendering so that transparent regions produce white rather than black or undefined pixels.

The canvas is then encoded to PNG, which stores the pixel data losslessly. Each canvas is discarded immediately after encoding so that memory does not accumulate across a long document.

Your files are not uploaded. When you add a PDF file, your browser reads it from your device into the memory of the tab you are looking at, and the pdf to png operation runs there using your own processor. Nothing is transmitted to any server at any point.

That means there is no file for anyone to store, no retention policy to trust, and no deletion schedule to take on faith. The document exists only in the memory of an open browser tab, and it is released the moment you close it, reload the page, or press start over.

The site uses standard anonymous analytics to count page views and how often each tool is used. Those events record which tool ran and whether it succeeded — never a file name, never file contents, and never anything that could identify a document or the person processing it.

No account is required, so no personal information is collected. There is no profile, no history and nothing tied to an identity, because no identity was ever created.

The strongest security property this tool has is structural: your file never travels anywhere, so there is no transmission to intercept and no server-side copy to breach. This is not a policy that could change — it is a consequence of where the code runs.

You can verify it in about thirty seconds. Open your browser's developer tools with F12, select the Network tab, and use the tool. You will see the page's scripts load — including the PDF libraries, which are fetched on demand the first time a tool runs — and then nothing further. No request carrying your document is ever made.

For a stronger test, disconnect from the network once the page has loaded. The tool will keep working exactly as before, which is only possible because nothing is being sent.

Uploaded files are validated in the browser before anything runs: the extension must match what the tool accepts, the file must not be empty, and it must be within the size limit. Malformed documents produce a clear error and a retry option rather than a silent failure.

Being clear about limits is more useful than a feature list that quietly omits them. Output is always opaque with a white background, produced whole-page at a time, and text in the resulting images is no longer selectable.

If you need capabilities beyond that — redaction, PDF/A conformance, OCR, or scripted batch processing across thousands of documents — dedicated desktop software genuinely earns its licence fee, and this is not trying to replace it. For the specific job of producing a PNG images, everything you need is on this page.