Decrypt a PDF you already have the password for

An archive that rejects every locked file

Tomas handles office admin for a small distributor. In March his company moves to a new document archive, and the migration stalls on day one: the archive refuses every password-protected invoice with the same blunt error. Forty files, all locked years ago by a bookkeeper who retired, all with their passwords sitting in the company password manager. The migration deadline is Friday, and the archive will not bend.

His job is decryption in its ordinary sense: use each known password once, save a plain copy, move on. Nothing is being broken into, because every file opens for him already. If that matches your situation, a password you hold and a file that opens for you, the rest of this guide is your path. If the password is gone, start instead with the guide for a lost PDF password.

Three things people mean by decrypt, and which ones work

The word carries three different wishes. Only two of them end with a file, so find your row before you spend time on the wrong one.

Tomas lives in the first row forty times over. The second row is the quiet surprise, a file that opens yet still counts as protected, and it has its own section below. The third row is where hopeful searching ends: PDF protection is real encryption, not a setting to switch off from the outside, so no browser tool opens a file whose password nobody knows.

Turn the locked file into a plain copy

The unlock tool does one file per pass, so a batch like Tomas's goes through file by file. Each pass looks like this:

1. Choose the protected file. Press the button or drop the PDF on the page. The file stays in this browser tab and is never uploaded anywhere.
2. Type the password that opens it. Unlock is already selected when the page opens. If the file opens on its own with no prompt, skip the typing: it carries only an owner layer, and the tool sees that.
3. Run the unlock. The password is used inside this tab only. It never reaches usage data, never lands in the page address, and never travels in diagnostics.
4. Read the verification, then download. The finished file is opened again with no password given. Its page count, page sizes and selectable text are compared with the source, and a copy that lost pages on the way through is not offered for download.

Test the copy the serious way: close everything, open the downloaded file fresh, and confirm no prompt appears. Then move to the next file. Forty files at a minute each is a lunch break, not a project.

Why the next tool kept refusing the file

Decryption is rarely the errand itself. It is the locked door in front of the errand: merging, compressing, splitting and rotating all need to read the pages, and an encrypted file hands them scrambled bytes instead. Most PDF tools stop there rather than produce something broken, which is why the error you face often names a different tool than the one you actually need.

Portals behave the same way. Tax offices, banks and archives commonly reject protected uploads at the door, because their intake cannot read inside an encrypted file to check it. Tomas learned this from forty identical errors. Save the plain copy once and every later step, the merge, the upload, the archive import, stops complaining. If you are unsure which lock your file carries, the unlocking guide walks through telling them apart.

The file that opens yet still counts as protected

Some PDFs open with no prompt and still refuse to print or to let text be copied. Those carry an owner password: a layer of limits on a file anyone can already read. The pages were never scrambled against you, only fenced, so the unlock tool can drop that layer with no password step at all.

Treat the two locks differently from here on. An open password is real protection, scrambled content that needs its password. Permission flags are advice that well-behaved readers follow and others ignore. Knowing which one you cleared tells you how much to trust the plain copy: against reading by strangers, only a file that once needed an open password was ever truly locked.

Mistakes that leave the lock in place

Typing a near miss. Passwords are exact, and capitals, spaces and diacritics all count. When the tool says the password did not open the file, retype it slowly before assuming anything worse.

Using the password of a different file. Old archives hold lookalike passwords per client or per year. Match the entry to the exact filename before blaming the tool.

Sending the password with the file. A plain copy emailed next to its old password in the same message is barely better than no lock at all. Share passwords through a different channel than the file.

Locking the copy again out of habit. If the next step is an archive or a portal that rejects protected files, do not re-protect before uploading. When you do need a fresh lock afterwards, the protect page writes AES-128 encryption and asks for at least six characters, entered twice.

Deleting the locked original first. Keep it until the plain copy is checked and accepted wherever it is going. A rejected upload with the original still around is a retry; without it, it is a problem.

When the sender or IT should handle it instead

Not every locked file is yours to open. When the file came from someone else and no password came with it, the honest move is to ask them for the password or for an unlocked copy. Guessing at a stranger's file wastes the afternoon and crosses a line, and the tool will not guess with you.

Workplace rules matter too. Some companies forbid removing protection from client or medical files outside approved software, and an archive migration is exactly when those rules get enforced. When in doubt, ask IT which route they bless before producing forty plain copies. And when the file is simply huge, remember the practical ceiling is your browser tab's memory: a very large file may need a desktop machine with room to hold it rather than a tired laptop.