PDF to JPG on Mac

Finished files land in your Downloads folder, or wherever you have pointed your browser. In Safari you can also hold the download and choose Save As if you would rather file it directly. Everything happens on your Mac — nothing is sent to iCloud or anywhere else.

The tool itself behaves identically regardless of what you are running it on. The same options, the same validation, the same progress reporting and the same output — a file produced on a Mac is byte-for-byte equivalent to one produced anywhere else, because the same code does the work in both cases.

That consistency is worth something practical. Start a job on a Mac and finish it on a different device, or hand the page to a colleague on another platform, and neither of you has to learn a different interface or account for a difference in behaviour.

Each page is rendered by pdf.js — the same rendering engine that displays PDFs inside Firefox — onto an HTML canvas at the scale you selected. A scale of 1 corresponds to 72 dpi, which is the PDF's native point resolution; a scale of 4 gives 288 dpi.

Before the page is drawn, the canvas is filled with white so that transparent areas do not become black in the output. The canvas is then encoded to JPEG at your chosen quality and turned into a downloadable file. Canvases are released as soon as each page is encoded, which keeps memory in check on documents with many pages.

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 jpg 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. Images are produced page by page with no cropping or region selection, and text in the resulting JPGs is no longer selectable or searchable.

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 JPG images, everything you need is on this page.