Send large files online — up to 10 TB per file
Your files stream straight from your browser to the recipient’s over an encrypted peer-to-peer channel. No cloud hop, no size wall, no account — a file leaves your device exactly once.
- DTLS encrypted
- SHA-256 verified
- 200 files per transfer
- No sign-up
Some perspective on size
Where the usual ceilings sit — and where a direct transfer gets to live.
Logarithmic scale — each gridline is 10× the one before it. Most services make you wait while the file uploads to their cloud, then pay when it's too big. A direct transfer skips that step entirely.
The cloud makes big files cross the internet twice
Upload services put a storage bucket between you and the recipient. A direct transfer removes it — along with the second trip, the waiting, and the copy of your file on someone else’s disk.
- 1
Upload
The full file travels from you to their storage. You watch a progress bar.
- 2
Wait
Nothing reaches the recipient until your upload finishes — every last byte.
- 3
Download
The file travels again, this time from their storage down to the recipient.
Plus: the file now sits on a server, tied to an expiry date and an account policy you didn’t choose.
- 1
Connect
The two browsers find each other and open an encrypted channel. Seconds.
- 2
Stream
Bytes flow directly, sender to recipient — the file crosses the internet exactly once.
- 3
Verify
SHA-256 digests computed on both sides must match before delivery counts.
Nothing to store, nothing to expire — the file was never anywhere but the two devices.
The honest comparison
Including the trade-off nobody likes to advertise.
| Feature | I Love Doc — direct | Cloud upload services |
|---|---|---|
| Max file size | 10 TB per file | ~2 GB on free tiers; paid plans for more |
| Internet crossings | Once — sender to recipient | Twice — upload to storage, then download |
| Recipient starts receiving | While the file streams | After the upload completes |
| Stored on a server | Never, on the direct path | Yes, until the link expires |
| Account required | No | Often, for larger files |
| Works after sender closes the tab | No — the sender stays online | Yes |
The direct path needs both browsers online at the same time. That’s the price of keeping servers out of the path — and it’s why nothing of yours is left behind when the transfer ends.
Built to move bulk
Large transfers aren’t an afterthought here — the protocol was designed around them.
What people move with it
Any file that’s too big for an email and too sensitive for a storage bucket.
Large-file questions
The specifics of sending big files browser to browser.
Ready to move something big?
No install, no account, no upload queue. Pick your files, share the code, and keep the tab open.
No install · no account · keep your tab open