b2KIT

Secure File Drop (Encrypted)

Encrypt a file with a password and generate a download link containing the encrypted payload as a data URL.

Tested tool guide Tested browser tools Checked August 16, 2026

What Secure File Drop (Encrypted) does and how it behaves

The file never leaves your browser. Secure File Drop reads a file you choose, encrypts it with a password you type, and folds the encrypted result into a link as a data URL, so the link itself is the payload. Send the link to anyone; they open it here, enter the password, and download the original file. Nothing is uploaded or stored, and the password is never saved, which means a lost password destroys the file permanently - there is no recovery. The common surprise is the link's size: it contains the whole encrypted file, so this suits small files, not archives or videos.

How the result is produced

1

Encrypting into the link

You pick a file and a password. The tool reads the file's bytes in the browser and encrypts them with a key derived from the password, so the result is unreadable without it. The encrypted bytes are then encoded and embedded in a data URL, whose content is the payload itself. You copy out one long string and send it by any channel.

2

Decrypting on the other end

The recipient pastes the link into the tool or opens it directly. The tool reads the embedded payload, and the recipient types the password; the key is re-derived from that exact password and the file is decrypted in the browser. A wrong password fails cleanly or yields garbage bytes, and since nothing was stored anywhere, there is no server-side reset and no way to recover a mistyped password.

Good uses

  • Sending a small sensitive file - a config, a credentials export, a signed document - over chat or email when you cannot vouch for the channel's confidentiality.
  • Delivering a file to someone you already share a password with, arranged out-of-band by phone or in person, so the link alone is worthless to anyone who intercepts it.
  • One-off transfers where you want no trace: nothing is uploaded, logged, or retained, and the payload exists only in the link you control, which you can simply never send if plans change.

Limits and checks

  • Data URLs are length-limited. Browsers stop handling them around 2 MB and address bars far sooner, and some clients truncate long links, so a large file can appear to encrypt fine yet arrive broken. Keep files to a few hundred kilobytes and test the full round trip.
  • The ciphertext is in the open once sent, so everything rests on the password: a short or reused one can be attacked offline. Sending the link and the password in the same message hands an eavesdropper both, leaving only the transport's own encryption to protect you.
  • A successful encrypt is not proof of delivery. Chat apps and email clients differ in how they handle very long data URLs - some strip or refuse them - and a recipient's browser may reject an oversized link, so verify the file actually decrypts at the other end.

Common questions

How large a file can I encrypt?

Data URLs are the limiting factor. Browsers stop handling them around 2 MB, address bars far sooner, and pasting a huge link into email or chat often fails, so keep files under a few hundred kilobytes and test before relying on it. Folders are not supported; encrypt one file at a time.

What happens if I forget the password?

The file is gone. The password is never stored or transmitted, and the ciphertext cannot be read without it, so there is no recovery mechanism anywhere - that is the point. If you still have the original file, re-encrypt it with a new password and send the new link.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools