NOPPAWEvery week, documents that should never travel naked — ID scans, payslips, contracts, medical letters — cross the internet as ordinary email attachments, readable by every system that handles them and by anyone who later gains access to either mailbox. A PDF open password does not make a document invincible, but it changes the default from "anyone holding the file can read it" to "only someone with the password can". Here is what that protection really does, what it does not, and how to use it without locking yourself out of your own files.
What PDF encryption actually does
Setting an open password encrypts the document's contents with AES — the same cipher family that protects banking traffic. The Protect PDF tool runs the qpdf engine in your browser and tries 256-bit AES first, the current standard, falling back only if a file resists it. Without the password, the pages, text and images are ciphertext: a stranger who intercepts the attachment gets noise, not your documents. With the password, the file opens normally in any standard reader. Nothing about the document's appearance changes — the protection is entirely in who can get in.
What it does not do
Encryption guards the door; it does not govern the room. Anyone who knows the password can open the file and then forward it, copy its text or photograph the screen — an open password cannot and does not try to police a legitimate reader. It also does not hide the file's existence, its name, or the metadata inside it: title and author fields travel with the document, which is why checking them with Edit PDF Metadata before sending anything sensitive is a two-minute habit worth having. And it proves nothing about identity — a password-protected file from the wrong sender is still from the wrong sender.
Share the password on a different channel
This single rule carries most of the real-world security. File by email, password by chat or phone call — never both in the same thread, and never in the message the file is attached to. A mailbox compromise then yields an unreadable attachment and no key, while the chat holds a password with nothing to open. Tell the recipient what the password is for ("for the contract PDF I just emailed"), use a password you do not reuse anywhere else, and if the document is going to several people, expect the password to spread accordingly — protect for the audience you actually have, not the one you wish for.
Choosing a password that holds up
Length beats cleverness. A short password of scrambled symbols falls to automated guessing faster than a long, plain passphrase of several unrelated words, and the passphrase has the virtue that a human can type it over the phone without spelling errors. Make it unique to this document or recipient — a password reused from your email account turns one leak into every leak. Store it in your password manager under the document's name, because the most common PDF password disaster is not an attacker at all: it is the sender, three weeks later, unable to open their own file.
One more judgement call: not every document deserves a password. A public brochure, a form anyone may download, a document already published elsewhere — encrypting those adds friction and achieves nothing, and it trains your recipients to treat your passwords carelessly. Reserve protection for files whose contents are genuinely someone's business: identity documents, finances, health, contracts, anything with a signature on it. Scarcity is what keeps the habit meaningful, on both ends of the exchange.
Receiving, and removing protection from your own files
On the receiving end, save the protected original as received; if you need a working copy, unlock a duplicate with Unlock PDF — it needs the password, because that is the point — and keep the unlocked copy somewhere private, never in the shared folder the protected one travels through. The same applies to your own protected files: keep one unprotected master in a safe place, and treat protected copies as the travelling edition. If a password is genuinely lost, there is no honest recovery to sell you: the encryption is doing its job, and the file stays closed.
A sane sending checklist
- Open the final file once and confirm it is the right document, complete and readable.
- Check the title and author metadata; clear anything that should not travel.
- Set the open password with a current tool — 256-bit AES where offered.
- Send the file through your usual channel.
- Send the password through a different channel, labelled with what it opens.
- Keep your own unprotected master somewhere only you can reach.
Six steps, most of them seconds long. The pattern pairs naturally with the signing workflow in the guide to signing a PDF without printing: sign first, then protect the signed copy, then send the password separately.