Localsend Not Working: Quick Fixes to Resolve Connection Issues

Local file sharing between devices should feel effortless. That's the promise of Localsend, a popular open-source tool that transfers files, folders, text, and links directly over your local Wi-Fi network—no internet required. But when Localsend stops working, the frustration hits fast. You're left staring at "no devices found," a spinning connection icon, or a baffling "connection refused" error.

Across Windows, macOS, Android, iOS, and Linux, users encounter the same core problems: devices that won't discover each other, transfers that stall, and errors that appear to come from nowhere. The good news? Nearly every Localsend failure has a clear, repeatable fix.

This guide walks you through every angle—from basic checks you can do in thirty seconds to advanced router and firewall configurations that solve persistent issues. You'll learn why Localsend breaks, how to fix it on any device, and how to prevent problems in the future. Let's get your file transfers working again.

A typical Localsend discovery screen showing available devices on the same Wi-Fi network.

How Localsend Connects Devices

Localsend operates differently from cloud-based services like Google Drive or Dropbox. Instead of uploading files to a remote server, it creates a direct peer-to-peer connection between devices on the same local network. Here's what happens under the hood:

• Discovery phase: Your device broadcasts a message across the local network using multicast or broadcast packets. Other Localsend instances listening on the same network respond with their availability.
• Connection phase: Once discovered, devices establish a direct encrypted channel using a custom protocol over a specific port (default 53317).
• Transfer phase: Files move directly from sender to receiver with encryption, never touching an external server.

Because this process relies entirely on your local network infrastructure, even small changes—a firewall update, a router setting toggle, a permission change—can break everything. Understanding this dependency is the first step toward reliable troubleshooting.

Common Reasons Localsend Stops Working

Before diving into fixes, it helps to know what typically goes wrong. These are the most frequently reported causes:

• Network mismatch: Devices on different Wi-Fi networks, guest networks, or different frequency bands (2.4 GHz vs 5 GHz)
• Firewall or antivirus blocks: Security software silently preventing Localsend from sending or receiving data
• Outdated app versions: Protocol mismatches between old and new installations
• Mobile background restrictions: Battery optimizers killing the app when it's not in the foreground
• Missing OS permissions: Operating systems withholding network or file access rights
• Incorrect app settings: Discoverability turned off, wrong port configured, or manual IP entry errors
• Router isolation features: AP isolation, client isolation, or guest network isolation blocking device-to-device traffic
• VPN or proxy interference: Network traffic rerouted away from the local subnet
• IP address conflicts: Two devices claiming the same IP address, causing confusion

Basic Troubleshooting Steps

Start here. These simple checks resolve the majority of Localsend failures.

Confirm Both Devices Are on the Same Wi-Fi Network

This sounds obvious, but it's the most common mistake. Go into Wi-Fi settings on each device and verify the exact network name (SSID). Pay close attention to:

• Guest networks that have similar names to your main network
• Networks with "5G" or "2.4G" suffixes that split frequency bands
• Different router configurations on mesh or multi-access-point setups

If one device is on a guest network, switch it to the main network. Many routers block guest devices from communicating with each other.

Update Localsend on Every Device

Mismatched versions cause protocol errors. Visit the official Localsend website or your device's app store and install the latest version on every device you use. After updating, restart the app completely—don't just leave it in the background.

If you're on Linux using a package manager like Homebrew or apt, update there as well. Package manager releases sometimes lag behind the app store versions.

Restart Everything

A full restart clears temporary glitches that can block local network communication:

1. Close Localsend on all devices
2. Restart your Wi-Fi router (wait 60 seconds for it to fully reboot)
3. Restart both devices (full power down, not just sleep mode)
4. Open Localsend and test the connection

A router reboot is especially effective if you have many devices connected or if your network has been running for weeks without a restart.

Turn Off VPNs and Proxies

VPNs and proxy services route your traffic through external servers, which breaks local discovery and direct connections. Temporarily disable any VPN or proxy on both devices. Some VPNs include a "local network bypass" setting—if you must keep the VPN active, enable that option.

Disable Airplane Mode and Battery Savers

Airplane mode obviously disables Wi-Fi. But aggressive battery-saving modes can also interfere by restricting background network activity. On Android, look for "Adaptive Battery" or "Battery Optimization" and temporarily disable it for Localsend. On iOS, check that "Background App Refresh" is enabled for the app.

Advanced Troubleshooting for Persistent Connection Issues

If basic steps don't work, these deeper fixes address the root causes of stubborn Localsend failures.

Firewall and Security Software Configuration

Firewalls are the number one culprit for unexplained Localsend failures. They can block the app even if everything else is configured correctly.

Windows Defender Firewall

1. Type "Windows Defender Firewall" in the Start menu and open it
2. Click "Allow an app or feature through Windows Defender Firewall"
3. Find Localsend in the list
4. Ensure checkboxes for both Private and Public networks are checked
5. If Localsend isn't listed, click "Allow another app," browse to the Localsend executable, and add it

A common trap: major Windows updates can reset these exceptions. If Localsend worked before but stopped after an update, check this setting first.

macOS Firewall

1. Open System Settings → Network → Firewall
2. Click "Options"
3. Confirm Localsend is listed and set to "Allow incoming connections"
4. If you see "Block incoming connections," change it to "Allow"

macOS may prompt you the first time Localsend tries to connect. If you accidentally clicked "Deny," you must manually change the setting—the system won't ask again.

Third-Party Antivirus

Temporarily disable your antivirus software (not just the firewall component). If Localsend starts working, add it as an exception in your antivirus settings. Some security suites have "network protection" features that block even allowed apps after updates.

Operating System Permissions

Modern mobile operating systems require explicit permission for apps to access the network and local devices.

Android (Version 10 and Above)

Navigate to Settings → Apps → Localsend → Permissions and enable:

• Nearby Devices (required for discovery)
• Files and Media (required for sending/receiving files)
• Wi-Fi permissions
• Allow background activity (may be in "Battery" or "App info" settings)

On Android 13 and later, you need to grant access to each media type separately (photos, videos, audio). Denying any one can cause partial failures.

iOS (Version 14 and Above)

Go to Settings → Localsend and enable:

• Local Network (required for device discovery)
• Files and Folders (required for accessing stored files)

If you ever denied these permissions, iOS won't prompt again. You must revisit Settings to change them manually.

Background Activity and Battery Optimization

Smartphones aggressively kill background apps to save battery. This is a frequent cause of Localsend failures during transfers.

On Android: Search for "Battery Optimization" in settings, find Localsend, and set it to "Not optimized." On devices from OnePlus, Xiaomi, or Samsung, also check for "Deep Sleep" or "App Hibernation" features and exclude Localsend.

On iOS: Enable "Background App Refresh" for Localsend in Settings → General → Background App Refresh.

For large transfers, keep the app open and the screen unlocked. Some devices will still kill the app even after you've disabled optimization if RAM runs low.

App Settings: Discoverability and Port

Open Localsend settings on both devices and verify:

• Discoverability: Must be ON for automatic detection
• Port: Default is 53317. Both devices must use the same port. If your network blocks the default, try a different port like 53318 or 54321
• Save Path: Ensure the destination folder exists and is writable

Manual Connection by IP Address

When automatic discovery fails entirely, you can bypass it by connecting directly:

1. On Device A, note its IP address. You can find this in Localsend's main screen or in Wi-Fi settings under "Advanced" or "Network Details"
2. On Device B, open Localsend and tap "Add device manually"
3. Enter Device A's IP address and port
4. Device B should now appear in Device A's device list

This method bypasses router discovery issues entirely and works even on networks that block multicast traffic.

Router Settings That Block Local Communication

Log into your router's admin panel (typically at 192.168.0.1, 192.168.1.1, or 10.0.0.1) and look for these settings:

• AP Isolation or Client Isolation: Turn OFF
• Guest Network Isolation: Turn OFF (or move devices to the main network)
• Multicast or Bonjour forwarding: Enable if available
• WMM (Wi-Fi Multimedia): Some routers restrict device-to-device traffic under this setting; disable it temporarily to test

If you can't find these settings, search for your router model plus "device isolation" online for specific instructions.

Multiple Network Interfaces

If your device has both Wi-Fi and Ethernet active, or virtual adapters from VPNs or virtualization software, Localsend may advertise itself on the wrong interface.

Windows: Open Control Panel → Network and Sharing Center → Change adapter settings. Right-click and disable any adapters other than your main Wi-Fi connection.

macOS: Go to System Settings → Network and disable any unused interfaces.

After disabling extra interfaces, restart Localsend and test.

Device-Specific Problems and Solutions

Each platform has unique quirks that can trip up Localsend users.

Windows

• Network profile type: If your Wi-Fi is set to "Public," change it to "Private" in Settings → Network & Internet → Wi-Fi → your network name. Public networks restrict device discovery.
• Admin rights: Some Windows configurations require running Localsend as Administrator. Right-click the app and select "Run as administrator."
• Company-managed PCs: Group policies may restrict network access. Contact your IT department for help.

macOS

