"Password protect" and "watermark" solve different problems
AES-256 vs. a stamp across the page — and which one you actually want when you're sharing sensitive work.
People reach for password-protect when they want a watermark and watermark when they want encryption. Five minutes of reading saves a leak.
Ready to try this yourself?
Open Add Password in a new tab and read the rest while you upload.
These two tools live next to each other in every PDF editor and they sound similar ("protect my document"), but they protect against completely different threats. Picking the wrong one is a common, embarrassing mistake.
Password protect
Encrypts the file with AES-256. The reader has to enter the password to open it. Without the password, the contents are gibberish — even if someone exfiltrates the file from your cloud storage, they can't read it.
What it doesn't do: stop a recipient who *has* the password from forwarding it, copying text out, or taking a screenshot. Once the password leaves your hands, the encryption stops mattering.
Watermark
Stamps text or an image across every page — your name, the recipient's name, "CONFIDENTIAL", a tracking code. Doesn't stop anyone from reading the document. The point is: if it leaks, the watermark tells you whose copy got out.
What it doesn't do: encrypt anything. Anyone who gets the file can open it without a password. Don't use it where you needed encryption.
When to use each
- Sending sensitive material to one specific person → password protect, share the password over a different channel (text, call — not email).
- Distributing a draft to a review group where you want to know who leaked it → watermark each copy with the reviewer's name.
- Both at once is fine, and common in legal/finance — watermark + password.
- Public marketing PDF, internal team doc with no real secrets → neither. Save yourself the friction.