PdfMerge Merge, Sort & Split PDFs

← All posts

2026-11-02

How to Check If a PDF Merger Uploads Your Files

How to Check If a PDF Merger Uploads Your Files
merge pdf sort pdf split pdf

How to Check If a PDF Merger Uploads Your Files

You are one drag away from handing a stack of signed contracts, invoices, or personnel records to a server you know nothing about. Most PDF mergers never tell you what happens after you click Merge — and the ones that do upload rarely advertise it.

The good news: you do not have to take anyone’s word for it. With the developer tools built into every browser, you can watch exactly what leaves your machine during a merge, a sort, or a split — and read the result in about two minutes. This article shows you the verification method, what counts as proof, and how to interpret what you see. RSJ PDF Merge, Sort & Split (PdfMerge) serves as a worked example of a tool that processes files locally in the browser.

Why You Should Verify Before You Merge

Merging is rarely a casual operation. The documents that need combining tend to be the ones you would least like to find on an unknown server: contracts with personal data, invoices with bank details, medical records, HR files, scanned ID documents.

A cloud-based PDF merger often requires you to upload the file to a server, which is convenient but creates a data-handling risk. Once the bytes leave your browser, you are relying on the operator’s retention policy, access controls, logging, and jurisdiction — none of which you can observe from the outside.

Verification gives you something better than trust: evidence. It lets you separate tools that process locally from those that upload, so you can make an informed choice about which documents go where. It is also fast, requires no installation, and works on any tool you are evaluating — not just the one in this article.

What Proof of Local Processing Looks Like

There are three levels of evidence, and a credible tool should give you at least two of them.

1. A clear vendor statement. Not marketing fluff like “privacy-first”, but a specific claim about where the work happens. PdfMerge’s documentation states that PDFs are processed entirely in the browser and are never uploaded. That is the kind of sentence you can hold a vendor to, because it is falsifiable — and you can falsify it with the next two steps.

2. Observable behaviour. If a tool merges locally, then during the merge itself there should be no network request carrying your document’s bytes. Page load, fonts, scripts and icons will produce traffic; a genuine merge operation should not.

3. Transparency features. Open documentation, published samples, a way to inspect what the tool is doing. PdfMerge publishes its SDK source and samples on GitHub, documents its API, and keeps a changelog and docs site at https://pdfmerge.rsj.de/docs. That does not prove anything on its own, but it means the claim is checkable rather than vague.

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. If you want the background on why that architectural difference matters at all, see What Is Local PDF Processing and Why Should You Care?.

Step-by-Step: How to Check If a PDF Merger Uploads Your Files

This procedure works for any browser-based PDF tool. The example uses PdfMerge, but nothing here is specific to it.

Step 1 — Open the tool with the Network tab already watching

Open the tool, then press F12 (or Ctrl+Shift+I / Cmd+Option+I) and switch to the Network tab. Clear the request list so you start from zero, and tick Preserve log if you want the history to survive a reload.

# macOS
open https://pdfmerge.rsj.de

# Linux
xdg-open https://pdfmerge.rsj.de

Do this before you load your documents. If you start watching after the merge, you may miss the very request you are looking for.

Step 2 — Filter for the traffic that would matter

The Network tab is noisy. Narrow it to the only thing that matters: requests that could plausibly carry a PDF. Two filters do most of the work.

method:POST
larger-than:100K

Type the first filter to see every POST request — the normal method for sending a file body. Type the second to see anything over 100 KB, which would include a multi-page PDF travelling as a body or a form upload. Some tools use PUT or PATCH; if you see none of those at all, even better.

Step 3 — Perform the operation and watch

Now load two or three PDFs and merge them. Then reorder pages, then split the document into parts. Watch the request list while you do it.

On PdfMerge, files are read through the browser’s file API and kept in memory. What you should observe is the app’s own assets loading and nothing else: no POST with a multi-megabyte body, no multipart form data containing your document. The merge, the sort and the split complete with the network panel effectively idle.

Take a screenshot of that idle panel if you are doing this for a compliance file. It is a dated record that you checked.

Step 4 — Read the vendor’s own documentation

Technical observation tells you what happened in one session; documentation tells you what the vendor intends. Look for a sentence that commits to a mechanism, not a mood. PdfMerge’s docs and its llms.txt state that PDFs are processed entirely in the browser and are never uploaded — a claim specific enough to be worth verifying, which is exactly what steps 1–3 did.

If a vendor’s privacy page says “we take your privacy seriously” and nothing else, treat that as an absence of evidence.

Step 5 — Repeat the check at every entry point

Tools rarely have one door. If there is a browser extension, a desktop wrapper, or a Google Drive integration, each is a separate path and deserves its own check.

The PdfMerge Chrome extension is a launcher: it opens RSJ PDF Merge, Sort & Split from https://pdfmerge.rsj.de and reuses an editor tab you already have open instead of spawning another one. The editor URL is configurable in the extension’s options page, which also means you can point it at a self-hosted instance if you are a licensed customer. Because it opens the same web app, the network inspection you did in steps 1–3 applies — but run it once through the extension anyway, and confirm the tab it opened is the URL you expect.

