How to Verify a PDF Merger Doesn’t Upload Your Files
You have a PDF you would rather not hand to a stranger’s server — a signed contract, a payslip, a medical report, a client’s draft. You also have ten minutes and a merge to do. So the real question isn’t which button to click; it’s whether the file stays in your browser tab or quietly travels somewhere else.
Vendors will happily answer that question in a privacy paragraph. That is not verification. This article is about checking the claim yourself, with the browser you already have open, in about as long as it takes to merge the document anyway.
Why Verification Matters Before You Merge Anything
A cloud-based PDF merger often requires you to upload the file to a server, which is convenient but creates a data-handling risk. You are not just merging pages — you are creating a copy of a document on infrastructure you don’t control, under a retention policy you probably haven’t read, governed by a jurisdiction you may not know.
The goal here is modest and practical: not to take a vendor’s word for it, but to check the claim yourself in a few minutes. You don’t need a security team, a packet analyzer, or a vendor questionnaire. You need one test file and the Network panel.
If you want the conceptual background first — what “local processing” actually means, and why it changes the risk model — the companion piece What Is Local PDF Processing and Why Should You Care? covers it. This article stays on the verification angle.
What a Real Proof of Local Processing Looks Like
“Local” is not a vibe. It’s an observable behavior with three signals:
- The browser opens the file. You pick or drop the PDF, and the tab reads it — the file never becomes a request body.
- Pages are rendered client-side. Thumbnails, previews, reordering — all of that happens from data already in the tab’s memory.
- The export is produced without a round trip. When you click save, the browser assembles the output and writes it to your downloads, rather than asking a server to build it.
There are three broad options when you need to merge or split a PDF:
- Full cloud upload. Maximum convenience, minimum control. The document leaves your machine by design.
- Desktop software. The file stays local, but you install and maintain an application, and you still have to trust the vendor’s binary.
- Browser-based tools that keep the document in the tab. Convenience of the web, plus something you can actually watch.
PdfMerge sits between those two extremes. It gives you browser-based convenience without the upload step of a typical cloud merger. You do not need to install anything, and you can inspect the network behavior yourself.
What does not count as proof:
- A “privacy first” badge on the marketing page.
- A single sentence like “your files are never stored” in a help center article.
- A trust logo, a compliance sticker, or a blog post asserting the same thing you’re trying to verify.
Those are claims. A Network panel is evidence.
Step-by-Step: Verifying PdfMerge in Your Browser
The whole procedure is: load a throwaway document, open DevTools, do the real work, and read what happened. Five minutes, start to finish.
Step 1: Confirm the app is an ordinary web page
Open https://pdfmerge.rsj.de in a normal tab. If you like a sanity check before you load anything, you can see what the page is served as:
curl -s -o /dev/null -w "status=%{http_code} type=%{content_type}\n" https://pdfmerge.rsj.de
That tells you it’s a plain HTTPS page — nothing exotic. The interesting part comes next.
Step 2: Load a test document, not the real one
First pass, use something you don’t mind exposing: a two-page export from a public PDF, a dummy invoice, anything disposable. Merge it with a second throwaway file, or split it into parts. You’re validating the workflow, not the confidentiality of the content.
Step 3: Open the Network panel before you act
In Chrome, Edge, or Firefox, press F12 and go to the Network tab. Then:
- Clear the list so you start from an empty state.
- Enable Preserve log so a reload or navigation doesn’t wipe the evidence.
- Keep the filter on All (or switch to Fetch/XHR when you want to look only at scripted requests).
Get the panel open before you drop the file. Requests that happen during the merge are the ones you’re here to see.
Step 4: Do the work and watch the panel
Drag your test PDFs in. Reorder pages by dragging. Select several pages and move or rotate them together. Split the document into parts, give a part its own title line, then export.
During the operation, the Network panel should look something like this:
Name Status Type Notes
document 200 document the app shell itself
main.<hash>.js 200 script editor code
main.<hash>.css 200 stylesheet layout
inter-<hash>.woff2 200 font UI font
-- no POST with your file, no multipart/form-data, no upload endpoint --
That is the shape of a clean result: assets the page needs to render, and nothing carrying your document.
Then complete the workflow end to end, because a partial test proves very little:
- Export one PDF per part.
- Export one merged PDF.
- Export a ZIP of all parts.
- Print, if printing is part of your job.
Each of those is a separate code path. Watch the panel during each one. If splitting is the workflow you care about most, our walkthrough on how to split a PDF into multiple files in your browser goes deeper on the feature itself — this article stays on the inspection.
Step 5: Repeat it with the Chrome extension
The extension is worth checking separately, because a toolbar workflow is where people assume the magic — and therefore the upload — happens. It doesn’t: the extension opens RSJ PDF Merge, Sort & Split from https://pdfmerge.rsj.de and hands the PDFs to the editor, reusing an already open editor tab instead of opening a new one. The editor URL is configurable on the extension’s options page.
Because the editor is the same app doing the same browser-side processing, the same Network panel check applies. Keep DevTools open on the editor tab while you capture a PDF from the toolbar, and read the requests exactly as before.
One note: because the extension reuses an open editor tab, requests may land in that tab rather than a new one. Watch the tab where the editor is actually running.
Step 6: The hard way (optional, and mostly unnecessary)
You could go further — capture raw request logs, or write your own interception script to log every outbound call. It’s possible, and it’s occasionally interesting for a one-off audit. But once you’ve watched the Network panel through a real merge, a real split, and a real export, the extra machinery buys you very little for the effort.
Interpreting What You See, and the Edge Cases
Reading the panel is a skill with a short learning curve. Here’s what separates the boring from the suspicious.
Expected traffic:
- The app shell, JavaScript, CSS, fonts, icons, language files — all from the app’s own origin.
- Requests that fire on page load, not on file drop.
Worth a second look:
- A
POSTorPUTthat fires exactly when you drop a file or click export. multipart/form-databodies, or any request whose size roughly matches your PDF.- Requests to a domain unrelated to the app, timed to your file operations.
Edge case: Google Drive. PdfMerge can open a file from Drive using Google’s picker, and save the result back to Drive. Those flows involve Google’s own services — a separate step you choose explicitly. The merge, sort, and split work itself happens in the browser, so you can verify that part independently of the Drive integration. If Drive isn’t part of your workflow, don’t enable it during the test.
Edge case: caching. If the page is served from cache, you’ll see fewer requests than you expect. Tick Disable cache in DevTools and reload so you start from a clean slate.
Edge case: your own setup. Extensions, proxy configurations, or a corporate network can add traffic that has nothing to do with the tool. Re-run the check in a clean profile if the noise makes the reading ambiguous.
And the honest caveat: a single observation is a signal, not a full security audit. The practical standard is to repeat the check on the exact workflow you actually care about — your file type, your merge, your export — and then proceed.
If you’re a developer embedding the same editor in your own product via the SDK, the guarantee is the same shape and the check is the same:
npm install @rsj-de/pdfmergesortsplit
Documents are still processed in the visitor’s browser, and the SDK runs in a free, unrestricted test mode with a banner until a licence token is applied — so you can verify the behavior before you buy anything. Configuration details live at pdfmerge.rsj.de/docs.
Making Local Processing Your Default Habit
Verification is a habit, not a one-time ceremony. The checklist that fits in your head:
- Open the tool.
- Load a throwaway file.
- Open the Network panel and clear it.
- Run the actual operation end to end.
- Read the requests. Then — and only then — load the real document.
PdfMerge processes PDFs entirely in the browser and never uploads them, so this check should come back clean on merge, split, and export. The tool is free, with no licence key, no account, and no watermark, which means you can run the check without signing anything.
For the wider comparison — what you give up and what you gain versus installed software — see Browser-Based PDF Merger vs Desktop Software: Which Is Better?.
FAQ
Can a browser-based PDF merger upload my file without me noticing?
It can only do so through network requests, which is exactly why the Network panel is the practical check. Load a test document, run the merge or split, and watch for requests during the operation. If the document is processed in the browser, you should see only the assets the page needs to render — not an upload of your file.
Does the Chrome extension send my PDF somewhere?
The extension opens RSJ PDF Merge, Sort & Split from https://pdfmerge.rsj.de and hands the PDFs to the editor, reusing an already open editor tab instead of opening a new one. Because the editor processes documents in the browser, the same Network panel check applies to the extension workflow.
Does using Google Drive with PdfMerge mean my file is uploaded?
Opening a file from Drive or saving the result back to Drive involves Google’s own services, which is a separate step you choose explicitly. The merge, sort, and split work itself happens in the browser, so you can verify that part independently of the Drive integration.
How do I check a PDF merger that does not run in the browser?
You cannot inspect network behavior for a desktop application the same way. That is the trade-off: browser-based tools let you watch requests directly, while desktop software requires trusting the vendor or monitoring system-level traffic. For a deeper comparison of browser-based and desktop workflows, see the article Browser-Based PDF Merger vs Desktop Software: Which Is Better?.
Conclusion
The takeaway is simple: you can verify instead of trust, and the Network panel is enough for a practical check. A tool that keeps your document in the tab will show you assets and nothing else, every time you look.
PdfMerge is the version of that idea you can try right now — free for everyone, no account, no watermark, with every page processed in the browser rather than on a server.
Next step: open https://pdfmerge.rsj.de, load a test file, and watch the Network panel once. Five minutes, and you’ll never have to take a privacy claim on faith again.
Related posts
- No Account, No Watermark: Choosing a PDF Merger
- How to Split a PDF into Separate Files with Their Own Titles
- How to Automate PDF Merge and Split Workflows in Your Web App