Unlock PDF

This removes protection from a document you can already open. You supply the password, the encryption layer is stripped, and you get back a plain PDF that opens with no prompt anywhere. It is not a password cracker, and the distinction is not a policy choice — it is the whole point of encryption working correctly.

When a PDF carries an open password, the content is encrypted with AES and that password is the only key. There is no copy stored in the file, no vendor override and no recovery mechanism. A forgotten password means a lost document, and any service claiming otherwise is guessing passwords rather than recovering them, which works against 'summer2019' and never against a passphrase.

The permission password is different. If a file restricts printing or copying but opens without prompting, entering either password removes the restrictions — and where only an owner password exists, the file is decryptable regardless, because the open password is blank. That case is the one most people arrive here with.

Protection is applied to a finished document, which makes it a wall around every subsequent operation. Nearly every PDF tool must read page content to work — merging copies pages, compressing re-encodes images, converting reads text — and none of that is possible while the content is ciphertext. This is why a protected file fails immediately in tools that handle its unprotected twin without complaint.

So the normal workflow is decrypt, work, re-protect. Unlock the file, do whatever you needed to do, then apply a fresh password with Protect PDF at the end. The result is a properly protected document rather than one you have quietly given up on editing.

It is also the fix for the everyday nuisance case: a bank statement or payslip that arrives encrypted with your date of birth, which you must retype every single time you open it. Unlock it once, store the plain copy somewhere you already trust, and stop paying that toll.

PDFs carry two independent kinds of restriction and they behave nothing alike. An open password genuinely prevents reading: without it there is no way to see the content, and the file is opaque to search indexers, mail scanners and preview generators as well as to people.

Permission flags are advisory. They say the document should not be printed, copied, edited or extracted, and mainstream viewers honour them faithfully — but the file is decryptable by anyone, so the enforcement lives entirely in the viewer's good manners. This is why a document can look locked down and yet be trivially readable by software that simply does not check.

Knowing which you are dealing with tells you what to expect. If the file prompts for a password, it is genuinely encrypted. If it opens straight away but greys out printing, it is carrying flags — and removing them is a matter of rewriting the file without them rather than defeating any cryptography.

Knowing the password is not the same as being entitled to remove it. Restrictions on a document usually express someone's intent — a publisher's licence terms, an employer's handling policy, a court's conditions on disclosure — and stripping them can breach a contract or the law even when it is technically effortless and even when the file was sent to you.

The uncontroversial cases are the common ones: your own documents, statements addressed to you, files your organisation owns, or anything where the person who applied the protection has said to go ahead. Purchased ebooks, licensed research and confidential material belonging to someone else are not in that set.

If you are unsure, the question worth asking is not whether you can, but whether the person who locked it would object. That is usually a much clearer answer than the legal one.