Sharing & sending
Anonymous Send
Drop someone an encrypted file without signing up for anything. Send encrypts in your browser, stores the result under a disguised name for a short window, and can wipe it the moment it's read.
What Send is for
Anonymous Send is the fastest way to hand off a single file when you don’t have, or don’t want to use, an account. It’s built for one-off transfers: a document to a journalist, a build to a tester, a photo to a friend. You get a link to share; the recipient needs no account either.
How it works
The file is encrypted on your device before it leaves your browser. zcrypt then splits the ciphertext into chunks and uploads them under a disguised name so the stored object reveals nothing about the original file. You receive a token-based link to pass on; the recipient’s browser downloads the chunks, verifies them, and decrypts locally.
- •The server stores only ciphertext: it cannot read the file.
- •The stored chunks carry disguised filenames, not your original’s.
- •No account, sign-in, or email is required to send or receive.
Limits and expiry
- •Size: up to 50 MB per file. Larger files belong in your vault, where you can use a share link instead.
- •Per day: anonymous senders can send up to 500 MB a day. Signing in raises the daily allowance.
- •Expiry: choose a lifetime between 1 and 24 hours. When it lapses, the link reports that it has expired and the data is no longer retrievable.
Need something bigger or longer-lived?
Sign in and upload the file to your vault, then create a share link: those support larger files and longer expiries.Burn after read
Turn on burn after read to make the send a one-time link. After the first successful access it is treated as already consumed, so a second visitor, or anyone who later finds the link: sees only that it has been used. Once the file has been served, the stored data is deleted, not just hidden.
Privacy and what we log
What's private, and what isn't
The file’s contents stay private: encryption happens in your browser and the server only ever holds ciphertext under a disguised name. For abuse prevention, the sender’s IP address is recorded with the transfer, coarsened to its /24 (IPv4) or /48 (IPv6) network. The integrity hash of the file is sealed too, so the server does not hold a plain hash of your content. If that matters to your threat model, send from a network you’re comfortable being associated with.