Merging copies page objects from each file into a new document and builds one page list in the order you set. Nothing is re-rendered, so text stays sharp and images keep their exact resolution. The output is roughly the sum of the inputs.
Three things do not survive any merge: certificate signatures, some internal page links, and the tagged reading order used by screen readers. Sign last, and test links in the result.
Someone wants one file and you have six. A cover letter, a CV and three references for a job portal. Twelve monthly statements for a mortgage underwriter. A contract that came back as separately scanned pages. The job is trivial and the tools are everywhere, which is exactly why almost nobody stops to ask what a merge does to the document, or why the result sometimes arrives in the wrong order with an invalid signature.
This page answers both. The tool at the top runs the whole merge inside your browser with the pdf-lib library, and the sections below explain what that library is doing on your behalf.
How to merge PDFs in your browser
Add every file before you touch the order
Drop them all onto the box at once, or add them in batches. Reordering is far quicker when the full set is on screen, and it stops you discovering a missing document after you have arranged the other eight.
Put them in reading order, not arrival order
The list order is the output order. Use the arrows on each row to move the cover to the top and the appendix to the bottom. Files land in the order the browser handed them over, which is not always the order you selected them in.
Press Merge PDFs
Each file is parsed in memory, its pages are copied into a fresh document, and bookmarks are shifted to their new page numbers. On a laptop this takes well under a second for a typical stack.
Open the result before you send it
Scroll the joins. The seam between two documents is where page-size jumps and upside-down scans announce themselves, and the check takes ten seconds.
Pages are copied, not re-encoded. No resampling, no recompression, no generation loss however many times you merge.
Structural overhead only. Fonts shared between files sometimes deduplicate, so the output can even come in slightly under.
The files are read into browser memory, processed there, and released when you close the tab.
What a merge actually does to the file
A PDF is a collection of numbered objects with an index at the end that says where each one lives. Pages are objects. Fonts, images and colour profiles are objects. A page does not contain its own content so much as it points at the content streams and resources it needs.
Merging walks that structure. It copies the objects from each source into a single new file, renumbers them so nothing collides, and builds one page tree listing every page in the order you asked for. The content stream that described page four of your second file is byte-identical in the output. It just answers to a different number now. That is why merging is lossless in a way compression and conversion never are.
- Page text, layout and fontsIntact
- Images and their resolutionUntouched
- Bookmarks and outlineKept, renumbered
- Form fieldsFirst form's fields kept
- Highlights and commentsUsually kept
- Internal page linksTest them
- Certificate signaturesAlways invalidated
- Tagged reading orderUsually lost
Internal links break for a reason worth understanding. A link that jumps to page twelve does not store the words "page twelve". It stores a reference to a specific page object. When the merge renumbers everything, the reference may still point at the right page or at nothing. If a source document had a clickable table of contents, click two entries in the output before you trust it.
Getting the order right the first time
Almost every complaint about merged PDFs comes down to order, and almost every one of those traces back to the same cause. Somewhere along the way the files were sorted by name, and names sort in a way people do not expect.
Computers compare text one character at a time. Under that rule page10.pdf comes before page2.pdf, because the character 1 sorts before the character 2. The fix is to pad the numbers so every name is the same length. page02.pdf and page10.pdf sort correctly everywhere, and so does anything with a date written year first.
01-cover, 02-body, 03-appendix survives every tool, every operating system and every colleague who reorganises the folder. This merge tool does not sort by name at all, which is deliberate: the list shows the order it will use, and the arrows let you change it.Mixed page sizes, rotations and other seams
The merge copies each page with its own dimensions and its own rotation flag. That is correct behaviour, and it produces a file that looks odd when the sources disagree. An A4 report followed by a Letter-size scan followed by a landscape spreadsheet is a legitimate PDF that every reader will display faithfully, jumps and all.
- Sideways scans. Run the offending file through Rotate PDF first. Rotation is a per-page flag, so fixing it costs nothing in quality.
- Different paper sizes. Usually harmless on screen. For printing, the printer driver scales each page to the tray, which is normally what you want.
- Blank backs from a duplex scanner. Remove them in the Editor before merging rather than hunting for them afterwards in a longer file.
Filled forms, bookmarks and signatures
Bookmarks come through. The tool reads each file's outline, shifts every entry by the number of pages that now sit in front of it, and writes a single combined outline. A textbook merged from chapter files keeps its chapter navigation.
Form fields are more delicate. Fields are addressed by name, and two filled forms usually contain a field called something like full_name in both. Readers resolve the clash inconsistently: some link the pair so typing in one fills both, some drop one. This tool keeps the form definition from the first file that has one. If you need several completed forms in one PDF with every answer preserved, flatten each one first. Flattening turns the typed values into ordinary page content, which merges without any ambiguity.
Large merges: memory is the only limit
Because nothing uploads, network speed is irrelevant. Two hundred pages merge as fast as twenty, and a 200 MB file on a train has the same experience as on office wifi. The one constraint is that the browser has to hold every source in memory while the new file is assembled.
On a modern laptop that ceiling is comfortably above 500 MB of input. Phones are tighter, and older tablets tighter still. If a very large merge stalls, merge in two halves and then merge the halves. The result is identical, because merging is lossless.
Why it matters that the file never leaves your device
Merging tends to be the last step before a document goes somewhere important. Contracts, statements, medical records, anything with a signature block. Most online merge tools upload every file to their server, combine them there, and hand back a link. For a recipe collection that is fine. For a mortgage application it means a complete copy of your finances sitting on hardware you have never seen, under a deletion policy you cannot verify.
The file stays on your machine
- Nothing crosses the network, so nothing can be intercepted or retained
- Works offline once the page has loaded
- No account, no email address, no queue, no daily limit
- Speed depends on your device, not someone's server load
The file becomes someone else's copy
- A full copy sits on infrastructure you do not control
- Deletion promises are policy, not physics
- Large files travel twice, up and back down
- Outages, rate limits and sign-up walls are out of your hands
What to do after merging
The merged file is a normal PDF 1.7 document. It opens in Acrobat, Preview, every browser and every mobile reader, and it uploads to signing services and government portals without complaint. A few follow-up jobs are common enough to plan for:
- Too big for the portal or the inbox. Compress PDF shrinks the combined file in one pass, which gives a better result than compressing the pieces beforehand.
- The reader needs to know where they are. Add page numbers across the whole document so the numbering runs continuously through every source.
- It should not travel unprotected. Password protect the finished file, then share the password by a different channel.
- You merged too much. Split PDF pulls a page range back out without touching the rest.
The tool is right above
Everything on this page runs in your browser. Scroll up, drop the file, and keep it on your machine.
Common questions
The things people discover halfway through a merge.
01Does merging PDFs reduce quality?
No. The merge copies page content across without re-encoding anything, so text stays vector-sharp and images keep the resolution they had in the source. Compression is the operation that costs quality, and it is a separate tool.
02Why is my merged file so large?
Because a merge adds rather than compresses. Each source contributes its own images and embedded fonts, already compressed, and they are copied across intact. Four 3 MB files make roughly a 12 MB file. If the result needs to be smaller, compress the merged document as a single pass afterwards.
03Can I merge password-protected PDFs?
Not while they are still encrypted. The merge has to read the page objects, and encryption exists to prevent exactly that. Remove the password from a file you own with the Unlock tool, merge the unlocked copies, then protect the finished file if it still needs it.
04Why did my pages come out in the wrong order?
Almost always filename sorting somewhere upstream. Text sorts one character at a time, so page10 lands before page2. Pad the numbers, or simply drag the files into position in the list above, which is the order the tool will use.
05Do bookmarks survive the merge?
Yes. Each file's outline is read, shifted to the new page numbers, and written into a single combined outline. Chapter navigation from separate chapter files works in the merged book.
06Is there a limit to how many files I can merge?
Not a policy limit. Every page has to sit in memory while the new file is built, so a few hundred pages is comfortable on any laptop and a few thousand may not be. If a large merge stalls, do it in two halves and merge the halves.
07Does it work on iPhone and Android?
Yes. The tool runs in Safari, Chrome and Firefox on phones with the same interface. Memory is tighter on a phone, so very large stacks are better done on a laptop.
08Can I reorder pages inside the merged PDF afterwards?
Within one file, the Editor reorders, deletes and extracts pages. For whole-file order, redo the merge with the list arranged the way you want; it takes seconds and loses nothing.