Images to PDF combiner

Combining a stack of images into a single PDF is one of those small tasks that comes up surprisingly often once you start paying attention. A passport page and a utility bill for a visa application, a sequence of receipts being sent to an employer for reimbursement, photos of a contract someone signed at a kitchen table, scanned pages of a child's school assignment that need to land in the teacher's inbox by Sunday night, a stack of evidence photos for an insurance claim — all of these end up needing the same shape: one PDF, ordered correctly, that opens cleanly on the receiving end. This tool handles that step without the friction of installing a desktop scanner application or paying for a one-off subscription.

Order is the part most other tools handle badly. The drag-to-reorder interface here exists because the order coming out of a phone gallery, a desktop folder, or a chat export is almost never the order the recipient needs to read pages in. Phones often sort by EXIF capture timestamp, which puts the second photo of a two-page document before the first if you happened to photograph the back side first; desktop folders sort alphabetically, which is a coin flip whether it matches the document layout. Being able to drop the files in, then drag them into the right reading order before generating the PDF, is the difference between something that works and something that creates a follow-up email asking for a corrected version.

Rotation is the other detail that catches people out. Phone photos taken in landscape sometimes embed the right rotation in EXIF and sometimes don't, depending on the phone, the camera app, and what edited the file along the way. The result is that a perfectly readable photo on the phone gallery shows up sideways in the PDF if rotation isn't handled. Each image can be rotated individually from the preview before generation, so a mixed bag of portrait and landscape photos all end up oriented correctly without having to round-trip through a separate image editor first.

Image quality is preserved end-to-end, which sounds obvious but isn't a given for this category of tool. Many free image-to-PDF tools re-encode every input as JPEG at a fixed default quality on the way through, which is fine for casual photos and a real problem for scanned documents — fine text turns into JPEG mush, line drawings get artefacts at every edge, and the output PDF prints visibly worse than the source images would. The path here passes pixel data through without recompression where the format allows, so a clean PNG scan stays a clean PNG inside the PDF, and a high-quality JPEG stays at the quality it arrived at.

Page size is genuinely worth thinking about. A4 is the right default for most of the world; US Letter is correct for North America. Fit-to-image is the right choice when the goal is digital viewing rather than printing — a tall, thin chat screenshot doesn't make sense forced into A4 with two thirds of the page blank, but it makes perfect sense as a page sized exactly to its own dimensions. Margins matter when the recipient is going to print the PDF, because most printers can't reach the edge of the paper and content placed flush to the edge will end up cropped on the physical sheet.

There are a couple of layout patterns worth knowing about. One image per page is the right default for documents, because the recipient expects to scroll one page per logical unit — page one of a contract, page two, page three. Multiple images per page is the right pattern for receipt bundles, photo grids, and reference sheets, because cramming six receipts into one A4 sheet means six pages of paper become one and the recipient still sees everything. The tool supports both and the choice is usually obvious once you see what's being assembled.

DPI handling is a quiet but important detail for anything destined for print or for documents containing fine text. The PDF preserves DPI hints from the source images, so a 300 DPI scan stays 300 DPI inside the PDF, and a 72 DPI screenshot stays at the resolution it was captured at. That means scanned documents print at the correct physical size — an A4 scan ends up on an A4 sheet at full size rather than scaled to fit something arbitrary — and that the text on a scanned page remains readable when printed at 100 percent. Some other tools normalise everything to 72 DPI on the way through, which produces visibly worse print output without any warning.

Real-estate listings and rental documentation are a quietly recurring use case for this kind of bundling. Property managers preparing lease agreements, real-estate agents assembling listing packages, landlords compiling damage-deposit photo evidence at move-out, and tenants documenting pre-existing condition at move-in all end up needing the same shape of artefact: a single PDF with photos, supporting documents, and signed forms in a particular reading order. The legal weight that a PDF carries — it's a frozen, immutable record of what was photographed and when — matters more than the technical conversion details. Building the PDF locally and sharing the file through a deliberate channel (email, agency portal, court submission) keeps a paper trail that holds up when someone disputes what was visible at a particular point in the rental cycle.

Receipt and expense workflows deserve a separate mention because they're one of the most common reasons people end up needing this tool every month. The expense-report cycle at most companies still works the same way it has for twenty years: you collect paper receipts and digital ones across a month of business travel, you take a phone photo of each paper one, you forward the digital ones to yourself, and at the end of the month you assemble the whole stack into a PDF that finance can attach to your reimbursement request. The order matters because it usually has to match the chronological order on the expense system, the rotation matters because the photos arrive at random orientations, and the file size matters because finance systems often cap inline attachments at 10 megabytes. Doing this manually in a desktop app each month is a small recurring tax on professional life; a single web tool that handles it in three minutes is the right shape of solution.

Visa and government applications are another reliable use case for this conversion. Most embassy applications, university admissions portals, immigration document submissions, and government benefit applications require supporting documents to be uploaded as a single PDF rather than as separate images, and they often specify a maximum total file size and minimum page dimensions. The reasons are bureaucratic rather than technical — somewhere there's a clerk who needs to print, file, and reference these things — but the requirements are firm and rejection means redoing the whole submission. Combining the right photos in the right order, at the right page size, into a single PDF is the difference between a successful submission and a polite request to try again next month. Worth taking the few extra seconds to get it right the first time.

Practically, the workflow is drag in, reorder, rotate where needed, pick page size and layout, generate. Files are processed in temporary storage with short-lived download links, no signup, no watermark on the output, and no page count cap. Multiple combinations can run through one after another without hitting a quota wall — useful when a single afternoon involves several different bundles for different recipients. The output is a standard PDF that opens in Acrobat Reader, Preview on macOS, the built-in viewer on Windows, every mobile PDF app, and every browser. There's no proprietary format or special viewer needed at the receiving end.