🖼️ Images to PDF

Why "just email the photos" stopped being good enough

For most of the history of digital photography, sharing a batch of images meant attaching them one by one to an email, zipping them into an archive nobody wants to unzip, or trusting a cloud link that expires in 30 days. The moment someone needs to print, archive, or submit those images through a formal channel — an insurance claim, a portfolio review, a construction progress report — the chaos of loose files becomes a real problem. A single PDF solves all of that. It preserves the order you chose, keeps everything in one file with a predictable size, and opens identically on every device without needing any particular app.

What actually happens when you convert an image to a PDF page

Understanding the internals makes it easier to make smart decisions about quality and file size. A PDF is not just a renamed JPG. It is a structured document format that contains embedded image data (usually stored as a JPEG stream inside the PDF), a coordinate system that maps that image onto a virtual page measured in points (1 point = 1/72 of an inch), and a catalog of pages with explicit width and height declarations. When you set the page size to A4, you are telling the PDF viewer that the canvas is 595 × 842 points. The image gets scaled to fit that canvas, centered with whatever margin you specified, and the scaling instructions are written as a transformation matrix in a content stream. None of the original pixel data is thrown away — only the display geometry changes.

Choosing the right page size for your use case

This is where a lot of people make a choice they later regret. A4 (210 × 297 mm) is the global default and works for almost every formal document context outside North America. Use it for portfolios, reports, and anything going to a European or Asian recipient. Letter (216 × 279 mm) is the North American standard — important if the PDF is going to a US printer, because mismatched page sizes cause cropped output at the edges. A3 is twice the area of A4, which makes it excellent for architectural photos, wide panoramas, or images where detail matters more than page count. Legal is niche — mainly US legal filings and some government forms. The "fit to image" option is underused but powerful: it creates a PDF where the page dimensions exactly match the image pixel dimensions, preserving the original aspect ratio with zero letterboxing. This is ideal for archiving photos where you want no reinterpretation of the original framing.

Portrait vs landscape vs auto — and why "auto" is usually the right call

Portrait orientation works well when your images are taller than they are wide — standard smartphone photos taken vertically, document scans, portraits. Landscape flips the page to be wider than it is tall, which suits horizontal shots, widescreen screenshots, and panoramic photos. The auto option does something more useful than either fixed choice: it looks at each individual image's aspect ratio and picks the orientation that wastes the least space. A batch of photos from an event will often have a mix of portrait and landscape shots, and auto ensures each one fills its page appropriately instead of leaving half the canvas blank. The only reason to avoid auto is when you need every page in the document to have the same physical orientation for print binding purposes.

Reordering matters more than most people realize

The order images appear in a PDF tells a story. For a real estate walkthrough, the exterior shot needs to come first. For a product damage report, the overview image precedes the close-ups. For a recipe photo sequence, the steps need to flow chronologically or the document becomes confusing. The drag-and-drop reorder interface exists precisely because file systems sort by filename or date modified, which almost never matches the logical narrative order you want. Taking 30 seconds to drag your images into the right sequence before converting is time well spent — especially because editing a PDF after the fact to reorder pages requires specialized software.

JPEG quality and the file-size tradeoff

Every image gets re-encoded as JPEG inside the PDF (unless it is already a JPEG, in which case it goes through a canvas pass to normalize orientation and color space). The quality slider controls the compression level. At 100%, you get essentially lossless output — the file size will be large, sometimes larger than the original images combined, because the PDF container adds overhead. At 70–80%, the visual difference is imperceptible on screen and in most prints, but the file size drops by 40–60%. Drop below 60% and you will see compression artifacts, especially on images with fine text, gradual gradients, or high-contrast edges. A practical sweet spot is 80–90% for photos going into a document that will be emailed or uploaded, and 95%+ for archival purposes where storage is not a concern.

Margins: the invisible frame that changes everything

A page with no margin looks striking in a photo book but awkward in a professional document — the images feel like they are straining against the page edge. A small margin (10 points, roughly 3.5 mm) creates breathing room without wasting much space. Medium margins are good for reports where the images sit alongside whitespace, giving readers' eyes a place to rest. Large margins suit presentation-style documents where each image is more illustration than primary content. From a purely practical standpoint, margins also protect against printer clip zones — many desktop printers cannot physically print to the edge of the page, so a document with no margin risks cutting off image content at the edges when printed.

Privacy: why browser-based conversion beats cloud tools

When you upload a photo to a web service for conversion, that file touches servers you know nothing about. For personal photos, medical images, legal documents, or anything with faces or identifying information, this is a meaningful concern. Browser-based tools process everything locally using the JavaScript APIs built into the browser itself — FileReader to load the images, Canvas to re-encode them as JPEG data, and a PDF binary assembled entirely in memory. Nothing ever leaves your device. The download link is created from an object URL pointing to a Blob in browser memory, which disappears when you close the tab. For professionals handling client materials or sensitive content, this is not a minor feature — it is a fundamental requirement.

When to use this vs a dedicated desktop app

For batches under 30–40 high-resolution images, a browser-based converter handles everything gracefully. Above that number, or when working with very large raw files (20+ MB each), a desktop application like Adobe Acrobat or Preview on macOS will be faster and more memory-efficient, because the browser JavaScript environment has memory limits that can cause it to slow down on truly massive batches. The browser tool wins on speed for typical use cases — no installation, no account, no cost, works on any operating system. The one feature that desktop apps add is OCR (making the text in scanned documents searchable), which requires server-side processing and cannot be replicated in a browser without a large ML model download.