You upload a file.
Cloud uploads pass through the service into private object storage. Check the uploader for the current size limit.
blinkdrop sends large files with a single expiring link. No account, no recipients list, no permanent archive — the file simply has a deadline.
Cloud uploads pass through the service into private object storage. Check the uploader for the current size limit.
Every upload produces a single download link. Anyone who has it can download the file until it expires.
You choose an expiry between 1 and 24 hours. Once it passes, the link stops working for new downloads.
A scheduled cron job removes stored files after expiry. Physical deletion can lag until cleanup succeeds; delays or failures can extend that interval.
Current behavior — expiry and scheduled deletion
There is no browse page, no search, and no index. Files are only reachable through their link.
Nothing is meant to stick around. Expiry is automatic, and storage cleanup follows on a schedule.
Enable encryption before a cloud upload to protect the file and original filename with AES-256-GCM in your browser. The encrypted envelope is capped at 32 MiB including overhead; browser copies use additional memory. Standard cloud uploads are not end-to-end encrypted. The complete download link carries the key after #key=, which is not sent in HTTP requests. Share it privately: anyone with that complete link can decrypt, and a lost key cannot be recovered by the service.
P2P mode transfers files up to 32 MiB directly over a WebRTC DTLS-encrypted data channel, without cloud storage. Exchange the offer and answer manually through a trusted separate channel and keep both tabs open. This is a local-network experiment with no STUN or TURN servers, not internet-wide or anonymous sharing. Network isolation and browser restrictions may prevent a connection; there is no automatic resume or cloud fallback.