Merge PDF
Every page from every file lands on one canvas. Drag any page anywhere, turn it, drop it, and change your mind as often as you like.
- Reorder pages across files, not just whole files
- Undo and redo every move, turn and deletion, sixty steps of it
- Pages are copied, not redrawn, so text stays selectable and nothing is flattened
- A protected PDF is refused by name rather than quietly opened
Up to 60 files and 3,000 pages, a memory limit, not a licence one.
Just looking?
- Pages
- 0
- Sources
- 0
- Turned
- 0
Your pages are copied, not redrawn. Text stays selectable, vectors stay sharp, and the file does not grow the way it would if each page were turned into a picture. Nothing is uploaded and no account is needed.
From several files to one, in three steps
Drop the PDFs in
Every page of every file appears as its own tile, in the order the files arrived. Add more at any point without losing the arrangement.
Arrange the pages
Drag a tile anywhere. Click to select, shift-click for a range, ⌘-click to add one. Turn or remove whatever is selected, and undo anything you regret.
Name it and download
The name sets both the file and the PDF's own title. A bookmark per file gives the merged document an index that a reader can navigate.
What you can hand it
| Input | What happens |
|---|---|
| Several PDFs | All of their pages land on one canvas, in drop order |
| Mixed page sizes | Kept as they are, each page keeps its own size |
| A password-protected PDF | Refused by name. It was protected for a reason |
| A damaged PDF | Refused by name; the others still load |
| A page that will not draw | Blank tile, but it still merges correctly |
| Images, not PDFs | Not accepted here, use Images to PDF |
The page canvas
| To do this | Do that |
|---|---|
| Move a page | Drag the tile. The half you drop on decides before or after |
| Select one | Click it |
| Select a range | Click, then shift-click the far end |
| Add or remove one | ⌘-click, or Ctrl-click |
| Move several | Select them, then drag any one of them |
| Turn | Turn left or Turn right, or R and ⇧R |
| Remove | Remove, or the Delete key |
| Undo | ⌘Z, sixty steps deep. ⇧⌘Z to redo |
| Put a file back to front | Select its pages, then Reverse |
Why page-level matters
Most merge tools online work on whole documents: you get a list of filenames and a pair of arrows, and the only thing you can change is which file comes first. That is fine when you are stapling three finished reports together, and useless the moment the job is "everything except page two of the scan, with the appendix moved to the front".
Doing it by file means going back to another tool to split the scan, then coming back here, then discovering the appendix is upside down. Every page being its own tile removes all of that: split, reorder and rotate are the same gesture.
Copied, not redrawn
There are two ways to put a page into a new document. You can copy the page's own content (its text, its vectors, its fonts) or you can rasterise it into a picture and draw that picture on a fresh page.
The second is much easier to implement and it is what a surprising number of tools do. It also destroys the document: text stops being selectable, stops being searchable, stops being readable by a screen reader, and the file gets several times larger because a page of text compresses far worse as an image than as text.
This copies. A merged file here is roughly the sum of its inputs, and everything in it still behaves like a PDF.
What it will not do
- Open a password-protected PDF. It is refused by name. A tool that strips protection silently is a tool that will do it to someone else's document too.
- Keep the bookmarks that were inside the original files. They point at structures that no longer exist after a merge. You get one bookmark per file instead, which is the part people wanted.
- Preserve tagging and reading order. A tagged, accessible PDF loses its structure tree in any page-level merge, including this one. If accessibility matters, merge at the source rather than at the end.
- Keep links that point within a document. A link to "section 4" in one file has nowhere to land once the pages have moved. External links to the web still work.
- Combine form fields with the same name. Two files with a field called
namewill fight over it. Flatten the forms first. - Go past 60 files or 3,000 pages. Each tile holds a rendered thumbnail and a few thousand of those is where a browser tab starts to struggle. It is a memory ceiling rather than a policy.
Everything happens in this tab
The file is read by your browser, arranged in your browser, and written by your browser. There is no upload, which is why there is no size cap, no queue, no watermark and no two-hour retention policy: there is nowhere for a document to be retained.
You can watch the network panel stay empty while you use this, which is a better guarantee than any privacy policy.
Questions
Are my files uploaded?
No. Everything happens in this tab. There is no server involved, which is also why there is no size limit and no waiting.
Can I reorder individual pages, not just files?
Yes. That is the whole point of the canvas. Every page is its own tile and can go anywhere, including between pages of a different document.
Does merging lose quality?
No. Pages are copied rather than redrawn, so text stays selectable and vectors stay sharp. Nothing is re-compressed.
Is there a watermark or a daily limit?
Neither. There is no account and nothing to pay for.
Why was my PDF refused?
Either it is password protected, or it is damaged badly enough that the library cannot parse it. Both are named in the notice rather than silently skipped.
Do links and form fields survive?
Links to the web do. Links that point inside a document do not, because their target has moved. Form fields survive, but two fields with the same name in different files will collide.