Initializing... drag & drop files here
Supports: PDF
To merge PDF files, upload two or more PDFs to our servers, drag the file tiles into the order you want, and click Merge. The pages are concatenated top-to-bottom into one combined PDF that you download — no sign-up, no watermark, no page limits.
Real result: five separate application PDFs become one ordered file that fits a single upload slot, with every page's fonts, layout, and links preserved exactly as in the originals.
PDF is a container format defined by ISO 32000-2 — every page carries its own size, fonts, and content stream, so combining files is a clean concatenation rather than a re-layout. That makes merging (or combining) PDFs the safest way to consolidate documents without altering them.
| Goal | Use | Notes |
|---|---|---|
| Combine existing PDFs in order | Merge PDF (this page) | Page-by-page concatenation; original formatting preserved |
| Convert images + combine into one PDF | Merge Image to PDF | Wraps JPG/PNG/HEIC pages into a new PDF, then concatenates |
| Output one PDF per image | Convert JPG to PDF | Per-file output, no combining |
| Shrink the merged file | Compress PDF | Run after merge if size matters for email/upload |
| Pull pages from one PDF | Split PDF | The inverse operation — extract a page range |
| Element | Preserved? | Notes |
|---|---|---|
| Page content, fonts, images | Yes | Pages are copied byte-level; no re-render |
| Page size and orientation | Yes | Letter, A4, Legal, custom sizes all coexist in the output |
| Internal hyperlinks (same document) | Yes | Links inside a source file still jump to the right page |
| External hyperlinks (URLs) | Yes | Clickable URLs remain intact |
| Form fields (AcroForm) | Mostly | Fields carry over; duplicate field names across source files may collide |
| Bookmarks / outlines | Generally yes | Existing outlines are kept; nesting under per-file headings is not auto-generated |
| Document metadata (Title, Author) | First file wins | Output inherits the first file's metadata; edit afterward if needed |
| Digital signatures | Invalidated | Any signed PDF's signature breaks once its pages are combined with others (PDF spec requirement) |
Merging itself has no quality or size setting — pages are copied as they are. When the combined file is too large, send it through Compress PDF and pick one of the Ghostscript distiller presets:
| Preset | What it does to images | Typical Use | Output Size |
|---|---|---|---|
| Screen (Best) | Downsamples to 72 DPI | Email, web upload | Smallest |
| Ebook | Downsamples to 150 DPI | Tablets, e-readers, reading copies | Small |
| Default | Leaves image resolution untouched; re-compresses only | General cleanup | Medium |
| Printer | Caps at 300 DPI | Office laser/inkjet | Large |
| Prepress | Caps at 300 DPI, color preserved | Commercial print | Large |
"Screen (Best)" means best compression, not best quality — it is the most aggressive preset, not the safest one. Printer and Prepress only resample images that are already above roughly 450 DPI, so a normal 300 DPI scan passes through them unchanged.
XConvert does not impose a hard file-count limit — in practice the only ceiling is total upload size and time, since the files are uploaded and combined on our servers. For comparison, Adobe's free online merger caps a single job at 100 files and 1,500 total pages, with each file up to 500 pages. Most users merging document packets stay well under those numbers.
Existing bookmarks inside each source PDF are preserved in the output. What is not automatic is a new top-level bookmark for each source file — tools like Adobe Acrobat Pro add those during their Combine Files workflow, but most online mergers (including this one) keep the original outline tree and append the next file's outline below it.
Yes, form fields are carried into the merged PDF and remain fillable. The one gotcha: if two source files share the same field name (common with templated forms), the values may link together. Rename fields in the source PDFs first if you need them independent.
Per the PDF specification, any digital signature is invalidated the moment the document changes — merging counts as a change because it adds pages. If you need a signed packet, sign the merged PDF after combining, not before. The visible signature appearance stays, but verification will report "signed PDF was modified."
Each source page keeps its native size — Letter pages stay Letter, A4 stay A4, scans at custom sizes stay at custom sizes. This is intentional and matches the PDF 2.0 model (one MediaBox per page). If you need uniform sizing, convert images through Merge Image to PDF with a fixed paper-size preset instead.
Compress after merging. This page only concatenates pages — it has no compression setting of its own — so the order is: merge here, then run the combined file through Compress PDF. One pass over the merged document is also more effective than compressing each source separately, because the distiller sees every duplicated font and image at once.
PDFs often share resources (fonts, images) within a single file via cross-reference tables. When two files are concatenated, duplicate fonts and images may end up embedded twice instead of being deduplicated. In our testing, merging document PDFs that share common fonts typically yields a file a little larger than the sum of the inputs rather than smaller; running it through Compress PDF recovers most of that overhead by deduplicating and downsampling.
Yes. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up required, never shared or made public. We do not retain document contents past that retention window.
Yes, without exception. Merging is a page-level concatenation, not a re-render — text, vector graphics, images, and embedded fonts are copied without re-compression, so the combined PDF looks identical to the originals. There is no quality setting on this page to get wrong. If you deliberately want smaller pages, that is a separate step with Compress PDF.