Snapdrop vs PairDrop: Which One Should You Actually Use?

If you used Snapdrop at any point in the last few years, you have probably noticed the signs: the site still loads, but development stopped, issues pile up, and the community quietly moved on. The successor most people landed on is PairDrop — a fork of Snapdrop built by one of its own contributors. This guide compares the two honestly, fixes the problems you'll actually run into with PairDrop, and covers what to choose if file-dropping isn't all you need.

Table of Contents

• The short answer
• What actually happened to Snapdrop
• Feature comparison
• Is PairDrop safe?
• Speed and reliability
• PairDrop not working: 5 fixes
• What neither tool does
• Quick decision table

The short answer

If you're choosing between the two today, use PairDrop. It is the actively maintained fork: same browser-to-browser, no-setup experience you liked in Snapdrop, plus device pairing for transfers across networks and the option to self-host. Snapdrop's repository is effectively unmaintained, and sticking with it mostly means waiting for something to break with nobody left to fix it.

But if you're evaluating because file transfer is only part of what you do at your desk — moving photos, sending texts, managing storage from the PC — a file-drop tool is the wrong category altogether. That case is covered in What neither tool does.

What actually happened to Snapdrop

Snapdrop was the original: open-source, browser-based, AirDrop-style sharing built on WebRTC, created by RobinLinus. It worked entirely in the browser with no accounts, and for years it was the default answer for "how do I send a file from my phone to my laptop".

Then development stalled. The repository went long stretches without meaningful commits, and the project was eventually acquired by LimeWire — a brand with its own products and priorities. The site still resolves, but "maintained" is no longer a word that applies. When things break — and our Snapdrop troubleshooting guide goes deep on how often they do — there is no one on the other end.

PairDrop was forked from Snapdrop by schlagmichdoch, a Snapdrop contributor, precisely to keep the idea alive: fix the bugs, modernize the stack, add what was missing. It keeps the same core promise — open a tab on both devices, drag, drop — while shipping the features Snapdrop never got around to.

Feature comparison

The two rows that matter in practice are maintenance and cross-network transfer. Maintenance decides whether the tool works next year. Cross-network pairing is the feature people don't know they need until they try to send a file to someone on cellular while they're on Wi-Fi — with Snapdrop that's simply a dead end.

Is PairDrop safe?

The security model is the same shape as Snapdrop's, which is worth understanding rather than just trusting:

• The file transfer itself is peer-to-peer WebRTC, which is encrypted end to end by design. The server never sees file content.
• The server does see connection metadata: IPs and the fact that two devices negotiated, because a signaling server is what introduces peers to each other. This is also true of Snapdrop.
• Internet transfers between paired devices route through relay infrastructure (TURN), since punching through NATs sometimes requires it. Same as any WebRTC service.
• You can eliminate the third party entirely by self-hosting. PairDrop ships a one-line Docker setup; then the signaling server, the metadata, and the network are all yours.

So: is PairDrop safe? For same-network browser sharing, yes — the usual WebRTC caveats aside, it's as safe as this category gets, and safer than uploading files to a cloud service. If the metadata exposure bothers you, self-host and the question closes. The one habit to break is treating any public web-drop tool as a place for sensitive documents — that was true of Snapdrop and is true of everything in this category.

Speed and reliability

Both tools are bound by the same physics: WebRTC directly between devices when the network allows it, so bulk speed is your network's speed, not the tool's. The differences that show up in real use:

1. Connection reliability favors PairDrop. Snapdrop's signaling server is the single point of failure, and it has had rough stretches. PairDrop's instance is monitored and actively operated — and again, self-hosting removes the dependency altogether.
2. Both struggle with hostile networks. AP isolation, corporate firewalls and restricted browsers break WebRTC in identical ways — see the fixes below.
3. Neither resumes interrupted transfers. A dropped transfer restarts from zero. For big files that's the moment people start looking at tools designed for syncing rather than dropping.

PairDrop not working: 5 fixes

The failure modes carry over from Snapdrop, with a few PairDrop specifics. In rough order of how often each one is the culprit:

1. Devices not on the same network. The classic. Your phone on 5 GHz and laptop on the guest SSID are different networks, even if the router is the same box. If you genuinely need cross-network, use PairDrop's device pairing instead of fighting it.
2. AP/client isolation enabled. Router settings that forbid clients from talking to each other kill P2P discovery. Look for "AP isolation", "client isolation" or "guest mode" in your router admin page.
3. Browser WebRTC restrictions. Strict privacy modes and some extension suites disable WebRTC entirely. A quick test: open another browser with no extensions.
4. Stale page state. Tabs left open for days drift out of sync with the signaling server. A hard refresh on both devices fixes an absurd share of "it doesn't see my phone" reports.
5. Self-hosting without WebSocket support. If you run your own instance behind a reverse proxy, the proxy must pass WebSockets through — nginx and friends need the upgrade headers configured, or devices will pair with the server and never find each other.

If you're hitting these constantly on networks you don't control, that's not a PairDrop bug — it's the category's ceiling. The way out is a tool that doesn't depend on browser networking at all.

What neither tool does

Here's the honest ceiling of both Snapdrop and PairDrop: they move a file from A to B. No phone management, no messaging, no media library, no clipboard, and no answer for "I want my phone's content available while I work, not just one file at a time".

That's the gap PlainApp fills. It's a free, open-source Android app that runs a private web panel on your own phone — you open it from any browser on the same network and get your files, photos, messages and notes, with transfers encrypted end to end and nothing routed through anyone else's server. Where PairDrop still needs its signaling infrastructure, PlainApp's only moving part is your phone.

If you arrived here comparing drop-tools, the combination that works for a lot of people is PairDrop for quick guest-to-guest drops, plus PlainApp as the daily driver between your own devices. For the full case, see the Snapdrop alternative comparison — and if you also weigh PairDrop against LocalSend's desktop-app model, the LocalSend alternative guide covers that angle in detail.

Quick decision table