Pick several photographs or scans and get one document back, with the pages in the order you arrange them. JPEGs are embedded exactly as they are, so nothing is recompressed on the way in.
Runs in your browser. Nothing is uploaded.
A PDF page can hold an image as an object, and for JPEG that object can be the original compressed data verbatim. This takes advantage of that: a JPEG you add is copied into the document byte for byte, with a page created at the image's own pixel dimensions and the picture drawn to fill it. Nothing is decoded, resampled or re-encoded, which is why the operation is close to instant and why a photograph looks exactly as it did before. Three 2550x3300 JPEGs totalling 3,549,756 bytes produced a 3,551,383 byte PDF, a difference of about 1,600 bytes for the document structure wrapped around them.
The consequence is that a PDF of photographs is as heavy as the photographs. There is no compression step to hope for, so a folder of twenty phone pictures makes a document of roughly twenty phone pictures. If that is too large to send, the answer is to make the images smaller before they go in rather than to look for a setting here. PNG behaves slightly differently, since PNG data is also embedded directly, and formats a browser has to convert first are passed through a canvas and written as JPEG.
Choose images
The same questions a security review would ask, answered plainly.
The list is the page order, so you arrange it here rather than renaming files into a sequence first. Remove anything that should not be in the document without starting again.
JPEG data is embedded as it stands, so there is no second round of lossy compression and no visible softening. A scan goes in and comes out at exactly the same quality.
JPEG, PNG and anything else your browser can decode can go into the same PDF. Each page is sized to its own image rather than forced onto a fixed paper size.
Three full-page scans became a document in 38 milliseconds, because copying compressed data is cheap. There is no upload to sit through at either end.
There is no upload step and no server to receive one. The page loads once, then all work on your PDFs happens in local JavaScript.
No daily limits, no per-file ceilings imposed by a server tier, no watermarks, and no account. The practical limit is your own device's memory.
What the document weighs, and what to do when that is too much.
The common case: photographs of paperwork that need to travel together.
Input
3 JPEGs at 2550x3300, 3,549,756 bytes total
Output
3-page PDF, 3,551,383 bytes, 38 ms
The document is 1,627 bytes heavier than the pictures that went into it, which is the page tree and cross-reference table. Nothing was recompressed, so each page is pixel-identical to the JPEG it came from.
What to do when the result is too large to send.
Straight conversion
3,549,756 bytes of images, 3,551,383 byte PDF
Images compressed first
compress each image, then convert
Because the images are embedded rather than re-encoded, the only way to reduce the PDF is to reduce them. Running each photograph through the compressor at quality 80 first typically halves the document, and this page will then embed the smaller versions unchanged.
Real files, real numbers, and the machine they were run on.
| Scenario | Input | Output | Time | Notes |
|---|---|---|---|---|
| three 2550x3300 JPEGs into one document | 3,549,756 bytes | 3,551,383 bytes | 38 ms | 1,627 bytes of PDF structure, no recompression |
How this was measured: Measured by driving this page in headless Chrome 152 on an Apple M4 Pro running macOS 15.5, on 2026-09-17. The fixture is handed to the page's own file input, the page's own button is pressed, and the figure recorded is the size of the file the page produces. Timings come from a warm page on a fast machine with no network involved, so treat them as a floor rather than a typical result.
Photograph each page, add them all here, drag them into reading order and create the document. Take the photographs square-on in even light; this does not deskew or crop, so the pages arrive exactly as shot.
Compress the images before adding them. Nothing on this page re-encodes them, so the document size is set entirely by what you put in. Quality 80 on each photograph usually halves the result without a visible difference.
Add them all in one selection, check the order in the list, and build. This is the usual fix for a scanner that saves each sheet individually instead of producing one document.
Drag the rows. The order in the list is the order in the document, and filenames are ignored, so there is no need to rename anything into a numbering scheme first.
Signed forms, receipts and identity documents are usually captured as separate pictures and wanted as one file. Doing it locally keeps the originals off any service.
A month of photographed receipts becomes one submission. There is no per-file charge or count limit, so a large claim is no harder than a small one.
Portals that accept a single PDF force photographs of certificates and transcripts into one document, in a specific order that matters to whoever reviews it.
Site photographs are far easier to circulate as a paginated document than as a folder, and they keep their original resolution for anyone who needs to look closely.
Pictures of pages or a whiteboard become something you can page through and annotate rather than a camera roll nobody will scroll.
The page keeps working with the network off once loaded, so a submission can be prepared while travelling and sent on arrival.
It assembles pages. It is not a scanner app.
There is no compression step, by design, because re-encoding would degrade photographs that have already been through a lossy encoder once. Reduce the images first if the document needs to be smaller.
This is not a document scanner. A photograph taken at an angle, with a desk visible around the page, becomes a PDF page showing exactly that. Crop and straighten before adding them.
Each page takes the pixel dimensions of its own picture, so a document built from photographs of different sizes has pages of different sizes. That prints unevenly unless your images are consistent.
A photograph of a page is pixels. The document cannot be searched or have text copied out of it, and there is no character recognition here to change that.
No. The images are read from your device, assembled into a document in this tab and handed to your downloads. Photographs of identity documents and paperwork are exactly the files worth being careful with, and the simplest check is to disconnect from the network before building one: it still works.
No. JPEG data is embedded into the document exactly as it is, with no decode and no second encode, so each page is pixel-identical to the file you added. That is also why the document is not smaller than its images.
Because it essentially is those pictures, in a container. Three JPEGs totalling 3,549,756 bytes produced a 3,551,383 byte document. The extra 1,627 bytes are the page structure. Nothing is compressed on the way in.
Drag rows in the list before creating the document. It reads top to bottom, and the filenames play no part, so photographs numbered awkwardly by a camera can still be put in the right sequence without renaming anything.
Yes. Both are embedded directly, and any other format your browser can decode is converted to JPEG on the way in. A document can contain a mixture without anything special being done.
Neither by default. Each page is created at the pixel dimensions of the image on it, so a set of photographs at different resolutions produces pages of different sizes. For consistent printing, resize the images to matching dimensions first.
You can select many files in one go, but the picker takes files rather than directories. Select the contents of the folder and they all arrive in the list together.
There is no imposed limit. Memory is the real one: every image and the finished document are held in the tab at once, so a hundred high-resolution photographs are much happier on a laptop than a phone.
It depends on the browser rather than on this page. Apple's own has the decoder built in; Chrome and Firefox on most platforms do not, and the file simply will not open. Setting the camera to Most Compatible, which makes it write JPEG, avoids the question entirely and is worth doing before a batch of scanning.
No. The document is images on pages and nothing else; there is no text layer, no template and no annotation. A PDF editor is the right tool if the result needs anything added to it.
Not at all. The pictures are read and a new PDF is written to your downloads. Everything on your disk stays exactly as it was, so you can rebuild the document in a different order as often as you like.
Yes, once the page has loaded. Building a PDF is done entirely in your browser, so no connection is needed afterwards and only a fresh reload depends on the cache.
There is no limit imposed by us, because there is no server tier to enforce one. The real constraint is your device's available memory, since the whole file is held in RAM while it is processed. Very large files are slower on phones than on a laptop.
No. There is no sign-up, no email, and no usage tracking tied to an identity. The tool works the first time you open it.