How to Check If a PDF Merger Keeps Your Files Private
You picked a PDF merger because it promised to be private. But promises are cheap, and “we never store your files” is printed on almost every tool’s landing page — including the ones that upload your document the moment you drop it in. The good news: how to check if a PDF merger keeps your files private isn’t a question you have to take on faith. It’s a question about network traffic, and you can answer it yourself in about five minutes with nothing more than your browser’s developer tools.
This article shows what counts as real evidence of local processing, how to run the check step by step, what the results do and don’t prove, and how RSJ PdfMerge is built so that the verification is easy to repeat.
Why You Can’t Just Trust a Privacy Claim
A privacy policy describes an intention. It doesn’t describe behavior. Between the two, only one of them is observable from where you’re sitting.
The reason this matters is structural. A cloud-based PDF merger often requires you to upload the file to a server, which is convenient but creates a data-handling risk. The file has to travel somewhere, it has to exist in memory on a machine you don’t control, and depending on the retention policy it may be written to disk, logged, or scanned. None of that is visible in the interface. The progress bar looks identical whether your document is being parsed on your laptop or copied across an ocean.
Verification, though, doesn’t require a security background. You don’t need to read source code, audit a TLS configuration, or know what WebAssembly is. You need to watch one panel in your browser while you do the thing you were going to do anyway — merge a couple of files.
This article focuses on those practical checks. Everything below can be done on a normal laptop with no extra software.
What Proof of Local Processing Looks Like
What Is Local PDF Processing and Why Should You Care?
Local processing means the PDF is handled entirely on your device using browser technologies like JavaScript or WebAssembly. The file is never sent to a remote server. The browser reads it from disk into memory when you select it, the page manipulates those bytes, and the result is handed back to you as a download.
Cloud processing is the opposite shape: your file is uploaded, processed on hardware you don’t own, and returned — usually with a temporary copy left behind for some retention window.
The difference matters because it changes the blast radius. If the processing is local, there is no server-side copy to leak, misconfigure, or subpoena. The file’s exposure is limited to your own machine.
Observable signals
You don’t need documentation to tell these two models apart. A locally processing tool leaves fingerprints:
- No upload requests in the Network tab. Merging produces no
POSTorPUTwhose body contains your document. - No file-size limits tied to server capacity. A tool that uploads usually caps upload sizes; a local tool is limited by your own browser’s memory instead.
- Immediate processing with no upload progress bar. If the tool starts work instantly, there was nothing to transfer.
- No permission prompts beyond the file picker. A tool that reads a file you selected through
<input type="file">doesn’t need broader filesystem access — and shouldn’t ask for it.
That last point is a good sanity check on any “we’re local” claim. Selecting a file through the browser’s own dialog grants the page access to that file, not to your disk.
PdfMerge sits between those two options. 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.
Step-by-Step: How to Verify a PDF Merger’s Privacy
Here’s the check, in order.
1. Open the tool in a normal browser tab. For RSJ PdfMerge, that’s https://pdfmerge.rsj.de. Load the page fully before you start.
2. Open developer tools and switch to the Network tab. In Chrome, Firefox, or Edge press F12 (or Ctrl+Shift+I / Cmd+Option+I) and select Network. Enable Preserve log if you want the list to survive a page reload, and clear the existing entries so the list starts empty.
3. Select a PDF and perform a merge or split. Pick a real document — something with a few dozen pages is fine. Add a second file and merge them, or open one and split it.
4. Read the request list. Sort by type and look for anything in the Fetch/XHR group, or any POST/PUT request. What you’re looking for is a request whose payload is your document. In a tool that uploads, it looks roughly like this:
POST /api/v1/documents HTTP/1.1
Host: example-pdf-tool.com
Content-Type: multipart/form-data; boundary=----7d91ab
Content-Length: 4821943
------7d91ab
Content-Disposition: form-data; name="file"; filename="client-reports.pdf"
Content-Type: application/pdf
%PDF-1.7 ... (your document bytes travel here) ...
------7d91ab--
If you see a request like that, the file left your machine. If you don’t, it didn’t.
On a locally processing tool, the log looks much duller — page assets in, nothing out:
Name Status Type
/ 200 document
/assets/app.js 200 script
/assets/worker.js 200 worker
/assets/styles.css 200 stylesheet
# (illustrative) — no request carries your PDF
5. Repeat with a different operation. Merging and splitting may take different code paths, so run both. Also try a large file: an upload-based tool will usually show a request whose Content-Length roughly matches your document size.
6. Check what the file picker asked for. If the page requested filesystem or download permissions before you chose a file, that’s worth a second look. A standard <input type="file"> doesn’t require any.
For RSJ PdfMerge specifically, the web app at https://pdfmerge.rsj.de processes PDFs entirely in the browser and never uploads them to a server. That’s the claim — the steps above are how you confirm it rather than assume it.
How to Split a PDF into Multiple Files in Your Browser
Splitting is the better operation to test, because it produces multiple outputs and some tools quietly route multi-file work through a server. Open a document, use the thumbnail sidebar to define the pages you want, and export the result as separate files. Then look back at the Network tab.
What you should see is a set of downloads — GET requests for the generated files, or nothing at all if the browser is creating them from memory via a Blob. What you should not see is an upload of the source document followed by a server-side response containing the pieces. If the split completes while the machine is offline, that’s about as strong as evidence gets.
If you use the Chrome extension, note that it opens RSJ PDF Merge, Sort & Split from https://pdfmerge.rsj.de, and the web app URL is configurable in the extension’s options page — so you can point it at the instance you trust.
Interpreting Results and Edge Cases
Seeing no upload requests is a strong indicator that processing happens locally, but it is not a formal audit. Keep these caveats in mind:
- Local technology looks local in the Network tab. A tool built on WebAssembly still counts as local processing. Wasm is just compiled code running inside your browser sandbox; it doesn’t imply a server round trip.
- Hybrid tools exist. Some products merge locally but send work to a server for specific features — OCR, format conversion, or compression are the usual suspects. Run the check on the exact operation you care about, not just the one on the homepage.
- Anything you load in the page could phone home. A tool can be honest about not uploading your PDF while still collecting analytics. Test in a private window with extensions disabled if you want the cleanest signal.
- Documentation is a secondary source. Check whether the product’s own docs state that processing happens in the browser. It’s weaker evidence than network behavior, but it’s a useful cross-check.
One more consistency check: limits. If a tool advertises page caps that line up with server-side processing tiers, that’s a hint — though not proof — that a backend is involved. For RSJ PdfMerge, the free version supports documents up to 100 pages, and the Pro version supports unlimited pages and ZIP files, but all processing remains local in the browser. The tier changes what you’re allowed to do, not where the work happens.
How RSJ PdfMerge Makes Verification Easy
RSJ PdfMerge is a browser-based app that merges, sorts, and splits PDFs with a drag-and-drop interface. The relevant part for this article is where the work happens:
- It processes files locally in the browser, so you can verify privacy by checking the Network tab as described above.
- The Chrome extension provides one-click capture and opens RSJ PDF Merge, Sort & Split from https://pdfmerge.rsj.de, where the merge, sort, and split operations run.
- No installation is required — start at RSJ PdfMerge and you’re working in seconds.
- The interface covers the full edit cycle: reorder, rotate, delete, insert custom text pages, and export as a single PDF or as a ZIP of individual PDFs (Pro).
If you want to weigh browser-based tools against installed software before committing, see the article Browser-Based PDF Merger vs Desktop Software: Which Is Better?.
FAQ
Can I verify that a PDF merger doesn’t upload my files without technical skills?
Yes. You can open your browser’s developer tools, go to the Network tab, and perform a merge. If you see no requests containing your file data, the tool likely processes locally. RSJ PdfMerge, for example, processes files entirely in the browser and never uploads them to a server.
What does ‘local processing’ mean for a browser-based PDF tool?
Local processing means the PDF is handled entirely on your device using browser technologies like JavaScript or WebAssembly. The file is not sent to a remote server. RSJ PdfMerge works this way: you can merge, sort, and split PDFs without uploading them.
Does the RSJ PdfMerge Chrome extension upload my PDFs?
No. The extension captures the PDF from the active tab and opens RSJ PDF Merge, Sort & Split from https://pdfmerge.rsj.de, where processing happens locally in your browser. The web app URL used by the extension is configurable in its options page.
Are there any limits to local processing in RSJ PdfMerge?
The free version supports documents up to 100 pages. The Pro version supports unlimited pages and adds ZIP file merging and downloading a ZIP of resulting PDFs. All processing remains local in the browser.
Conclusion: Verify, Then Decide
A privacy claim is a hypothesis. Five minutes with the Network tab turns it into an observation, and the observation is usually unambiguous: either a request carrying your PDF leaves the machine, or it doesn’t. Do the check once on any tool you’re about to trust with client documents, tax records, or contracts — and if the log stays quiet, you’ve got your answer.
RSJ PdfMerge is designed so that answer is easy to reach. Open https://pdfmerge.rsj.de, merge or split something, and watch the Network tab stay empty. The free tier covers documents up to 100 pages; Pro (€3.99/month, €29.99/year, or €69.99 lifetime) lifts the page limit and adds ZIP merging and ZIP export — all still processed locally in your browser.
Related posts
- How to Reorder PDF Pages with Drag and Drop
- How to Automate Repetitive PDF Document Workflows
- How Accountants Can Merge and Sort Client PDFs in the Browser