Password-Protecting a PDF Online: Are You Handing the File to a Stranger First?

Published 9 July 2026 · 5 min read

There's a specific kind of irony in this one. You're locking a PDF with a password precisely because it contains something you don't want just anyone to read — a contract, someone's personal information, financial figures you're about to send by email. And the most common way people do that is by uploading the unprotected, fully readable file to a website first, so it can add the lock for you.

Whoever's on the other end of that upload gets to see the document in the exact state you were trying to protect it from being seen in, before the password even gets added.

Why this one deserves extra thought

Nobody adds a password to a grocery list. The documents people protect this way are, almost by definition, the ones that matter: signed contracts, salary details, medical paperwork, anything meant for one specific recipient and nobody else. Choosing to password-protect a file is a deliberate signal that you consider its contents sensitive — which makes it an odd moment to hand that same file over, unprotected, to a server you don't control.

And it's worth being specific about what "real" password protection even means here. A password that just blocks the file from opening in certain viewers isn't doing much; genuine protection means the document's actual content is encrypted, so that without the correct password, the data itself is unreadable, not just hidden behind a prompt.

How FormatDog handles this without the upload step

FormatDog's Password Protect tool applies real AES-256 encryption — the same standard used for encrypting sensitive data in banking and government systems — directly inside your browser, using pdf-lib running as WebAssembly on your own device. Your file is never uploaded in either its protected or unprotected form. The encryption happens locally, and the only copy of the password that ever exists is the one you typed in, which we never see, store, or transmit anywhere.

That last point matters on its own: since we never receive your password, we also can't recover it for you if you forget it. That's not a missing feature so much as a direct consequence of the password never leaving your device in the first place.

Confirming this yourself

Open developer tools in your browser (F12), click the Network tab, then select a file and add a password. If a tool is uploading your file, you'll see outgoing network activity carrying that data while it processes. If protection happens locally, that tab stays quiet, because nothing is being sent out to check.

To be fair to everyone else

Most established PDF sites aren't doing anything malicious with files passing through their servers, and most delete them on the schedule their policy describes. But for a document you're specifically choosing to lock down, it's worth picking the option where that exposure window doesn't exist at all, especially when it costs nothing to do so.