LocalSend: File Transfer Over LAN Without a Central Server

The Problem: Local File Sharing Without an Internet Connection

Most file-sharing tools depend on a cloud server or an internet connection. If you are on a local network with no internet access, a cloud-based tool cannot push a file to a colleague's phone. LocalSend solves that by transferring files and messages directly between nearby devices over the local network. It is built for people who need a quick, secure transfer without standing up a server or relying on an external service. The README is explicit: it does not require an internet connection or third-party servers. That makes it a fit for field workers, labs, and anyone who values privacy over convenience.

How LocalSend Works: REST API and HTTPS on the LAN

LocalSend uses a REST API and HTTPS encryption to communicate between devices. Each device runs a local HTTP server, and discovery happens over the local network. When you send a file, the sender pushes it to the receiver's IP address using the API, and the receiver's app accepts or rejects the transfer. There is no central relay, so both devices must be on the same local network. The architecture is simple: no internet, no third party. That design keeps data on your own network, but the README says to disable AP isolation on your router, which is often enabled on guest networks.

Getting Started: Installation and First Run

LocalSend is distributed through app stores and package managers rather than auto-update. On Windows, you can install it via winget, scoop, or Chocolatey, or download an EXE installer or portable ZIP from the latest release. On macOS, use the App Store, Homebrew, or a DMG installer. Linux users can get it from Flathub, Snap, AUR, or as a TAR, DEB, or AppImage. Android users can use the Play Store, F-Droid, or an APK. iOS users get it from the App Store. The README recommends using an app store or package manager because the app has no auto-update. After installation, the app should work out of the box in most cases, but you may need to configure your firewall to allow LocalSend to communicate over the local network. The README mentions that Linux desktops require xdg-desktop-portal and the GTK or KDE variant, so those are prerequisites on that platform.

Compatibility and Platform Support: What You Need to Know

LocalSend supports Android 7.0 and later, iOS 13.0 and later, macOS 11 Big Sur and later, Windows 10 and later, and Linux with no stated minimum version. Windows 7 support ends at v1.15.4, so if you have legacy machines, you are stuck on an older release. For macOS, users on older hardware may need OpenCore Legacy Patcher 2.0.2, as referenced in issue #1005. Linux users must have the appropriate xdg-desktop-portal backend installed. This is not a tool that runs everywhere; it is a tool that runs on modern systems, and you should check your fleet's OS versions before rolling it out.

A Real Limitation: No Auto-Update and Manual Firewall Configuration

The most obvious operational limitation is the lack of auto-update. The README explicitly says the app does not have an auto-update, and it recommends installing via an app store or package manager to get updates. That means you are responsible for tracking new releases and applying them yourself. On a managed fleet, that is an extra step. The second limitation is firewall configuration. If you have trouble sending or receiving files, the README says you may need to configure your firewall to allow LocalSend to communicate over the local network. That is a real failure mode: a strict corporate firewall can silently block transfers, and the README lists the rules: allow incoming TCP and UDP on port 53317 and outgoing TCP and UDP on any port, and disable AP isolation on your router.

Alternative Approach: Centralized File Transfer Services

The obvious alternative is a cloud-based tool such as Dropbox or WeTransfer. Those services route data through a server, which allows transfers across the internet and between different networks. The difference in approach is fundamental: LocalSend keeps traffic on the LAN and requires no server, while a centralized service needs an internet connection and stores or relays your data on a third party's infrastructure. If you need to send a file to someone on a different network, LocalSend will not work; you would need a service that can traverse the internet. Conversely, if you want to avoid sending data through a third party, LocalSend is the better fit. The trade-off is clear: local-only versus global reach.

Maintenance and Upgrade Cost: What You Should Budget

Because LocalSend has no auto-update, the maintenance cost is manual. You must monitor the releases page or rely on your package manager to notify you of updates. The project is actively maintained, with recent releases v1.18.0, v1.18.1, and v1.18.2 pushed in August 2026. The license is Apache-2.0, which permits commercial use, modification, and distribution, but you should review the license terms yourself for your specific use case. The README mentions a code signing policy for Windows binaries, so you can verify that builds are signed. For upgrades, you need to test that new versions still work with your firewall and OS versions, especially if you are on an older platform like Windows 7, where you cannot upgrade beyond v1.15.4. The cost is not high, but it is not zero: plan for periodic manual updates and regression testing on your target platforms.

Editorial conclusion

Adopt LocalSend if you need a no-internet, no-server file transfer tool across Android, iOS, Windows, macOS, and Linux, and you are comfortable managing firewall rules and installing updates manually through package managers. Do not use it if you require automatic updates, cross-network transfers, or if your devices run Windows 7 (support ends at v1.15.4). Before deploying, verify that your firewall permits LocalSend's ports and that all devices are on the same local network with AP isolation disabled, since the app relies on local discovery and HTTPS encryption without a central broker.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes