How to password-protect a PDF — and what that really protects

The two passwords, and the one that matters

The PDF format defines two separate passwords that do very different jobs:

• The open password (formally the user password) encrypts the document. Without the password, the file's contents are ciphertext — unreadable everywhere, by any software. This is the real protection.
• The permissions password (the owner password) does not encrypt anything from readers: it sets flags like “printing not allowed” or “copying not allowed”, and viewers are supposed to honour them. Supposed to. The document itself is fully readable, and much software simply ignores the flags. Treat permissions as a polite notice, never as security.

When people say “password-protect a PDF”, what they almost always need is the open password.

What AES-256 means on the label

Modern PDF protection encrypts with AES-256 — the same encryption family used for banking and government archives. Practically, this means nobody is “cracking the encryption”: with a strong password, the mathematics is not the weak point. Older PDFs used RC4-based schemes that today fall to off-the-shelf recovery tools in minutes — if a protected file matters and it was created many years ago, re-protect it with a current tool. Our Protect tool applies AES-256, and does the encrypting in your browser, so the unprotected file never travels anywhere.

The weak point is always the password itself

Attackers do not break AES; they guess passwords, billions per second, starting with the likely ones. Which makes the rules unglamorous and familiar:

• Length beats cleverness. A four-word phrase — orbit-mango-ladder-June — is both stronger and easier to type than P@ssw0rd!.
• Don't derive it from the document. The recipient's name, the invoice number and the current year are the first guesses, not the last.
• The document dies with the password. There is no “forgot password” for encryption — that is the entire point. Store the password in a password manager, and keep an unprotected copy of the file somewhere already secure, like an encrypted drive.

Sending a protected PDF without undoing the protection

One rule carries most of the value: never send the password in the same channel as the file. Email carrying both the attachment and “the password is Tiger2026” protects against exactly nothing — anyone who has the email has both. Send the file by email and the password by text message or a phone call, or agree it in person beforehand. And before protecting at all, ask whether the file's contents are the issue rather than access — if specific names or numbers must go, that is redaction, a different job entirely.

Removing a password you know

The legitimate everyday case: your bank sends statements locked with a code, and you file them in an already-encrypted archive where the per-file password is pure friction. Opening the file with the password and saving an unprotected copy is exactly what a remove-password feature does — it requires knowing the password, since without it the file is unreadable ciphertext. What no honest tool offers is removing an open password you don't know; despite what some websites advertise, that is password-guessing, and against AES-256 with a decent password it does not work.

Summary

• Open password = real encryption. Permissions password = a request, widely ignored.
• Insist on AES-256; re-protect files encrypted many years ago.
• Long passphrase, not related to the document, stored in a password manager.
• File and password travel by different channels, always.
• Contents secret? Redact. Access restricted? Encrypt. Know which job you're doing.

Keep reading