Convert JPG to PDF

The photo that arrives lying on its side

Almost every complaint about this category of tool is the same complaint. You feed in twenty holiday shots, you get back a document where half of them are on their side, and there is no setting anywhere that seems to be responsible. It is not a bug in one particular website. It is a gap between two file formats, and it catches nearly everyone who writes one of these converters without knowing to look for it.

Here is what happens. A phone camera does not turn the sensor when you turn the phone. It always records the same landscape frame, and then writes a tiny note in the file's metadata — the EXIF orientation tag — saying which way up the result should be shown. Your camera roll reads that note. So does the picture viewer on your laptop, and so does every web browser. A PDF has no equivalent note, so if a converter copies your photo across and never checks, it hands the reader a sideways frame with nothing to correct it by. Worse, the page it was measured for was the wrong shape, so the picture is squashed as well as turned.

This page reads the tag, works out the shape the photo should be, and then puts the quarter turn into the drawing instruction that places it on the page. That last part is the trick worth knowing about: the turn costs nothing, because a document already draws every picture through a transformation, and giving that transformation a rotation is free. The alternative — turning the pixels themselves and saving them again — is what most tools do, and it quietly costs you image quality on exactly the photos that needed help.

What a good JPG to PDF converter leaves alone

A JPEG is already a compressed picture, and a document can hold that compressed data directly. Nothing has to be unpacked, redrawn or squeezed again. That is the single most useful property of this particular conversion, and it is worth protecting: every time a JPEG is saved a second time it loses a little more, and the loss is cumulative and never comes back. Photographs of text and diagrams show it first, as soft fringing around edges that used to be crisp.

So the rule here is that your photo goes in exactly as it already is. There is no quality slider on this page, and its absence is the point rather than an omission — a slider would imply we were re-compressing, and we are not. Files in formats a document cannot carry directly, such as WebP or GIF, are the one exception; those get rebuilt once, and the receipt names them so a silent change never happens behind your back.

A pleasant consequence is that the finished size stops being a mystery. Add up the photos, add a few kilobytes of scaffolding for each page, and that is your answer. The estimate appears before you press anything, and the receipt afterwards shows what it actually came to, so you can see how close the arithmetic landed. If the result is larger than you want, the honest fix is to make the photos smaller first, which is a different job with its own page: compress an image to an exact size.

Order is the whole job, not a detail

One picture in, one picture out, is barely a conversion. The reason people reach for this is a stack: receipts for an expense claim, a passport and a boarding pass, the pages of a form photographed one after another because there was no scanner in the house. Get the sequence wrong and the document is useless, however good the pictures are.

The list on the left is therefore the main control, not a preview. Rows carry a handle you can drag with a mouse or press and hold on a touchscreen, and beside every row sit plain arrows and a remove button that work with a single tap. Files arrive in the order your browser hands them over, which for camera files is usually chronological, so most stacks need no rearranging at all. Reordering never re-reads anything from disk, and neither does changing the page size, so experimenting is free.

Choosing a page, and what the choice means

Letter is the default because most people reading this are printing on Letter. A4 and Legal are there, and so is a fourth option that behaves differently: Fit each photo makes the page exactly the shape of the picture, with no empty margin at the sides of a wide shot. That mode is where resolution starts to matter, because a pixel has no physical size of its own — it only acquires one once you say how tightly the pixels sit. At 300 per inch a four-thousand-pixel photo is a page thirteen inches across; at 96 it is nearly three and a half feet. On a fixed page size the question never arises, which is why the setting only appears in the mode where it changes something.

What this page deliberately does not do

It will not make the text in your photographs searchable. Recognizing characters in a picture is optical character recognition, a genuinely different problem, and a converter that quietly did a mediocre job of it would be worse than one that does not pretend. It will not shrink your photos on the way through, for the reasons above. It will not merge in an existing PDF. And it will not go the other way: pulling pictures back out of a document needs a renderer instead of a writer, so that lives atPDF to JPG. If your material is screenshots or logos rather than photographs — anything that might have a transparent background — PNG to PDF is the page built for that, with the background handling this one has no use for.

One more thing it will not do: refuse you. A very large stack earns a plain warning about how much memory the job is going to want, and then runs regardless, because it is your hardware and your decision. Photos it cannot identify are named and set aside while the rest continue, so a mixed selection never yields a document with pages silently missing.

Your photos stay on your machine

There is no server involved in this conversion. The code that assembles the document is running in the page you are looking at, working on data your own browser read from your own disk, and the download link points at something that has never existed anywhere else. That is a different promise from a service that deletes your files after an hour, and a stronger one, because a file that was never sent cannot be kept.

It is also a promise you can check rather than believe. Open the developer tools, watch the network activity, and run a conversion: you will see the page fetch its own code and nothing else. If you would like the longer version of how to do that on any site, not just this one, we wrote it up in how to check that a site is not uploading your files.