A PairDrop alternative — same idea, and here's where it differs
Neither needs an app; we add verification and a relay fallback, it adds open source and self-hosting
PairDrop is a fork of Snapdrop's code, still actively maintained, purely a web page, built on WebRTC, and able to pair devices across different networks rather than only within one LAN. It belongs to the same family as this site, so the table below contains no verdict about which is better overall — only a handful of concrete differences.
SourceDrop your files here to start right now Start transferring now
Two differences actually matter. First, we compare a sha-256 value after each file lands and fail loudly if the two ends disagree — that addresses the case where a file arrives but is quietly corrupt, which matters most with multi-gigabyte video or a whole folder of assets.
Second, when a direct link genuinely can't be established — some corporate or campus networks, or both sides behind strict NAT — we ask whether to switch to a relay, label it as relayed, and delete the copy the moment the other side picks it up. Going the other way, it has something we don't: the code is open, you can deploy your own instance, and the server side is entirely yours. That one we can't offer.
Side by side
| What | PairDrop | TutuDrive Send |
|---|---|---|
| Anything to install | Nothing to install — it's a web page | Nothing to install — it runs in the browser |
| Where the bytes go | WebRTC peer-to-peer, the same mechanism this site uses | Peer to peer. If a direct link can't be made we switch to a relay and label it as relayed — we don't pretend it's still direct. |
| Across different networks | Yes — pairing across different networks is one of its stated features | Yes — the two sides don't have to be on the same network |
| Integrity check | Not documented publicly | Every file gets a sha-256 comparison when it lands; one byte off and it fails loudly |
| Is a copy left behind | No — on a direct connection the files don't pass through a server | On a direct connection nothing is left — the bytes never reach us. On a relay the copy is deleted the moment the other side picks it up, with a 24-hour sweep as a backstop. |
| Open source and self-hosting | Open source and self-hostable — it has this and we don't | Not open source, no self-hosting — this one we don't have |
When you should pick it instead
- You want full control of the server side, or a permanent in-house deployment on your own network: PairDrop can be self-hosted, and we can't offer that route.
- You trust code you can read line by line: it's open source, and nothing substitutes for that.
How it works here
- 1
Drop your files in, or click Choose files. A whole folder works too.
- 2
A QR code and six digits appear. The other person scans, types the digits, or opens the link you send.
- 3
Once connected the transfer starts. Neither side signs up, and nothing gets installed.
Common questions
PairDrop doesn't see the other device — what now?
The usual causes are the two devices not being on the same network, or the network having client isolation switched on (common on public Wi-Fi, guest networks and corporate networks) — devices can't see each other, so automatic discovery stops working. You can use its pairing feature, or take a route that doesn't rely on discovery at all: this page uses a six-digit code, so neither side needs to «see» the other; typing the code connects them.
Is one of them faster than the other?
When both are running a direct connection, speed comes down to the two networks rather than the site — on the same Wi-Fi you'll usually saturate the network adapter. What actually separates them is whether a direct link can be established at all: when it can't, one may fall back to a relay (bounded by the relay's bandwidth) while the other simply fails. So instead of comparing headline speeds, look at whether it connects in your particular network.
Is switching to this more steps than I'm used to?
Same number of steps: open the page, pick files, the other side scans or types the code. The difference is that this doesn't depend on devices discovering each other, so it still connects on public Wi-Fi or guest networks where devices are hidden from one another — which is exactly where automatic discovery tends to fail.
Can I send a whole folder?
Yes. Drag the folder in and the page packs it automatically, keeping the directory structure intact, so unpacking on the other side gives back the original layout. Several loose files aren't packed at all — they go one by one, and each is usable as soon as it lands.