1
Create
Add a file, text or link. Drop encrypts the content before upload.
Free · Live · No account
Share once. Then it's gone.
Create an encrypted one-time link for a file, text or URL. No account for you or the person receiving it.
No accountEncrypted before uploadOne successful receive
One-time access is not DRM: a recipient can still save or screenshot what they receive.
What do you want to share?
Choose one item and create a temporary encrypted handoff.
FileTextLink
project-note.pdfEncrypted in your browser before upload
Receive rule1 successful receive
How it works
Three steps. Nothing else to learn.
Drop is intentionally narrow: create something, share the link, and the recipient receives it once.
2
Share
Send the generated Drop link through the channel you already use.
3
Receive once
The recipient explicitly opens the Drop. A second receiver is denied after the receive is confirmed.
Why Drop
Built for a small, specific job.
You should not need a new account, inbox or collaboration space just to hand something over once.
◎
No account
No signup for sender or receiver.
⌁
Encrypted first
Content is encrypted in the browser before it is uploaded.
1
One-time by design
Drop is for a single successful receive, not a reusable sharing link.
i
What “one-time” actually means
Ordinary page loads and link previews do not consume the Drop. The receive is completed through the explicit claim flow. After that, another receiver is denied. The recipient can still save or screenshot the content they received.
Product boundary
Know when Drop is the right tool.
Good for
- A document you want to hand over once
- A short note, code or text snippet
- A URL you do not want to leave as a reusable Drop link
- Quick temporary sharing without creating an account
Not designed for
- Ongoing collaboration or shared folders
- Long-term cloud storage or file history
- Preventing the recipient from saving or screenshotting content
- Repeated access by multiple recipients
Privacy & security
Simple above. Strong underneath.
The useful part is simple: your content is encrypted before upload and the server stores the encrypted form. Technical details are here if you want them—not in the way if you do not.
What happens before upload?
Drop encrypts content in the browser using AES-GCM before the encrypted data is uploaded.
Where is the decryption secret?
The secret stays in the URL fragment after the #. URL fragments are not sent as part of the normal HTTP request to the server.
What does the server store?
The storage path receives ciphertext rather than the readable file content. Runtime state manages expiry and the one-time receive lifecycle.
Why do link previews not consume a Drop?
Opening the page alone is not the one-time receive. Drop uses an explicit claim flow before the receive is confirmed.
FAQ
Quick answers.
Do I need an account?
No. Neither sender nor receiver needs to sign up.
Can the same Drop be received twice?
No. After the receive is confirmed, another receiver is denied.
Can a link preview or bot consume it?
Ordinary page loading and link unfurling do not start the one-time claim.
Can the recipient save or screenshot it?
Yes. Drop limits the receive path; it is not DRM and cannot control what a recipient does after receiving the content.
Is Drop free?
Yes.
Need to hand something over once?
Open Drop, add a file, text or link, and create your one-time encrypted link.