Set a password and drop your PDFs in. They come back encrypted with AES-256 — the cipher the current PDF standard specifies — and cannot be opened without it. The file and the password both stay on your device, which is the only sensible arrangement for a tool whose entire purpose is keeping a document private. One distinction this page makes that most do not: the password is real cryptography, and the permission flags for printing and copying are not. Those are a request recorded in the file that only well-behaved viewers honour, and any tool that ignores them removes them in seconds — including the password remover on this same site. Encrypt with a password if you need the document protected; treat the permission switches as a polite notice.
| User password | Permission flags | |
|---|---|---|
| What it is | Encryption | A request in the file |
| Stops reading the file | Yes | No |
| Removable without the password | No | Yes, in seconds |
| Honoured by every viewer | Yes, it must be | Only well-behaved ones |
| Use it for | Actual confidentiality | Signalling intent |
Neither. The PDF is encrypted in your browser and the password never leaves your device. Using a server-side encryption tool means handing both the confidential document and its key to someone else, which rather defeats the exercise.
AES-256, which is what ISO 32000-2 specifies for PDF and is not breakable by any known practical attack. AES-128 is offered for viewers older than Acrobat 9 (2008) and is still sound. The broken RC4 variants the format permits are deliberately not offered.
No. That is what encryption means — there is no backdoor, no reset and no recovery, for you or anyone else. Write the password down somewhere safe before encrypting anything you need back.
The password is cryptography: without it the content cannot be read. The permissions are a flag in the file saying 'please do not allow printing', which only viewers that choose to honour it will respect. Any tool that ignores them strips them instantly. They are worth setting as a signal of intent, but they are not protection.
It grants full access regardless of the permission flags, while the user password opens the document subject to them. If you only need one password, leave it blank and it matches the one above — two different passwords on a document going to one person is more often a mistake than a feature.
Length, more than anything. Four unrelated words beat a short string with punctuation in it, and are easier to remember. AES-256 is only as strong as what it is keyed with — an unbreakable cipher guarding a guessable password protects nothing.
Almost certainly not. That flag blocks assistive technology from reading the document, which makes it unusable for people who rely on a screen reader. It exists for narrow legal situations and is a poor default.
Encryption is real AES-256 applied to the document's content streams and strings, the cipher ISO 32000-2 specifies, with AES-128 available for viewers older than Acrobat 9. The RC4 variants the PDF format also permits are not offered: they are broken, and a tool that lists them alongside AES invites someone to pick the one that does not work. The distinction the interface makes loudly is between the password and the permission flags, because they are not the same kind of thing at all. The user password is genuine cryptography — without it the bytes cannot be read, by anyone, ever. The permission flags for printing, copying and editing are a request recorded in the file, honoured only by viewers that choose to; any tool that ignores them strips them instantly, including this site's own password remover. Presenting both as 'protection' is the standard misrepresentation in this category, so the page says which is which. When no separate owner password is set it defaults to the user password, since two different passwords on a document meant for one recipient is a footgun rather than a feature. Password strength is shown because AES-256 guarding 'letmein' protects nothing, and the advice favours length over symbol variety, which is what actually resists a guessing attack. Everything runs in your browser: neither the file nor the password is transmitted, which is the only arrangement that makes sense for a tool whose whole purpose is confidentiality.