Remove a Password From a PDF
Removing a password from a PDF means writing a decrypted copy that opens without prompting — useful for a bank statement you must unlock every time you file it. The tool on this page runs qpdf, the standard open-source PDF engine, compiled to WebAssembly in your browser: enter the password you know and it produces an exact decrypted copy locally, with the file and password never leaving your device. If the file opens without a prompt but blocks printing or copying, it carries only owner-password restrictions, which qpdf can lift without any password. It cannot and will not crack a password you don't have — this is for documents you are authorized to open.
How it works
The button above drives qpdf — the same open-source C++ engine used on servers and command lines everywhere for PDF transformation — compiled to WebAssembly. The ~1.2 MB engine downloads once, on first use, and is cached; from then on the whole operation happens inside the browser sandbox. Your PDF and the password you type are combined in memory on your device, the decrypted file is handed back as a download, and nothing is transmitted anywhere — the network tab of your browser's developer tools will show no upload.
An encrypted PDF keeps its structural skeleton readable but stores every string and stream — the text, images, and page-drawing instructions — as AES (or, in older files, RC4) ciphertext, alongside an /Encrypt dictionary holding algorithm parameters and password-verification values. When qpdf receives the correct password, it derives the file's encryption key, decrypts each object, and rewrites the document without the /Encrypt dictionary. Because this works object for object, the output is structurally faithful: bookmarks, hyperlinks, form fields, and embedded fonts survive intact, and the file size shifts by only a few kilobytes — unlike the print-to-PDF workaround, which re-renders appearance and discards interactive structure.
There is an important distinction between encryption and restrictions. A file protected with a user password is genuinely sealed: the key derivation is one-way, AES-256 cannot be reversed without the password, and no tool — this one included — can open it otherwise. A file protected with only an owner password is different: the PDF specification requires viewers to open it using an effectively empty user password, so the content is already being decrypted on every screen it appears on, and only advisory permission flags (the /P bits) disable printing or copying. qpdf can rewrite such a file without those flags and without being told any password — which is exactly why "no copy, no print" restrictions should never be mistaken for security, and why you should only lift them on documents that are yours.
The honest limit follows directly from the mathematics: this tool decrypts, it does not crack. A wrong password fails qpdf's verification check and produces nothing. If you have lost the password to a properly protected file, the recourse is the document's issuer, not software.
Worked example: 36 monthly statements
A real archival chore: 36 bank statements (three years), each protected by the bank with the customer's date-of-birth-based password, averaging 210 KB per file. Dropped one at a time onto the widget above with the known password typed once per file, each decrypted in well under a second; the first file also triggered the one-time 1.2 MB engine download. Every output landed within 2 KB of its input's size and was pixel-identical, with the bank's internal links still working. The same statement unlocked via Chrome's print-to-PDF for comparison came out at 348 KB — 66% larger — with those links flattened away.
The decrypted set (7.4 MB in total) then went into an encrypted disk image, replacing 36 password prompts with one. That is the pattern worth copying: remove the per-file passwords you already know, then re-protect the collection once at the storage layer, where unlocking is centralized. For a single file that needs to stay individually protected under a password you choose, run it back through the protect tool linked below.
Frequently asked questions
Can this tool crack a PDF password I forgot or never had?
No — it decrypts only with the correct password, and no legitimate tool can bypass AES encryption without it. If you have lost the password, ask the document's issuer for it or for an unlocked copy; this page is for documents you are authorized to open.
Why does my PDF open without a password but refuse to let me print or copy?
That file has only an owner password: viewers decrypt it automatically with an empty user password and then honor advisory permission flags. Because the content is already decrypted, this tool can remove those restrictions without asking you for any password at all.
Is my PDF or my password uploaded when I use this tool?
No. The decryption runs in qpdf compiled to WebAssembly inside your browser, and the only download is the ~1.2 MB engine on first use. The file and the password you type stay in your device's memory and are never sent anywhere.
Is it legal to remove a password from a PDF?
Removing protection from a document you own or hold the password for, for your own use, is generally fine — like keeping an unlocked copy of your own bank statement. Circumventing protection on documents you have no rights to can violate laws such as the DMCA, so when in doubt, ask the issuer.
Will the unlocked PDF be identical to the original?
Yes, structurally: qpdf decrypts each object and rewrites the file without the encryption dictionary, so bookmarks, links, form fields, and fonts are preserved and the size changes by only a few kilobytes. It is not a re-rendered lookalike, unlike the print-to-PDF workaround.
What happens if I enter the wrong password?
qpdf's password check fails and the tool reports an invalid password without producing a file — there is no partial decryption. You can simply correct the password and try again; nothing about the original file is changed by a failed attempt.