How PDF Merging Works: Where Do Your Files Go, and When Are They Deleted?

You've got five separate PDFs: a proposal document, two invoices, a contract addendum, and a signature page. You need to combine them into a single file, in the right order, and send it to a client as one email attachment. Or maybe a university application asks you to turn a transcript, a reference letter, and a statement of purpose into one PDF. This is one of the most common — and most annoying — small problems in office life and digital paperwork.

A PDF merge tool solves exactly this need: it gathers multiple PDF files into a single file, in whatever order you want. But this article isn't just about "what" it does — it's about "how" it does it: where your files go, what happens to them there, and when they're deleted. If you work with sensitive documents, those details matter.

What does a PDF merge tool actually do?

At its core, it takes multiple PDF files and produces a single PDF output. But in practice, this covers several different use cases:

• Document packaging: Bundling separately scanned or created files — a contract, an addendum, a copy of an ID — into a single package.
• Report consolidation: Turning report sections prepared by different teams or departments into one final report.
• Invoice/accounting archiving: Collecting monthly invoices or receipts into a single yearly file to simplify archiving.
• Combining scanned pages: When you scan a multi-page document, each page can come out as a separate PDF; these need to be brought together into one file.
• Application packages: Fitting documents like a resume, cover letter, and portfolio into the "single file" format that institutions often require.

Page order is critical here. A good merge tool doesn't just append files one after another — it lets you easily change which file comes first and which comes last. On PDF Move, you do this with the up (↑) and down (↓) arrows next to each file in the list. Get the order wrong, and the "merged" file you end up with becomes a mess that needs reorganizing all over again.

What happens behind the scenes: your files' journey

Like most online file tools, PDF Move's merge tool does its work on a server, which means your files leave your device for a short time. Here's what happens, step by step:

1. You make your selection on your device. Nothing is uploaded while you pick and order your files; the list lives only in your browser. Once you've chosen at least two PDFs, the "Run" button becomes active.
2. Files are uploaded over an encrypted connection. When you click "Run", your files are uploaded over HTTPS (an encrypted connection) to the storage on our server. Each file is stored under a randomly generated name; your file's original name isn't used. The only thing added alongside them is a small list that records the order.
3. The job is queued. The server creates a merge job and puts it in a job queue. Meanwhile, your page checks the job's status every second or two, and the button reads "Processing...".
4. Pages are copied, not converted. The server creates an empty PDF and adds every page of your files in the order you set, keeping each file's own page order. Pages aren't turned into images, and the images inside them aren't recompressed. That's why selectable text stays selectable, and portrait and landscape pages or different paper sizes keep their own dimensions.
5. The result comes through a signed link. When the file is ready, a "Download result" link appears on screen. This isn't a permanent public address; it's a short-lived, signed link.
6. Files are deleted automatically. A 2-hour retention period starts the moment the job is created. When it runs out, the PDFs you uploaded, the order list, and the merged result are deleted by a cleanup task that runs on the server at regular intervals.

You don't need to create an account at any point in this process; the tool works without signing in.

So what is WASM, and does this tool use it?

WebAssembly (WASM for short) is a technology that lets code run inside the browser at close to native application speed. Libraries written in languages like C/C++ or Rust can be compiled to WASM and run directly in a browser tab, which means some file operations can be done on the user's own device without ever going to a server.

PDF Move's merge tool doesn't work that way: as described above, merging happens on the server. An earlier version of this article stated that merging was done in the browser with WASM and that files never reached a server; that was incorrect and has been corrected.

Some tools on our site do keep your document on your device the whole time: Edit PDF and Sign PDF run entirely in your browser, and your document is never sent to a server. Other tools, such as merging, conversion, compression, and OCR, process files on the server. In short, the two approaches differ like this:

• In-browser processing: The file never leaves your device, but how fast the job runs and how much it can handle depend on your device's memory and processor.
• Server-side processing: The file is uploaded over an encrypted connection and stays on the server until the retention period ends; in return, the processing doesn't depend on your device's power.

Why and when you need it

The need to merge PDFs generally arises in two situations. First, your source documents are already scattered — some are email attachments, some come from a scanner, some are reports converted from Word to PDF. Second, there's an institutional or bureaucratic requirement: many application systems, tender platforms, or official institutions require "a single PDF file" and won't accept separate files.

You can also merge PDFs with desktop office software, but that usually means installing extra software, sometimes a paid add-on. That's where the appeal of an online tool comes in: no installation, instant access, and it works regardless of operating system (Windows, Mac, even a tablet). And because the merge runs on the server, a low-powered computer or a phone is no obstacle either.

What does this mean for security and privacy?

This matters a lot, especially for anyone working with sensitive documents. Uploading PDFs with personally or commercially sensitive content — invoices, contracts, ID documents, health records — to some random "free online tool" website understandably makes many users hesitate: how long does this file stay on the server, who can access it, is there a guarantee it gets deleted?

For merging on PDF Move, here are the answers to those questions:

• Encrypted transfer: Files are uploaded and downloaded over HTTPS only.
• Limited retention: Uploaded files and the merged result are deleted automatically after about 2 hours; they aren't stored permanently.
• Unguessable addresses: Files are stored under random names, and the result is delivered through a short-lived, signed link.
• No account required: You don't need to sign up or provide any personal details to merge files.
• No sharing with third parties: As stated in our privacy policy, your files are used only for the operation you requested.

To be upfront about it: in this model, your file sits on our server while it's being processed and until the retention period ends. If your company's policy says "don't upload client documents to external servers," merging those files with PDF software installed on your computer is the better choice. For documents containing personal data, we also recommend checking your organization's data-protection policy (and any rules that apply to you, such as the GDPR or Turkey's KVKK) before uploading.

What to know before you merge

Merging carries every page over intact, but some document features don't make it into the merged file:

• Bookmarks aren't carried over. Bookmarks in the source files (the table of contents in your PDF reader's side panel) aren't transferred to the merged file; the pages themselves come through in full.
• Form fields may stop being fillable. In a PDF with a form, the fields and their values may still show on the page, but they may no longer work as fillable fields in the merged file. The safest route is to fill in the form first, turn it into fixed content with Flatten Form, and then merge.
• Encrypted PDFs can't be merged. If any file in the list has an open password or usage restrictions (encryption), the job will fail. If you know the password, remove the protection first with Remove PDF Password.
• Ordering works per file. The pages inside a file keep their own order. To rearrange individual pages or remove some of them, use Organize Pages after merging.

How it works in practice

The general flow looks like this: on the Merge PDF page, you choose your files from the "Click to add PDF files" area, and you can repeat this step to add more files to the list. Your files appear as a list of file names; you set the order with the arrows and take out any file you don't need with "Remove". Then you click "Run", and when the job is done, you get your single PDF from the "Download result" link. The total time depends largely on the file sizes and your connection's upload speed.

In the end, PDF merging is a need that seems simple but keeps coming up in everyday workflows. Whichever tool you use, knowing where your file goes, how long it stays there, and who can access it matters just as much as getting the pages in the right order.