How to Combine Multiple Photos Into One PDF

Yes, your phone or computer can already combine several photos into one PDF, and you don't need to install anything to do it. Whether you're stacking scanned receipts, ID photos, or product shots into a single file, the Photos app, the Files app, or File Explorer already has a built-in path to get there. Two things commonly go wrong along the way: a HEIC photo that refuses to add, and pages that land in an order you never picked. Both have a specific, fixable cause, not just a workaround.

TL;DR: Your phone or computer can already combine photos into one PDF, no app needed. HEIC photos need converting first because PDFs can't embed them directly, and photo order can scramble depending on which built-in method you use. I explain why both happen below, along with the fix for each.

Roughly 94 percent of all photos taken worldwide in 2026 are forecast to come from smartphones, according to Photutorial, up from 89 percent in 2020.

Yes. On iPhone and Mac, two built-in methods turn a set of photos into a single PDF: the Photos app's Print option, and the Files app on iPhone or Finder's Quick Actions on Mac, both offering a Create PDF action. On Windows, File Explorer's Print function, pointed at the Microsoft Print to PDF driver, does the same job from a selection of images. None of these require downloading anything new.

Every one of these methods creates a brand new PDF and leaves your original photos untouched, so there's nothing to lose by trying one. Where they differ matters more than you'd expect. Apple's own Mac documentation states that Finder's Quick Actions keeps your files in the PDF in the same order you selected them, while the iPhone's Files app doesn't preserve that order the same way. That difference is worth knowing before you pick a method, and I cover exactly why it happens in the next section.

On iPhone, open the Files app, tap Select, choose your photos, then tap the More button, shown as three dots, and choose Create PDF. On some iOS versions that same action sits one level up under Quick Actions instead, since Apple has reorganized file actions before. On Mac, select the photos in Finder, right-click or Control-click, and choose Quick Actions, then Create PDF. On Windows, select the images in File Explorer, choose Print, and pick Microsoft Print to PDF as the printer, which saves a PDF instead of sending anything to an actual printer.

HEIC photos won't add directly to a PDF because HEIC isn't a variant of JPEG, it's a HEIF container holding HEVC-compressed image data, and the PDF format has no built-in way to read that. That mismatch, not a bug in whichever app you're using, is the actual cause.

Here's the mechanism, since I write code that builds PDFs for a living. A PDF embeds a raster image as an Image XObject, a block of image data tagged with a filter that tells a PDF reader how to decode it. The common filter for photos is DCTDecode, built around baseline JPEG compression. HEIC photos are compressed with HEVC instead, an entirely different codec, and there's no equivalent filter for it in how PDFs are structured. A HEIC photo has to be decoded and re-encoded as something a PDF can actually embed, usually JPEG, before it can become a page. That's not a limitation of one particular app. It's built into how the file format itself works.

Apple designed HEIC to compress more efficiently than JPEG, which is part of why it saves storage space on an iPhone and in iCloud Photos, but that same efficiency is exactly why a PDF reader has no filter ready to decode it. That mismatch is the real reason a HEIC photo needs converting before it becomes a PDF page, no matter which app or method does the converting.

The simplest fix happens before you ever take the photo. Go to Settings, then Camera, then Formats, and choose Most Compatible instead of High Efficiency. Every photo you take afterward saves as JPEG, so it adds to a PDF without a conversion step in between.

It depends on which built-in tool you used. Apple's own documentation for Mac says it plainly: "The files appear in the PDF in the same order that you select them." That's true when you use Finder's Quick Actions to create the PDF. The iPhone's Files app doesn't behave the same way. Instead of preserving your selection order, it sorts photos alphabetically by filename before building the PDF.

That iPhone behavior isn't documented by Apple the same way the Mac behavior is, and Apple's iPhone-specific Files documentation doesn't spell out its sort order directly, so this is triangulated across independent sources rather than quoted from Apple. MobiSystems notes that images appear in the PDF in alphabetical order by filename, not the order you selected them, when using the Files app method, and the same pattern shows up across other independent guides and Apple's own community forums.

