Email is a postcard, not an envelope. A contract, payslip or scan sent as a plain attachment can be forwarded, misdelivered or read on any device that syncs the inbox. Password-protecting the PDF takes half a minute and changes the maths completely: even a forwarded copy stays sealed. Here is how to do it properly.
What PDF protection actually does
Modern PDF encryption — AES-256 in current tools — scrambles the document's contents with a key derived from your password. There are two passwords in the PDF standard: the user password, required to open the file at all, and the owner password, which controls permissions such as printing or copying. For sharing sensitive documents, the user password is the one that matters: without it, the file simply does not open.
Protection is only as strong as the password. A short or guessable password can be brute-forced offline at leisure, because the attacker has the file forever. Twelve or more characters with a mix of words beats a short string of symbols, and a password you have never used elsewhere beats both.
Send the password separately — always
The password must never travel with the file. Sending the PDF and its password in the same email is locking the door and taping the key to it. Send the file by email and the password by a different channel — a chat message, a call, a separate email later. That way a single compromised account or misdirected message exposes nothing on its own.
Tell the recipient what the password is for and which document it opens, especially if you share files often. And agree in advance: if your bookkeeper or HR contact knows the routine, protected attachments become a habit rather than an exception that gets questioned.
Practical habits that keep protection useful
Protect the final version only. Encrypting drafts means juggling passwords for files that will change tomorrow; instead, finish edits, merge and organise first, then protect the exact file you send. Keep your own unprotected master copy in your archive — forgotten passwords are unrecoverable, and a locked archive is just an expensive form of deletion.
Name the file clearly (invoice-1042-protected.pdf is fine; the name itself leaks nothing sensitive), and check the result by opening it once: the password prompt should appear before any content does. Finally, remember what protection is not: it does not stop a legitimate recipient from forwarding the opened document, and it does not expire. For a copy that should be readable once and useless later, you need process agreements, not just encryption. For everyday sharing — the payslip, the signed contract, the ID scan a form demands — a strong password, sent separately, is the single highest-value habit in this article.
What to do when the recipient struggles
Most sharing friction is mundane, not malicious. The recipient's PDF app might be ancient, the password might be mistyped with caps lock on, or the file might have been renamed so many times that nobody knows which password belongs to it. Anticipate all three: mention the reader works in any modern PDF app, write the password exactly (passwords are case-sensitive, and a trailing space copied from a message breaks more logins than hackers do), and state the filename in the same message as the password hint.
For repeated sharing — monthly statements to an accountant, say — agree on a standing arrangement through a secure channel once, rather than inventing a fresh password per file in the same email thread. The goal is a routine both sides can execute half-asleep at month-end without either party loosening the rules.
Finally, audit your own sent folder occasionally. Anything you once emailed unprotected still exists there and in the recipient's inbox; you cannot recall it, but you can stop adding to the pile from today.
Ready to try it? Open the Protect PDF tool — it runs entirely in your browser, so your files never leave your device.
Try it yourself: Protect PDF runs entirely in your browser — your files are never uploaded.