Snapdrop is one of those tools people discover exactly when they need it: two devices, one file, no cable. So when the page loads but nothing connects — or the site itself is down — it's uniquely frustrating. This guide walks through what actually goes wrong, the fixes worth trying, and when to give up and switch tools.
Table of Contents
- First, the context: Snapdrop is no longer maintained
- Cause 1: The signaling server is having a bad day
- Cause 2: The devices are not on the same network
- Cause 3: AP isolation is blocking peer-to-peer traffic
- Cause 4: Browser WebRTC is restricted or blocked
- Cause 5: Corporate firewall or proxy interference
- Cause 6: Stale page state
- Cause 7: You're asking it to do more than it can
- When to switch: an alternative with no relay dependency
- Quick decision table
First, the context: Snapdrop is no longer maintained
The original Snapdrop project has stopped receiving updates. The community fork PairDrop carries the idea forward, but the underlying architecture is the same: devices discover each other through a signaling server on the internet, then try to open a direct WebRTC connection for the actual transfer. Most "Snapdrop not working" reports trace back to one link in that chain.
Cause 1: The signaling server is having a bad day
Because discovery depends on a public server, an outage on their side looks exactly like a bug on yours: the page loads, but no other device appears. Fix: check whether both devices show someone in the list. If neither device sees anything, wait or retry later — nothing on your end is broken.
Cause 2: The devices are not on the same network
Snapdrop needs both devices on the same Wi-Fi (or at least on networks that allow peer-to-peer traffic between them). Common traps:
- One device is on the guest Wi-Fi, the other on the main network
- One device silently fell back to mobile data
- A VPN on either device routes traffic elsewhere
Fix: verify both IPs look alike, disable VPNs, and reconnect both devices to the same SSID.
Cause 3: AP isolation is blocking peer-to-peer traffic
Many public and hotel networks enable "client isolation," which lets you reach the internet but blocks devices from reaching each other. WebRTC then fails even though discovery worked. Fix: test on a phone hotspot — if transfers work there, the router is the culprit. On your own router, disable AP/client isolation.
Cause 4: Browser WebRTC is restricted or blocked
Snapdrop is WebRTC-only. If your browser (or an extension) blocks WebRTC, pairing never completes. Fix: try another browser with no extensions, and check that WebRTC isn't disabled in browser flags or by privacy plugins.
Cause 5: Corporate firewall or proxy interference
Corporate networks often allow HTTP out but block the UDP ports WebRTC prefers. Fixes on that network are usually out of your hands — a phone hotspot sidesteps the problem entirely.
Cause 6: Stale page state
Long-lived Snapdrop tabs drift out of sync with the signaling server. Fix: hard-refresh (Ctrl+Shift+R) on both devices, or close and reopen the tab.
Cause 7: You're asking it to do more than it can
Snapdrop moves files and nothing else. If you came looking for phone management — browsing storage, replying to SMS, mirroring the screen — no fix will get you there. That's a different tool.
When to switch: an alternative with no relay dependency
If outages keep eating your transfers, the structural fix is to stop depending on an external server at all. PlainApp takes the opposite approach from Snapdrop: your Android phone itself runs a secure local web server, and any device on the same Wi-Fi connects to it directly through a browser — no signaling server, no relay, no account.
The trade-off is honest: PlainApp serves Android as the hub (the other side just needs a browser), while Snapdrop is OS-agnostic on both ends. If your workflow is "Android phone + whatever computer I'm at," the direct connection is faster and works even when the internet doesn't. See the full comparison in Snapdrop alternative: private sharing with no relay server.
If what you liked about Snapdrop was the nothing-to-install browser experience itself — and you don't need phone management — PlainICU (from the PlainApp team) is that idea kept current: open the page on both devices, files transfer directly over WebRTC, no account and no install on either side.
Quick decision table
| Symptom | Likely cause | First fix |
|---|---|---|
| No devices appear at all | Signaling server or network | Hotspot test, retry later |
| Devices appear, transfer fails | AP isolation / WebRTC blocked | Hotspot test, disable isolation |
| Works at home, fails at hotel | Client isolation | Use phone hotspot |
| Works then stalls mid-transfer | UDP blocked mid-session | Retry on hotspot |
| Only need it once a month | — | Any of the above, patiently |
Whatever you pick, the one thing worth knowing is why it broke: with a relay-based web tool, half the failures aren't yours to fix.