How to send large files online with no size limit
Email stops at 25 MB. Free cloud links stop at 2 GB and make you upload first, then your receiver downloads — you pay the transfer twice. Peer-to-peer sharing skips the upload entirely: bytes stream straight from your device to theirs, so there is no cap to hit and nothing to delete afterwards.
Why size limits exist at all
Every mainstream tool stores your file first. Gmail, Drive, Dropbox, WeTransfer — the flow is always upload → store → download. Storage costs money, so free tiers cap it: 25 MB on email, ~2 GB on free transfer links, 15 GB shared across your whole Google account. The limit is not your internet speed. It is someone else's hard drive bill.
Peer-to-peer removes the middle step. The server only introduces the two browsers (a few kilobytes of connection setup), then gets out of the way. No storage means no storage bill — and that is why there can be no size limit on our side. A 100 MB deck and a 20 GB video project take the same three clicks.
Cloud vs P2P: where your time actually goes
| Step | Email / Drive free | P2P (this app) |
|---|---|---|
| Upload | Full upload first (often fails past 2 GB) | None — stays on your device |
| Wait | Upload time + processing + download time | One transfer, live progress |
| Size cap | 25 MB – 2 GB | No cap |
| Account | Both sides usually need one | Nobody needs one |
| Afterwards | File sits on a server until you delete it | Close the tab — nothing remains |
Send a large file in 3 steps
- Pick your files on the home page.
The moment you add a file, a private link, a QR code and a 4-digit nearby code appear. No button hunt, no form.
- Send the link however you like.
Paste it in chat, show the QR in person, or read out the 4-digit code — the receiver types it on the same page.
- Keep the tab open until they finish.
The stream is live: closing your tab ends it instantly. That is the privacy guarantee — and the one rule. Watch the live speed and ETA while it flies.
One-off big sends: video projects, photo shoots, disk images, datasets. If both of you are online together, this is the fastest and most private way to move bytes — nothing to upload, nothing to clean up, nothing stored anywhere. That is why we call it the best way to send large files when privacy matters.
Real limits to know (honest version)
No cap on our side does not mean no limits anywhere. Here is the full truth:
- Both devices must be online together. P2P is live by nature — unlike a drive link, the receiver can't fetch it while you sleep. If you need async pickup, use cloud storage instead.
- Your network sets the speed. Home and café networks work; some strict corporate NATs block direct connections (a relay fallback covers those).
- Safari holds files in memory (~4 GB). Chrome, Edge and Firefox stream straight to disk with no practical ceiling.
- Every file is checksum-verified. The receiver confirms byte count + SHA-256 before anything is saved, so a truncated 18 GB video fails loudly instead of arriving broken. More on that in the creator's guide.
Closing the sender tab kills the link instantly. Keep it open until the receiver's progress hits 100% — the live ETA tells you exactly how long that is.
Questions, answered
Is there really no file size limit?
Correct on our side: the limit is your devices and your network, not us. Chrome, Edge and Firefox stream to disk; Safari holds files in memory at around 4 GB.
How is this different from Google Drive?
Drive stores your file on Google's servers (upload, then download, counted against quota). P2P never stores it anywhere — it streams once, directly. See the full P2P vs cloud comparison.
Is it safe for private files?
Yes — the connection is DTLS-encrypted end to end, and the server never receives file bytes at all. Read how the encryption works.
What if the transfer interrupts?
Interrupted transfers fail loudly and save nothing half-written. Re-share and retry — the receiver's progress resets cleanly.
Send your large file now
No account. No upload. Your link appears the moment you pick a file.