Most share links protect your file with a login on someone else's server. The server holds the plain file and decides who gets it. A locked Hushdrop works the other way around: the page is encrypted on your laptop, the server only ever receives ciphertext, and the decryption happens in the reader's browser. Here's each step, with the real parameters.
1. You publish
hush report.html # auto-generates a password hush report.html -p 'correct horse battery'
The CLI first adds your branding to the page (title, social preview tags, a small corner badge). Then it hands the page to StatiCrypt, an open-source encryption tool, before anything touches the network.
2. The password becomes a key
Your password is never used directly. It goes through PBKDF2 with SHA-256 for 600,000 iterations, together with a salt, to produce a 256-bit key. The iteration count is there to make guessing slow: every password an attacker tries costs them the same 600,000 rounds.
3. The page is encrypted
The whole HTML document is encrypted with AES-256 in CBC mode, and an HMAC over the ciphertext lets the browser detect tampering. The result is wrapped in a small unlock page: your logo, a password field and the decryption script. That unlock page plus the ciphertext is the only thing uploaded.
4. The server stores ciphertext
Whether you self-host on your own Vercel Blob or publish to hushdrop.dev, the stored file is the encrypted blob. The password is not sent anywhere, and it isn't in the URL. Every drop is served with X-Robots-Tag: noindex and a strict Content-Security-Policy, so a leaked link doesn't end up in search results.
5. The reader decrypts in their browser
Your recipient opens the link, types the password, and their browser derives the same key with the Web Crypto API, checks the HMAC and decrypts the page in memory. The decrypted page never travels over the network.
What this does and doesn't protect
It protects the content from the host, from anyone who intercepts or scrapes the link, and from search engines. It does not protect against a weak password: the ciphertext can be downloaded, so someone with time can try guesses offline. The auto-generated passwords are long for that reason. Send the password through a different channel than the link when the content matters.
Two modes work differently. Raw files published without a lock are protected by an unguessable URL only. A whole static site locked with hush site/ -p secret (self-host) uses a password check at the edge (PBKDF2, 100,000 iterations) instead of encrypting every file.
Check it yourself
The CLI, the unlock template and the server are all in the public repo. Publish a page, download the stored file with curl, and you'll see ciphertext and the unlock page, nothing else.