The PDF that refuses to merge, print or be edited
You try to combine a bank statement with three other documents and the tool stops. You try to print a form and the print button is greyed out. You open the file happily enough — no password was ever asked for — so it does not feel protected. It is. A PDF can carry two entirely different passwords, and the one causing your problem is usually the one you were never told about. This guide explains the difference, what each restriction really enforces, and what you can and cannot legitimately do about it.
Two passwords that do very different jobs
| User password (open password) | Owner password (permissions password) | |
|---|---|---|
| Asked for when | You open the file | Never — the file opens normally |
| What it does | Encrypts the content; without it nothing is readable | Sets permission flags: no printing, no copying, no editing |
| How it fails | You simply cannot see the document | Software politely refuses actions |
| Strength | Real encryption — AES-128 or AES-256 in modern files | A flag in the file that software chooses to respect |
| Typical source | Bank statements, payslips, medical results | Contracts, reports, published documents, exam papers |
The crucial point is that an owner password is not really security. The document is not encrypted against you — the restriction is a request in the file's dictionary, and every PDF reader decides on its own whether to honour it. Adobe honours it. Most tools honour it. That is a convention, not a lock.
A user password is the opposite: genuine encryption. Without it, the bytes of every page are unreadable and no tool can do anything with them at all.
Why encryption blocks merging specifically
Merging means reading the page objects out of each source file and writing them into a new document. When the pages are encrypted, there is nothing to read until the file is decrypted with its password. This is why a merge tool reports a failure rather than producing a partial result — it never got as far as seeing a page.
The same applies to splitting, compressing, rotating, extracting text and every other operation. The practical order of work is always: decrypt first with the password you have, then perform the operation, then re-protect the result if it needs protecting. Unlock PDF does the first step — it takes a password you know and writes out an unencrypted copy — and Protect PDF does the last.
Where the password usually is
Documents that arrive encrypted almost always use a password the sender considers obvious, and it is typically stated in the covering email. The common conventions:
- Bank and card statements: date of birth as
DDMMYYYY, the last four digits of the account, or a national ID number. - Payslips: employee number, or a fixed prefix plus date of birth.
- Insurance and medical results: policy or patient reference.
- Utility bills: customer number from a previous paper bill.
If none of these work, the sender is the only route. There is no legitimate way to recover an encrypted PDF whose password nobody has, and that is by design — a document you could open without the password would not be protected at all.
What to do about each situation
- You know the password and want to stop typing it. Unlock once, keep the plain copy somewhere appropriate, and remember that you have just removed the protection that made it safe to store — an unencrypted payslip in a shared folder is a different risk from an encrypted one.
- You own the document and set restrictions you no longer want. Remove them and re-protect with whatever you actually need.
- Someone else restricted the document. The restriction expresses their intent about how the document should be used. Ask them for a copy without it. Whether bypassing it is permissible depends on the document and where you are, and it is not a judgement a tool can make for you.
- You need to protect something yourself. Use a user password so the file is genuinely encrypted, pick a password with real entropy, and send it through a different channel from the document. An owner password alone protects nothing.
Choosing a password that is worth setting
PDF encryption is only as strong as what it derives the key from. Modern files use AES-256, which is not the weak point — the weak point is a six-character password that a commodity graphics card tries a few billion times a second. A date of birth is guessed instantly. Use a passphrase of several unrelated words, or a generated string, and send it by message rather than in the same email as the attachment. And if the recipient needs it long-term, accept that they will store the password next to the file; for genuinely sensitive material a PDF password is a weaker choice than a proper secure-sharing service.