A laptop, phone, and tablet securely share files over Wi-Fi in a cozy home office.
LocalSend replaces the email-to-myself habit for one narrow job: moving files between devices that sit on the same network. XDA Developers writer Jasmine Mannan describes using it that way across Windows, macOS, Android and iOS. The project's own documentation backs up most of what she says. It also adds caveats that anyone setting this up on a Windows PC should know.

A laptop, phone, and tablet securely share files over Wi-Fi in a cozy home office. What LocalSend is​

LocalSend is a free, open-source app for sharing files and messages with nearby devices over a local network, with no internet connection required. The project site says it needs no account or login. It lists Windows, macOS, Linux, Android and iOS as supported platforms.

The repository lists these minimum versions:

  • Windows 10
  • Android 7.0
  • iOS 13.0 (sharing from other apps needs iOS 14 or later)
  • macOS 11 Big Sur

Older systems are covered by older releases. The last Windows 7 build is v1.15.4, and the last Android 5/6 and iOS 12 builds are v1.17.0.

One practical detail from the README: the app has no auto-update. The project recommends installing it from an app store or package manager so you still get updates. On Windows that means Winget, Scoop, Chocolatey or the Microsoft Store, with an EXE installer and a portable ZIP also available.

How it works​

The protocol spec (currently v2.2) describes a REST-style design with no external servers. It needs only one party to run an HTTP server.

  • Discovery: each device announces itself by UDP multicast. The default group is 224.0.0.167 and the default port is 53317. Devices that hear the announcement reply with their alias, device type, port and protocol.
  • Fallback discovery: if multicast fails, the spec describes a legacy mode that probes local IP addresses directly.
  • Transfer: the sender first submits file metadata only. The receiver can accept, partially accept or reject the request, and a PIN can be required. Only then does the binary data flow.
  • Identity and encryption: with encryption on, a device's fingerprint is the SHA-256 hash of its locally generated certificate. With encryption off, it is a random string.

The security caveat​

This is where XDA's piece needs a clearer reading. App-to-app transfers use HTTPS. The "Share via link" fallback is different. The protocol says it uses plain, unencrypted HTTP because browsers reject self-signed certificates.

That fallback is the right tool for handing a file to a guest whose device has no LocalSend. It does not have the same protection as a transfer between two LocalSend installs. Anyone else on the network could in principle observe that traffic.

"Local" also doesn't mean "trusted." On a café, hotel or office guest network, other devices share your segment. The project site says PIN verification can be turned on as an extra safeguard, and it is worth enabling on any network you don't control.

XDA's claim that this keeps documents off third-party mail servers is accurate in a limited sense. The transfer doesn't pass through an email provider. It isn't a backup, and it doesn't make the network private.

Windows setup and troubleshooting​

The README says LocalSend should work out of the box in most cases. If it doesn't, its guidance is:

  1. Allow incoming TCP and UDP on port 53317, and allow outgoing traffic.
  2. Disable AP isolation on your router. Guest networks often have it switched on, and it blocks device-to-device connections.
  3. If the receiving PC is Windows, set the network profile to Private. The README warns that Windows can be more restrictive on Public networks.
  4. On macOS and iOS, try toggling the Local Network permission in Privacy settings.
  5. If a VPN is active, allow local traffic or disconnect it temporarily.
  6. If discovery still fails, use manual sending and type in the receiver's IP address. If that works, add the device to favorites so it is probed directly.

Community reports on the project's GitHub issues match the network profile advice. One user couldn't send from a phone to a PC until they changed a network that Windows had labeled "Public" to "Private." That user said the Windows firewall applied different rules to the Public profile, and switching to Private fixed the transfer.

A Windows-specific port problem​

A second Windows failure is separate from firewall blocking. Several GitHub reports describe LocalSend failing to start with a "failed to create server socket" error, errno 10013, on port 53317. One report says the port wasn't in use by any other process, but Windows had it inside an excluded port range. Users linked this to Hyper-V, WSL, Docker or WinNAT, which can reserve ranges.

Workarounds users report include:

  • Changing the port in LocalSend's network settings. The project maintainer said in a discussion thread that any port between 1024 and 65535 works.
  • Restarting WinNAT, which one report says forces Windows to release and reallocate reserved ports.
  • Checking whether another program, such as GitHub Desktop in one reported case, is holding the port.

These are community workarounds, not official fixes. A change of port has to be made on every device you use, because they need to agree on it. A Microsoft Q&A thread from October 2026 describes the same symptom after a Windows update. The poster fixed it by changing the port on all their devices.

Some third-party guides also give a Defender click-path or netsh commands. They are plausible, but they are not from the LocalSend project. Check any firewall rule against your own network policy before applying it, especially on managed machines.

Limits to know before dropping email​

  • Both devices must be reachable at the same time. LocalSend has no store-and-forward queue. A sleeping PC or a device on another network can't receive. Mannan says she fell back to email in those cases.
  • iOS and Android background behavior. Mannan reports that iOS needs the app in the foreground to receive reliably, and that some Android manufacturers' battery optimization kills the background receiver. These are her firsthand observations, and I haven't corroborated them against platform documentation here.
  • Speed and size limits. The project says transfers run at your Wi-Fi's maximum speed with no bandwidth limit. That isn't a guaranteed rate. The sources don't establish a universal maximum file size, so don't assume every multi-gigabyte transfer will succeed on every device combination. The README's own troubleshooting advice for slow transfers is to use 5 GHz Wi-Fi and disable encryption on both devices. That trades away protection for speed, so think twice on shared networks. It also lists slow speeds on Android as a known issue.
  • Gmail's 25 MB cap is the author's reported obstacle. Check current limits yourself if that matters to your decision.

Where it fits​

For the phone-to-PC screenshot, receipt or raw photo batch, LocalSend removes the upload and download round trip and the leftover copies in your mailbox. It sits next to AirDrop and Quick Share rather than replacing cloud storage. For IT admins, it is also worth knowing about as something users may install themselves: it opens a listening port, uses multicast and needs firewall exceptions. Managed networks with multicast filtering or AP isolation will break it, and policy may restrict it.

The simplest approach is to use LocalSend at home or the office on a Private network profile, with PIN verification where appropriate. Keep email or a cloud drive for anything that needs to arrive while a device is asleep or somewhere else.

 

References

  1. I stopped emailing files to myself after installing this free open-source app XDA 2026-11-20T15:30:21+00:00
  2. README.md github.com
  3. README.md github.com