ShareDrop vs tosstome
ShareDrop started as an open source, peer-to-peer "AirDrop in the browser". The site at sharedrop.io now works differently: you upload a file, get a link, and the file is kept by LimeWire for a few days.
What sharedrop.io does today
From the page itself: "ShareDrop is part of LimeWire." Files are uploaded, the receiving link "leads to limewire.com", and without an account the limits are 4 GB per transfer, 20 files and 4 GB a day, and a link that "stays alive for 3 days". Source: sharedrop.io, checked 2026-10-28.
The original source code is still on GitHub at szimek/sharedrop under the MIT license.
Side by side
| sharedrop.io (LimeWire) | tosstome | |
|---|---|---|
| How files travel | Uploaded to storage, downloaded from a link | Device to device, or through a relay that keeps nothing |
| File kept on a server | Yes, 3 days without an account | No |
| Receiver can be offline | Yes | No |
| Size limit | 4 GB per transfer without an account | None set |
| Account | Optional | No |
| Always-on inbox on a computer | No | Yes, with tosstome listen |
Which one to use
Use a stored link like sharedrop.io when the other person will pick the file up later. Use tosstome when both devices are in front of you, or when the receiver is your own computer running the inbox, and you would rather the file never sat on a server.
What tosstome does
- Runs in the browser. Nothing to install on the sending side.
- Devices on the same network see each other automatically. On different networks, one device shows a 6-digit code and the other types it in.
- Files go device to device over WebRTC when the networks allow it. If a direct connection does not come up within a few seconds, they go through a relay on Cloudflare that forwards the bytes and keeps nothing.
- An optional command line tool,
tosstome listen, keeps an always-on inbox on a computer. It prints a link and QR code; open it on a phone and files land in a folder on that computer, with no browser open on the computer side. - Text messages and links travel the same way as files, with a Copy button on the receiving side.
- Nothing is stored. If the receiver is offline, nothing is sent.
What tosstome does not do (yet)
- The relay is protected by TLS between each device and Cloudflare, but it is not end-to-end encrypted yet. Direct WebRTC transfers are encrypted end to end by the browser (DTLS).
- A receiving browser keeps the file in memory until you save it, so very large files are better received with the command line tool, which writes straight to disk.
- Both sides must be online at the same time. There is no "upload now, download tomorrow".
- It is new. Browser-side device pairing and end-to-end encryption on the relay are still being built.
Last checked 2026-10-28.