The short answer: to combine many PDFs at once, use a batch merge page — select all your files, click once, download one combined PDF. For other operations (compress, split, rotate), process files one at a time for now.
"Batch processing" gets thrown around loosely, so let's be precise about what you can actually do in bulk today with free browser tools — and what's still one-at-a-time.
What batch merging does
PDFEdit's batch PDF page is built for one job: combining many PDF files into a single document in one operation.
- Select your files — all of them, dozens at once, via the file picker.
- Confirm the list — the page shows what you selected, in selection order.
- Click "Merge All into One PDF." The tool copies every page from every file (using pdf-lib, no re-rendering — so it's lossless) and downloads the combined result.
The practical limit is device memory rather than a file count. Fifty invoices? Fine on any laptop. Two hundred 50 MB scans on a phone? That's where you'll feel it — split those into smaller batches.
Batch vs. the standard merge tool
Two merge options exist for a reason:
| Batch page (/batch-pdf) | Standard merge tool | |
|---|---|---|
| Best for | Many files, one shot | Precise control |
| Ordering | Selection order | Drag-and-drop reorder |
| Speed | Fastest for large sets | A bit more setup |
Rule of thumb: if the order doesn't matter much (monthly receipts, a folder of invoices), use batch. If order matters (contract + appendix + exhibits), use the standard merge tool with drag-and-drop.
The honest limits of batching
Here's what I won't pretend: most online PDF tools, PDFEdit included, batch merging — not universal batch processing. Today:
- Batch: merging many files into one.
- One file at a time: compress, split, rotate, organize, extract, delete pages.
So the "process 50 PDFs" workflow is really: batch-merge the 50 into one file, then compress/split/rotate the combined file once. In practice this covers most real jobs — you rarely need to compress 50 files individually when one compressed merge does it.
Workaround for repetitive single-file tasks: open the tool once and run files through sequentially. It's manual but fast — each operation takes seconds, and there's no upload queue to wait on.
Batch jobs this handles well
Monthly invoice packs. Thirty invoices from a folder → one PDF → compress → send to accounting. Four steps, five minutes.
Legal bundles. Exhibits A through K → one bundle → add page numbers so counsel can cite "page 47."
Scan consolidation. A scanner that outputs one file per page: batch-merge 60 single-page scans into one document, then delete the blanks and compress.
Report assembly. Chapters written separately → one document → add page numbers → distribute.
Tips for big batches
- Order your selection deliberately. The batch page uses selection order — in most file pickers, shift-click selects a range in the displayed sort. Sort by name first if your files are named sensibly.
- Watch total size. The batch page doesn't enforce a per-file size cap, but the whole job lives in your browser's memory — very large files or dozens of heavy scans can slow things down or fail on low-memory phones. On a phone, keep batches modest.
- Verify the merge. Open the result, check the page count equals the sum of inputs, and spot-check the start of each section.
- Then post-process once. Compress the merged file, add page numbers, whatever it needs — one pass on the combined file instead of fifty passes on parts.
Preparing files for a batch merge
Batch merging is one click, but ten minutes of prep makes the result professional:
Name files for sort order. The batch page merges in selection order, and most file pickers select in the displayed sort. Name files so alphabetical order is the right order: 01-Contract.pdf, 02-Appendix-A.pdf, 03-Appendix-B.pdf. Zero-padded numbers sort correctly; 1, 10, 2 does not.
Convert non-PDFs first. Got JPGs or Word docs in the mix? Convert them: image to PDF for photos, Word to PDF for documents. The batch merger only takes PDFs, so convert stragglers before the batch.
Unlock protected files. A password-protected PDF will fail in the batch. Unlock it first, then include the unlocked copy.
Check for corruption. Open each file once in your PDF reader before a big batch. One corrupted file can stall the whole merge — finding it beforehand beats debugging afterward.
Estimate the total size. Ten 5 MB files → ~50 MB merged. If the result needs emailing, plan the compression step now, not after you've already sent a bounced email.
Batch merging on mobile
It works on phones — the batch page is just a file picker and a button — but with caveats:
- Selection is clumsier. Multi-selecting 30 files in a mobile picker is tedious. For big batches, a desktop is meaningfully faster.
- Memory is tighter. Phones have less RAM for the in-browser processing. Keep mobile batches to a dozen or so typical files; save the 100-file jobs for a computer.
- Do it on Wi-Fi. Nothing uploads, but a stable connection keeps the browser tab alive and the phone from throttling background work.
For the "client called while I'm in a taxi" scenario — five files, merge, send — mobile batch merging is perfect. For the monthly 80-invoice consolidation, wait until you're at a desk.
After the batch: the standard finishing sequence
A batch merge is rarely the last step. The usual pipeline:
- Batch merge → one big file.
- Delete the blanks/duplicates the batch revealed (delete tool).
- Rotate any sideways pages (rotate tool).
- Add page numbers so the combined document is navigable (add page numbers).
- Compress for distribution (compress tool).
Five steps, all in-browser, no uploads. The batch merge does the heavy assembly; the finishing tools do the polish. Learn this pipeline once and document assembly becomes routine instead of a chore.
Do it with PDFEdit
Batch merge PDFs — select dozens of files, one click, one combined download, 100% in-browser. For precise ordering, use the standard merge tool.
The bottom line
Batch merging is the 80/20 of batch PDF work: one page, one click, dozens of files combined. Everything else is currently one-file-at-a-time — but since most jobs end with "combine everything, then process the result once," that limitation rarely bites.
