How TransferFiles.net works
We never store your files. Your file travels in a direct encrypted tunnel from your device to the receiver using technology already built into every modern browser.
The core idea: peer-to-peer
Every traditional file-sharing service (WeTransfer, Google Drive, Dropbox) works the same way. You upload your file to their server. The receiver downloads it from that server. The company pays for bandwidth and storage, which is why they charge for large files.
TransferFiles.net works differently. We use a technology called WebRTC (Web Real-Time Communication) to create a direct connection between your browser and the receiver's browser. Your file goes straight across, device to device, without ever touching our servers.
What is WebRTC?
WebRTC is an open standard built directly into Chrome, Safari, Firefox, and Edge. It was originally designed for video calling (it powers Google Meet and WhatsApp Web). We use the same technology to stream file data instead of video. Every transfer is encrypted using DTLS-SRTP, the same standard used for encrypted video calls. This is automatic and cannot be disabled.
What happens when you send a file
- You pick a file. It stays on your device. Nothing uploads anywhere.
- A session code is generated. Our server creates a short code and link. This is the only data that touches our server. The actual file never does.
- You share the link or code with the receiver via WhatsApp, email, Slack, or any app.
- The receiver opens the link. Their browser connects using the code. Our server introduces the two browsers to each other, then steps aside completely.
- A direct encrypted tunnel opens between the two browsers. Our server is no longer involved.
- The file streams across in 64 KB chunks, directly from your device to the receiver's Downloads folder.
Why both tabs must stay open
Because your device is the source of the file, not a server. If you close your tab, the stream stops. This is the trade-off that makes the service free, private, and unlimited in size.
What about firewalls?
Most connections allow direct peer-to-peer. When a strict firewall blocks it, WebRTC automatically falls back to a relay server that passes the encrypted data without being able to read it.
Is it really private?
Yes. Our server only handles the session code, a short random string. Your file, its name, its contents, and all metadata never leave the two devices involved. We cannot see what you send.
Why is it free?
We have no storage costs and no bandwidth costs. The only infrastructure we run is a tiny signaling server that generates session codes. We keep it free through ads shown on the page.