Merge PDF Files — Free, Online, No Signup
Add multiple PDFs, reorder them (drag & drop or arrows), then merge in one click. Mobile-friendly UI.
Add PDFs
Quick tools
Files to merge (0)
PDF merge & split FAQ
Everything about lossless PDF merging, splitting, and page extraction on Omnvert—security, syntax, performance, and quality.
Yes. We rely on qpdf’s page-level assembly (`--pages`) instead of rendering through Ghostscript or LibreOffice. Text, vectors, forms, bookmarks, and embedded fonts stay intact; only the page tree is rearranged. When you toggle the optional “lossless recompress,” we run `--stream-data=compress --object-streams=generate`, which repacks streams without changing visual content.
Use qpdf syntax: `1-3` (inclusive range), `5` (single page), `7-` or `7-z` (from page 7 to the last). Combine with commas, e.g., `1-3,5,7-`. The UI validates and normalizes input, stripping any characters outside digits, commas, dashes, spaces, and `z`.
Each job runs in `/tmp/omnvert-pdf/<jobId>/` with random UUIDs for filenames, so user-supplied names are never used as paths. Files live only for the duration of the request; once the response stream finishes, we delete the folder in a `finally` cleanup step. No long-term storage or cross-job reuse occurs.
Uploads are capped at 50 MB per PDF for these tools, with a 30s execution timeout per qpdf call. A lightweight in-memory queue limits concurrent heavy jobs (default 2) to protect CPU and memory. Large PDFs are streamed to disk rather than buffered in RAM to avoid spikes.
Internal links, outlines, and metadata are preserved because we are not rasterizing pages. Digital signatures may break if you split or merge in ways that alter the signed structure—this is expected for any structural edit. If you must keep signatures, avoid structural changes or re-sign afterward.
qpdf rewrites the PDF object graph without rendering content, so vectors, embedded fonts, and transparency stay identical. It is fast, scriptable, and stable on Linux servers, and it avoids image downsampling that visual converters often introduce. That matches Omnvert’s goal: precise, high-fidelity document tools without lossy surprises.
For merging, add files in the exact order you want and optionally constrain each file with ranges (e.g., File A: `1-5`, File B: `all`). For splitting, pick “Split by ranges” and define chapter breaks like `1-10,11-22,23-30`; you’ll receive a ZIP with one PDF per range. “Per-page” creates one PDF per page for fine-grained work.
Recompress asks qpdf to recompress streams and regenerate object streams. It can shrink PDFs that contain uncompressed streams while keeping visuals identical. It is optional because some PDFs are already optimized; when there’s nothing to gain, output size will be similar while still remaining lossless.
If you see “invalid range,” double-check for typos and keep ranges ascending. For “file too large,” trim inputs or compress separately. Password-protected PDFs are not supported. Corrupted PDFs may fail `--show-npages`; try re-saving with a viewer first. If a job times out, split the work into smaller ranges or fewer files.
This tool uses a server-side service for processing; uploaded files or requests are not kept for long-term storage.
About
Merging multiple PDFs into one is one of those operations that occupies a strange middle ground in office life — it comes up constantly, almost everyone has done it at least once, and yet there's no obviously right tool to reach for that doesn't either gate the operation behind a paid plan, slap a watermark on the output, or cap the number of files you can combine. The actual operation is technically simple: PDF as a format already supports concatenation, the page streams from multiple files just get appended in order, and the result is structurally a normal PDF that any reader opens without issue. The complications come from the surrounding details — preserving bookmarks across files, maintaining consistent page numbering, handling rotated pages, recompressing if the output is too large — and those are what distinguish a usable merge tool from a bad one.
The cases that drive most everyday merging are predictable: an expense report where five different receipts need to land in a single PDF for finance to attach to the reimbursement, a signed contract where three separate amendments need to follow the base agreement in chronological order, a multi-author report where each writer produced their section as a separate PDF, a school assignment that combines a handwritten cover page (scanned to PDF) with a typed body and an appendix of supporting images, an immigration application where six supporting documents need to arrive as a single submission. The pattern is always the same: multiple PDFs, in a specific order, becoming one cohesive document. The tool collapses the operation into drag-reorder-merge.
Order is the part most other tools handle badly. The drag-to-reorder interface here exists because the alphabetical order in which files arrive in a folder almost never matches the reading order the recipient needs. Receipts from a business trip are typically named by date or vendor, neither of which corresponds to how finance wants them displayed. Contract amendments come with whatever filenames the lawyer gave them, which may or may not reflect the order they should appear. Being able to drop the files in, then drag them into the right reading order before merging, is the difference between a merge tool that actually saves time and one that creates a follow-up cleanup task because the page order came out wrong.
Rotation is the second detail that catches people out. Scanned PDFs sometimes arrive with pages oriented sideways because of how the scanner picked them up, photo-PDFs from phones often have pages in mixed orientations, and old archived PDFs from before scanners got good at orientation detection sometimes have a few pages that opened correctly individually but look strange when stitched into a longer document. The per-file rotation option in the merge interface handles this without requiring a separate trip through a rotation tool — flip the affected file 90 or 180 degrees as part of the merge operation, and the resulting combined PDF has consistent orientation throughout.
Bookmark and table-of-contents preservation is a subtle feature worth understanding because it distinguishes professional merge tools from quick-and-dirty alternatives. Source PDFs that contain bookmark hierarchies (most reports, books, and structured documents do) should produce a merged PDF where each source's bookmarks become a section under a parent bookmark named for the source file. The result is a single PDF whose navigation pane lets you jump to any section of any source file as if they were chapters of a single book. Bad merge tools strip bookmarks entirely, producing a flat document that might be hundreds of pages but offers no navigational structure. The path here preserves bookmarks where the sources have them, which means a 500-page merged report stays usable rather than becoming a wall of text.
Page numbering is another decision worth being deliberate about. Default behaviour is continuous page numbering across the merged document — page 1 of the first source becomes page 1 of the merged output, the second source's pages continue from where the first left off, and so on. This is what most readers expect for a single coherent document. Some workflows benefit from preserving the original per-source numbering (a court submission where each exhibit needs to retain its own internal page count, for example), but that's a niche case; the continuous numbering default works for the vast majority of everyday merging.
File-size considerations come up more often than people initially expect. A merge of ten scanned PDFs at 5MB each produces a 50MB output, which immediately runs into email attachment limits at most companies (typically 10-25MB) and shared-drive quotas at others. The recompression option in the merge tool addresses this by passing the merged output through a compression pass before download, which can reduce size by 30-60% depending on the source content. For everyday use the recompression is opt-in rather than mandatory, because some merges (legal exhibits, archival material) need to preserve the original byte-perfect content, and the user knows their case better than a tool's default ever could.
Multi-author collaboration is one of the bigger drivers of regular merge usage. A research paper assembled from three authors' separate sections needs to come together as a single PDF for submission. A corporate report where finance, sales, and operations each produced their own section needs to land as one document for board distribution. A wedding album combining photos from multiple guests' contributions needs to be assembled in chronological order. In all of these the merge step is the final assembly that turns parallel work into a single deliverable, and the per-source quality is preserved through the merge so each contributor's section looks the way they intended.
There's an interaction with signed PDFs worth being aware of. PDFs that carry digital signatures protect the file's bytes at the moment of signing; merging signed PDFs with other content invalidates the signatures, because the merged output's bytes are different from the signed source's bytes. For documents where signature validity matters (executed contracts, legal exhibits, regulatory submissions), the typical pattern is to merge first and then sign the result, rather than merging already-signed components. If the existing signatures must be preserved through the merge, the right answer is keeping the source PDFs separate and providing them as a bundle rather than a single concatenated file.
There's a small but useful detail about how the tool handles inconsistent page sizes across source files. Some merges combine PDFs that were originally generated at different page sizes — A4 alongside US Letter, a portrait scan alongside a landscape report, a small note-card sized PDF alongside a full-page document. The default behaviour preserves each source's original page size in the merged output, which means the resulting PDF has pages of varying dimensions. This is usually correct because trying to normalise everything to a single size would require either cropping content or adding white space margins, both of which compromise the source. Readers handle mixed page sizes without any issue; printers may need orientation auto-detection enabled to print mixed sizes correctly.
Comparing this with the alternative of working in a desktop tool is worth a moment. Most desktop PDF editors (Acrobat, PDF Expert, Preview on macOS) can merge PDFs, and for someone who has the licensed software installed those tools work fine. The case for a web-based merge tool is twofold: people who don't have desktop software installed, and people who do have it but find the web flow faster for one-off merges. Acrobat's merge interface is genuinely capable but loads slowly compared to a browser tab; Preview's merge is built into the file viewer and works well on Mac but has limited options. The web tool is fastest for small jobs and avoids the licence overhead for people who don't already pay for a PDF editor.
Operationally the tool takes a single drop. Add the PDFs in any order, reorder them by drag in the stack, optionally rotate individual files, optionally enable recompression, click merge, download the result. Files are processed in temporary storage, links expire quickly, no signup is required, no watermark is added, no per-day quota counts down in the background, no cover page is added by the tool. Multiple merges can run through one after another without hitting limits, useful when assembling several different document packages in one sitting rather than a single one-off merge. Most merges complete in a few seconds; very large multi-source merges of multi-hundred-page sources take proportionally longer but still finish in a single pass.
Use cases
- Join signed agreement pages and annexes into one delivery file.
- Compile receipts or statements into monthly or quarterly bundles.
- Build a pitch deck from separate PDFs without losing order.
- Bundle homework, scans, or application documents into one upload.
How it works
- 1Add PDFs (drag & drop) and arrange them with drag handles or sorting.
- 2Optionally enter page ranges per file and toggle recompress for smaller output.
- 3Merge and download instantly without watermark.
FAQ
How many PDFs can I merge?
Designed for common workflows with several files; dozens work, very large stacks may take longer.
Will quality drop?
By default we keep original streams; optional recompress reduces size if you enable it.
Can I pick specific pages?
Yes—enter ranges like 1-3,5 per file to include only what you need.
Do you watermark files?
No. Output PDFs remain clean and temporary.