A tax return, a signed contract, an HR document with someone's personal details — some PDFs shouldn't open for just anyone who gets hold of the file. Protect PDF adds real password encryption entirely in your browser, so the password itself never leaves your device either.
This guide covers how to protect a file, what the encryption actually is, how to choose and share the password sensibly, and — just as important — what a PDF password realistically does and doesn't protect against.
How to password-protect a PDF
- Open Protect PDF and drop in your file.
- Set a password.
- Download the protected PDF — anyone opening it will be prompted for that password first.
The protected file is a normal PDF in every other respect: same pages, same content, same behavior in any reader. The only difference is the prompt standing between the file and anyone who tries to open it.
When a password is worth the friction
Password protection trades convenience for a genuine control, so it's worth being deliberate about when that trade pays off:
- Documents in transit — the classic case. A file attached to email passes through multiple servers on its way to the recipient; a password means a copy intercepted or misdelivered along the route is unreadable.
- Files in shared storage — a PDF dropped into a shared drive, cloud folder, or team workspace is visible to anyone with access to that space. A password limits the document itself to the people you actually intended.
- Personal documents on a shared or work device — scans of ID, contracts, and financial statements living on a machine other people can open.
- Documents sent to a group — where "everyone who has this file" should be a smaller circle than "everyone who might receive it forwarded."
The common thread: a password protects the file wherever it goes, independent of the security of whatever system carried it there. That's the property nothing else gives you quite as simply.
What encryption is actually used
AES-256 by default — the current PDF 2.0 standard, and the same encryption strength used well beyond PDFs. If you need the file to open in an older PDF reader that doesn't support AES-256, you can switch to RC4 128-bit instead, though RC4 is the weaker, legacy option and should only be used when that compatibility is genuinely needed.
In practice the compatibility concern is rare today: every current release of Acrobat, Preview, Edge, Chrome, and the major third-party readers handles AES-256 without complaint. RC4 mainly earns its keep for readers stuck on decade-old versions or for embedded devices (some printers' direct-print features, some scanner panels) whose PDF support froze in time. If you don't know you need RC4, you don't need RC4.
The strength question deserves a plain answer, too: for a properly chosen password, AES-256 is not "hard to crack" — it's computationally infeasible, by an margin so large it's not a serious discussion. The realistic weak point of any encrypted PDF is never the cipher; it's the password. Which is the next topic.
Choosing a password — and sharing it safely
Since the encryption is only as good as the password, choose one that resists guessing. Length matters more than symbol-soup: a four-word passphrase no one else would associate with you ("amber-cartwright-violin-harbor") is both easier to type correctly and harder to crack than "P@ssw0rd!". Avoid anything derivable from the document or the recipient — names, birthdays, the company name, "invoice2026" — because those are exactly what someone holding the file would try first.
Then think about the channel. The file and the key to it shouldn't travel together: if you email the protected PDF, send the password by text message or a chat app — a different route entirely. Sending both through the same pipe means anyone who intercepted the email got the safe and the combination. This one habit costs nothing and closes the biggest practical hole in the whole approach.
Password vs. permissions — they're not the same thing
The password you set controls whether the file opens at all. Separately, a PDF can also carry permission flags — no printing, no copying text, no editing — which conforming readers respect, but which aren't cryptographically enforced the way the open-password is. Think of permissions as a polite request most software honors, not a lock; the password is the actual lock.
This distinction explains a lot of real-world confusion: "I set 'no editing' in my PDF software and my colleague changed it anyway" happens because their tool simply declined to honor the request — which the format permits. If the goal is that nobody without the key can read the document, that's the password's job, and it's the one guarantee on offer.
There's no recovery if you forget it
Because everything happens in your browser, PDFlyHQ never sees or stores the password you set — which also means there's no "forgot password" flow to fall back on. Write it down somewhere safe before you send the file anywhere.
This is the honest cost of the privacy model. Services that host your file can offer password reset because they hold both the document and the key; a tool that holds neither can't. Keep a copy of the password in whatever system you already use for credentials, and tell the recipient how you'll communicate it before the file arrives.
What the password doesn't protect against
Being clear-eyed about limits beats trusting a lock for more than it does. A PDF password guards the file — it does nothing about what happens after someone legitimate opens it. A recipient with the password can re-save an unprotected copy, screenshot pages, forward the content, or print and rescan it. Password protection controls access, not behavior; if you need to stop intentional redistribution by the reader, no PDF feature will do that.
It's also worth remembering who the threat model is: encryption defeats someone who obtains the file without the password. For confidential documents in email and storage — the overwhelming majority of real cases — that's precisely the risk worth closing.
Removing protection later
If you (or whoever you send the file to) later need to remove the password from a PDF you already have the password for, that's the reverse job — see Unlock PDF.