ToffeeShare and Beamaroo agree on the part that matters: files should travel directly between two browsers over encrypted WebRTC and never sit on a server. If that's why you use ToffeeShare, nothing here will talk you out of it. The differences are at the edges — how the two devices prove they're talking to each other, what happens when a strict network blocks a direct connection, and whether the sender gets real confirmation of delivery. Beamaroo pairs the devices with a one-time human code plus a QR handshake that cryptographically verifies the connection, falls back to an encrypted relay that cannot read your data when a direct path is blocked, and reports "Delivered, verified on their device" once the receiving browser has hash-checked every file.
Beamaroo vs ToffeeShare
An honest, side-by-side look — including where they beat us.
| Feature | Beamaroo | ToffeeShare |
|---|---|---|
| Browser-to-browser P2P over WebRTC | Yes | Yes |
| Files stored on a server | Never — server only introduces the two devices | Never — "we store nothing online" is its own stated model |
| End-to-end encryption | Yes, DTLS | Yes — states it uses DTLS 1.3 |
| Account to send or receive | None | None |
| Cryptographic peer verification | One-time human code + QR (SAS over DTLS fingerprints); a wrong or intercepted code burns the channel | Secret share link — anyone who opens the link is the peer; no short-code check |
| Verified-delivery receipt | Yes — receiving device hash-checks files, confirms back to sender | Not part of its published feature set — transfer progress only |
| Encrypted relay when a direct connection is blocked | Yes — Cloudflare TURN forwards ciphertext it cannot read | No relay documented — its FAQ describes direct shortest-path P2P |
| Both devices online at the same time | Required — it's a live beam | Required — close the tab and sharing stops |
| Very large multi-gigabyte transfers | Limited today — received files held in tab memory before saving (stream-to-disk planned) | No stated size limit — "share files of any size"; device memory and bandwidth still bound it |
| Cost | Free | Free, donation-supported |
ToffeeShare is an independent peer-to-peer file sharing service from the Netherlands, and it deserves its reputation: real WebRTC transfer, end-to-end encryption with DTLS 1.3, nothing stored online, no accounts, and by its own count more than 50 terabytes moved every month. People searching for an alternative usually aren't running from the privacy model — they want specific things it doesn't offer.
The first is proof of arrival. ToffeeShare shows a transfer progressing, but a published verified-delivery receipt isn't part of its feature set. Beamaroo's receiving browser hash-checks every file and returns a receipt — "Delivered, verified on their device" — so the sender isn't left guessing whether the last byte landed intact.
The second is what happens on hostile networks. ToffeeShare's FAQ describes direct shortest-path P2P, with no relay documented for when a corporate or university firewall blocks WebRTC entirely. Beamaroo falls back to an encrypted Cloudflare TURN relay in that case — the relay forwards ciphertext it cannot read, so the transfer completes without giving up end-to-end encryption. And where ToffeeShare's security rests on keeping a share link secret, Beamaroo verifies the actual connection: a one-time human code plus QR handshake checked cryptographically against the DTLS fingerprints, so a wrong or intercepted code fails and the channel is burnt after a single guess.
Delivery receipt built in — you'll know it landed
Every file is hash-checked on the receiving device over an encrypted WebRTC connection (DTLS), and the confirmation beams back to you: “Delivered — verified on their device.” Like a boomerang, it comes back. Most tools say “sent” the moment a file leaves your hands; Beamaroo waits until it's proven to arrive.
A verified pairing code, not a shareable link
A share link works for anyone who gets it. A Beamaroo verified pairing code cryptographically checks you're connected to the right device — and the channel burns after one wrong guess, so a leaked or mistyped code can't quietly reach the wrong person.
When to choose ToffeeShare instead
ToffeeShare is the better choice when the link workflow is the point — you paste one share link into any chat and the other person just opens it, with no code to read out. It has years of public operation behind it, moving more than 50 TB a month by its own count, and for very large single files its no-stated-limit model may fare better today than Beamaroo, which still holds received files in tab memory before saving. If you're happy trusting a secret link and don't need a delivery receipt or a relay for strict networks, ToffeeShare already serves you well.
Questions
Is Beamaroo a drop-in replacement for ToffeeShare?
For one-to-one transfers, yes — both are free, account-free, and beam files directly browser-to-browser over encrypted WebRTC with nothing stored on a server. Beamaroo adds a cryptographic pairing code, a verified-delivery receipt, and an encrypted relay for networks that block direct connections.
Does ToffeeShare upload my files to a server?
No — and that's worth saying plainly. ToffeeShare is genuine peer-to-peer: it states files go directly between devices and nothing is stored online. If you've read otherwise, it's usually confusion with cloud transfer tools. The differences with Beamaroo are at the edges — peer verification, delivery confirmation, and relay fallback — not the core privacy model.
How is Beamaroo's security different from ToffeeShare's?
ToffeeShare's security rests on keeping a share link secret — whoever opens the link becomes the receiving peer. Beamaroo verifies the connection itself: a one-time human code plus a QR handshake, checked cryptographically against the DTLS fingerprints of the actual connection. A wrong or intercepted code fails, and the channel is burnt after one guess.
What happens on a work or university network that blocks P2P?
Direct WebRTC is sometimes blocked by strict firewalls. Beamaroo falls back to an encrypted Cloudflare TURN relay — it forwards ciphertext it cannot decrypt, so the transfer completes and your files stay end-to-end encrypted. ToffeeShare documents direct shortest-path P2P with no relay fallback, so those networks can be a dead end.
Do both devices need to be online at the same time?
Yes, for both tools — that's the nature of true peer-to-peer. ToffeeShare says it directly: close the browser tab and your files are no longer accessible. Beamaroo is the same live beam. Neither parks your files in a cloud locker, which is exactly why nothing is ever stored.
Which handles very large files better?
Honestly: possibly ToffeeShare, today. It states no file size limit, bounded only by device memory and bandwidth. Beamaroo currently holds received files in the browser tab's memory before saving, which constrains multi-gigabyte transfers — stream-to-disk is planned. For typical photo, video and document sends, both are quick.