LocalSend not finding the other device
Last checked
LocalSend is a very good app, and when it cannot see the other device the cause is almost always the network, not the app. Here are the fixes from LocalSend's own guide, and what to do when the network simply will not let two devices talk to each other.
Fixes from LocalSend's troubleshooting guide
From the LocalSend README (checked 2026-10-30):
- Turn off AP isolation on the router. "If it is enabled, connections between devices are forbidden." The README adds that some routers enable it, "especially guest networks".
- On Windows, set the network to Private. "Windows might be more restrictive when the network is configured as public."
- On a Mac, iPhone or iPad, check Local Network access. Toggle the "Local Network" permission under Privacy in the system settings.
- Pause the VPN. "Some VPNs block local network connections by default." Allow LAN traffic or disable the VPN for a moment.
- Open the firewall. Allow incoming TCP and UDP on port 53317.
- Send by IP address. Use manual sending and type the receiver's IP. If that works, add the device to favorites so it is probed directly.
For slow transfers, the guide suggests using 5 GHz Wi-Fi. Also check the minimum versions: Android 7.0, iOS 13.0 and Windows 10, per the same README.
When the network will not cooperate
Some networks are built to keep devices apart: hotel and café Wi-Fi, guest networks, office networks you do not control. You cannot change their settings, and LocalSend, which only works on the local network, cannot get around them.
A browser tool can. With tosstome:
- Open toss2.me on both devices.
- If they do not appear in each other's list, press Create a code on one and type the 6 digits (or scan the QR code) on the other.
- Tap the other device and pick the files.
tosstome first tries a direct WebRTC connection. If the network blocks it, the transfer goes through a relay on Cloudflare that forwards the bytes and keeps nothing; the transfer row shows Direct or Relay. The relay path needs internet and is slower than a local transfer, but it gets the file across. More about codes.
Which one to use
On a home network you control, fix the setting above and keep using LocalSend: it works without internet and does not depend on any server. Use tosstome for the networks you cannot fix, for devices on two different networks, or on a computer where you cannot install an app. See the full LocalSend vs tosstome comparison.
Questions
Why can't LocalSend see my other device?
LocalSend only works on the local network, and its troubleshooting guide lists the usual causes: AP isolation on the router (common on guest networks), a Windows network set to Public, the Local Network permission switched off on macOS or iOS, an active VPN, or a firewall blocking port 53317.
Does LocalSend work on different Wi-Fi networks?
No. LocalSend shares files with nearby devices over the local network. For devices on different networks, a browser tool with a pairing code, such as tosstome, works instead.
Will tosstome work where LocalSend does not?
Often. tosstome tries a direct connection first and, if the network blocks it, sends through a relay on Cloudflare that keeps nothing. That path is slower than a direct local transfer and needs internet access.