JUST BETWEEN TWO DEVICES
A little closer.
A lot more private.
Send a file straight to another browser.
No account. No upload. Just a direct connection.
BROWSER TO BROWSER
Make a connection.
Choose a file, then invite your other device.
Invite your other device.
Open this private link in the other browser. Keep this tab open.
Treat this link like a password. It pairs only two devices and expires in 10 minutes.
Ready to receive?
Connect to the device that shared this invitation. You’ll approve each file before it’s sent.
Send this response back to the sender. They’ll paste it into their tab to finish connecting.
You’re connected.
Encrypted. Direct. Just the two of you.
Waiting for the sender to choose a file…
INCOMING FILE
Checking browser support…
Do the devices need to be on the same Wi-Fi?
The same Wi-Fi is the easiest place to start, but local routes can be blocked even there. Drop uses Google STUN to discover direct routes by default. You can disable discovery or choose your own STUN server in Connection options on each device. Some restrictive networks still require a relay; Drop will report a connection failure instead of relaying your file.
How private is the connection?
WebRTC encrypts every file in transit. Your invitation authenticates the connection, and the pairing secret stays in the link’s fragment, outside server requests. Anyone with the full invitation can join, so share it privately. The other device learns your network address. As with any web app, you must trust the site hosting the JavaScript.
Can I send large files?
Browsers with a file save picker, such as desktop Chrome and Edge, can write directly to disk. Other browsers keep the received file in memory, with a 128 MB limit per file. Keep both tabs active and your devices awake. Interrupted transfers need to restart.