"Protected" is one of the most loosely used words in the PDF world. A file can be called protected because it refuses to print, because it asks for a password before it opens, or because its contents are actually encrypted. Those are three different things, and only one of them keeps a stranger from reading the document. If you send client files, it helps to know which one you're getting before you rely on it.
Two passwords, two very different jobs
The PDF format defines two kinds of passwords. They are often presented side by side in the same dialog box, which is why they get confused.
- The open password (the specification calls it the user password). Without it, the document doesn't open at all. The viewer asks for it before showing a single page.
- The permissions password (the owner password). It doesn't stop anyone from opening the file. It sets rules about what can be done once the file is open: printing, copying text, changing the document, adding comments.
A PDF can have either one, or both. The difference matters far more than the dialog box suggests.
Why permissions alone are weak
When a PDF has a permissions password but no open password, its content is technically encrypted, but the key needed to decrypt it can be derived without knowing any secret. That's how every viewer manages to display the file without asking you anything. The "no printing" or "no copying" rule is then a flag inside the file, and it's up to the viewing software to honor it.
Most mainstream viewers do honor it. Some software doesn't, and tools that remove these restrictions are easy to find. So a permissions-only PDF is best thought of as a polite request: "please don't print this." It discourages casual misuse by honest recipients. It doesn't protect confidential content from someone who wants it.
The same logic applies after a file is opened with its open password. From that point on, the permissions are again rules the viewer is asked to follow. They're useful, for example to signal that a report is final and shouldn't be edited, but they're not a lock.
What real protection looks like
A PDF is genuinely protected when two conditions are met:
- It has an open password. The encryption key is derived from that password, so without it the content can't be decrypted. There's no shortcut that a viewer, or anyone else, can take.
- It uses strong encryption. Older PDF encryption relied on RC4 with short keys, which is now considered weak. PDF 2.0, published as ISO 32000-2, specifies AES with 256-bit keys (the method known in the file as AESV3) and treats the older RC4-based methods as deprecated.
Put simply: password protection is what you see, encryption is what does the work. A password with weak or no real encryption behind it is a door with a painted-on lock. Strong encryption with no open password is a safe with the combination written on the front. You need both.
What encryption doesn't do
Even a properly encrypted PDF has limits worth stating plainly:
- A weak password can be guessed. AES-256 is only as strong as the password it's derived from. "Smith2026" can be found by software that tries likely combinations; a long random password or passphrase is a different story. The guide to sending a PDF password explains how to get it to the recipient separately.
- Anyone with the password can open the file. Encryption doesn't know who is typing. If the password travels in the same email as the attachment, anyone who gets the email gets both.
- A recipient can re-share. Once someone has opened the document, they can forward it with the password, take screenshots, or print it if printing is allowed. Encryption protects the file in transit and at rest, not what an authorized reader does next.
A quick way to tell what you're dealing with
When you receive a "protected" PDF, or before you send one, open it in a regular viewer:
- If it opens without asking for anything, it has at most a permissions password. Its content should be considered readable by anyone who has the file.
- If it asks for a password before showing any page, it has an open password. Check the document properties or security panel of your viewer to see which encryption method is used; look for AES-256 rather than RC4 or a 40-bit or 128-bit key.
As an example, imagine Harbor Lane Bookkeeping, a fictional firm, sending year-end statements to its clients with "no printing, no copying" set, but no open password. The firm feels the files are locked down. In reality, anyone who intercepts or is mistakenly forwarded one of those emails can read every figure. Adding an open password, sent by text message, changes that completely.
How PDF Protect Plus handles it
PDF Protect Plus is built around the combination that actually protects: an open password plus AES-256 encryption.
- The encryption is done by qpdf, an established open-source PDF engine (its documentation is public), using AES-256 in the AESV3 form defined for PDF.
- The open password is the one you choose, up to 127 characters. If you'd rather not make one up, the built-in generator creates one from 16 to 64 characters, using your operating system's random source and mixing uppercase, lowercase, digits and symbols. A strength meter shows how it holds up.
- Permissions can be set on top: printing (allowed or not), copying and extracting content, modifying, and annotating. They're presented for what they are, useful rules for the recipient's viewer rather than a second lock.
- The permissions password is generated randomly by the app, 48 characters long, and never shown. You don't have to manage it, and there's no risk of reusing the open password for it by mistake, which would quietly cancel the permissions.
- Your original stays untouched. The protected version is saved as a new file.
All of this happens on your own device, on Windows, macOS or Android. The document isn't uploaded; the app talks to our server only for account sign-in, licence checks and the subscription. If you need to protect many files with a different password per client, batch protection handles up to 200 PDFs at once from a spreadsheet.
And when a client sends a protected file back, the app can unlock it, as long as you know the password. It doesn't try to crack passwords, which is precisely the point of using a strong one.
The short version
- A permissions password limits what a viewer lets you do. It doesn't keep the content private.
- An open password with AES-256 encryption keeps the content unreadable without the password.
- The password's strength and the way you send it matter as much as the encryption.
- Permissions are still worth setting as a signal, on top of an open password.
For the step-by-step version, see how to password protect a PDF without uploading it or the protection tutorial. You can download PDF Protect Plus and test it on a sample document during the 7-day trial.