LocalSend
LocalSend 1.17.0 is an open-source cross-platform tool for sending files and text over a trusted local network without an internet account or third-party server, using local HTTPS transport.
What LocalSend provides
LocalSend transfers files and text between trusted devices on the same reachable local network. It does not require a cloud account or third-party relay for the normal local flow, while device discovery and firewall rules still depend on the network configuration.
Discovery and trust
Devices may fail to see each other when guest Wi-Fi, client isolation, local-network permissions or firewall rules block discovery. HTTPS protects the transfer channel, but the sender should still verify the displayed device and request before accepting a file.
Maintenance note
This page reviews LocalSend 1.17.0 for Windows, macOS, Linux, Android and iOS, including local discovery, port 53317, permissions, HTTPS and public-network handling. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave LocalSend to this cloud drive
Baidu Netdisk
Save LocalSend to this cloud drive
LocalSend 1.17.0 local-network file transfer guide
Install the app on two trusted devices, connect them to a network that allows peer access, and transfer one test file before sending important data.
Before you start
- Install matching LocalSend versions on the sender and receiver.
- Connect both devices to a trusted local network that allows client-to-client access; avoid guest or public Wi-Fi.
- Prepare a small test file with no sensitive data and record its name and size for verification.
Installation steps
- 01
Install and grant local-network access
Allow local-network access when prompted, set Windows to a private network when appropriate, and add a narrow firewall rule for LocalSend or the required port.
- 02
Confirm device discovery
Open LocalSend on both devices, compare the displayed device names and verify that the test network does not isolate clients.
- 03
Send and verify a test file
Select the receiver, accept the request on the intended device, and compare the received file name, size and checksum when available.
Quick start
- 01
Use explicit device names
Give each trusted device a recognizable name and review the request before accepting; do not enable automatic acceptance on an untrusted network.
- 02
Check the transfer directory
Choose a dedicated receive folder, confirm available space and avoid exposing a folder that contains unrelated private files.
- 03
Finish by disabling temporary access
Leave the trusted network, close the app or remove temporary firewall permissions, and confirm that the received file is where expected.
Usage tips
- Same Wi-Fi does not always mean peer access; client isolation, VLANs and firewall policies can block discovery.
- HTTPS protects the connection but does not identify a human recipient. Verify device name, request and file before accepting.
- Public Wi-Fi is a poor place for automatic receiving. Keep automatic acceptance off and use a private network for important transfers.
Troubleshooting and uninstall
Why can the two devices not find each other?
Check local-network permission, private-network status, firewall rules and whether the Wi-Fi uses client isolation. Test both devices on a trusted peer-access network.
Why is a transfer slow or interrupted?
Reduce distance and interference, keep both devices awake, check free space and verify that the network does not switch between isolated access points.
- Verify received filesCompare names, sizes and checksums where needed, then move important files into the intended storage or backup location.
- Remove the app and temporary rulesClose LocalSend, remove temporary firewall permissions or receive directories, and uninstall through the operating system if the app is no longer needed.
Frequently asked questions
Does LocalSend require the internet or an account?
The normal transfer uses a reachable local network and does not require an internet account or third-party server. Network isolation can still prevent discovery.
What should I check when devices are not visible?
Check local-network permissions, Windows private-network status, firewall rules and whether TCP or UDP port 53317 is blocked.
Is LocalSend suitable for public Wi-Fi?
Use a trusted private network for important files. Keep automatic receiving disabled and verify every device and request on an untrusted network.