Merge PDF Files Online — Free, No Upload
Add the PDFs you want to combine, put them in the order you want them, and download one file. The merging runs in your browser — there is no upload, no queue and no server copy — so a contract, a medical scan or a passport photocopy never leaves your machine.
Drop PDFs here or browse
Several at once · drop more later to add them to the list · nothing is uploaded
This browser cannot unpack compressed PDFs, so it cannot read them either. Try the current version of Chrome, Edge, Firefox or Safari.
What merging actually does to the file
A PDF is not a picture of a document. It is a small database: numbered objects — dictionaries, arrays, numbers and compressed streams — with a cross-reference table at the end recording the byte each object starts at, and a tree of page objects hanging off a catalog. A page is a dictionary that points at its content stream, its fonts, its images and its annotations. It does not contain them. It refers to them by object number.
So merging is a copy-and-renumber job. Every page is copied into a new file with everything it points at, object numbers are reassigned so that two files which both called something "object 14" stop colliding, a fresh page tree lists the pages in your order, and a new cross-reference table goes at the end. The content streams — drawing instructions, embedded fonts, image data — cross over byte for byte, in the compression they already had.
Why merging is lossless and compressing is not
Because nothing is decoded. The JPEG inside page four of your second file arrives in the output as exactly the same bytes; the tool never turns it into pixels, so there is nothing to degrade. Text stays text, vector art stays vector art, and a 300 DPI scan is still a 300 DPI scan. Each page's size and rotation come across too, because both are numbers in the page dictionary rather than something done to the pixels — a page rotated 90 degrees in the source is still rotated in the result.
A compressor works the other way round. It opens the images, throws away detail, re-encodes them smaller, and often subsets or drops fonts. That is why "merge, then compress" produces a smaller file than merging ever will on its own, at a cost you can see when you zoom in. Merging changes the size of the result by a rounding error.
What does not survive the merge
The pages survive. The document-level furniture mostly does not, and it is better to know that now than after you have sent the file:
- Bookmarks and the outline panel. The outline is a structure hanging off the catalog, not off the pages, and the merged file gets a new catalog. Chapter bookmarks are gone.
- Form fields stop working. A page's form widgets are drawn in the output, but the document-level form that gave them names and values is not rebuilt, so the fields come across as pictures of fields. If someone filled the form in, export or flatten it before merging.
- Internal links can miss. A link to "page 40" points at a specific page object. When that page is copied later than the link that references it, the link resolves against a copy rather than the page in the new tree, and lands nowhere. Links to a website still work.
- Attachments, page labels and metadata. Title, author, the roman numerals on a preface, embedded files: none of it is carried over. The merged file has no metadata at all, which is a privacy win as often as a loss.
- Digital signatures break. A signature covers the exact bytes of the file it was applied to, and a merge writes new bytes. Any merge invalidates it — in any tool, not just this one. That is what a signature is for.
How large will the merged file be
Roughly the sum of the parts, because nothing is recompressed. Within one source document, objects shared between pages — the font used on all forty pages, a logo repeated in every header — are copied once. Across documents nothing is shared: merge two copies of the same 4 MB brochure and you get an 8 MB file, since the tool compares object references rather than content and has no way to know the two are the same thing.
Where this tool stops
Everything happens in this tab, with no server to fall back on:
- Password-protected files are refused, not opened. An encrypted PDF is named in the list and skipped. Removing a password is the owner's job, in the application that set it.
- There is no preview. Drawing a PDF page needs a font engine and a rasteriser, several megabytes this page will not make you download. You order files by name and page count, not by thumbnails.
- Pages inside a file cannot be reordered here. Merging takes whole files: every page of the first, then the second. Moving pages around inside one document is a different job, and interleaving two documents means splitting them into pieces first and adding the pieces in the order you want.
- A file it cannot take apart is skipped, not half-merged. Some PDFs store their page structure with a compression this tool does not carry — LZW is the one still in circulation. Those files are reported as unreadable and left out, and the message says only that the file could not be read, not which compression was to blame. Re-saving from the application that made it is the fix. Image data is a different matter, because it is copied without ever being decoded: a page that opens at all brings its pictures across whatever they were compressed with.
- Memory is the real limit, not a file count. A hundred one-page invoices is nothing; six 200 MB scans are all held in one tab at once, and a phone gives up before a laptop does. Past about 100 MB the tool warns you — if it fails, merge in two batches and merge the results, which costs nothing because merging is lossless.
- No conversion. This does not turn a PDF into Word, extract its text or run OCR on a scan. It moves pages between files, which is a different job.
Frequently asked questions
How do I merge PDF files without uploading them anywhere?
Use a tool that runs in the browser rather than on a server. This page reads the files with JavaScript on your own device, builds the combined document in the tab’s memory and hands it back as a download. Open your developer tools and watch the Network tab while you merge: there is no request, and unplugging the internet after the page loads does not stop it working.
Does merging PDFs reduce the quality?
No. Merging copies each page’s content stream across byte for byte without decoding it, so images, text and fonts are identical to the originals. Quality loss comes from compressing a PDF, which re-encodes the images, and that is a separate operation.
Why is my merged PDF so large?
Because the size of a merged file is roughly the sum of its inputs: nothing is recompressed, and identical content in two different files is copied twice rather than shared. If the total is too big for an email, compress the merged file afterwards, or check whether one input is a scan saved as full-resolution images.
Can I merge a password-protected PDF?
Not without removing the password first. An encrypted PDF is refused rather than circumvented: the file is named in the list, skipped, and the rest of the batch still merges. Open it in the application that created it, save an unprotected copy, and add that instead.
Is there a limit on how many PDFs I can combine?
There is no fixed limit on the number of files, only on memory, because everything is held in one browser tab. A hundred small documents is fine; a handful of very large scans may not be. Past about 100 MB of input the tool warns you, and if a merge fails you can do it in two batches and merge the results.
Do bookmarks and form fields survive the merge?
No. Bookmarks live on the document catalog rather than on the pages, so the merged file starts with none, and form fields come across as drawn but inert because the document-level form is not rebuilt. Flatten a filled-in form before merging if the values matter.
Last updated September 19, 2026