Decrypt a PDF you can open — in your browser, nothing uploaded
| Your file | What's really happening | Outcome here |
|---|---|---|
| Asks for a password to open; you know it | User-password (AES) encryption | Removed — type the password, done |
| Opens freely, but Print or Copy is greyed out | Owner password only, empty user password | Removed — leave the password empty |
| Asks for a password; you don't know it | AES encryption doing its job | Not possible — no back door exists |
| Unknown password, but you also have an unprotected copy | Same document from the source | Use the unprotected copy; re-request if lost |
| Prints with a watermark saying "secured" | Restrictions flags, not encryption of content | Restrictions stripped with the rest |
The second row is the quiet majority: files from banks, insurers, and government sites are often restrictions-only, which is why some "password removers" appear to work without ever asking for a password. This tool tells you which case you have before you click anything — it inspects the file on load.
Decrypting a PDF you can open isn't hacking — it's the format working as designed. The reader derives a key from your password, deciphers the streams, and writes them back out plainly. What this tool adds is doing that without an upload and verifying the result before handing it over.
Same engine as the protect page: qpdf compiled to WebAssembly, running in this tab. On file load it inspects the encryption (asks: encrypted? does it require a password to open?) and tells you which of the table's rows you're in. On Remove, it decrypts with your password, then re-checks the output — unencrypted, page count unchanged — and offers the download. First use loads ~2.2 MB of WebAssembly, cached afterwards; works offline from then on.
Start from the protect page's example: a 3-page policy manual, 1,852 bytes plain, 2,665 bytes after AES-256 encryption. Removing the password here returns a 1,993-byte file — 141 bytes over the original, the residue of structural packaging, none of it content — verified unencrypted with all 3 pages present, title ("Policy Manual") and author intact, text still selectable. The same session tested the failure path: a deliberately wrong password produced a clean rejection, and a restrictions-only file (owner password, empty user password) — the kind that opens freely but blocks printing, copying, and editing — stripped in one pass with no password typed at all.
Open the file below, type the password you use to open it, and hit Remove Password. The tool decrypts the document locally and hands back a copy with no password and no restrictions. If the PDF opens without asking for a password but blocks printing or copying, leave the password field empty — restrictions-only encryption strips the same way.
No, and any site promising otherwise is selling something. Modern PDF encryption is AES with a key derived from the password; there is no master key, and 'remover' services only work on files whose password you effectively have. What recovery actually looks like: try the usual suspects (old passwords, the document's subject, a vendor's default), check whether the file came from a bank or employer that also sent an unprotected copy, or ask the sender for a fresh unprotected version.
That's restrictions-only encryption: the file was encrypted with an owner password but an empty user password, so it opens freely while carrying no-print or no-copy flags. It's also the file type most online 'PDF password removers' quietly work on, which is why they look magical. This tool handles it directly — leave the password empty, hit Remove Password, and the flags are gone. Verified behavior: such a file reports encrypted-but-opens-without-password, and after decryption prints and copies freely.
For documents you own or are authorized to modify, yes — that's the ordinary case: your own tax forms, a report you bought, files your employer gave you rights to. Removing protection on material you don't have rights to (someone else's copyrighted document, exam files, licensed courseware) can violate law or contract depending on jurisdiction. This tool simply does the math; the responsibility for having the right to unlock sits with you.
No loss at all. Decryption is the exact inverse of encryption: in a verified test, a 3-page encrypted file decrypted back to readable pages with title and author metadata intact, and the byte size landed within a few hundred bytes of the original (1,993 vs 1,852 bytes — the difference is structural packaging, not content). Text stays selectable text, images stay images, forms stay fillable.
No. The decryption engine is qpdf compiled to WebAssembly running in this page — the PDF and the password you type are processed on your machine and never transmitted. The engine caches after first load, so the tool keeps working offline, which is the tell for a genuinely local tool.