About NOBSPDF

File tools should not need an account.

Why this exists

Needing to merge two PDFs is a two-minute job. The usual way to do it is not. You search, land on a site that looks helpful, upload a document you would rather not hand to a stranger, wait through a progress bar that is often only an animation, and then discover that downloading the result requires an email address, or a free trial, or that the free tier stamps a watermark across the page you are about to send to a client.

The irritating part is that none of that is technically necessary. Modern browsers can read a PDF, rearrange its pages, re-encode a JPEG and produce a new file entirely on your own machine. The upload was never a requirement of the task. It is a requirement of the business model — once your file is on somebody's server, there is a reason to make you sign up to get it back.

NOBSPDF is what is left when you remove that. There are currently 28 tools here. None of them ask who you are.

How it actually works

Every tool on this site runs as JavaScript and WebAssembly inside your browser tab. When you choose a file, the browser hands the page a reference to it; the page reads the bytes into memory, does the work, and generates a new file which is handed back to you as an ordinary download.

PDF pages are rendered with PDF.js, the same engine Firefox uses to display PDFs. Documents are modified with pdf-lib, which copies page objects rather than flattening them into pictures, so text stays selectable and vector graphics stay sharp. Images are re-encoded with the same codec families that browsers and image editors use, compiled to WebAssembly.

This is not a claim you have to take on trust. Open your browser's developer tools, switch to the network tab, and use any tool on this site. Nothing carrying your file leaves. There is no upload endpoint to send it to.

What we deliberately do not do

Being specific about limitations is more useful than a feature list, so:

• No accounts. Nothing to sign up for, no email capture, no password to forget.
• No watermarks. The file you download contains your changes and nothing else.
• No daily limits. There is no counter, because there is no server-side cost per file to recover.
• No editing of existing PDF text. Our editor adds content on top of a document. Rewriting text already inside a PDF means reconstructing fonts, kerning and layout, and tools that promise it often break the page quietly. We would rather not offer it than offer a version that damages your document.
• No “compress PDF” tool. Real PDF compression means re-encoding embedded images and subsetting fonts. What most browser-based tools in this category actually do is rasterise your pages into JPEGs, which destroys selectable text. We would rather have a missing page on this site than a dishonest one.
• No OCR. Reading text out of a scan is a genuinely hard problem and doing it badly is worse than not doing it.

Signing, and what a signature really proves

There are two different things people mean by signing a PDF. One is visual: a picture of a signature placed on the page, which is what most documents actually need. The other is cryptographic: a certificate-backed signature that a PDF reader can verify, proving the bytes have not changed since they were signed.

This site does both, and keeps them clearly separate, because conflating them misleads people. A drawn signature is not tamper-evident. A cryptographic signature made with a self-signed certificate proves the document is unaltered, but it does not prove who you are — recipients' readers will show it as untrusted, and they are right to. Your certificate and its password are used in your browser and never sent to us.

How this is paid for

The site is funded by advertising. That is a deliberate trade: ads let the tools stay free and account-free, without the alternative of monetising the files themselves.

The advertising is kept structurally separate from the file-processing code and is never given anything derived from your document — not the file, not its name, not its size. Ads sit in the page margins and below the content, never between a result and its download button, never as a pop-up or overlay, and never in a way that blocks a tool. If you block them, every tool still works. The privacy page describes exactly what the ad and analytics code does collect.

Getting in touch

Corrections, bug reports and tool requests are all welcome on the contact page. If you find a case where this site's behaviour disagrees with what these pages claim, that is a bug in the product and we want to know about it.