Four PDFs sat in Files on my iPhone: a one-page cover, a one-page ID, six pages of bank statements and an eight-page signed lease. The letting agent wanted one 16-page document. I did not install an app. I opened the merge page in the browser, selected the four files through the file picker, merged them locally and saved the download. This guide covers that exact route, including the order rule, the 10MB per-file cap and the memory behaviour that matters on a phone.
Part of the PDF workflow guide. Merge in the PDF merge tool; turn scans into a PDF first with image to PDF. For covers, chapters and mixed bundles, read merge order.
Why the browser works on iPhone
The merge is performed by the page itself, not by a remote server. Your PDFs are read into memory on the phone and written into a new file locally. Nothing is uploaded, there is no account to create, and there is no app to install or update. Safari and Chrome run the same merge page, and the important behaviour is similar even though the surrounding interface differs.
The limits are fixed and worth learning before you start: 2 to 20 PDFs, 10MB per file, and 200 pages in total. Encrypted PDFs and corrupt files fail because the merge engine cannot parse them. Everything is local, so there is no server-side cleanup step and no second attempt on another machine. If the phone runs out of memory, the work is lost and you start again.
The browser's file picker is the only bridge to your documents. It can open PDFs you select from Files or Downloads, but this is not an iOS app and not a Files extension. It does not browse your folders on its own, sync a cloud drive or keep a library. You choose the files, and the page receives the copies the picker hands over.
Prepare the files before you add them
Put every PDF somewhere the picker can see, usually Files or Downloads. If a file lives in iCloud Drive and is not downloaded yet, let the download finish before you select it. A placeholder that has not fully arrived can fail to load, which looks like a broken PDF rather than a sync delay.
Rename the files with a numeric prefix such as 01-cover.pdf and 02-id.pdf. You will still verify the order on screen, but clear names make a wrong sequence obvious. Check three limits at the same time: each file is under 10MB, the set is no more than 20 files, and the page counts add up to 200 or less. A file that is password-protected or damaged will not merge; unlock it or request a fresh copy before adding it.
Decide the final order now. The order in which files are added becomes the page order in the result. There is no drag handle in the list, so changing position means removing a file and adding it again at the end. If the images belong between pages of an existing PDF, this tool cannot interleave them; split the PDF first and merge the parts around a separate image PDF.
Merge steps on the iPhone
- Open Safari or Chrome and go to the PDF merge page.
- Tap Add PDFs. The system file picker opens. Choose a PDF from Files or Downloads. Select several at once if your picker offers it, or add them one at a time; each addition appends to the list.
- Read the numbered list from top to bottom. It shows each file name and size. That number is the page order the merge will follow.
- If a file is out of place, tap Remove and add it again so it lands at the end. Repeat until the sequence matches your plan.
- Confirm the list has 2 to 20 files, every file is 10MB or less, and your expected total is 200 pages or fewer.
- Tap Merge. Keep the page open and wait. The success message reports how many files and pages were merged.
- The browser downloads
merged.pdf. Rename it with the content and date, save it through the browser's download or share control, then open it and check the pages.
Do not assume the download went to a particular folder. Use the browser's download list or the share control to keep the file in Files, send it by email or pass it to another app. The exact placement varies with the browser and the iOS version, so verify that the file exists before you close the tab.
Memory, speed and the 200-page ceiling
A PDF's memory cost depends on page complexity, not only on file size. A 200-page text document can be lighter than a 40-page scan with large images. The phone does the parsing and writing, so a long merge may take noticeably longer than the same job on a laptop. The browser can also discard and reload a background tab when memory gets tight, which wipes the selected list and any progress.
Close other tabs before a large merge, keep the merge page in front, and avoid switching apps while it runs. Download each result before starting another batch. If the tab reloads, do not immediately retry the same 20-file set. Split it into two smaller runs, download both outputs, and merge those outputs only if each is under 10MB and the combined page count stays within 200. Keep the intermediate files until the final PDF opens correctly.
| Situation | What to do | Why |
|---|---|---|
| 2 to 5 short PDFs | Merge in one run | Low memory use and a quick result |
| One file near 10MB | Merge it with small files and wait | The per-file cap is checked, and heavy pages take longer |
| 20 files | Use numeric names and check the list twice | 20 is the maximum, and there is no drag reorder |
| More than 200 pages | Split or compress the source first | The merger stops at 200 pages total |
| Encrypted or corrupt PDF | Unlock it or get a fresh copy | The engine cannot parse protected or damaged files |
| Wrong sequence | Remove the file and add it again | Add order becomes page order |
| Tab reloads mid-merge | Split the job into smaller batches | iOS may reclaim memory and discard the page state |
Two worked examples
Example 1: a 16-page rental application. The set was a one-page cover at 180KB, a one-page ID at 1.9MB, a six-page statement at 3.2MB and an eight-page lease at 4.1MB. I added them in that order, read the numbered list, and merged. The success message reported 4 files and 16 pages. The download was about 9.3MB, close enough to common 10MB attachment limits to be worth checking before emailing. I opened the result and confirmed the cover was page 1 and the lease ended on page 16. If the statement had been encrypted, the merge would have refused it, so unlocking it first was part of the preparation.
Example 2: 14 statements, 188 pages. A mortgage file arrived as 14 PDFs with 188 pages in total, each between 2MB and 9MB. The file count was under 20 and the page total was under 200, but this was a heavy job for a phone. I closed other tabs, kept the merge page in front and let it finish. The success message confirmed 188 pages. If the tab had reloaded, the plan was to merge seven files, download the result, merge the other seven, then combine the two outputs only if both were under 10MB. Sampling the first, middle and last pages caught a sequence error before the file was sent.
Verify the download before sharing
Open the downloaded PDF on the iPhone and check the page count against your expectation. Then inspect the first page, a middle page and the last page. Confirm the sequence by the page numbers printed on the documents, not only by the file names. Check that no page is sideways, blank or missing, and zoom in on small text if the file will be printed.
Check the byte size against the recipient's limit, then rename the file with content and month, such as rental-bundle-2026-10.pdf. Keep the original PDFs until the recipient accepts the upload. Merging can flatten form fields, signatures and annotations into static page content, so archive any editable originals you may need again. If the order is wrong after merging, rebuild from the sources rather than trying to edit the finished file.