DEV Community

ahmed isam
ahmed isam

Posted on Originally published at pdfmergenext.shop

Merge PDFs on iPhone Without an App: Files App vs a Safari Tool

--
title: "Merge PDFs on iPhone Without an App: Files App vs a Safari Tool"
description: "Two on-device ways to merge PDFs on iPhone, with limits and pre-send checks."
tags: ["ios", "pdf", "iphone-tips", "privacy", "webassembly"]

canonical_url: https://pdfmergenext.shop/blog/merge-pdf-iphone-safari-tool

Merging PDFs on an iPhone used to mean installing an app. It does not have to anymore. There are two routes that avoid uploading your files to a server: the built-in Files app, and a local tool that runs inside a Safari tab. This post walks through both, with the limits of each and the exact checks to run before you send the result.

Why avoid the upload route? Nearly every free PDF site defaults to uploading. Your file goes up, gets merged, comes back down, and then sits on someone else's disk for as long as their retention policy allows. If the file is a lease, a medical form, or anything with an ID number, that copy is a real problem. The Files app keeps the document on the phone. A local browser tool does the same.

Method 1: the Files app

  1. Put the PDFs into one folder.
  2. Tap Select in the top right.
  3. Tap each file you want, in the order you want them.
  4. Open the share sheet and choose Create PDF.
  5. The combined file lands in the same folder.

No account, no upload, nothing to pay. For two or three short documents this is the fastest option on the phone.

Two limits matter:

  • The output stops at roughly 15 pages.
  • The order locks the moment you select files. You cannot rearrange afterwards.

Also note that iOS sorts filenames as text, not as numbers. page-2.pdf sorts after page-19.pdf unless you renamed things first. Spend thirty seconds renaming and you avoid a full redo.

Method 2: a Safari local tool

Open Safari and load a tool that processes files locally. Add the PDFs, order them, and save the result back to Files. PDFMergeNext runs the merge through WebAssembly inside the tab, so the document never leaves the iPhone, and the tab keeps working after you lose signal.

Take this route when:

  • You are past 15 pages.
  • The sequence needs fixing.
  • You only want part of a file.

Page selection uses a syntax like 1-3,5. That drops a cover sheet and the blank trailing scan in a single pass. If you are merging phone snapshots rather than proper scans, check the quality cost of a compressed PDF merge before you start, because the merge is not what degrades the image.

The screen is small, so judge a tool by whether its controls were built for a thumb. A drag handle the width of a finger beats a tiny arrow you have to hit twice.

Comparison table

| Option | Page limit | Reorder | Page selection | File location | Offline |
| Files app | About 15 pages | No | No | Stays on iPhone | Yes |
| Safari local tool | None | Yes | Yes, 1-3,5 | Stays on iPhone | After page loads |
| Upload site | Varies | Usually | Sometimes | Server you don't control | No |
| App Store app | Often capped | Yes | Varies | Depends on app | Sometimes |

Three checks before the file leaves your phone

  1. Count the pages. Open the merged output and compare the total to what you expected. A merge that quietly drops two pages surfaces three days later, in front of whoever needed it.
  2. Check the joins, not the filenames. Scroll to where one source ends and the next begins and confirm the transition reads right.
  3. Compare file size. Output much larger than the sum of inputs means something re-encoded the pages. Output much smaller means images were compressed again. Neither is automatically wrong, but you want to know which one happened.

The choice comes down to two numbers: how many pages, and how much the order matters. Full guide: https://pdfmergenext.shop/blog/merge-pdf-iphone-safari-tool

Top comments (0)