Where locked PDFs come from
Most password-protected PDFs people deal with were not locked by them. Banks send monthly statements protected with part of an account number or a date of birth. Payroll systems lock payslips, insurers lock policies, utilities lock bills, and some e-ticket and visa services lock confirmations. The password is usually explained in the email that delivered the file.
That protection is reasonable while the file travels through email, but it gets in the way once the document is safely on your own device:
- Typing the password every time you open a statement from a folder of twelve.
- Tax or accounting software that refuses to import encrypted files.
- PDF tools that cannot merge, compress, sign or OCR a protected document.
- Printing at a copy shop where you would rather not type your password on a shared computer.
- Archiving: in five years you may no longer remember which digits a bank used in 2026.
Two locks, two situations
A PDF can carry an open password, a permissions password, or both, and you can tell which from how the file behaves.
- It asks for a password before showing anything. This is an open password. Enter it in the field above, then add the file.
- It opens freely, but printing, copying text or editing is greyed out, and the reader may show "Secured" or "Restricted" in the title bar. This is a permissions password only. Leave the field empty and add the file.
When you know the open password, the restrictions are removed together with it, so you do not need the second password as well. The output is a plain, unencrypted copy with "-unlocked" added to its name. Pages, text, images, bookmarks and form fields are unchanged.
How it works
The decryption uses qpdf, an established open-source PDF toolkit, running in your browser as WebAssembly. Nothing is uploaded, and the password is used only for the files you add. Files up to 100 MB are handled in the browser; for larger ones the page offers server processing, in which case the file and the password are sent to our server for that job and deleted about an hour after it was created.
Each file is processed the moment you add it, using whatever is in the password field at that moment. This shapes how batches work:
- Several files with the same password, such as a year of statements from one bank: type the password once, then drop all of them together.
- Files with different passwords: type the first password, add its file, then change the field before adding the next.
- A file that failed: changing the password does not retry it. Correct the password, remove the failed entry and add the file again.
When the password is rejected
If you are sure of the password but it does not work, the cause is usually small:
- Copied whitespace. Copying a password from an email often grabs a trailing space or line break. Type it by hand instead.
- Case and layout. Passwords are case-sensitive, and a keyboard set to another language changes what some keys produce.
- The wrong rule. Bank passwords are often built from several pieces, such as the first letters of a name plus a birth date in a particular format. Check whether the date should be DDMMYYYY or DDMMYY, and whether letters should be capitals.
- A different document's password. Statements from different accounts or years may use different passwords.
The tool cannot recover or guess an unknown password. It removes protection you are able to open, which is also the only situation where doing so is legitimate: only unlock documents you own or are entitled to use.
After unlocking
The unlocked copy can be read by anyone who gets hold of it, so treat it like any other sensitive paper. Keep it in an encrypted folder or a password manager's file storage rather than in your downloads folder.
Unlocking is often a step towards something else. A year of monthly statements becomes one tidy file with Merge PDF, and heavy scanned documents become email-friendly with Compress PDF. If the combined file needs to travel again, put a password of your own back on it with Protect PDF.