Interpreting Results and Edge Cases

A few requests in the Network tab are normal and prove nothing either way. Here is how to read what you find.

  • Page assets are not uploads. The HTML document, JavaScript bundles, fonts, icons and analytics beacons all produce requests. None of them contain your PDF. Look at the method and, more importantly, the payload.
  • Requests to the tool’s own domain still require inspection. A POST to pdfmerge.rsj.de is not automatically suspicious, but it is not automatically innocent either — click it and look at the request body and size. A few hundred bytes of telemetry looks very different from a two-megabyte body matching your file.
  • Feature-specific uploads are a real pattern. Some tools keep merging local but send files away for OCR, format conversion, or AI features. Check whether the core merge/sort/split path stays local, and whether the optional feature is one you can simply not use.
  • Cloud storage is a transfer you initiate. If you deliberately open a file from Google Drive or save the result back to Drive — both of which PdfMerge supports — data moves between your browser and your own Drive account. That is your storage, not the tool operator’s server, and it is a choice you make per file.
  • If you find an upload request, believe it. The tool is not fully local. Decide whether the risk is acceptable for that document, and consider a different tool for the ones where it is not.

None of this is exotic. It is the same method you would use to check whether a form posts your data anywhere unexpected.

How to Merge, Sort, and Split Safely in Your Browser

Once you have verified that a tool processes locally, the workflow should be as convenient as the cloud alternative it replaces.

Open PdfMerge in your browser, then:

  1. Load documents. Drag and drop any number of PDFs, or use the file dialog. Drop the pages where you want them.
  2. Reorder. Drag pages by thumbnail. Hold Ctrl/Cmd+click to select several pages, or Shift+click to select a range, then move, rotate, duplicate or delete them together.
  3. Undo freely. Every edit is undoable, so aggressive rearranging costs nothing.
  4. Export. Save one merged PDF, one PDF per part, or a ZIP of all parts. Print directly if that is the destination.

Two features are worth knowing about because they survive the export. Page provenance keeps track of which file and which page every page came from; it can be written into the exported PDF and is restored when you open such a PDF again. And bookmarking pages by colour makes long documents navigable while you work. Both are local operations like everything else.

How to Split a PDF into Multiple Files in Your Browser

Splitting is where local processing earns its keep, because a split usually means one sensitive document becoming several.

  1. Load the PDF into the editor and create as many parts as you need.
  2. Give each part a title line and a name of your choice.
  3. Drag pages from the document into the right part — or select a page and use the keyboard: Space to pick it up, arrow keys to move it, Space to drop it.
  4. Each part is its own output PDF with its own save and print button, so you can export exactly one part without generating the rest.
  5. Export the lot as a ZIP if you need every part in one download.

The free version of PdfMerge handles documents with up to 100 pages; the Pro version removes that limit and adds .ZIP import and export. There is no account to create and no watermark on the output.

For the wider question of when a browser beats a desktop application for this kind of work, see Browser-Based PDF Merger vs Desktop Software: Which Is Better?.

If you are building a product and want this editor inside it, the SDK (@rsj-de/pdfmergesortsplit) embeds the same component and still processes documents in the visitor’s browser. Test mode is free and unrestricted — a banner marks the unlicensed embedding — and licensing is per integration and volume, not per page, with self-hosting available under an offline licence.

FAQ

How can I tell if a PDF merger uploads my files?

Open your browser’s developer tools, go to the Network tab, and perform a merge. Look for requests that contain your file data (for example, large POST requests with a multi-megabyte body). If you see none, the tool likely processes locally. Then check the vendor’s documentation for an explicit statement about where processing happens — a specific, falsifiable claim is worth far more than a generic privacy promise.

Does RSJ PDF Merge, Sort & Split upload my PDFs?

No. PdfMerge processes PDFs entirely in your browser and never uploads them. You can verify this yourself by inspecting network activity while using the tool at https://pdfmerge.rsj.de — the merge, sort and split operations complete without a request carrying your document.

What are the limits of the free version of PdfMerge?

The free version supports documents with up to 100 pages. The Pro version supports unlimited pages and .ZIP files. Neither requires an account or a licence key, and neither adds a watermark to your output.

Can I use PdfMerge without installing software?

Yes. PdfMerge is a web app that runs in your browser. You can also use the Chrome extension, which opens RSJ PDF Merge, Sort & Split from https://pdfmerge.rsj.de — handy when you want the editor one click away and want it to reuse the tab you already have open.

Conclusion

Verifying a PDF tool takes less time than reading its privacy policy, and it produces better evidence. Open the Network tab, filter for POST requests and anything over 100 KB, run the operation, and look for your file leaving the building. If nothing does, you have confirmed local processing with your own eyes.

PdfMerge is built so that check passes: files stay in the browser, the merge, sort, split, rotate and export operations all run locally, and the free version handles documents up to 100 pages with no account and no watermark. Open pdfmerge.rsj.de, turn on the Network tab, and watch it stay quiet.

Related posts

EU label: AI-generated content