◈ private file sharing
Drop a file.
Share the link. It’s gone when it expires. Files are encrypted in your browser before upload, so NullDrop stores nothing it could read — and nothing it could hand over.
What happens to your file
- 01
Encrypted here
Your browser generates a key and encrypts every file before a byte leaves the tab. The key goes in the link, never to us.
- 02
Stored as noise
We hold ciphertext and a size. Not the file, not its name, not its type — those are encrypted too.
- 03
Deleted on time
Every drop expires. A worker removes the metadata and the stored bytes, and retries until both are actually gone.
The rules
- Max file size94 MB
- Max per drop94 MB
- Files per drop20
- Longest expiry7 days
- AccountsNone, ever
- Permanent storageNot offered
Frequently asked questions
- Do I need an account to share a file?
- No. Drop a file, get a link, share it. NullDrop has no accounts, no sign-up and no email step.
- Can NullDrop read my files?
- No. Files are encrypted in your browser with AES-GCM-256 before they are uploaded, and the key lives only in the share link's fragment — the part of a URL browsers never send to a server. Filenames are encrypted too.
- How long do files last?
- Between 10 minutes and 7 days, whichever you choose. There is no permanent option: every drop expires, and a background worker deletes both the metadata and the stored bytes.
- What does burn after download do?
- The drop is destroyed once its first download completes. Even if the downloader's browser dies mid-transfer, the drop is destroyed after a short grace period — the promise does not depend on the client checking back in.
- What happens if I lose the link?
- The file is unrecoverable. The decryption key exists only in the link, and NullDrop keeps no copy — that is what makes the encryption meaningful.
- Is there a size limit?
- Yes. On this deployment: 94 MB per file, 94 MB per drop, across at most 20 files. The limit is configured per deployment, so it can differ elsewhere NullDrop is run.
