No Account, No Watermark: Choosing a PDF Merger
You need to merge two contracts, split a scanned report into chapters, or reshuffle the pages of a proposal before it goes out. So you search for a free PDF merger, pick the first result, and discover the real price: a sign-up form, a confirmation email, and a faint logo stamped across the bottom of every page you export.
That is the decision this article is about. When you compare a PDF merger with no watermark and no account, you are not really comparing feature lists — you are comparing what the tool takes from you. Time, an email address, a copy of your document on someone else’s server, or a branded footer on a file you are about to send to a client.
Here is how to evaluate those trade-offs, what “free” usually hides, and where RSJ PdfMerge sits in that landscape.
The Purchase Decision: What “No Account, No Watermark” Really Means
Two short phrases, both frequently abused in marketing copy.
No account means no registration, no email confirmation, no login wall, and no “continue with Google” prompt before you can touch your file. It also means there is no profile storing your documents, because there is no profile.
No watermark means the exported PDF contains exactly the pages you assembled — no branding strip, no “Created with …” footer, no nudge to upgrade baked into the output. It matters more than people expect: a watermarked PDF is not just ugly, it is unusable for anything client-facing, so you end up redoing the work somewhere else.
A typical “free” PDF merger gives you neither. Instead you get a limited number of tasks per day, a mandatory account, and a watermark that disappears the moment you enter a card number. The document is also uploaded to a server, processed there, and returned — convenient, but a data-handling decision you may not be allowed to make on your employer’s behalf.
RSJ PdfMerge takes a different route. It is a browser-based editor for merging, sorting, rotating and splitting PDFs that requires no account, adds no watermark, and processes everything locally in the browser. The free tier covers documents up to 100 pages. The Pro tier removes that page limit and adds ZIP support, so you can import and export bundles of PDFs rather than one file at a time.
That is the whole pitch, and it is enough to make the comparison concrete.
What You Get at Each Tier: Free, Pro, and the SDK
Three tiers, three different jobs. The trap is assuming they are the same product with features switched off — they are not.
| Free web app | Pro | SDK | |
|---|---|---|---|
| Cost model | Free, no licence key | Paid upgrade | Licensed per integration and volume |
| Account required | No | No | N/A (embedding your own app) |
| Watermark | None | None | None |
| Page limit | Up to 100 pages | Unlimited | Unlimited |
| ZIP import/export | — | Yes | Yes |
| Best for | Occasional, single-document work | Recurring, large or batched work | Shipping the editor inside your product |
Free. The full editor: drag and drop PDFs, reorder pages, select several pages with Ctrl/Cmd+click or Shift+click a range and move, rotate, duplicate or delete them together. Split the document into parts, each with a title line, a name of your choice, and its own save and print button. Insert custom text pages, bookmark pages by colour, undo and redo every edit. Export one merged PDF, one PDF per part, or print. Seven interface languages. No account, no watermark, no licence key.
Pro. Everything above, minus the ceiling: unlimited pages plus ZIP import and export. You can upgrade within the app when you hit the limit.
SDK. This is the commercial product. @rsj-de/pdfmergesortsplit embeds the same editor inside another web application, and documents are still processed in the visitor’s browser — you are not standing up a document-processing backend. Licensing is per integration and volume, not per page.
The Chrome extension is free as well, and it opens RSJ PDF Merge, Sort & Split from https://pdfmerge.rsj.de, reusing an already open editor tab instead of spawning a new one. The editor URL is configurable in the extension’s options page.
Cost/Benefit and ROI: Why Pay for Pro or the SDK?
Start with what the free tier actually costs you: nothing, and no hidden strings beyond the page count. There is no task counter, no “3 free merges per day”, no email drip. If you merge a handful of documents a month, you may never see a reason to upgrade — and that is fine, because the free tier is not a demo.
Pro becomes rational the moment the page limit stops you mid-task. Redoing a 150-page report by splitting it into two files, merging each half, and then recombining is not just annoying; it is a place where page order quietly goes wrong. The time you spend verifying a workaround usually exceeds the cost of removing the limit, and you get ZIP handling on top of it.
For the SDK, the arithmetic is different and usually larger. Per-page pricing scales with success — the more your users process, the more you pay, which punishes exactly the usage pattern you want to encourage. Per-integration and volume licensing decouples cost from page count, so a customer running a 3,000-page archive costs you roughly what a customer running a three-page invoice does. If PDF handling is a supporting feature in your product rather than the product itself, that predictability matters more than the headline rate.
There is also a risk line item that rarely makes it into comparisons: watermarked or account-bound tools create rework. A stamped export goes back through the whole pipeline. An account-bound tool creates a shared credential you have to manage. A cloud merger creates a data-handling question your security team has to answer. All three cost money, just not on the invoice.
Evaluating the SDK costs nothing. An unlicensed embedding runs in test mode: every feature works, with a banner marking the unlicensed integration. You can build the whole flow, show it internally, and only then buy a licence token to remove the banner.
Upgrade Path: From Free to Pro to Self-Hosted
The path is deliberately short.
- Start in the browser. Open the app, drop in a PDF, rearrange pages, export. No install, no account.
- Add Pro when you hit the ceiling. Unlimited pages and ZIP support, upgraded in place.
- Embed with the SDK when PDF work belongs inside your own product. Two levels are available:
PDFMergeSortSplitClassfor any framework, and<PDFMergeSortSplit>plususePdfMergeSortSplit()for React. - Self-host when policy demands it. Customers can run the editor on their own infrastructure with an offline licence.
Installing the SDK is a normal npm step:
npm install @rsj-de/pdfmergesortsplit
The framework-agnostic entry point looks like this:
import { PDFMergeSortSplitClass } from '@rsj-de/pdfmergesortsplit';
const editor = new PDFMergeSortSplitClass({
target: document.getElementById('pdf-editor'),
title: 'Merge and split invoices',
// omit the licence to run in free test mode (banner shown)
license: process.env.PDFMERGE_LICENSE_TOKEN,
// further options cover icon, hidden UI parts, injected buttons,
// provenance attachment, and the licence itself
});
// Illustrative only — see https://pdfmerge.rsj.de/docs for the exact API.
// You can load documents, read pages and their provenance, and export
// a single part or everything as PDF/ZIP.
In React, the component and hook give you the same editor with your own controls around it:
import { PDFMergeSortSplit, usePdfMergeSortSplit } from '@rsj-de/pdfmergesortsplit';
export function PdfWorkspace() {
const editor = usePdfMergeSortSplit();
return (
<>
<button onClick={() => editor.exportAll()}>Export everything</button>
<PDFMergeSortSplit
title="Contract assembly"
provenance
license={import.meta.env.VITE_PDFMERGE_LICENSE}
/>
</>
);
}
Source and runnable samples — a React sample (sdksample) and a plain JavaScript sample (sdksimple) — live at github.com/pdfmergesortsplit/pdfmergesortsplit.
What Is Local PDF Processing and Why Should You Care?
Local processing means the work happens on the device in front of you, not on a server you never see. In practice, for a browser tool, that means the PDF is read into memory by JavaScript running in the page, edited there, and written back out as a download.
Why care? Two reasons.
First, risk. A cloud-based PDF merger often requires you to upload the file to a server, which is convenient but creates a data-handling risk. Contracts, medical records, payroll exports, and anything under an NDA are exactly the files people merge most often, and exactly the files that should not take an unnecessary round trip through a third party.
Second, accountability. With local processing there is nothing to audit on the server side, because there is no server side of the operation. You can watch the network panel in DevTools while you export and see for yourself what the page talks to. For a detailed walkthrough, see How to Check If a PDF Merger Uploads Your Files.
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.
Self-Hosted vs. Cloud: Which Fits Your Workflow?
Three shapes of deployment, three different constraints:
- Cloud merger. Zero setup, works everywhere, and your documents leave your machine. Fine for public brochures, awkward for anything confidential.
- Browser-based local processing. Zero setup, works everywhere, documents stay on the device. The default for most individuals and small teams.
- Self-hosted. The editor runs on your own infrastructure with an offline licence. The right answer when procurement or a regulator wants the software inside the perimeter, not just the data.
For most readers of this article, the middle row is the answer: the web app and Chrome extension are free for everyone, and the free tier’s only real limit is the 100-page cap. Organisations that need the editor embedded and fully on-premise move to the SDK with a self-hosting licence.
One more benefit of local processing that only shows up after a few weeks of use: page provenance. Every page in the editor keeps track of which file and which page number it came from, and that provenance can be written into the exported PDF and restored when the file is opened again. When you are assembling a document from nine source PDFs, being able to answer “where did this page come from?” without opening nine files is a real time saver.
For a deeper comparison of browser-based and desktop workflows, see the article Browser-Based PDF Merger vs Desktop Software: Which Is Better?.
How to Split a PDF into Multiple Files in Your Browser
A short walkthrough, because this is where most people first hit a page limit or a watermark.
- Open the app and drop in your PDF — or, on Pro, a ZIP of PDFs.
- Create the parts you need. Each part is its own output PDF, with a title line and a name of your choice.
- Drag pages into the right part. Keyboard works too: hold Space to pick up a page, use the arrow keys to move it, press Space to drop it.
- Select several pages at once with Ctrl/Cmd+click or Shift+click, then move, rotate, duplicate or delete them together.
- Export one PDF per part, a single merged PDF, or print. No watermark is added at any point.
If you want per-part titles and naming in more detail, How to Split a PDF into Separate Files with Their Own Titles covers that flow end to end.
FAQ
Is RSJ PdfMerge really free with no watermark and no account?
Yes. The web app and the Chrome extension are free for everyone, with no account required and no watermark added. The free version supports documents up to 100 pages; the Pro version removes that limit and adds ZIP support.
What happens if my PDF has more than 100 pages?
The free version supports up to 100 pages. For unlimited pages you need the Pro version, which also includes ZIP file support. You can upgrade within the app.
Does the Chrome extension require an account or add a watermark?
No. The Chrome extension is free, does not require an account, and does not add a watermark. It opens RSJ PDF Merge, Sort & Split from https://pdfmerge.rsj.de and hands the PDFs to the editor, reusing an already open editor tab where possible.
How can I be sure the PDF merger doesn’t upload my files?
PdfMerge processes PDFs entirely in the browser, so files are never uploaded. You can inspect network activity yourself while you work; for a detailed guide, see How to Check If a PDF Merger Uploads Your Files.
Conclusion
Choosing a PDF merger with no watermark and no account comes down to three questions: does the output carry someone else’s brand, does using it require an identity, and does the document leave your machine? The free tier of RSJ PdfMerge answers all three cleanly for documents up to 100 pages, Pro removes the page and ZIP limits, and the SDK is there when you need the same editor inside your own product — with a free, unrestricted test mode so you can evaluate before you license.
Open the web app, drop in a PDF, and check the export for yourself.
Related posts
- How to Split a PDF into Separate Files with Their Own Titles
- How to Automate PDF Merge and Split Workflows in Your Web App
- PDF Combiner Compared to Adobe Acrobat: What Actually Differs