PDF Passwords Explained: Open vs Permissions, AES-256 and Limits

Two passwords, two very different jobs

A PDF can carry two separate passwords, and most confusion about PDF security comes from treating them as the same thing. Adobe's documentation calls them the Document Open password and the Permissions password; the PDF specification and tools such as qpdf call them the user password and the owner password.

• Open (user) password. Without it, the reader cannot display the file at all. The page content, images and attachments are stored encrypted, and the password is what unlocks the key.
• Permissions (owner) password. The file opens normally, but it carries flags asking the reading software to block certain actions, typically printing, copying text and images, and editing. The owner password is what you need to change those flags later.

The practical difference is simple to remember. An open password decides who can read the document. A permissions password only expresses what you would like readers to do with it. If confidentiality is the goal, the open password is the one that matters.

	Open (user) password	Permissions (owner) password
Needed to view the file	Yes	No
What it controls	Access to the content	Printing, copying, editing flags
Enforced by	Encryption	The reader app choosing to obey
Real protection against a determined person	Yes, if the password is strong	No

What AES-256 actually protects

Modern PDF encryption uses AES with a 256-bit key. The qpdf manual notes that 256-bit encryption always uses AES and recommends it over the older 128-bit variants; older files may still use RC4, which is weak. Nobody is going to break AES-256 itself by brute force. What an attacker can do is guess the password, because the key is derived from it.

This is the part people underestimate. A website login can lock you out after a handful of wrong attempts. A PDF file sitting on someone else's laptop has no such limit: they can run guessing software against their own copy for as long as they like, with no one watching. So the strength of an encrypted PDF is, in practice, the strength of its open password. "AES-256" on a file protected with 123456 or a date of birth is a strong lock on a door with the key taped to it.

Encryption also has a boundary in time. Once a recipient opens the file with the correct password, they can read it, screenshot it, or print it if printing is allowed. Encryption protects the file in transit and at rest, for example as an email attachment or on a lost USB stick. It does not control what an authorised reader does next.

Why permission restrictions are weak

A restrictions-only PDF has to be readable by anyone, so every copy carries everything needed to display it. The qpdf manual is blunt about the consequence: since any program that can read the file has the decryption key, there is fundamentally no way to stop an application from ignoring the restrictions. Adobe Reader, browsers and most mainstream apps honour the flags; plenty of other software does not, and some simply removes them.

That makes restrictions useful for one thing: signalling intent and preventing accidents. Blocking edits on a final contract reminds colleagues not to tinker with it. Blocking printing on a draft discourages paper copies floating around the office. Neither stops someone who actually wants to copy the text.

There is a second, less obvious weakness. Anyone who knows the open password has the same key as the owner. With the open password, a tool such as qpdf can decrypt the file and write a copy with no restrictions at all. So if you send a PDF with an open password and restrictions, assume every recipient could remove the restrictions if they chose to. For anything where copying really matters, the protection has to be a contract, a watermark naming the recipient, or not sending the file at all.

Choosing a password that holds up

Length beats cleverness. NIST's digital identity guidelines (SP 800-63B) require passwords used on their own to be at least 15 characters, recommend allowing at least 64, and tell services not to impose composition rules such as "one symbol and one capital". The UK's National Cyber Security Centre suggests three random words joined together as a memorable way to reach that kind of length, and warns that swapping letters for look-alike symbols (a zero for an o) adds little, because guessing tools try those substitutions automatically.

Some plain arithmetic shows why random words work. If each word is picked truly at random from a list of 7,776 words, three words give 7,776 × 7,776 × 7,776, about 470 billion combinations; four words give about 3.7 quadrillion. By comparison, eight random lowercase letters give 26 to the power of 8, about 209 billion. The key word is random: words you choose yourself ("summer", "london", your pet's name) are far easier to guess than the numbers suggest.

For a PDF, keep these rules in mind:

• Use a fresh password for each file or batch of files you send. Never reuse your email or banking password.
• Avoid anything printed in or derivable from the document itself, such as an account number, name or date of birth.
• Generate and store it in a password manager if you will need it again. Both NCSC and Adobe recommend password managers over notes or emails.
• Remember that recipients have to type it. Four lowercase random words with a hyphen between them are much easier to read over the phone than 16 random symbols, with comparable strength.

Send the password a different way from the file

The most common real-world failure is not a weak password; it is a strong password sent in the same email as the attachment. Anyone who sees that email, whether through a forwarded thread, a shared mailbox or a compromised account, gets both halves at once.

Use a second channel instead. If the PDF goes by email, send the password by text message, a messaging app, or read it out in a phone call. For regular exchanges with the same person, agree the password once in person or by phone and reuse it only for that relationship. Adobe's own best-practice list makes the same point: share passwords through a secure method, not alongside the file.

If you forgot the open password

This is the hard truth: without the open password, an AES-256 PDF cannot simply be unlocked. PDFora does not crack or guess passwords, and Unlock PDF needs the open password whenever the file asks for one. Services that promise to "recover" any password are guessing; against a long random password they will fail, and you would be handing your document to a stranger in the attempt.

Before giving up, work through the realistic options:

1. Check where it came from. Banks, insurers and payroll systems that encrypt statements usually explain the password format in the covering email or on their website, often a combination of name and date details. Follow that format exactly, including upper or lower case.
2. Search your password manager and sent messages for the file name or the recipient's name. If you protected it yourself, you may have saved or sent the password at the time.
3. Look for an unprotected original. The Word file, the scan, or an earlier export may still be on your computer or in cloud storage.
4. Ask the sender to reissue it. For a statement or certificate, this is almost always quicker than any other route.

If none of those work, the document is effectively gone. That is the point of encryption, and it is why the next section starts with keeping an unprotected master copy.

Using Protect PDF and Unlock PDF

Both tools run entirely in your browser using qpdf compiled to WebAssembly, so the file and the password never leave your device. Here is the full procedure for protecting a file:

1. Keep an unprotected original somewhere safe. The protected copy is for sending; the original is your backup if the password is lost.
2. Open Protect PDF and choose the file. Files that are already encrypted are refused; unlock them first if you want to change the protection.
3. Type the open password twice. This is the password recipients will need.
4. Untick Allow printing, Allow copying text and images or Allow editing and form filling only if you want those restrictions, bearing in mind the limits described above.
5. Optionally set a separate permissions password. If you leave it empty, a long random one is generated and never shown, which means the restrictions cannot be changed later with that password; you would unlock the file with the open password and protect it again instead.
6. Download the result, named like report-protected.pdf, then reopen it yourself to make sure it really asks for the password before it goes anywhere.

Unlock PDF works the other way. If the file asks for a password when opened, enter it and the tool writes a copy with the encryption and restrictions removed (report-unlocked.pdf). If the file opens without a password but has restrictions, no password is needed. Use it only on files you are entitled to unlock, such as your own statements, and treat the decrypted copy as sensitive: it opens for whoever finds it, so delete it when the job is finished.

One sequencing tip: password protection should be the very last step. Merging, compressing or adding page numbers to an encrypted file will either fail or need unlocking first, so finish the document with tools such as Merge PDF or Compress PDF, check it, and protect it just before sending.