JPG to PDF
JPG to PDF turns images into a PDF in your browser, one page each. JPEG and PNG data is embedded into the file byte for byte rather than re-encoded, so the images in the PDF are pixel-identical to the ones you started with — which is not true of tools that render each image to a canvas first.
Drop images here
or drop anywhere on this page · Choose files · 100 MB
How does JPG to PDF work?
A PDF can carry JPEG and PNG data directly. The image bytes are written into the file unchanged and the page simply references them — which means the picture in the PDF is the picture you started with, not a re-compressed approximation of it.
Embedding versus re-encoding
The lazy implementation draws each image onto a canvas and encodes the canvas as a new JPEG. That works, and it costs a generation: JPEG is lossy, so decoding and re-encoding introduces artefacts even at high quality, and a photograph that has been through that twice starts to show it around edges and text.
Here JPEG and PNG go in as-is. WebP, AVIF and HEIC cannot — the PDF format has no filter for them — so those are decoded and re-encoded as JPEG, and the tool tells you which files that happened to rather than leaving you to notice.
Fit to page, or page to image
Fit to page puts each image on a standard page — A4, Letter, whatever you choose — scaled to fit inside the margins and centred. It contains rather than covers: the whole image is visible and there are bands of white where the aspect ratios differ. Cropping someone's photograph to fill a page is a decision they did not ask for.
Page per image makes each page exactly the size of its image, with no margins. This is the right answer for scanned documents, screenshots and anything where white bands would look like a mistake — and it produces a document whose pages are different sizes, which is perfectly legal and occasionally surprising.
Margins are in points
PDF measures in points: 72 to the inch. The default 36 points is half an inch, which is a conventional document margin. Zero is fine for a photo book.
Order is the order you set
Images become pages top to bottom, and the arrows reorder them. This matters more here than almost anywhere, because a file picker returns files in the operating system's order — which is alphabetical, so IMG_10 lands before IMG_2.
Input
scan-1.jpg (2480 × 3508) scan-2.jpg (2480 × 3508) fit: page (A4), margin 36 pt
Output
images.pdf — 2 pages JPEG data embedded byte for byte, scaled to contain, centred
What options and edge cases does JPG to PDF support?
| Parameter | Type | Default | Behaviour & edge cases |
|---|---|---|---|
| JPEG | embedded | lossless | The image bytes go into the PDF unchanged. No re-encoding, so no second generation of JPEG artefacts. |
| PNG | embedded | lossless | Also carried verbatim, including transparency where the page shows through. |
| WebP, AVIF, HEIC | re-encoded | to JPEG at 0.92 | A PDF has no filter for these. They are decoded and re-encoded, which costs a generation of quality — and the tool names the files it happened to. |
| Fit to page | mode | default | Scaled to fit inside the margins and centred on a standard page. Contains rather than covers, so nothing is cropped. |
| Page per image | mode | — | Each page exactly the size of its image, no margins. Right for scans and screenshots; produces pages of differing sizes. |
| Page size | A4 / Letter / Legal / A3 / A5 | A4 | Only applies in fit-to-page mode. |
| Margin | points | 36 | 72 points to the inch, so 36 is half an inch. Zero for edge-to-edge. |
| Order | list order | as dropped | Reorderable with the arrows. A file picker sorts alphabetically, which puts IMG_10 before IMG_2. |
| Transparency | white behind | when re-encoding | A transparent WebP encoded as JPEG would come out black where the transparency was, so white is painted first. |
Frequently asked questions
Does converting to PDF reduce my image quality?
Not for JPEG or PNG — their data is written into the PDF byte for byte, so the image in the document is pixel-identical to the one you started with. WebP, AVIF and HEIC have no PDF equivalent and are re-encoded as JPEG, which does cost one generation; the tool lists which files that applied to rather than leaving you to spot it later.
Why are there white bands around my photos?
Because fit-to-page contains the image rather than cropping it: the whole picture is visible, and where its aspect ratio differs from the page there is white. The alternative — filling the page — means cutting off the edges of someone's photograph, which is not a decision a converter should make quietly. Switch to page-per-image if you want no bands and no crop.
Why is my PDF so much larger than the images?
It should not be by much — the image data is the same bytes plus a small amount of PDF structure. If it is dramatically larger, check whether your images are WebP or HEIC: those get re-encoded as JPEG at quality 0.92, which for a heavily compressed source can be bigger than the original. Converting them to JPEG yourself first, at whatever quality you want, gives you control over that trade.
Can I put several images on one page?
No — one image per page, deliberately. Laying out multiple images per page is a design decision with many reasonable answers (grid, rows, captions, spacing) and no obvious default, and a tool that picks one for you gets it wrong most of the time. For a contact sheet, a word processor or a layout tool is the right instrument.
Why did my pages come out in the wrong order?
The file picker returned them that way. Operating systems sort file names alphabetically as text, so IMG_10.jpg comes before IMG_2.jpg — nine files in, the order goes wrong and stays wrong. The arrows in the file list reorder them; the PDF follows the list top to bottom.
Are my images uploaded?
No. They are read, embedded and written into a PDF in this tab. The page's Content-Security-Policy sets connect-src 'self', so the browser itself blocks any request to another origin — which is worth knowing given that the images people convert to PDF are usually scans of documents, receipts and identity papers.