JPG to PDF in Your Browser

Browsers stopped being document viewers a long time ago. The File API lets a page read local files with your permission. Canvas and WebAssembly give it real rendering and computation. Blob URLs let it construct a file in memory and hand it back as a download. Together those are everything a PDF tool needs.

The libraries doing the work are the same ones desktop and server tools rely on. pdf.js is the renderer built into Firefox, and it is what draws pages here. pdf-lib handles reading and writing PDF structure. Neither is a cut-down browser substitute — they are the real implementations, running locally.

For locked-down machines this is often the deciding factor. A managed work laptop that blocks installers will still open a web page, so a browser-based tool is frequently the only route to getting the job done without raising an IT ticket.

Each image is read as bytes and embedded into a new PDF document with pdf-lib, using the JPEG or PNG embedder as appropriate. If the first decoder rejects the file, the other one is tried before reporting an error, which handles files whose extension does not match their real format.

In A4 mode the tool works out the largest scale at which the image fits inside the page minus your margins, then centres it. When orientation is set to follow the image, a picture wider than it is tall gets a landscape page. In match mode the page is created at the image's own pixel dimensions and the image is drawn edge to edge.

Your files are not uploaded. When you add a JPG or PNG file, your browser reads it from your device into the memory of the tab you are looking at, and the jpg to pdf 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. One image per page, JPG and PNG only, with no cropping, rotation or multi-image page layouts.

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