How to Password-Protect a PDF (and What the Password Does Not Hide)

Sending a contract, a payslip or a medical summary by email usually means one question: what stops the wrong person reading it? A PDF password is the obvious answer, and it is the right one - but it is worth knowing exactly what it does, because the gap between "encrypted" and "private" is where most disappointments happen.

What the password actually protects

An open password on a PDF encrypts the content. Without the password, the pages are not hidden behind a grey box - they are not there. There is no rendering to intercept, no "print" button to press, no text to copy out of a viewer. The file is bytes that only become a document again when the right key is supplied.

Modern tools use AES-256, which is the same standard used for classified government material. It is not a toy lock, and it is not a speed bump.

That covers the realistic risk: an attachment forwarded to the wrong person, a file left in a shared folder, a laptop that gets borrowed. For those, an open password does the job properly.

What it does not protect

Here is the list people rarely hear:

• A photograph of the screen. If the recipient is allowed to see the document, they can photograph it, screenshot it, or read it out loud. Encryption stops the file being opened without the password - it cannot stop someone who has the password from copying what they see.
• A weak password. password123 on an encrypted file is a locked door with the key taped to it. If the file might travel, use a passphrase - four unrelated words are longer, easier to remember, and far harder to guess than a short password you have to write on a sticky note.
• The metadata. This one surprises people, and it matters more than you would expect. Encryption hides the pages; it does not touch the document information, which can still carry the author, the title, the company, the software that produced the file and the exact time it was created. Hand an encrypted file to a stranger and they can still learn your name. For that case, encrypt and strip the metadata.
• A file you have already sent. Changing the password after the fact does nothing about the copy that was already in their inbox.

Two different passwords, doing two different jobs

This is the distinction that catches people out.

Most people mean the first one and assume they are getting the second. If your real worry is "they can read it and then paste it into their own document", an open password does nothing for you - you want printing and copying blocked instead.

The mistakes that lock people out

Every one of these is avoidable, and every one of them has happened to somebody this week.

Sending the password in the same email. An encrypted attachment with "the password is 1234" in the body of the message is an encrypted file with the key attached. If you are going to send both, send them separately - a message to a different app, or a phone call. If that is not practical, agree a password in advance over a channel you already trust.

Typing the password into the same tool that encrypts it. The Protect PDF tool asks for the password twice, specifically so a typo cannot lock you out of a document you have no other copy of. Take the extra click.

Forgetting it and expecting a recovery. There is no backdoor. An encrypted PDF is decrypted with the key or not at all - which is the point, and which is also why you should keep the unencrypted original somewhere safe. This is worth saying plainly: password protection is a commitment, and you should make it deliberately.

Encrypting a 300-page scan. A big scanned document can be hundreds of megabytes before encryption and slightly larger after it. Check the file size before you attach it, or you will discover the problem when the upload fails on the receiving end.

Assuming every reader supports it. Older mobile readers and some corporate viewers still struggle with AES-256. If the recipient is using something old, send them an unencrypted copy over a channel you trust rather than a file nobody can open.

Sending a protected PDF without sending the password

The practical pattern, and it works:

1. Send the file and the password through different channels. The file by email, the password by text message or a phone call. A forwarded email no longer contains the key.
2. Use a passphrase the two of you can both remember and change on a schedule - no password manager needed for a one-off.
3. For repeat exchanges, agree one password over a channel you already trust and reuse it. The security comes from the channel you agreed on, not from the password itself.

Before you send: what the file still reveals

If the recipient is someone you have never met - a buyer, a landlord, an employer, a journalist - an encrypted PDF is not the end of the story. The metadata still identifies the machine and the person who made it.

That is why the two tools go together. Remove PDF Metadata deletes the document information dictionary - the author, the title, the keywords, the producer and the timestamps - so the file you send does not describe you before it even asks for the password. Protect PDF encrypts the content. Neither one makes a document anonymous on its own; together they are the difference between "this file is locked" and "this file says nothing about who made it".

And the order is the reverse of what you would guess: strip the metadata first, then encrypt. A PDF's metadata sits in the trailer, outside the encrypted content, so encrypting first would not hide it - and you cannot strip metadata from a file you have already locked without the password. The full explanation is in how to remove metadata from a PDF.

A short checklist

• The password goes in a separate channel from the file. Never in the same message.
• Use a passphrase - four unrelated words - not password123.
• Keep the unencrypted original. There is no recovery.
• Check the file size before you encrypt a large scan.
• Confirm the recipient's reader can open AES-256 before they need to.
• If the file is going to someone you do not know, strip the metadata too.
• Send the plain file over a channel you trust rather than a locked file nobody can open.