Assemble Photos and Scans Into a PDF

What image-to-PDF conversion really does

A PDF is a container that can hold many things — text, vectors, images, forms. Image-to-PDF conversion wraps each image on its own page and stores layout instructions describing where the image sits and how large it prints. The pixels themselves are usually embedded unchanged (or re-compressed once, depending on settings), which is why a well-made image PDF prints exactly as the source photos look.

This matters because it clarifies what the tool can and cannot do: it assembles and lays out; it does not perform OCR. A photo of a contract becomes a PDF page that looks like the contract but is not searchable text.

Page sizing: fit, fill, and actual size

The layout decision that defines the whole document is how images meet the page:

Fit is the safe default. Fill surprises people when portrait photos lose their tops and bottoms on landscape pages — check the preview before committing. Page format (A4, Letter, square) compounds with orientation: an A4 portrait page fits a 3:2 landscape photo with large top and bottom margins, which is correct behavior, not a bug.

Ordering pages before converting

PDF page order is frozen at creation, so sequence your images before the conversion, not after. The reliable habits: name files with leading numbers (01-cover, 02-intro...), verify the thumbnail strip in the tool's queue matches your intent, and remember that mixed orientations do not change order — a common panic is seeing a rotated page and assuming it moved.

For scanned documents, the ordering step is also your duplicate-page check: scanners love feeding the same page twice, and catching it in the preview costs nothing compared to discovering it after sending.

Orientation and rotation

Photos arrive sideways (see the rotation guide for why EXIF does this). Fix orientation in the queue before converting rather than asking readers to tilt their heads: a PDF whose pages rotate between portrait and landscape reads as careless even when every page is individually legible.

Compression: the file-size lever

Ten phone photos at 4 MB each become a 40 MB PDF if embedded raw — too heavy for email, fine for print handoff. Compressing the images during conversion (typical target: quality 75-85 JPG for photos) drops the same document to 3-8 MB with no visible difference at screen size. The decision rule: documents destined for email and web forms get compressed; documents destined for print get original quality or close to it.

If a recipient imposes a hard limit (many portals cap at 2-5 MB), compress first, then if still oversized reduce image dimensions with the resizer — for document reading, 1600-2000px on the long edge is more than enough.

Common assembly patterns

• ID and application packets: one image per page, fit mode, compressed, exact order per the form's instructions.
• Photo lookbooks: consistent margins via fit mode, one or two images per page, uncompressed if print-bound.
• Receipts and records: chronological naming, compressed, and a descriptive filename on the output (2026-07-receipts.pdf) because PDFs inherit no metadata from their source images.
• Scanned multi-page documents: crop each scan to the page edge first (see the crop guide), hold identical margins across pages, then assemble.

Privacy for document-grade content

Receipts, IDs, contracts, medical paperwork — image-to-PDF is exactly where uploading files to a random website is least acceptable. This tool assembles everything in your browser: the PDF is generated locally and downloaded, never stored on a server. You can confirm it by taking your machine offline after the page loads.

Troubleshooting assembled documents

PDF is a one-way street for images

Images embedded in PDF can be extracted by dedicated tools, but the extraction is lossy in workflow terms: page geometry, compression, and color handling have already been decided, and pulling images back out yields whatever the PDF stored, not your original files. This makes the conversion a publishing decision rather than a storage one — keep source images outside the PDF for any future editing. Archives follow the rule: originals in a folder, PDFs as delivery artifacts built from them whenever needed.

Building image PDFs that behave like documents

The difference between a PDF someone can work with and one they dread is built at conversion time. Page order is the first decision: multi-image conversion should follow a deliberate sequence — cover, then content in reading order — because reordering pages inside a PDF after the fact is possible but tedious. If your source files come from a camera or a phone, their filenames sort chronologically, which is usually the order you want; verify before converting, not after.

Page size deserves an explicit choice. Fitting each image to its own page size produces a document where every page differs — fine for an art portfolio, frustrating for printing and annotation. Forcing a standard page size (A4 or Letter) with the image scaled to fit produces a consistent document where printing, watermarking, and page-numbering all work normally. The trade is margins: images with very different aspect ratios get large ones. For receipt scans and similar documents, matching page size to content reads better than forcing A4.

Resolution is the quiet quality lever. A PDF can embed images at their full resolution or downsample them; a document scanned at 300 DPI and embedded at full quality is sharp when zoomed and prints cleanly, while the same pages downsampled to screen resolution turn to blur on paper. For documents meant to be archived or printed, keep the source resolution; for email-bound previews, downsampling is what makes the file small enough to send.

Common mistakes with this tool

• Converting before ordering the queue and emailing a document with page 4 second.
• Using fill mode on mixed orientations and cropping heads off portrait photos.
• Embedding raw 12-megapixel photos and sending a 40 MB file through a 5 MB portal.
• Sending photo-PDFs expecting text search — there is no OCR layer.

Frequently asked questions