Drop files here, or click to browse
Multiple PDFs supported · up to 100 MB each
How to use
01
Drop two or more PDFs
Upload the batch in one go. Each file appears as a numbered row showing its name and size, and the first document expands automatically so its pages are visible immediately.
02
Verify and fix the order
Click Preview on any row to open a thumbnail grid of that document's pages, then use the up and down arrows until the numbering matches the order you want in the output.
03
Merge, then repeat per group
Press the Merge button to download merged.pdf. For per-client bundles, rename that download, hit Clear, load the next client's files, and run the merge again.
Why Bulk PDF Merger
- See every page of every PDF before you merge, no surprises.
- Reorder PDFs with the up/down arrows; pages combine in that order.
- Files never leave your device, merge happens in your browser.
Common questions
How do I merge many PDFs at once into separate per-client files?
Run one merge per client rather than one giant merge. Load only client A's invoices, merge, rename the download, then press Clear and load client B's set. The tool always produces a single combined document per run, so the grouping is done by what you load together.
Does the bulk pdf merger keep the page order predictable?
Yes, pages are copied strictly top to bottom through the numbered list. Each row shows its position, and the arrow buttons let you correct anything the drop order got wrong. Check the numbers one last time before merging a long batch.
Can I see what's inside each file before a big batch merge?
Every row has a Preview toggle that expands a grid of page thumbnails, five across. Thirty seconds of scanning those grids catches the classic batch accident: a stray statement or a duplicate invoice hiding among the month's files.
What limits apply when I combine multiple pdfs in batch?
Each source file can be up to 100 MB. The practical ceiling is your browser's memory, because every document is loaded and copied client-side; total megabytes matter more than the file count. A batch of fifty slim invoices is easy, five 90 MB scans is pushing it.
Why is every output called merged.pdf, and how do I manage that across runs?
The download name is fixed, so consecutive runs stack up as merged.pdf, merged(1).pdf, and so on. Rename each result the moment it lands, something like acme-2026-03-invoices.pdf, before starting the next client's merge. It keeps a multi-run session from turning into a guessing game.
Will bookmarks and metadata survive a batch merge?
Page content transfers intact, but document-level extras like bookmarks, outlines, and source metadata don't carry into the combined file. For invoice bundles that's rarely a loss; for structured reports, plan on the merged output being pages only.
Is there a smart way to name files before merging monthly batches?
Name sources with sortable dates, like acme-2026-03-14.pdf, so your file picker lists them chronologically and they drop into the tool already in order. It turns reordering from a manual chore into a quick visual confirmation.