LocalSend · Transfer files across your local network
Send files between Windows, macOS, Linux, Android and iOS devices on the same network, without an account or cloud upload. Includes practical setup checks and a recent reported limitation.
Quick start
Get LocalSend from the official download page or the v1.18.2 release. Install it on both devices, connect them to the same trusted local network, choose files on the sender, select the receiving device and approve the request there. Current README lists Windows 10+, macOS 11+, Android 7+ and iOS 13+; Linux dependencies vary by desktop. Allow the app's local-network permission and only the necessary firewall access; do not disable network protections broadly.
A useful bridge between devices
LocalSend is a practical option when a photo, PDF or folder needs to move between different operating systems nearby. Its official documentation describes direct transfers over the local network using HTTPS, without an account or a third-party transfer server. It is a transfer tool: do not expect remote access, version history or continuous folder sync.
Start with one small transfer
Install the official app on both devices and put them on the same trusted network. Choose a small file, select the receiving device, approve the request on that device, then open the received file before sending a large batch. If discovery fails, check local-network permission, guest-network isolation and the app-specific firewall rules. The official default port is 53317 for TCP and UDP; keep changes limited to a network you control.
The publisher's desktop image below illustrates the receiving queue and per-file progress. It is an existing official illustration, not a screenshot of our testing or evidence of v1.18.2 performance.
An independent October 17 report by Lightning-Lion describes LocalSend 1.18.2 on macOS losing an unfinished text message when an incoming request closes the composition dialog. Issue #3605 remains open when checked on October 22. For important text, write it in a separate editor or send a saved file rather than relying on an unsaved in-app draft. This is a specific user report, not a finding reproduced by Boloop.
The v1.18.2 release also documents fixes for compatibility with older clients and peer redirects. Prefer an official distribution channel, confirm the receiving device before approval, and judge speed on your own network. Our recommendation is for simple cross-platform local transfers; it is based on documentation and reported use, not a promise of transfer speed or a security certification.
Sources and further reading
- LocalSend official README and troubleshootingOfficial documentation · LocalSend contributors
- LocalSend v1.18.2 releaseOfficial documentation · LocalSend contributors
- Issue #3605: unfinished text lost after incoming requestUsage record · Lightning-Lion
- Official desktop illustration and Apache-2.0 licenseOfficial documentation · LocalSend contributors