Security & Privacy
PDF Encryption Explained: What Actually Protects Your File
AES-256, RC4, user and owner passwords, permission flags — what each one really does, and which of them provide genuine protection.
PDF security is a stack of features with very different strengths, presented in most software as one dialogue. Knowing which parts are cryptography and which are politeness is the whole subject.
The two passwords
A user password encrypts the document. Without it, the contents are ciphertext — no software can display them, because there is nothing to display until the key is supplied. This is real protection.
An owner password sets permission flags: no printing, no copying, no editing. The document is not encrypted against the reader at all; it is fully readable, and a flag politely asks software to disable certain actions. Compliant readers honour it. Anything else does not have to.
| Control | Mechanism | Real protection? |
|---|---|---|
| User password | Encryption | Yes, with a strong password |
| Owner password | Permission flags | No — advisory only |
| No printing | Flag | No |
| No copying | Flag | No |
| No editing | Flag | No |
The encryption algorithms
- RC4 40-bit — from the 1990s, broken, present only in very old files.
- RC4 128-bit — obsolete and not considered secure.
- AES-128 — still sound in practice.
- AES-256 — the current standard and what any modern tool should produce.
If you are creating protection today, AES-256 is the only sensible choice. If you are relying on protection someone applied a decade ago, it may be considerably weaker than it looks.
What encryption cannot do
It controls who can open the file. It has nothing to say about what an authorised reader does afterwards: they can forward it, print it, photograph the screen, or strip the protection from their own copy. Any claim that a PDF can be prevented from being shared after opening is describing DRM, which needs separate infrastructure and is not what a password does.
Choosing the right control
| Goal | Use |
|---|---|
| Only certain people may read this | User password with AES-256 |
| Signal that this should not be edited | Permission flags, understood as advisory |
| Prove the document has not been altered | A digital signature, not encryption |
| Trace a leaked copy | Per-recipient watermarking |
Do it now
Protect PDF
Add password protection to PDF. It runs in this browser tab — your file is not uploaded anywhere.
Open Protect PDFFrequently asked questions
Is PDF encryption secure?+
AES-256 with a strong password is. Permission flags are not encryption and offer no real protection.
Can PDF encryption be broken?+
Not the modern cipher. Weak passwords and obsolete RC4 encryption both can be.
Why can some tools remove a PDF password without knowing it?+
Because they are clearing permission flags on an unencrypted file, not decrypting anything.
Does encryption stop editing?+
It stops opening. Anyone who can open the file can edit their copy.