You encrypted a payslip before emailing it, and now it’s sitting in your own archive folder, still asking for a password every time you open it to check something. Or someone sent you a protected contract, you typed the password they texted you, confirmed it’s the right document, and now you’d rather not re-type it every single time you reference it over the next year. Or you’re trying to run a batch of scanned statements through a merge or search tool, and every one of them stops the process cold with a password prompt the tool has no way to answer. In all of these cases the password already did its job — it kept the file safe in transit or in a specific context — and now it’s just friction on a document you’re allowed to open freely.

That’s what Unlock PDF is for: removing an existing password from a PDF, given the correct password.

What this tool requires — and what it won’t do

Worth being direct about this upfront, because the name invites the wrong assumption: Unlock PDF is not a password-cracking or bypass tool. It doesn’t guess, brute-force, or find a way around a password you don’t have. You have to type the file’s actual current password before anything happens — the tool decrypts the file with it, the same way a PDF reader unlocks the file for viewing when you type the password there.

If you don’t know the password, this tool can’t help you, and there isn’t a legitimate way around that. A real password on a PDF is deliberately designed to resist exactly that kind of guesswork — that’s what makes it a real lock rather than a suggestion. If you’re the one who set the password and forgot it, or you never had it in the first place, the honest answer is that the file stays locked until you get the password from whoever set it. That’s not a gap in the tool; it’s the whole point of encryption actually working, which the companion post on protecting a PDF covers from the other side — the same unforgiving property that makes a password worth setting is what makes it un-removable without it.

The other kind of PDF password, and why this tool won’t touch it

Worth naming, because it’s the thing most likely to confuse someone landing on this exact tool: a PDF can be locked in two genuinely different ways, and Unlock PDF only deals with one of them.

The first is an open password (sometimes called a user password) — the file refuses to open at all until you type it in, the experience you’d normally picture when you hear “password-protected PDF.” That’s the whole subject of this page, and it’s what Unlock PDF removes.

The second is a permissions password (also called an owner password) — the file opens with no prompt whatsoever, but printing, copying text, or editing is blocked or limited once you’re in it. A PDF can carry that kind of restriction on its own, with no open password attached to it at all.

That distinction matters here because of how this tool decides whether to even ask you for a password: before showing the password field, it tries opening the file with no password at all, using pdfjs-dist. A permissions-only PDF opens fine at that check — nothing stops it — so the tool reports it as not password-protected and offers to hand it back to you as-is, restrictions and all, rather than asking for a password it has no open-password lock to check it against. If you’ve got a PDF that opens freely but refuses to let you print or copy from it, that’s a permissions password doing its job, and it’s a different problem than the one this page — or this tool, as it stands today — solves.

What actually happens when you unlock a file

Under the hood, Unlock PDF runs on qpdf — the same open-source PDF engine, compiled to WebAssembly, that Password Protect a PDF uses to add AES-256 encryption in the first place. Unlocking is the same mechanism run in reverse: the tool hands qpdf your file and the password you typed, and asks it to decrypt with --decrypt. If the password is correct, qpdf strips the encryption and writes out a plain PDF with the same content, now openable by anything with no password at all. That output then gets opened once more with pdfjs-dist — a separate, independent PDF parser — specifically checking that it now opens with no password required, so the tool only calls it done once a genuinely different piece of code confirms the file is actually unlocked, not just that qpdf reported success.

A couple of things it checks along the way, so the tool doesn’t do anything confusing:

  • Wrong password. qpdf fails to decrypt, and you get a plain error telling you the password was wrong (or that the file isn’t password-protected at all) — nothing about the file changes, and you can just try again.
  • A file that was never protected. Before it even asks you for a password, the tool checks whether the PDF is encrypted in the first place. If it isn’t, it tells you so directly and offers to hand you the file as-is, rather than asking for a password that wouldn’t mean anything on an unlocked file.

Who this is for

  • The original sender, later on. You protected a document before sending it, the recipient has since confirmed receipt and verified it’s them, and you want a plain copy for your own records without re-typing a password every time.
  • A recipient simplifying their own copy. You were sent a protected PDF, you know the password, and now that it’s safely stored on your device you’d rather not re-enter a password on every future open.
  • Batch processing. A folder of protected statements, scanned forms, or reports needs to go through a merge, split, search, or archiving step, and an automated pipeline has no way to type a password at each one. Unlocking them first — once you have the passwords — lets the rest of the workflow run without stopping.
  • Internal documents past their need for protection. A file was encrypted for a specific transfer or a specific audience, and now that it’s filed away internally where the protection no longer serves a purpose, removing it is just cleanup.

What it’s explicitly not for: getting into a file whose password you don’t have. If that’s the situation you’re in, there’s no version of this tool — or any other legitimate one — that solves it, because that’s what the encryption is supposed to prevent.

Nothing leaves your device

Decryption happens entirely in your browser, using qpdf compiled to WebAssembly and pdfjs-dist running as JavaScript — your file and the password you type are never uploaded anywhere. This is worth emphasizing more than usual here: typing a password into a random web tool is exactly the kind of thing worth being careful about, and the honest answer is that you don’t have to trust this one with it. The password you enter is used locally, in your own browser tab, to run a local decryption, and it’s never sent to a server, logged, or stored anywhere — the whole operation could work with your network cable unplugged.

If you still need the file protected in some form afterward — for a different recipient, or a different purpose — Password Protect a PDF is the tool for putting a real, AES-256 password back on it, entirely client-side as well.