1
Install LocalSend on All Target Devices
LocalSend requires installation on every device involved in the transfer. Visit the official GitHub releases page at https://github.com/localsend/localsend/releases. Download the appropriate installer for each operating system: `.exe` for Windows, `.dmg` for macOS, `.deb` or `.AppImage` for Linux, and the `.apk` or Play Store version for Android/iOS.
For desktop systems, run the installer and grant necessary permissions. On macOS, you may need to authorize the app in System Settings > Privacy & Security > Local Network. On Android and iOS, ensure the app has permissions for 'Local Network' (Android) or 'Local Network' (iOS Settings). Crucially, ensure all devices are connected to the same Wi-Fi network. LocalSend uses mDNS (Bonjour/Avahi) for device discovery, which does not work across different subnets or guest networks with client isolation enabled.
Pro Tip
If devices fail to discover each other, check if your router has 'AP Isolation' or 'Client Isolation' enabled, as this blocks local device-to-device communication.
2
Verify Device Discovery and Connection
Launch LocalSend on all devices. You should see a list of available devices on the main screen of each app. The interface displays the device name, operating system icon, and connection status. If a device does not appear, click the 'Scan' button (usually a refresh icon) to manually trigger a network discovery.
For advanced troubleshooting, note the IP address and port shown in the 'About' or 'Settings' section. LocalSend typically listens on port 5333. If automatic discovery fails, you can manually connect by entering the IP address of the target device. This is particularly useful if you are on a complex corporate network where mDNS might be blocked. Ensure that firewalls on Windows, macOS, or Linux allow incoming connections on port 5333 for both TCP and UDP protocols.
Pro Tip
Rename your device in the settings to something recognizable (e.g., 'MacBook-Pro' vs 'Device-1') to easily identify it among multiple connected devices.
3
Transfer Files Between Devices
To send files, select the target device from the list. You can drag and drop files directly onto the LocalSend window, use the 'Select Files' button, or copy files to the clipboard and use the 'Paste' option. For sending a message, switch to the 'Message' tab.
Once files are selected, click 'Send'. The receiving device will show a notification and open the LocalSend app, displaying a preview of the incoming files. The receiver must click 'Accept' to begin the transfer. The progress bar shows the transfer speed and remaining time. Once completed, the receiver can choose the save location. Files are transferred via a secure HTTPS connection using self-signed certificates, ensuring encryption in transit without requiring manual key exchange.
Pro Tip
For large file transfers, ensure both devices are plugged in to power to prevent battery-saving modes from throttling Wi-Fi performance.
4
Configure Default Save Locations
By default, LocalSend saves incoming files to a 'LocalSend' folder within the standard Downloads directory. You can customize this in the Settings menu under 'Saving'. On Windows, this is typically `C:\Users\<User>\Downloads\LocalSend`. On macOS, it is `~/Downloads/LocalSend`.
You can set different default folders for different file types if you wish, though the standard setting applies to all. This customization helps keep your downloads folder organized. You can also configure the app to automatically accept files from trusted devices, though this is generally discouraged for public networks. For professional workflows, setting a dedicated project folder as the default save location can streamline your pipeline.
Pro Tip
On Linux, you might need to create the LocalSend folder manually in your home directory if the app fails to create it due to permission issues.
5
Use Command Line Interface (CLI) for Automation
LocalSend offers a powerful CLI tool for scripting and automation. This is ideal for developers or power users who want to integrate file sharing into their workflows. Download the CLI binary from the GitHub releases page.
To send files, use the command: `localsend send --target <device-name-or-ip> <file-path>`. For example, `localsend send --target 192.168.1.5 ~/Documents/report.pdf`. To receive files, you can listen for incoming requests. The CLI supports JSON output for easier parsing in scripts. You can also list available devices with `localsend list`. This allows you to write bash or PowerShell scripts to automatically back up files to a server or send large datasets to a workstation without opening the GUI.
Pro Tip
Use the `--alias` flag with the CLI to verify the device name matches what is expected in the GUI, avoiding connection errors due to name changes.
6
Troubleshooting Connectivity Issues
If devices cannot see each other, first verify they are on the same subnet. Check your IP addresses (e.g., 192.168.1.x) to ensure they match the network prefix. If they do, check firewall settings. On Windows, ensure 'Private Network' profile is selected for your Wi-Fi adapter, as Public networks block discovery. On macOS, verify 'Local Network' permission in System Preferences.
If automatic discovery still fails, use the manual connection feature. Enter the IP address of the target device and port 5333. If connection times out, the firewall is likely blocking the port. If you receive a certificate error, it is safe to accept it as LocalSend uses self-signed certs for local HTTPS. Remember, LocalSend does not connect to the internet; all traffic stays within your LAN.
Pro Tip
Restarting the LocalSend service on both devices often resolves transient mDNS caching issues.
7
Maintain Privacy and Security
LocalSend is designed with privacy first. It does not require an account, does not upload data to the cloud, and does not track usage. However, since it operates on a local network, be cautious when using it on public Wi-Fi (like in cafes or airports). While the transfer is encrypted, broadcasting your presence on a public network can reveal your device type and OS.
It is recommended to disable 'Auto-Discovery' when on public networks to avoid unwanted connection attempts. You can do this in the Settings > Network section. Also, ensure you delete transferred files from the LocalSend cache folder after use, as the app does not automatically delete received files. Treat LocalSend as a secure bridge for your trusted local devices, not a general-purpose cloud dropbox.
Pro Tip
Enable 'Require PIN' in settings if you are sharing sensitive documents on a shared or semi-public local network to prevent unauthorized access.