Merge PDF Files Online for Free

PDF Merge: Combine Multiple PDF Files Into One Document

A PDF merge tool takes two or more separate PDF files and stitches them into a single document, page order intact, with nothing rasterized or flattened along the way — every page keeps its original text, vectors, and embedded fonts exactly as they were in the source file. This tool does the combining with pdf-lib, a JavaScript PDF library, running directly in your browser: pick your files, arrange them in the order you want the final document to read, and click merge. There's no upload queue to wait on and no server round trip in the way, because the library that builds the merged file is loaded into the page itself and does the work on your own machine.

Merging shows up constantly in ordinary paperwork. A signed contract arrives as three separate scans from a copier. A grant application needs a cover letter, a budget PDF, and a set of supporting letters combined into one submission. A set of monthly invoices needs to become a single quarterly bundle before archiving. In every one of these cases the underlying task is identical — take N PDFs, decide an order, produce one PDF — and that's exactly what this tool is built to do without asking you to install desktop software or learn a command-line utility.

How to Merge PDFs With This Tool

1. Drop your PDF files onto the upload area, or click it to open a file picker — you can add them one batch at a time and keep dropping more in afterward, up to 20 files in a single session.
2. Each file appears in a list with its name and size, numbered in the order it will appear in the final document. Drag any row by its handle to move it earlier or later in that list — this is the only control over page order, so get it right before merging.
3. Remove a file from the list with its X button if you added the wrong one, without having to start the whole selection over.
4. Once at least two files are queued, a Merge button appears. Click it and pdf-lib reads each file, copies its pages in full fidelity, and appends them to a single new document in the order shown in the list.
5. When merging finishes, a summary shows how many source files went in and how many total pages came out, plus the resulting file size, with a Download button for the combined PDF.
6. A "Merge more PDFs" option resets the tool so you can start a fresh combination without reloading the page.

The whole sequence — upload, reorder, merge, download — happens without an account, a save step, or any indication that a file went anywhere beyond the browser tab it's open in.

Why People Combine PDFs So Often

• Assembling a submission from parts. Job applications, grant proposals, and legal filings are frequently built from documents that were created separately — a resume from a word processor, a reference letter as its own scan, a portfolio exported from design software — and the recipient usually wants one file, not an email with five attachments.
• Consolidating scanned paperwork. A flatbed or all-in-one scanner often produces one PDF per pass, so a ten-page signed agreement fed through a few pages at a time comes out as several small PDFs that need to become one before filing or sending back.
• Building a periodic archive. Combining a month's worth of individually-generated invoices, receipts, or statements into a single quarterly or yearly PDF makes long-term storage and later searching far easier than keeping dozens of loose files.
• Bundling a report with its appendices. A main report generated from one tool and supporting data exported from another routinely need to travel as one document rather than as a set of files the reader has to open separately and match up themselves.
• Recombining a document you split earlier. After extracting or removing a page with a splitting tool, putting the remaining pieces back together into one file again is the same underlying operation as merging from scratch.

What Happens Inside a Merge

Structurally, a PDF is a tree of objects — pages, fonts, images, and the content streams that describe what's drawn on each page — all referenced by an index at the end of the file. Merging two PDFs isn't concatenating their bytes; it means reading the object tree of each source document, copying the specific objects that make up its pages (and everything those pages reference, like an embedded font or an image), and re-numbering everything into one consistent object index for the new file. pdf-lib's copyPages function does exactly this: for each source file it walks the requested page indices, deep-copies every object a page depends on, and appends the result to the destination document, which is why a merged file's text stays selectable and its embedded fonts stay intact rather than getting flattened into a picture of the page.

Step	What happens	Why it matters
File validation	Every input is checked for the PDF file signature before anything is parsed	A renamed non-PDF file is rejected immediately with a clear message instead of a confusing crash partway through
Page copying	Each source document's pages are deep-copied, not re-rendered	Text stays selectable, vector graphics stay sharp, and embedded fonts are preserved
Re-indexing	Copied objects get new IDs in the destination file's object table	Prevents ID collisions between documents that were authored independently
Page-count check	The running total of pages is capped at 500 as files are added	Keeps the operation predictable and bounded rather than open-ended

That 500-page ceiling is a combined limit across everything you're merging, not a per-file cap — three 150-page reports would already be close to it, while a stack of short one- and two-page scans has a lot more room. If you're merging exactly the two files this tool requires as a minimum, the total simply needs to fit under that number, which the vast majority of everyday document-merging tasks do comfortably.

