How to password-protect a PDF — and safely remove a password

What encryption on a PDF really means

Password-protecting a PDF is not a warning label — it is encryption. The contents of the file are scrambled using a key derived from your password, so the bytes on disk are meaningless without it. Someone who obtains the file cannot read a word of it, cannot extract its images, and cannot recover its text, unless they have the password. This is real protection, the same category of technology that secures messaging apps and online banking.

AES-256 and where the security really lives

The PDF standard supports AES-256 encryption — the same algorithm trusted for classified government material. In practical terms the encryption itself cannot be broken; nobody is going to brute-force an AES-256 key. That means the entire security of your protected PDF rests on one thing: the strength of your password.

This has a clear implication. A short password, however "complex", can be guessed by a program trying millions of candidates. A long passphrase — several unrelated words — is dramatically harder to guess and easier to remember. When protecting something that matters, favour length over cleverness, and store the password somewhere safe, because a forgotten AES-256 password means a permanently unreadable file with no recovery.

Open password versus permission restrictions

PDFs actually support two different kinds of protection, and it is worth not confusing them. An open password (also called a user password) is the one that stops the file being opened at all — this is the strong, encryption-backed protection. Permission restrictions are separate flags that ask a reader to disable actions like printing or copying text, even after the file is open.

The important caveat: permission restrictions are advisory. A compliant reader honours them, but someone determined, with the right software, can bypass them once they can open the document. So use permission flags to discourage casual reuse, but never rely on them for genuine confidentiality — for that, the open password is what counts.

Removing a password you know

The reverse task is just as common. Banks, employers and government systems often send documents permanently encrypted, forcing you to type a password every time you open your own statement or payslip. If you have the password and the right to the document, you can decrypt it once and keep an ordinary, unprotected copy.

Be clear about what this is: decryption with the correct password, exactly as your PDF reader does when you type it in. It is not "cracking" — no tool can open an AES-encrypted PDF whose password you do not know. Removing protection from your own documents is normal use; removing it from documents whose restrictions you are bound to respect is not.

Why the "where" matters as much as the "how"

Here is the uncomfortable irony of most online encryption tools: to protect your private document, they ask you to upload it — and often the password too — to a server you do not control. You are handing your secret to a stranger in the act of trying to keep it secret.

This is exactly why doing it client-side matters. Pdfect encrypts and decrypts in your browser using a WebAssembly build of qpdf, so the file and the password never leave your device. There is no server that sees your document, no upload to intercept, and nothing retained anywhere. You can confirm it by going offline after the page loads — the encryption still works, because it was always going to happen on your machine.