About BeamDrop
I’m Maya, a web developer in Seattle. For about ten years I’ve built real-time features for the browser — video calls, collaborative editors, live dashboards — which means I’ve spent a lot of time with WebRTC, the technology that lets two browsers talk to each other directly.
BeamDrop started with a small annoyance. I kept needing to move big files between my own machines, or to a client in the next building, and every option involved uploading gigabytes to someone’s cloud, waiting, then downloading them again — and leaving a copy behind on a server I didn’t control. Browsers have been able to send data directly to each other for years. I wanted a tool that did just that, and nothing else.
What I promise
- No copies. BeamDrop’s server never receives your files. It only introduces the two browsers. The security page lists exactly what it can see.
- No relay, even when it would be convenient. If a direct connection can’t be made, BeamDrop says so instead of quietly routing your files through a server.
- No accounts, ads or trackers. The site loads no analytics scripts or third-party code.
- Plain explanations. The how it works page and the guides describe the real mechanics, limits included.
How it’s built
The pages are plain HTML with a small amount of JavaScript. Transfers use the browser’s built-in WebRTC data channels, SHA-256 checksums computed with WebAssembly, and a zip builder that runs in the recipient’s browser. The only server component is a tiny Node.js signaling service that pairs rooms and passes connection messages; it keeps rooms in memory and forgets them when the sender leaves.
Get in touch
Bug reports, feature ideas and abuse reports all go to hello@wetransfertool.com. See the contact page for what to include.