How to password-protect a PDF (and what the protection really does)
The difference between an open password and permission restrictions, which encryption to use, and the situations where a password is not enough.
Adding a password to a PDF is quick, and it is genuinely useful: a protected file can be emailed, stored in shared folders and backed up without the content being readable by anyone who stumbles across it. But "password-protected" covers two very different things in PDF, and only one of them actually keeps content secret. This guide explains both, shows how to apply them, and is honest about what a password cannot do.
Two kinds of password
The open password (the PDF specification calls it the user password) encrypts the content. Without it, a viewer cannot display the pages at all. This is real protection: the file is scrambled with a key derived from the password, and nobody can read it without either the password or a successful brute-force attack.
The permissions password (the owner password) does not hide anything. The document opens normally, but the viewer is asked to honour restrictions: no printing, no copying text, no editing, no adding comments. The word "asked" is the important one. The restrictions are flags inside the file, and software is expected to obey them. Many programs do. Many do not, and removing owner restrictions from a PDF that has no open password takes seconds with free tools. Treat permission restrictions as a polite request, not as security.
The practical consequence: if the goal is confidentiality, set an open password. If the goal is to discourage casual copying or editing of a document that is not secret, permission restrictions are fine, as long as you understand that a motivated person can ignore them.
Which encryption to choose
Modern PDF tools offer AES-256 encryption (introduced with PDF 2.0 and supported by Acrobat X and later, and by every current reader). Older options are AES-128 and RC4, which exist for compatibility with software from the early 2000s. There is no reason to choose anything but AES-256 unless a recipient is stuck on very old software. Protect PDF uses AES-256.
Encryption strength is only as good as the password. A six-character word can be brute-forced in minutes regardless of the algorithm. Use a passphrase of at least four random words or 12+ mixed characters, and send it to the recipient by a different channel than the file (for example, the PDF by email and the password by text message or phone).
Protecting a PDF on webutilitypro.com
- Open Protect PDF and upload the document.
- Enter the open password. Choose a strong one; you cannot recover it later if it is lost.
- Optionally set permission restrictions (printing, copying, editing) with a separate owner password.
- Click Protect, then download the encrypted file. The unprotected original and the result are deleted from our server after 60 minutes.
- Test it: open the downloaded file and confirm it asks for the password.
The original on your computer is unchanged. Keep an unprotected copy somewhere safe (an encrypted disk, a password manager's file storage) in case the password is forgotten; there is no "forgot password" for a PDF.
What a password does not do
- It does not stop the recipient sharing the file, or the password, or a screenshot. Once someone can read a document, they can copy it. Digital rights management systems try to prevent this and are a different product category.
- It does not remove hidden content. Metadata (author name, software, edit history), comments, previous versions in some files, and text under black rectangles are all still there. If you need to remove information permanently, use Redact PDF, which deletes the content rather than covering it.
- It does not protect the document while you work on it. Encryption happens when the file is saved; the open copy on your screen and in temporary files is readable.
- It is not a signature. A password proves nothing about who created the document. For that you need a digital signature with a certificate.
- It does not survive conversion. Converting the PDF to Word or images produces unprotected output.
When a password is the wrong tool
- Sending to many people. Everyone shares the same password, and it leaks. Use a document portal with per-person access instead.
- Long-term archiving. A password you need in ten years is a password you will lose. Archive unencrypted inside an encrypted disk or vault, not as a per-file password.
- Compliance requirements that specify audit trails, access revocation or expiry. PDF passwords offer none of these.
- Forms that will be filled and returned. Permission restrictions can block form filling in some viewers; test before sending.
Removing a password you know
If you have the open password and want to work with the file (merge it, split it, convert it), it has to be decrypted first, because tools cannot read encrypted pages. Unlock PDF does this when you supply the password. Our guide on removing a password from a PDF covers the legitimate cases and the limits.
Doing it offline
For files you would rather not upload, every mainstream PDF application can encrypt: Adobe Acrobat (Protect → Encrypt with Password), macOS Preview (File → Export, tick "Encrypt"), LibreOffice (Export as PDF → Security tab) and the command line (qpdf --encrypt --user-password=... --owner-password=... --bits=256 -- in.pdf out.pdf). The result is the same standard encryption; the password you choose matters more than the tool.
A reasonable default
For a confidential document sent to one or two people: AES-256, a strong open password sent by a separate channel, no reliance on permission flags, and a plain reminder in the email that the file is confidential. That is about as much as a PDF password can do, and for most everyday documents it is enough.