Your password required

Unlock a PDF

Remove a password you already know, so the document opens without a prompt — decrypted locally, with the result re-loaded without a password to prove nothing is left.

Decryption runs in this browser tab. Your document and its password never leave the device.

Short answer: drop the locked PDF, type its current password, download the unlocked copy. If the password is wrong the library refuses and no file is produced — that is the whole behaviour, and it is why this is not a cracking tool.

Decrypted, not rebuilt

The file is not re-printed or re-rendered: qpdf removes the encryption layer, so text stays selectable, images keep their original compression and bookmarks survive. A rebuilt PDF would look the same and lose all of that, which is why the rebuild approach is worse even when it looks identical on screen.

After you unlock it

The output has no password at all — anyone who receives it can open it. If the file is going to someone else, lock it again with a password you are happy to share, and consider stripping the metadata that names your machine or your tool.

Unlock questions

Does this need the current password?

Yes. It decrypts with the password you supply — nothing here guesses, brute-forces or exploits anything. A tool that removed passwords without them would be a cracking tool, and this page is not one.

Why would I unlock my own PDF?

Because you locked it and the prompt is now in the way: a bank statement you cannot merge, a form you cannot fill, a document your own scanner passworded. Removing the password produces a normal PDF that any tool can read.

What comes over, and what does not?

Pages, text and images come over intact — the content streams are copied, not re-rendered, so text stays selectable and images keep their compression. What a rebuild cannot carry is document-level extras: outlines and bookmarks, form fields, annotations and comments, and the metadata. That is the honest trade, and the page says it rather than claiming a perfect copy.

Why not just save the decrypted file as it is?

Because it does not work, and this was measured rather than assumed: the library keeps the original cross-reference stream, whose dictionary still points at the encryption entry, so the “plain” copy still refuses to open without the password. Rebuilding the pages is the only route that produces a file with no encryption entry at all, and the result is re-loaded without a password to prove it.

What if the password is wrong?

The library refuses to open it, the page says the password is wrong, and no file is produced. Nothing partial is written, which is the only honest outcome for a wrong password.

Related tools