Drift Transfer lets you send large files instantly, directly between browsers. No downloads, no accounts, no uploads — your files never touch a server. Just open a link, connect, and transfer. Simple, fast, and private.
No reviews yetBe the first to leave a review for Drift Transfer
Maker
📌
Hey everyone 👋
Drift Transfer started from a very simple frustration.
I was on Discord with friends, trying to send a large game file.
Discord wouldn’t allow it, email was out of the question, and even tools like WeTransfer felt slow or inconvenient for what we needed.
We also didn’t want to install anything.
So I built a small web app that connects two users directly in their browser to transfer files peer-to-peer.
The goal was simple:
remove all friction.
No downloads
No accounts
No uploads
No files stored anywhere
Just open a link, connect, and send.
Technically, it’s powered by WebRTC, which allows direct browser-to-browser communication. The challenge was making it feel simple and reliable enough for non-technical users.
This is not meant to replace full file-sharing platforms — just to solve that one annoying moment when you need to send something quickly, without overthinking it.
I’d love your feedback:
- Did it work smoothly for you?
- Any issues depending on your network or device?
- What would you improve?
Thanks for checking it out 🙌
how does it establish connection? are there any servers involved?
Report
Maker
@eremeev Drift Transfer establishes the connection in two steps:
Signaling server A small server is used only to help the two browsers find each other. It exchanges connection metadata such as WebRTC offers, answers, and ICE candidates. This is not your file data.
Direct WebRTC connection Once both browsers have enough connection info, they open a WebRTC DataChannel between them. The files are then split into chunks and sent directly from one browser to the other.
So yes, there is a server involved for setup/signaling, but files are not uploaded to or stored on a server. The actual file transfer happens peer-to-peer between the two devices whenever the network allows it.
If the direct connection cannot be established because of strict networks, VPNs, firewalls, or browser limitations, the transfer may fail unless a TURN relay is configured. Even then, a TURN server would only relay encrypted WebRTC traffic; it would not store the files.
Mailwarm
Any size limits or does it just depend on the browsers staying open?
@othman_katim No limits :)
how does it establish connection? are there any servers involved?
@eremeev Drift Transfer establishes the connection in two steps:
Signaling server A small server is used only to help the two browsers find each other. It exchanges connection metadata such as WebRTC offers, answers, and ICE candidates. This is not your file data.
Direct WebRTC connection Once both browsers have enough connection info, they open a WebRTC DataChannel between them. The files are then split into chunks and sent directly from one browser to the other.
So yes, there is a server involved for setup/signaling, but files are not uploaded to or stored on a server. The actual file transfer happens peer-to-peer between the two devices whenever the network allows it.
If the direct connection cannot be established because of strict networks, VPNs, firewalls, or browser limitations, the transfer may fail unless a TURN relay is configured. Even then, a TURN server would only relay encrypted WebRTC traffic; it would not store the files.