Remove a watermark from a protected PDF

A protected PDF is one you can read but not edit. It is workable: the tool rebuilds it locally first, then deletes the watermark objects. What it will not do is open a document you are locked out of. It is free to use and needs no account.

or drop a PDF here One file at a time · never uploaded · nothing kept

What "protected" usually means

In practice, a protected PDF is one that opens normally and then refuses something: editing, copying text, printing, or adding comments. Nothing asked you for a password, yet the file behaves as if it is locked. That is permissions encryption: the document was saved with an owner password and a set of restrictions, and the page content is encrypted to enforce them.

This is the case where most browser tools quietly fail. They accept the file, report success, and hand back a document whose content is still encrypted, or one that a reader refuses to open at all.

State of the file	What it means	What this site does
Opens freely, no restrictions	An ordinary PDF	Scan and remove directly
Opens freely, editing restricted	Permissions encryption. No password needed to view.	Rebuild locally, then remove
Asks for a password to open	Access control. The content is not meant for you.	Refused: not attempted

The workflow

Choose the file. The scan reports it as edit-restricted and explains why removal is disabled in that state.
Rebuild it locally. Each page is copied into a new document with MuPDF WebAssembly, which leaves a normal PDF with no encrypted content stream. Nothing leaves your device. Note that annotations and metadata are not carried over; see Rebuild a PDF.
Scan again and remove. The rebuilt copy is scanned automatically, and the watermark objects are now readable and deletable.
Download and check. Confirm the mark is gone and your content is intact.

What the extra step costs, measured: a 60-page, 20.08 MB test file rebuilt to 20.76 MB, about 3% larger, with all 60 pages preserved. Metadata, bookmarks and attachments are dropped, and the page content is re-serialised.

The line this tool does not cross

Restrictions exist to protect the file's owner. Removing them from a document you were given permission to edit (your own file, a report you commissioned, a template your client sent you with editing switched off) is ordinary work. Getting into a document that was deliberately withheld from you is not, and this tool has no mechanism for it: no password attempts, no dictionary attacks, no "recovery" feature.

If you own the document and cannot open it, the answer is with whoever set the password, not with a browser tool.

Use it on documents you are entitled to change. Your own files, documents you have a licence to edit, material you have been given permission to modify. Removing someone else's copyright notice, or making a document look like it came from somewhere it did not, is not what this was built for.

Questions

My file opened without a password but the editor says it is protected. Can this fix it?

Usually yes. If it opens, the restrictions are permissions-based rather than access-based, and the local rebuild removes them. Try it and see: the scan tells you which state your file is in before you commit to anything.

Does rebuilding a protected file change how it looks?

The pages should look the same. Annotations and document metadata are not carried across, so if the file has comments or form fields you care about, work on a copy and compare.

Is removing an edit restriction legal?

That depends on the document and your relationship to it, and no tool can answer it for you. What this site can say is what it does: it rebuilds pages you can already open, and refuses anything that needs a password. Do not use it to defeat restrictions on someone else's document.

What if the rebuilt file still refuses edits?

Then the restriction is not the kind this handles; most likely the file needs an open password. The tool stops and says so rather than producing a broken file.