Order Matters More Than It Seems

Because pages are appended in the exact sequence the source files are processed, the order you arrange your files in before clicking merge is the order they'll appear in forever after — there's no separate "reorder pages" pass once the combined document exists. It's worth double-checking the list before merging, especially when working from files with similar names (three scans all called "scan1.pdf" from different folders, for instance) where it's easy to lose track of which physical document corresponds to which row. If a merge does come out in the wrong order, the fix is simply to run it again with the rows rearranged — nothing about the process is destructive to the original files, since they're only read from, never modified.

Merging Large Batches Without Losing Track

A handful of files is easy to keep straight by eye, but a merge involving a dozen or more similarly-named scans benefits from a quick pass of renaming before you even open the tool — "01-cover.pdf," "02-budget.pdf," and so on — so the order shown in the reorder list matches what you'd expect just from reading the filenames, rather than relying purely on memory of which row is which. Because the entire operation runs inside your browser tab using your device's own processing power, merging a large number of files or a few especially large ones simply takes longer on modest hardware than it would on a fast desktop; there's no server-side queue to wait behind, but there's also no way to speed up a big merge beyond what your own machine can do. For a merge that's timing out or feeling sluggish in the tab, splitting it into two smaller merges — combine the first half, then merge that result with the second half — is a reliable workaround that keeps each individual step light.

It's also worth knowing that PDF as a format has no problem with a merged document containing pages of different sizes side by side — a merge can freely combine a letter-sized report with a wider landscape spreadsheet export or an oddly-proportioned scanned receipt, and every page simply keeps its own original dimensions in the combined file. There's no forced resizing or cropping to make everything uniform, which is exactly what you want when the source files were never meant to share identical page dimensions in the first place.

Privacy When Combining Sensitive Paperwork

The documents people merge are often the opposite of throwaway — signed contracts, tax paperwork, medical intake forms, identity document scans bundled for a visa or loan application. Because this tool runs pdf-lib inside the browser tab itself, the files you drop onto it are read, combined, and turned into a downloadable result entirely on your own device; at no point does the merge operation described above open a network connection to send your PDFs anywhere. If instead you're calling the merge functionality through this site's metered API — useful for scripting a recurring merge job rather than doing it by hand in a browser — that request necessarily carries your files to the server over HTTPS, since an API call has no other way to deliver input; the server runs the identical pdf-lib merge logic, streams the combined file back in the response, and does not retain your uploads afterward. Choose the browser tool when a file should never leave your machine, and the API when you need the same merge folded into an automated pipeline.

Is there a limit to how many PDFs I can merge at once?

The on-page tool accepts up to 20 files per session, and the combined output is capped at 500 total pages across every file you include. Most everyday merges — a handful of scans, a report plus its appendices — land well within both limits.

Will merging change the quality or formatting of my pages?

No. Pages are copied at the object level rather than rendered to an image and reassembled, so text remains selectable, vector artwork stays crisp at any zoom level, and embedded fonts travel with the document exactly as they did in the source files.

Can I merge a password-protected PDF?

Not directly — an encrypted PDF can't be read and copied like an ordinary one until it's decrypted, so remove its password with a dedicated unlock tool first, then merge the resulting file.

What if one of my files isn't actually a PDF?

Every upload is checked for the standard PDF file signature before the merge begins, so a file that's been renamed with a .pdf extension but isn't really a PDF is rejected with a clear message rather than silently breaking the merge partway through.

Does the merged file keep bookmarks or hyperlinks from the originals?

Page content, embedded fonts, and images all carry over faithfully; document-level extras like a bookmark outline are not reconstructed in the merged output, so treat the result as the combined pages themselves rather than a full one-to-one clone of every source file's metadata.

Can I merge PDFs that have different page sizes or orientations?

Yes. A merged document has no requirement that every page share the same dimensions — a portrait report, a landscape spreadsheet export, and an odd-sized scanned receipt can all sit in the same combined file, each keeping its own original page size.

Related Tools

Once a set of PDFs is combined, a few companion tools handle what typically comes next. Use PDF split if you need to break a document back apart into individual pages or ranges, or PDF page rotator to fix any pages that came from a scanner sideways or upside down before they went into the merge. If the combined file needs to travel with a "draft" or "confidential" label, run it through PDF watermark, and if the finished document is larger than you'd like to email, PDF compress can shrink it without re-merging from scratch.