Merge PDF files without uploading them anywhere

Combining PDFs is one of the most common document tasks and one of the easiest to get wrong. Most online mergers ask you to hand over the file first and sort out the details later. That is unnecessary: browsers can already parse a PDF, build a new document, and hand you the result without a round trip to a conversion server.

What actually happens when two PDFs are merged

A PDF is a container of page objects plus the resources those pages depend on: fonts, images, colour profiles, and annotations. A correct merge copies each page object and the resources it needs into a new container, then writes a new page tree in the requested order.

That distinction matters. A merge that preserves page objects keeps text selectable, keeps vector artwork sharp at any zoom, and keeps file size close to the sum of the inputs. A merge that renders each page to an image and restacks the images produces a document that looks similar on screen but is no longer searchable, is often much larger, and cannot be edited later.

The browser-local merge PDF tool copies structured pages rather than rasterising them, and shows the resulting page count before you download anything.

Put the files in order before you export

The order of the source list is the order of the output. If a three-page cover report sits above a two-page appendix, the exported file opens with the three report pages and continues with both appendix pages. There is no separate "sort" step afterwards.

Two habits make this reliable:

1. Name files so alphabetical order already matches the intended reading order when you select them in bulk.
2. Check the page count next to each row. A file reporting zero pages is usually encrypted, truncated, or not a PDF at all.

If you need a different sequence inside one of the source files, fix that first with the page organiser and then merge. Doing it the other way around means hunting for pages in a longer combined document.

Which files fail, and why

A merge can fail for reasons that have nothing to do with the merging tool:

• Password-protected sources. A file that requires a password to open cannot be read until it is decrypted with that password.
• Structurally damaged files. A truncated download or an interrupted export can leave a cross-reference table that no reader can follow.
• Files that are not PDFs. A renamed .docx or .jpg will not parse, even though the filename looks right.

A useful merge workspace reports the problem file by name and keeps the rest of your selection intact, so you are not forced to start the whole selection over.

What to review after merging

Merging changes the page set of a document, and some PDF features are tied to that page set:

Feature	What to check after merging
Bookmarks and outlines	Entries that pointed into a single source may need to be rebuilt
Named destinations and internal links	Links across former document boundaries can resolve differently
Form fields	Duplicate field names from two sources can share a single value
Digital signatures	Treat a merged file as a new document, because changing the page set invalidates the expectations a signature was created under
Attachments and portfolios	Embedded files are not always carried into a flat merged document

None of this makes merging unsafe. It just means a merged contract, tax pack, or signed agreement deserves the same final read-through you would give any newly assembled document.

When not to merge at all

Merging is the wrong answer when the real goal is to reduce what you share. If you only need pages 4 to 9 of a long report, extract them with the split tool instead of merging everything and deleting later. Smaller, purpose-built documents are easier to review and leak less context than a combined file that happens to contain everything.

A short checklist

• Select every source file and confirm each shows a plausible page count.
• Arrange the rows to match the reading order you want.
• Export, then open the result and confirm the total page count matches the sum of the sources.
• Re-check bookmarks, links, and form fields if the document relies on them.