How to remove a password from a PDF you own

A password-protected bank statement you download every month, an insurance form you need to reopen repeatedly, a scanned document a family member encrypted before sending — all reasonable cases where you already know the password perfectly well, and you’re just tired of typing it in every single time. Removing that password requirement from a document you have full legitimate access to is a normal, legal thing to do, and it’s a quick operation once you know where to do it.

Before going further, one thing worth being direct about: this isn’t a tool for getting into a PDF you don’t have the password for. It requires the correct password to work. If that’s what you’re looking for, this article — and honestly, any legitimate tool — isn’t going to help, because that’s a fundamentally different (and generally not legitimate) problem than the one this addresses.

How to remove a password from a PDF

On the unlock PDF tool:

1. Drop your password-protected PDF into the upload box, or click it to browse your device.
2. Enter the file’s current password.
3. Click Unlock PDF and download the unprotected file.

The decryption runs inside a WebAssembly engine in your browser — the file and the password you enter both stay on your device throughout, with no upload involved.

This is not a password cracker

To be unambiguous about scope: this tool removes an existing password from a PDF when you supply the correct one. It does not guess, brute-force, or otherwise attempt to bypass a password you don’t know. That’s a meaningful and deliberate limitation, not a missing feature — a tool that could strip password protection without knowing the password would be a security problem for every PDF that’s ever been protected, including your own documents on the days you’re the one relying on that protection to hold.

If you’ve genuinely lost access to a password on a file, there generally isn’t a legitimate shortcut back in — the whole point of a password is that it’s the difference between “protected” and “not protected.” Depending on how the file was protected and by whom, contacting whoever originally sent or created it may be the only real path back to it.

Why people unlock their own PDFs

The most common motivation isn’t secrecy at all — it’s friction removal. A recurring bank statement, an insurance document, a scanned tax form: any file you open regularly enough that re-entering a password each time becomes genuinely annoying. If it’s your document and you know the password, there’s nothing legally or ethically questionable about removing the requirement to retype it — you’re adjusting a convenience setting on a file you already have complete, legitimate access to, not bypassing a protection meant to keep you out.

That said, it’s worth thinking briefly about where the unprotected copy will live afterward. If the original was protected because the document contains sensitive information and might end up somewhere less controlled (a shared drive, an email thread, a device other people use), removing the password removes that layer of protection along with the friction. For a file that stays on your own personal device, that trade-off is usually a reasonable one. For a file you’re about to forward or store somewhere shared, it’s worth reconsidering whether the password was doing useful work.

It’s also worth keeping the original, still-protected file around somewhere if the document ever needs to be shared with someone else who should go through the same password gate you did. Unlocking creates a new, separate file — it doesn’t retroactively change how the source document was protected, so you can keep both versions for their respective purposes: the unlocked copy for your own repeated use, and the original if you ever need to send it onward with its protection intact.

Why this runs locally instead of on a server

Unlocking a PDF necessarily involves handling both the encrypted document and its password together — which makes it one of the worst possible operations to hand to an unfamiliar server. Sending both pieces to a third party to have them decrypt the file means that server briefly holds everything needed to access the document’s contents, precisely the information a password is meant to gate. Running the decryption locally, using a real WebAssembly-based PDF engine in your browser, means neither the file nor the password ever needs to leave your device to get the job done — the same guarantee that applies when you add a password in the first place, covered in our companion post on how to password-protect a PDF.

The short version

If you know the password and just want the prompt gone: drop the file into the unlock PDF tool, type the password you already know, download the result. No upload, no account, no waiting — and no pretending this can get you into a file you don’t already have legitimate access to.