Protect PDF

The formula

• Your PDF is read locally in your browser's memory, nothing is sent anywhere.
• The password you typed is used to encrypt the document with AES-256 encryption.
• A new encrypted copy of the PDF is built, and the password becomes required to open it.
• The locked PDF is saved to your device; your original file stays exactly as it was.

A worked example

A contract you want to email safely: open it here, set the password BlueRiver-2026!, press Protect PDF, and download contract protected.pdf, anyone opening it is asked for the password first.

More about the Protect PDF

Choosing a password that actually protects

Length beats cleverness. A 12 character mixed password like BlueRiver-2026! resists guessing far better than an 8 character 'clever' one. The tool asks for at least 8 characters with letters and numbers, treat that as the floor, not the goal.

And never reuse the password you use for email or banking. A PDF password's whole job is to be unique to that document; a password manager is the sane place to keep it.

Send the file and the password separately

This is the step people skip: email the locked PDF, then text or call the recipient with the password. Sending both in the same email defeats the purpose, anyone who intercepts the message gets the lock and the key together.

Test the locked file yourself before sending it: open the download fresh and confirm it asks for the password. Thirty seconds of checking beats an embarrassing 'it didn't ask me for anything' reply.

What your recipient experiences

The locked PDF uses the standard PDF encryption format, so it opens in Adobe Acrobat, Chrome, Edge, Preview and phone readers, the recipient just enters the password first. Nothing special to install on their end.

Your original file is never altered. You get a new password locked copy alongside it, which means you can keep working from the unlocked original and only lock copies you send out.

The one rule: do not forget it

A forgotten PDF password cannot be recovered, that unrecoverability is exactly what makes the encryption trustworthy. Save the password in your password manager before you lock the file, not after.

If you are protecting something you will need for years (tax records, legal documents), consider whether a password you will remember in 2030 is realistic, or whether an encrypted drive is the better home for it.

Protecting without annoying people

Not every document needs a password. Reserve encryption for files that would genuinely cause harm in the wrong hands, contracts, medical records, financial statements. Password protecting a lunch menu trains recipients to resent the friction.

When you do protect, tell the recipient a password is coming and how you will send it. A locked attachment with no explanation looks like spam and gets ignored, a one line heads up gets it opened.

Passwords vs permissions: know the difference

This tool sets an open password, the file cannot be viewed without it. Some PDFs also carry a permissions password that allows viewing but blocks printing or copying; that is a weaker, separate mechanism and not what this tool creates.

If your goal is 'they can read it but not forward it usefully', an open password is the right call. If your goal is DRM style control after sending, no PDF password truly provides it, once someone can view a document, they can photograph the screen.

What to do when recipients cannot open it

The most common support call: 'it says I need a password.' Nine times out of ten, they missed your separate message with the password. Resend the password through the other channel before assuming a technical problem.

If they have the password and it still fails, suspect special characters: some older PDF readers mangle passwords with unusual symbols. Stick to letters, numbers and basic punctuation (- _ !) for maximum compatibility.

And if a recipient genuinely cannot use passwords (a locked down corporate system, an accessibility tool), consider whether protection is the right call for that document, or whether a secure sharing link serves better.

Protecting vs. redacting: know the difference

A password stops casual access; it does NOT remove information from the file. If the PDF contains text that must never be seen (SSNs, account numbers), you need redaction, actually removing the content, not just a password.

Redaction means deleting the underlying text and images, not drawing black boxes over them (which can be removed to reveal the text). Use a proper redaction tool, then protect the redacted file if it still needs access control.

The rule: passwords control WHO opens it; redaction controls WHAT is in it. Sensitive content needs both, redact first, then protect.

Worked example: locking a signed contract end to end

Say you are emailing an 18 page signed agreement. Open it here, set a password of at least 12 characters, the example used elsewhere on this page, BlueRiver-2026!, runs to 14, and download the locked copy, which arrives as a separate file while your original stays unlocked on your machine. Before sending anything, open the download yourself and confirm the password prompt appears and your password opens it.

Then split the delivery: the locked PDF goes by email, the password by text message a minute later. The whole routine adds perhaps two minutes to sending a contract, and it means an intercepted email, a forwarded thread or a misaddressed message exposes a locked file instead of the agreement itself. Test, split, send, the same order every time, so it becomes habit rather than effort.

Which documents earn a password, and which do not

Ask one question: what happens if a stranger reads this? Tax returns, bank statements, medical letters, salary documents and signed contracts answer badly, so they earn a password every time. A price list, a meeting agenda or a document already published on your website answers “nothing much”, and locking those only trains your recipients to ignore the friction when it actually matters.

The grey zone is the mildly personal file, a school report, an insurance quote with your address on it. A sensible rule is to protect anything containing an account number, a financial figure or a home address, and to leave purely informational documents open. When in doubt, protect: a recipient mildly inconvenienced beats a document mildly leaked, every single time.

Habits that quietly undo good encryption

AES-256 cannot rescue a careless workflow. The three classic failures are sending the password in the same email as the file, reusing your email password as the PDF password, and choosing something guessable from your social media, a pet, a team, a birthday. Each one hands an attacker the shortcut that the encryption was specifically built to deny them.

A subtler leak is the filename and the email subject. A locked file named with a client’s full name and account reference announces exactly what is inside before anyone tries the password, and the subject line travels unprotected even when the attachment does not. Keep names and subjects plain. “Agreement for signing” protects the metadata while the password protects the contents.

How to use the Protect PDF

1. Click Select PDF file and choose one PDF document.
2. Type a strong password (at least 8 characters, mixing letters and numbers) and confirm it.
3. Press Protect PDF and wait for the encryption to finish.
4. Click Download PDF to save the password locked copy to your device.
5. Share the password with the recipient through a separate message, never in the same email.