Snapdrop Not Finding Devices? Causes and Fixes

October 14, 2026

Snapdrop is a popular browser tool for sending files between nearby devices, and the most common complaint about it is simple: the other device does not show up. When Snapdrop is not finding devices, the cause is almost always the network the two devices are on, not a fault in either browser. This guide covers the usual reasons, the fixes worth trying, and what to do when none of them work.

How Snapdrop decides which devices to show

Snapdrop-style tools find peers by grouping devices that appear to come from the same network, then letting you pick one from a list. There is no pairing code to enter. That is what makes it feel instant, and it is also the source of every problem below, because the grouping only works when both devices look like they share a network. Details of Snapdrop's current behavior can change, so treat this as a general explanation of how local-discovery tools work.

Cause 1: The devices are on different networks

The most common mistake is one device on Wi-Fi and the other on mobile data, or one on the main network and the other on a guest network. Check that both devices show the same Wi-Fi name, and turn off mobile data on the phone so it cannot quietly take over.

Cause 2: Client isolation or a guest network

Many routers, hotels, offices and cafes enable client isolation, which stops devices on the same Wi-Fi from talking to each other. Guest networks often turn it on by default. If you control the router, look for a setting called AP isolation or client isolation and switch it off. If you do not, a different network, or a personal hotspot, is the fix.

Cause 3: A VPN, private relay or proxy

A VPN changes how your device appears on the network, so two devices that share a router can look like they are in different places. Turn off VPNs and iCloud Private Relay style features on both devices and reload the page.

Cause 4: Browser settings and stale tabs

Hard-refresh both pages, close extra tabs, and try a different browser if one is misbehaving. Some privacy settings and extensions block the connection types these tools use. A phone that went to sleep may also have paused the tab, so wake it and keep the screen on while you connect.

Cause 5: Corporate or school networks

Managed networks often block the peer-to-peer connections local-discovery tools depend on. If you are on a work or school network, expect trouble, and consider a hotspot or a tool that does not rely on shared-network discovery.

When the fix is a different pairing method

If you cannot control the network, the reliable answer is a tool that does not depend on it. Nearsend pairs two devices with a QR code, a six-digit PIN or a spoken voice phrase, so the devices do not need to share a network to find each other. It connects directly in the browser, encrypted, with no account and no app. Nearsend also shows nearby devices on the same network for one-tap pairing when they are available, so you get the convenient path when it works and a dependable fallback when it does not.

A fast troubleshooting order

Check both devices are on the same Wi-Fi with mobile data off. Turn off any VPN. Reload both pages. Try another network or a hotspot. If it still fails, switch to a pairing-code tool rather than fighting the network. Working through that order takes a couple of minutes and covers nearly every case.