ToffeeShare vs tosstome
ToffeeShare and tosstome are close relatives: both send files straight from one browser to another with WebRTC, without a size limit and without keeping a copy. They differ in how the two sides find each other and in what happens when a direct connection is not possible.
What ToffeeShare says it does
From toffeeshare.com (checked 2026-10-28):
- "Send files of any size directly from your device without ever storing anything online", using "the peer-to-peer technology WebRTC".
- "Your data is encrypted end-to-end" and it "currently uses an implementation of DTLS 1.3".
- Files stay available while the tab is open: "When you close the browser tab your files are no longer accessible".
- The site also offers a Nearby devices option and a downloadable app. It is run from the Netherlands and reports more than 50 TB transferred per month.
Side by side
| ToffeeShare | tosstome | |
|---|---|---|
| How the other side connects | A share link, or nearby devices | Nearby list, 6-digit code, or an inbox link |
| Size limit | None | None set |
| Encryption | End to end (DTLS 1.3) | End to end when direct (DTLS); the relay fallback is TLS to Cloudflare, not end to end yet |
| Always-on receiver on a computer or server | Not described on the site | Yes, tosstome listen |
| Text messages | Not described on the site | Yes |
| Files stored | No | No |
Which one to use
ToffeeShare fits well when you want to hand someone a link and have every byte encrypted end to end. tosstome fits better for moving files between your own devices, for receiving on a headless machine, and on networks where a direct connection fails, because it falls back to a relay instead of stopping.
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.
Related
- FilePizza vs tosstome
- JustBeamIt vs tosstome
- Send large files without uploading them
- Snapdrop alternatives that still send peer to peer
Last checked 2026-10-28.