If order matters, skip the Files app on iPhone and use the Photos app's Print option instead, which follows the order you selected or are viewing the photos in, not alphabetical order. If you'd rather stick with the Files app, rename your photos with a number prefix first, like 01-receipt.jpg and 02-receipt.jpg, so alphabetical order and your intended order become the same sequence.

No, not from a resolution standpoint. The federal government's own digitization standard for permanent records requires only 300 to 400 pixels per inch, and a modern phone photo already exceeds that by a wide margin at a normal printed page size.

NARA's federal regulation for digitizing permanent records, 36 CFR Section 1236.50, sets a minimum of 300 pixels per inch for modern textual paper records, sized to the source document. For photographic prints and other fine-detail records, the minimum rises to 400 pixels per inch, which the regulation equates to the FADGI three-star Prints and Photographs category.

A modern iPhone's default photo runs 24 megapixels on supported models, with 12 or 48 megapixel options also available. At a standard letter-size page, even the lower end of that range works out to several hundred pixels per inch, comfortably past NARA's 300 ppi floor and close to or above its 400 ppi ceiling for fine-detail records. This is documented math against a published standard, not a visual check I ran myself, but it's the number that actually decides the answer, not a compression slider's label.

The table below lays out both thresholds side by side, so you can compare them directly against whatever photo resolution you're starting with.

Combining photos into a PDF puts each image on its own page, so the file's size is driven almost entirely by the source photos, not by anything the PDF format adds. A dozen full-resolution phone photos in one file usually means a document far larger than its page count suggests.

That follows from the same embedding mechanism covered above. A PDF page holding a photo is largely just that photo's original JPEG data wrapped in an Image XObject, not re-compressed for the page. A short-looking file, six or eight pages, can end up far bigger than its page count implies, because each page carries a full-resolution photo behind it.

If size is the problem, the more effective fix happens before conversion, not after. Reducing a photo's resolution before turning it into a PDF page controls output size directly. Compressing the finished PDF afterward is a weaker second pass, since it has to re-encode data that already went through one round of lossy compression when the photo was taken.

If you've already made the PDF and it's too big to send as is, getting the resulting file size back down is still possible, it just works better as a cleanup step than as the only plan.

If you need real control over page order, want to combine photos that started on different devices, or the HEIC conversion step keeps getting in the way, none of the native tools above solve all three at once. A browser-based tool that processes your photos on your own device handles all three without installing anything.

I built JoyPDF's photo-to-PDF tool to run entirely in your browser. You can combine your photos into a PDF in the browser, in whatever order you drag them into, and it accepts JPEG, PNG, and HEIC directly, so there's no separate conversion step to remember.

If you're starting from photos and already have a PDF you need to add to the same file, you can combine it with a PDF you already have instead of building two separate documents. And if your starting materials are already PDFs rather than photos, combining PDF files you already have is the more direct path, a different task from the one this article covers.

This matters beyond convenience for scanned IDs, signed forms, or receipts you'd rather not upload anywhere. Because the file is processed in your browser and never sent to a server, there's no server-side copy of a document you might not be allowed to share with a third party in the first place.

Native tools already handle this. The Photos app's Print option and the Files or Finder Create PDF action cover iPhone and Mac, and Print to PDF via File Explorer covers Windows, with nothing to install.

HEIC needs converting first because it's a HEIF container built around HEVC video compression, not a JPEG variant, and PDFs have no filter built for HEVC-compressed images.

Order preservation depends on the tool. Mac's Finder keeps your selection order. iPhone's Files app sorts alphabetically by filename instead, so use the Photos app's Print option or rename files first if sequence matters.

Quality isn't the real risk here. A modern phone photo already exceeds NARA's own archival scanning standard at a normal page size.

If you've got a batch of photos to combine right now, especially ones already tripping over one of these two snags, turn your current batch into one PDF and see the result directly.