Merge confidential PDFs on your own device, free
Combine a contract, a set of accounts, NDA paperwork or patient documents on the machine in front of you — 0 bytes uploaded, because the merge happens in your browser and not on a server.
Yes — you can merge a confidential PDF for free without uploading it. Open the merge tool in a browser tab, choose your files, and your own device joins them into one document. 0 bytes uploaded. No account, no sign-in, nothing to install, and once the page has loaded it keeps working with the network switched off.
That last detail is the whole point. If the merge finishes in airplane mode, no copy of your document was sent anywhere, which answers the question you actually came here with: not "how do I combine these files" but "where does my file go while it is being combined".
Upload-based tools are not careless. They delete their copies, usually within a few hours, and they say so in their own help pages. But a promise about a copy you cannot see is a promise you have to take on trust, and a contract, a set of accounts or a referral letter is a poor thing to take on trust. Not making a copy at all is a different and shorter argument.
This page covers why confidentiality changes the calculation, what an upload actually means for four kinds of document, how the merge works step by step, and — at some length, because it is what makes the rest believable — what Filezaar cannot do for you.
Key takeaways
- The merge runs in your browser tab. Your document is opened from your disk and written back to it; 0 bytes are uploaded.
- There is no account, so there is nothing to attach a file to, and no email address to give.
- Once the page has loaded the tool works with the network off — the simplest proof that the job is local.
- Metadata and hidden content travel with the source files. Strip it first if it should not go; Filezaar cannot redact for you.
- What it cannot do: redact text, add a password, edit a page, or open an encrypted PDF.
Why "confidential" changes the calculation
For an ordinary PDF, the question is whether the tool works. For a confidential one, the question is what happens in between.
A merge is a copy operation. Something has to read every page of every file, hold them, and write them out in a new order. On an upload site, all of that happens on hardware you did not choose, in a country you did not pick, under a retention policy you did not negotiate. The work takes seconds. The copy exists for as long as their policy says it does, and the only evidence you have that it was deleted is the policy itself.
Run the same operation on your own machine and the intermediate copy never exists anywhere but in a browser tab you can close. There is no retention period to look up and no third party to list in a disclosure note, because there was no transfer.
Two caveats, both honest. First, Filezaar holds no compliance certification of any kind — not GDPR, not HIPAA, nothing — and this page does not claim one. What it can say accurately is narrower and usually more useful: the file is never transferred, so there is no transfer to disclose. Second, if the documents are already on a managed work device, your organisation's own rules still apply to them. This page removes one problem from your list, not all of them.
What an upload actually means for a legal, financial or medical file
Think about what is inside the file, not what the file is called.
- A contract bundle carries names, addresses, a price, and often bank details for a completion payment. It also tells anyone reading it that a transaction is happening.
- A set of accounts carries account numbers, salaries, supplier terms and margins. A payroll export is a list of named people and what they are paid.
- A signed NDA carries the names of both parties and the subject matter — and in a fundraising or acquisition context, the existence of the document is itself the sensitive fact.
- A patient document carries a name, a date of birth, an identifier, and clinical detail. A referral letter is a short summary of someone's medical history.
None of that is improved by being copied to a server for ninety seconds. The risk is not that a stranger reads it; the risk is that you now have a copy you cannot see, on a machine you do not control, for a period you did not set, and you are the one who has to explain that if you are ever asked.
The local alternative is not more secure in the abstract. It is simpler: there is no copy, so there is nothing to explain.
Thursday, 4.40pm: a completion pack
The sort of afternoon this page is for. A solicitor has eleven PDFs in a folder — the contract, the transfer deed, the replies to enquiries, the mortgage offer, the searches, a lease, six more — and they need to go to the other side as one document before five. Every one of them contains a client's name and address, and three contain bank details.
The obvious move is the free online merger that ranks first. It will work. It will also put the entire pack on somebody's server in the time it takes to drag the files in, and the client — who is a director at a company that takes data handling seriously — will never be told that happened. If the matter is ever audited, the answer to "where has this file been" is a policy document rather than a fact.
The alternative takes the same amount of time. Open the merge tool in a tab, drop the eleven files in, drag them into the right order, check the page count, merge. The pack is written to the laptop. Nothing left it, and when the tab is closed there is no working copy left anywhere. The answer to "where has this file been" is: nowhere.
How to merge a confidential PDF on your own device
- Put the pieces in one folder, and look at them first. This is your redaction step, and it is the one Filezaar cannot do for you. If a page contains something that should not go out, take it out before you merge. Merging keeps everything that is in the source files.
- If any of the sources are photos or scans, turn them into one document first with Image to PDF — page size, margins and quality are yours to set.
- Strip anything hidden. A PDF or a photo can carry author names, timestamps and location data that never appears on the page. Run the files through the metadata remover if that matters for what you are sending.
- Open the merge tool. Nothing to install, nothing to sign in to. Choose your files and drag them into the order you want — order is much easier to fix here than after the fact.
- Check the page count and size shown before you save. It is the cheapest possible check that you are sending what you think you are sending.
- Merge, then save. Your browser writes the result to your device. Your originals are never touched.
- If the bundle is too big to email, shrink it with PDF Compressor — or send only the pages that were asked for with Split PDF. Sending less is its own kind of care.
- Close the tab when you are done. On a shared or managed machine, this is the step that matters: the working copy is discarded.
Worth knowing: there is no target-size control here. You choose a quality setting, not a number of megabytes, so you cannot ask for "exactly 5 MB". Compress, read the size, adjust.
What this means for four kinds of document
Legal agreements
Bundling a completion pack, a lease or a settlement means putting every sensitive page of a matter into a single file. The value of a local merge here is not speed; it is that you can answer a client's question about where their documents went with a fact rather than a link to someone's policy. Note that merging does not privilege anything and does not redact anything — a page that should not be in the pack has to come out before you start.
Financial records
An accountant sending a client's books is usually sending a year of payroll, bank statements and management accounts in one attachment. Local processing means the file never sits on a third party's infrastructure while being combined, which is the part that is hardest to explain afterwards. If the bundle ends up too large for the client's mail server, compress it or split it rather than reaching for a different tool.
NDA material
The awkward thing about NDA paperwork is that the metadata of the transaction is the sensitive part: who signed, with whom, and when. A local merge leaves no server-side record of the file being processed, and no account to tie it to. What it cannot do is stop the combined PDF carrying the author name or timestamps from the originals — strip those first if the document is going somewhere they should not.
Patient documents
A clinician sharing a referral, a consent form or a discharge summary is handling identifiers and clinical detail together, which is the combination regulators care about most. Merging them locally means no transfer to a third party to record. Be clear-eyed about what that does and does not cover: it means the file did not leave the device while being combined. It does not change your obligations as the person sending it, and it does not help if the device itself is shared or unsecured.
What Filezaar cannot do
This is the longest section on the page, because it is what makes the rest of it worth believing.
- It cannot redact. Merging copies pages exactly as they are. If a name, an account number or a paragraph needs to come out, remove it before you merge. There is no tool here that blacks anything out.
- It cannot add a password. If the combined file needs to be encrypted before it goes, you will need a different tool for that job. Filezaar has no protection or encryption tool.
- It cannot open an encrypted PDF. Password-protected files stop with a plain message. Remove the password first, then merge the unlocked copies.
- It cannot edit or rewrite a page. No PDF editor here. It joins, splits, shrinks and exports pages; it does not change what is on them.
- It cannot make a scan searchable. Text in a scanned page stays an image. No text layer is added.
- It cannot remove metadata on its own. Author names, timestamps and location data travel with the source files — use the metadata remover first.
- It holds no certification. No GDPR, HIPAA or any other compliance claim is made here, because Filezaar has none. The accurate statement is that the document is not transferred, so there is no transfer to disclose.
- It does not make a managed device safe. If the laptop is monitored, or the folder is shared, those are your organisation's controls, not ours.
If any of those is the thing you need, this is the wrong tool for the job, and you should use one that does it.
Check it yourself, in thirty seconds
You do not have to believe any of this.
- Open the merge tool and open your browser's network panel.
- Choose two files and merge them. Nothing carrying your document appears in the requests, because nothing is sent.
- Then run the test that settles it: load the page, turn on airplane mode, and merge again. If the merge finishes with no network, the work was done on your machine.
Want step-by-step instructions for inspecting the DevTools network tab? See our 30-second verification guide.
The how-it-works page sets out the four stages — choose, process, keep using the page, save — and why nothing leaves the device.
Questions
Can my employer, my client or my IT department tell I used this?
Partly, and it is worth being precise. A request to load filezaar.com leaves a record in ordinary network logs — DNS lookups and connection records — the same as any website. If your device runs endpoint monitoring that records browser activity, that is your organisation's software on your machine, and nothing on this page can affect it. What nobody outside your device can see is the document or anything inside it, because the file is never transmitted. If the question you are really asking is whether the contents of a contract, a set of accounts or a referral letter left your network, the answer is no.
What happens if I close the tab halfway through a merge?
The job stops and the working copy is discarded. Nothing half-finished is kept anywhere, because nothing was ever sent anywhere — there is no server holding a partial file. Your original documents are untouched; the tool reads them and writes a separate result. Reopen the tool and start again.
Can I use this on a locked-down work laptop?
There is nothing to install, which removes the usual objection, and it runs in any current Chrome, Edge, Firefox or Safari. But a managed device can block the site outright through a proxy or an allowlist, and some locked browser profiles restrict file access. If it loads, it works; if your organisation blocks it, that is a conversation with your IT team, not something a browser tool can work around.
Is merging this way compliant with GDPR, HIPAA or similar?
Filezaar holds no such certification and this page claims none. What can be said accurately is that the document is not transferred to a third party while it is being combined, so there is no processing disclosure to make for the merge itself — which removes one of the questions you would otherwise have to answer. It does not remove the rest. Your obligations as the person sending the document are unchanged, and if it lives on a managed device your organisation's policies still apply to it.
Does the combined PDF carry hidden data from the originals?
Yes. Whatever the source files contain travels with them — author names, creation timestamps, and, on photos, location data. None of that is visible on the page, and merging does not remove it. If it should not go out, run the files through the metadata remover first, then merge.
Do you keep a copy of what I merged?
No. There is no copy to keep. The files are read from your disk, worked on in the tab, and the result is written back to your device; closing the tab discards the working copy. The only things stored are your theme preference and a short list of recent tools, both in your own browser — see the privacy page.
Will merging reduce the quality of my documents?
No. Pages are copied across exactly as they are, so text stays selectable and images keep their original resolution. If you need the result smaller, compress it afterwards as a separate step.