Restrictions (the file opens but blocks printing or copying) come off without any password, because every reader can already decrypt the file and the restrictions are enforced only by the reader.
Encryption (the file will not open without a password) requires the password. Supply it once in Unlock PDF and it writes an unlocked copy. Without it, nothing can be done.
Removing protection from a document you own is a routine, legitimate task. A bank statement you cannot print. A payslip you need to forward to a mortgage adviser. A report you have to combine with others and cannot, because the encryption blocks every tool from reading it.
Two locks, two answers
The PDF specification defines both, and they work so differently that treating them as one thing is the source of most confusion on this subject.
- Opens, printing greyed outOwner password, none needed
- Opens, cannot select textOwner password, none needed
- Opens, editing blockedOwner password, none needed
- Prompts before displayingUser password, required
- Prompts on a thumbnailUser password, required
- Other tools refuse to open itUser password, required
The asymmetry looks strange until you see what each one does. An owner password writes a set of flags into the file: printing not permitted, copying not permitted, editing not permitted. The file is encrypted, but with an empty open password, so any reader decrypts it without asking. Readers honour the flags because the specification asks them to, and a tool that declines to honour them is not defeating any cryptography.
A user password is different in kind. It feeds a key derivation function whose output encrypts every content stream in the document. Without the password there is no key, and without the key the page data is noise.
Removing restrictions
No password is involved because none is needed. In Unlock PDF, leave the password field empty and run it. The tool opens the document with the empty open password, and saves it again without encryption or permission flags. Everything else is carried across unchanged.
The file opens with an empty password. The restrictions were advisory flags on top.
The content is decrypted and saved as it was. Text, images and layout are identical.
The permission bits, and the owner password entry that set them.
Removing a user password
Here the password does real work. You supply it, the tool derives the key, decrypts each content stream, and writes a new document with no encryption applied. From then on the file opens normally everywhere.
Where this runs matters more than usual. Handing an encrypted document and its password to a web service means handing over both halves of the protection at once, to a machine you know nothing about. A browser-based tool reads the file into local memory, does the decryption in JavaScript or WebAssembly, and hands back a download. Neither the file nor the password crosses the network.
What the unlocked file looks like
Identical. Unlocking is not a conversion and not a re-render, so there is no quality question to ask.
Text remains selectable vector text. Images keep their exact resolution and encoding. Annotations, form fields and bookmarks carry over. The only differences are that the encryption dictionary is gone and the permission flags are cleared, both of which live in the file structure rather than on the page.
The protection layer
- The encryption dictionary and its key derivation
- Permission flags for printing, copying and editing
- The password prompt on opening
- Restrictions that blocked other tools from reading it
Everything you can see
- Page content, unchanged once decrypted
- Image resolution and encoding, untouched
- Fonts, annotations, form fields and bookmarks
- Document metadata, unless you strip it separately
Why this comes up
The usual trigger is not wanting to defeat protection, it is wanting to do something ordinary that protection is blocking.
A PDF that needs a password to open cannot be merged, split, compressed or converted until it is unlocked, because every one of those operations needs to read the page objects and encryption exists to prevent exactly that. A bank statement that has to go into a mortgage application bundle has to be unlocked before it can be merged. That is the single most common reason people arrive at this.
What this cannot do
It cannot open a file whose user password you do not have. No tool can, for anything using modern encryption, and any tool claiming otherwise is either removing owner restrictions and renaming the operation, or guessing passwords and hoping yours is weak. If that is where you are, start with what can and cannot be recovered from a forgotten password.
It also cannot tell you whether you are entitled to remove the protection. Technical possibility and permission are separate questions, and only one of them is the tool's business.
Unlock a PDF in your browser
Removes restrictions, or the password if you have it. The file never leaves your device.
Common questions
What changes and what does not.
01Can I remove a password I do not know?
Only if it is an owner password, meaning the file opens and merely restricts what you can do. Such a file decrypts with an empty open password, so the restrictions come off without the owner password. A user password, the kind that blocks the file from opening, cannot be removed without it.
02Does unlocking reduce quality?
No. Unlocking removes the encryption layer and the permission flags, both of which live in the file structure rather than on the page. The content is decrypted and saved as it was, so text stays sharp and images keep their original resolution.
03Why do other tools refuse to open my encrypted PDF?
Because they cannot read it. Merging, splitting, compressing and converting all require reading the page objects, and a file with an open password cannot be read without the key. A file that only restricts printing or copying is different: most of PDFslime's tools open those directly, though many other tools still refuse them.
04Is it safe to unlock a PDF online?
It depends entirely on whether the file is uploaded. A tool that runs in your browser keeps both the document and the password on your machine. A tool that uploads is receiving a sensitive document and its password together, which is a great deal to hand to a service you cannot inspect.
05Can I put the password back afterwards?
Yes. Protecting a PDF is a separate operation you can run at any time, and it is generally better to do it last, after the document is finished, so the protection covers the final file rather than one component of it.
06What happens to form fields and annotations?
They survive. Unlock PDF decrypts the document and saves it without encryption or permission flags, changing nothing else, so form fields, comments, highlights, bookmarks and the document's metadata all carry across.