Merge PDFs into one file
Files in, one file out — in the order you set. The merge happens in this tab’s memory; nothing is uploaded.
All the tools
Mechanism, plainly
Each source file is parsed on your device and its pages are copied, in your order, into a new document, which is then written out and handed back to you. Page contents are copied byte-faithfully — nothing is re-compressed or resampled on the way through.
What merging can cost, said before it happens
Some document features don't survive concatenation intact, and the receipt lists anything that was dropped rather than letting you discover it later. The common case: bookmarks (outlines) point at pages by internal identity, and a merged document gets a new one — if your sources carry outlines, the receipt says what happened to them. Links that point within a copied page keep working; links that pointed at pages you didn't include are dead by definition, and are listed.
Refusals are loud
A file that would be silently damaged by merging is refused with the reason stated — an XFA form, for instance, is an XML program wearing a PDF costume, and its visible pages are often just a placeholder; merging those pages would hand you a convincing-looking file with the form logic gone. You get told that, instead of getting a broken file.
Questions people actually ask
- Is there a limit on how many files I can merge?
- No quota. The practical ceiling is your device’s memory, since the work happens in this tab.
- Will merging recompress or degrade my pages?
- No. Pages are copied as they are — the merge changes the container, not the content.
- What happens to bookmarks and links?
- Anything that cannot survive the merge is dropped and listed in the receipt, not silently. Links within copied pages keep working.
- Are my files uploaded to be merged?
- No. All parsing and rebuilding happens in your browser.
We invite you to double-check our work
Open your browser’s developer tools, switch to the Network tab, and run any tool on this page and nothing leaves your device.
The whole source is on GitHub. Read it.
Found a bug, or a claim that doesn’t hold up? Tell us: pdf@geodeforge.com. An example file turns a guess into a quick fix — and if yours is too sensitive to share, we understand; a description still helps.
That’s the difference between a privacy policy and a fact.
This slot pays for the page
One static, labeled sponsor link — an image we host and a plain link. No ad network, no tracking script, no third-party request. That is the entire business model, and it is why nothing above has a price.
Sponsor this slot →More from GeodeForge
GeodeForge is a one-person studio that crafts open-source tools that do what they say, and let you check — in your browser.