Password-protecting a PDF is one of the few file operations where the stakes are obvious. A bank statement, a contract, a medical letter or a passport scan is about to travel through email or a chat app, and a password is the difference between —anyone who finds the attachment can read it— and —someone needs the secret as well—.
It is also an area full of half-truths. Permission checkboxes are described as security. A forgotten password is treated as a support problem. —Military-grade encryption— is printed on pages that never explain what is actually encrypted. This guide keeps the useful parts and drops the theatre.
Two different locks
PDF has two password concepts, and they are often confused:
- The user password (also called the open password) is required to open and decrypt the document. This is the one that matters for confidentiality.
- The owner password (also called the permissions password) controls whether a reader allows printing, copying or editing. Many tools can remove these restrictions without knowing the owner password, because the document is not strongly encrypted for that purpose.
A site that says —remove restrictions from any PDF— is usually removing owner-password flags, not breaking a user password. That is a useful feature for a file you own; it is not a decryption service for a file you do not.
What to choose in the tool
PocketPDF—s Protect PDF tool offers two encryption options:
- AES-256 (PDF 2.0, revision 6). The modern default. Current readers — Adobe Acrobat, browsers, Preview, most PDF apps — support it. Use this unless you have a specific compatibility reason not to.
- RC4 128-bit. An older algorithm for older readers. It is weaker than AES-256 and should be treated as a compatibility mode, not a first choice.
The permission switches are separate. They can request that the file not be printed, copied or edited. A well-behaved reader will honour them. A determined person with the right software can bypass them. If confidentiality matters, the user password is the control that counts.
What encryption protects
A password-protected PDF is encrypted at rest: the file on disk is not readable without the password. If you attach it to an email, the encrypted bytes travel through the mail system; someone who intercepts the attachment gets ciphertext, not the document. If the file is later copied to a USB drive or a cloud folder, it remains encrypted.
That is a real and useful property. It covers the most common accident: the file ends up somewhere you did not intend, and the password is not with it.
What it does not protect
- A recipient who can open it. Once someone has the password, they can read, photograph the screen, copy text by hand or forward both the file and the password. Encryption does not control a person who is authorised to see the content.
- A weak password. AES-256 with —123456— is still a weak lock. An attacker with the file can try guesses offline; the algorithm cannot save a bad secret.
- A compromised device. Malware, a keylogger or someone with physical access can read the file before it is encrypted or after it is opened.
- Metadata you left in. Author, title, creation date and software fields can reveal information even when the content is encrypted. Remove them first if they matter.
- Legal authenticity. A password is not a signature, a certificate or a notarial act. It proves possession of a secret, not identity.
The password is the weak point
Use a long passphrase or a generated password stored in a password manager. Length matters more than a clever mix of symbols. A sentence of four or five random words is easier to type and harder to guess than —P@ssw0rd2026—.
Do not reuse the password from your email, bank or main account. If the PDF password leaks in a chat thread, you do not want it to open anything else. If you are sending several files to the same person, a unique password per file is better, even if it is less convenient.
How to share the password
The password should travel through a different channel from the file. If both are in the same email, the encryption protects you only against someone who finds the attachment but not the email — a narrow case. Practical options:
- Send the file by email and the password by Signal, WhatsApp or a phone call.
- Put the file in a shared folder and send the password by a different service.
- Use a password manager—s secure share feature if both people use one.
- For a one-off, agree on a password in person or by voice, not in the same thread.
Tell the recipient which channel the password will use before you send the file. A surprising encrypted attachment with no explanation tends to produce a —this file is broken— reply.
If you lose the password
There is no recovery path. The Unlock PDF tool can remove encryption only when you supply the correct password. It does not guess, crack or phone home for a master key. That is not a limitation to apologise for; it is what encryption means.
If losing access would be serious, keep an unprotected copy in a safe place before you delete the original. A password manager entry plus an offline backup is a reasonable belt-and-braces approach. Test that the protected file opens in a reader before you rely on it.
Remove metadata before you encrypt
Encryption hides the content, not necessarily the file—s metadata. A document can carry an author name, a company, a title, creation and modification dates, and the software that produced it. If those fields matter, run Sanitize PDF first, then encrypt the cleaned file. Check the result in a PDF reader—s document properties.
Sanitizing is not forensic redaction. It removes common metadata fields; it does not guarantee that every hidden object, layer or revision is gone. For a legal disclosure or a hostile review, use a dedicated redaction workflow and verify the output.
Encryption is not a signature
A password-protected PDF is not automatically signed. The signature tool places a drawn image on the page; it carries no cryptographic identity and no tamper evidence. For a contract that needs signer identity, use a qualified e-signature service. A password and a drawn signature solve different problems and should not be presented as one another.
A five-step checklist
- Clean first. Remove metadata if it reveals more than the document should.
- Choose AES-256. Use RC4 only if an old reader cannot open the modern format.
- Use a long, unique password. Store it in a password manager; do not reuse it.
- Test the output. Open the protected file in a reader, confirm the password works, and check the page count.
- Share the password separately. Send the file through one channel and the password through another; keep a safe backup if access matters.
That is the whole job. The encryption is real; the discipline around the password is what makes it useful.