• Gatekeeper bypass: If you downloaded Localsend outside the App Store, right-click the app and choose "Open" on first launch to bypass Gatekeeper restrictions.
• Energy Saver: Go to System Settings → Energy and enable "Prevent computer from sleeping automatically when the display is off." Network activity can pause during sleep.
• Post-update resets: macOS updates frequently reset firewall permissions. Always recheck after updating.

Android

• Manufacturer-specific battery settings: Samsung, OnePlus, Xiaomi, and other brands have aggressive background app management. Search your settings for "Auto-launch," "App Lock," or "Smart Manager" and exclude Localsend.
• Dual SIM phones: Disabling the second SIM can sometimes resolve network confusion.
• Wi-Fi data switching: Some phones automatically switch to mobile data when Wi-Fi is weak. Lock Wi-Fi by disabling "Switch to mobile data" in Wi-Fi settings.

iOS

• File type restrictions: iOS limits which file types can be shared directly. If transfers fail for specific file formats, try compressing them into a ZIP archive first.
• Screen Time restrictions: Parental controls can block network access. Check Settings → Screen Time → Content & Privacy Restrictions.
• Keep app in foreground: iOS restricts background network activity heavily. For large files, keep Localsend open and the screen active.

Linux

• UFW or firewalld: Run sudo ufw allow 53317 or add the port in firewalld to allow Localsend traffic.
• Snap or Flatpak sandboxing: These package formats can restrict network access. If using Snap, try sudo snap connect localsend:network-control to grant broader permissions.
• SELinux or AppArmor: Additional security modules may block network activity. Check logs with ausearch -m avc for denials.

Preventing Future Localsend Problems

A few proactive steps keep Localsend running reliably:

• Update app and OS together: After any system update, open Localsend and perform a test transfer immediately. This catches permission resets early.
• Exclude from battery optimizers: Do this once and forget it. On Android, also check after major OS version upgrades.
• Use private Wi-Fi: Avoid guest networks, hotel Wi-Fi, and public hotspots that restrict local communication.
• Document custom settings: If you changed ports or use manual IP connections, keep a note. You'll need it after reinstalling the app.
• Router firmware updates: Some router updates reset isolation settings. If Localsend stops working after a router update, check your router's isolation settings.

When to Use Alternative File Transfer Methods

If Localsend still won't work after all these steps—or if you're on a restricted network—these alternatives can help:

Localsend remains the best cross-platform, private, open-source option when your network supports it. Alternatives fill the gap when it doesn't.

Frequently Asked Questions

What should I do if Localsend can't find other devices?

First, verify both devices are on the same Wi-Fi network and that Discoverability is ON in the app settings. If automatic discovery fails, try connecting manually using the other device's IP address and port. Also check your router for AP isolation settings and disable any VPNs on both devices.

Why does Localsend show "connection refused" or "timed out"?

This usually means a firewall is blocking the connection, or the target device isn't listening on the correct port. Allow Localsend through your firewall (both Private and Public profiles on Windows). Verify both devices use the same port (default 53317). Restart both devices and try again.

Can I use Localsend over mobile data or without Wi-Fi?

No. Localsend requires both devices to be on the same local Wi-Fi network. It does not work over cellular data, mobile hotspots with device isolation, or Bluetooth. For offline transfers, use a USB cable or Bluetooth as alternatives.

Is Localsend safe and private to use?

Yes. Localsend transfers files only over your local network with end-to-end encryption. No data passes through external servers. The app is fully open-source, meaning anyone can audit the code for security vulnerabilities. For more details, visit the official Localsend GitHub repository.

How do I fix Localsend on a guest or restricted Wi-Fi network?

Many guest networks, hotel Wi-Fi, and public hotspots enable AP isolation, which blocks device-to-device communication. If possible, switch to a personal or home network. As a workaround, create a mobile hotspot from one device and connect both devices to that hotspot. Localsend will work as long as the hotspot doesn't enable client isolation (most modern phones do not by default).

Conclusion

Localsend fails for predictable reasons—wrong network, blocked firewall, missing permissions, or router isolation settings. The fix for each is straightforward once you know where to look.

Start with the basics: confirm both devices are on the same Wi-Fi, update the app, restart everything. If the problem persists, check your firewall settings first—that's the most common hidden cause. On mobile, battery optimizations and OS permissions are the next suspects. For stubborn cases, switch to manual IP connection or dive into your router's configuration.

Your next step: Open Localsend on two devices right now and perform a test transfer. If it works, you're set. If not, walk through the checklist above, starting with the network check. Most problems solve within five minutes when you know what to look for.