File Transfer
Send files of any size straight to any device — no uploads, no limits
Why peer-to-peer beats uploading
Classic sharing sites make you upload first and download later: your file sits on a stranger's server, counts against a size cap (usually 2 GB), expires after days, and travels the internet twice. Peer-to-peer transfer skips the middleman — the two browsers connect directly, so the file moves once, privately, with no cap to hit and nothing left behind on a server.
What this tool does
- 📡 Sends any files from one browser to another, any device
- 🔗 One link or short code connects sender and receiver
- 📊 Live progress per file on both sides
- 🔒 Encrypted connection (DTLS) with no server storage
When to use it
- Sending a 10 GB video that email and chat apps refuse
- Moving photos from phone to computer without cables or accounts
- Sharing Project files with someone on another network
Privacy: file bytes never touch our servers — only the tiny connection handshake passes through a public coordinator, and even that carries no file content.
Last updated · 2026-09-01
How the transfer works
Your browser opens an encrypted WebRTC data channel to the other browser after a short handshake coordinated by the public PeerJS network (it sees connection metadata, never file bytes). Files stream in 64 KB chunks with progress on both sides and are reassembled into a download on arrival. Close the sender tab and the link stops working — nothing remains anywhere.
Why transfer here?
No size cap, no expiry
Because nothing is stored anywhere, there is no 2 GB wall and no 7-day link rot. Send a 50 MB deck or a 15 GB video the same way — the only ceiling is device memory.
Private by physics
Files stream straight from sender to receiver over an encrypted channel. There is no upload step to trust and no server copy to leak, subpoena or breach.
Any device with a browser
No app to install on either end — Windows, Mac, Linux, Android and iPhone all join through the same link, which is exactly where installed apps fail cross-platform users.
Frequently asked questions
Where do my files go during transfer?⌄
Nowhere in between: they travel directly from the sender's browser to the receiver's browser over an encrypted WebRTC connection. No server ever stores them, which is exactly why there is no file-size limit on our side.
Is there really no size limit?⌄
We impose none — the limits are your devices: the receiver assembles the file in memory, so very large files (multiple GB) need a receiver with enough free RAM, and the sender tab must stay open until done.
What if the other device is on a phone?⌄
It works on any modern mobile browser including Mobile Safari: open the link, tap Join, and download each file when it arrives.
Frequently asked questions
Where do my files go during transfer?
Nowhere in between: they travel directly from the sender's browser to the receiver's browser over an encrypted WebRTC connection. No server ever stores them, which is exactly why there is no file-size limit on our side.
Is there really no size limit?
We impose none — the limits are your devices: the receiver assembles the file in memory, so very large files (multiple GB) need a receiver with enough free RAM, and the sender tab must stay open until done.
What if the other device is on a phone?
It works on any modern mobile browser including Mobile Safari: open the link, tap Join, and download each file when it arrives.