LocalSend: File Transfer Over LAN Without a Central Server
LocalSend transfers files and messages between nearby devices over the local network without a central server.
At a glance
- What is it?
- LocalSend is a cross-platform, open-source app that moves files and messages between nearby devices over the local network using a REST API and HTTPS. It requires no internet connection or third-party server, but that architecture brings specific constraints you should weigh before adopting it.
- Who is it for?
- 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).
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Dart, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
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 in a meeting room with no Wi-Fi, on a plane, or in a facility with strict network isolation, you 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 README does not detail the discovery protocol, but the architecture is clear: no internet, no third party. That design keeps data on your own network, but it also means the app cannot route around network segments that block multicast or broadcast traffic. If your network isolates devices by VLAN, you may need to configure routing or use a different tool.
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 5.0 and later, iOS 12.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. The README notes that there might be backports for Windows 7 in the future, but nothing is guaranteed. 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 troubleshooting section is thin on specifics. The README does not list the exact ports or protocols, so you will have to inspect the source or test empirically.
Alternative Approach: Centralized File Transfer Services
The obvious alternative is a centralized transfer service like Snapdrop or 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 subnet, since the app relies on local discovery and HTTPS encryption without a central broker.
Community notes