Password-Protecting and Unlocking a PDF, and What Each Actually Does

"Lock" and "unlock" get used loosely enough that it's worth being precise about what's actually happening to a PDF file in each case, since the two operations are genuinely opposite and mixing them up wastes a round trip.

What a password-protected PDF actually is

A password-protected PDF isn't a regular PDF with a password prompt bolted on top — the file's content is genuinely encrypted, using an algorithm built into the PDF specification itself (most commonly AES). Without the correct password, the encrypted content simply can't be read by any PDF viewer, including this site's own tools, which is exactly the point. This is different from a "view restriction," which some PDF software applies as a software-level rule that a determined tool can often bypass — real password protection can't be brute-forced around by a different program, only by the password itself, or by cracking the encryption directly, which is computationally impractical for a reasonably long password.

What "unlocking" a PDF actually removes

Unlock PDF does the reverse of that: given the correct password, it decrypts the file and produces a normal, unencrypted copy. It is not a way to bypass a password you don't have — that would require breaking AES encryption, which isn't a thing a browser tool (or most tools, period) can meaningfully do. What Unlock PDF is actually for is the extremely common situation where you're the legitimate owner of a password-protected file — your bank sent you an encrypted statement, or you encrypted your own document months ago — and you're tired of typing the password in every single time you open it. Decrypt it once, keep the unlocked copy somewhere you control.

Where a watermark fits into this

Watermarking is a different kind of protection entirely — not encryption, but a visible or semi-visible marking (a name, a date, "DRAFT," a company name) stamped across every page. It doesn't stop anyone from opening the file; it discourages a document from being passed off as something it isn't, or makes clear which copy of a contract is the draft versus the signed final. Encryption controls who can open a file; a watermark controls how a file is understood once it's already open. They solve different problems and are often used together — a draft contract might be both watermarked and password-protected before it goes out for review.

Where e-signing fits in

E-signing is neither of the above — it's adding a signature (drawn, typed, or uploaded as an image) to specific positions on a document, turning a PDF that needs a physical signature into one that's already been signed. It doesn't encrypt anything and it isn't a legal-validity service — what it produces is a PDF with your signature placed exactly where you put it, which you can then password-protect afterward with a separate pass through the encryption tool if the document needs both.

The one thing all four have in common

Encryption, decryption, watermarking, and signing are all, at their core, byte-level operations on a PDF file's internal structure — no different in principle from what desktop PDF software does. Running them in the browser instead of on a server matters specifically because of what kind of document tends to need a password in the first place: the ones worth protecting are, definitionally, the ones you'd least want passing through a server you don't control on the way to being unlocked.