LocalSend can only discover devices that are running the app, reachable on the same non-guest Wi‑Fi or wired LAN, and allowed through the operating system and router. Start LocalSend on both devices, leave any guest network, and check isolation settings. On Windows, use a Private network profile and allow LocalSend’s incoming TCP and UDP traffic on port 53317 plus its outgoing traffic. On macOS and iOS, grant Local Network permission. Temporarily disconnect or configure VPN and security software to allow LAN traffic. If discovery still fails, send to the receiver’s IP address manually; a successful manual transfer proves that discovery, rather than file transfer, is the failing layer.
What LocalSend discovery actually requires
LocalSend is free, open-source software for sending files and messages directly over a local network. It does not need an account or cloud storage. Each device must advertise and receive traffic locally, so a device can have working internet access and still be invisible to another device.
As an Amazon Associate I earn from qualifying purchases.
Both devices must be running LocalSend
Open LocalSend on the sender and the receiver before testing. A phone that is asleep, has the app force-closed, or has LocalSend stopped in the background cannot reliably appear in the peer list. Keep the receiver’s app open while you refresh the sender’s device list.
They must share the same reachable LAN segment
Use the same ordinary Wi‑Fi network or the same wired LAN. A Wi‑Fi name alone is not proof of reachability: guest SSIDs, mesh settings, and enterprise networks can separate clients while allowing all of them to browse the internet. A wired computer and a wireless phone can work together when the router bridges those networks; they will not work when the router deliberately isolates them.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Discovery and transfer are different layers
Automatic discovery is the device-list mechanism. A transfer also needs a working route, an allowed port, and compatible LocalSend settings. Therefore, an empty device list does not necessarily mean LocalSend cannot transfer files. Testing a direct IP address later separates a discovery problem from a broader connectivity or firewall problem.
Follow this troubleshooting sequence
Work from the least disruptive checks to the changes that affect a whole network. After each step, close and reopen LocalSend on both devices and check whether the receiver appears.
1. Confirm the network and app state
- Open LocalSend on both the sender and receiver.
- Confirm both are connected to the same non-guest Wi‑Fi network, or to a wired and wireless LAN that the router bridges together.
- Turn off cellular data temporarily on a phone so you can see which Wi‑Fi connection it is using.
- Move both devices to the same ordinary SSID if one is on a guest SSID, an isolated IoT SSID, or a separate access point.
- Retry discovery with both screens awake. If the receiver appears now, no firewall change is required.
Do not use internet connectivity as the test. Being able to open a website only shows that each device can reach the router and the internet; it does not show that the two clients can reach one another.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
2. Remove router isolation
Log in to the router or access-point administration page and look for settings named AP isolation, client isolation, wireless isolation, or guest-network separation. These features intentionally block device-to-device traffic. Disable the relevant isolation for the network on which the two devices should communicate, or place both devices on a trusted SSID without isolation.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
- Guest Wi‑Fi: Guest networks commonly permit internet access while preventing guests from reaching LAN devices. Move both devices to the main network rather than weakening guest security for every guest.
- Multiple access points: A mesh or extender can place clients in separate isolation zones. Check the isolation setting on the access point serving each device, not only on the main router.
- Security trade-off: Disabling isolation increases local reachability for devices on that SSID. Use it only on a network you trust, and keep guest separation for visitors and untrusted hardware.
Router changes are broader and less reversible than a one-device permission change. If only two trusted devices need to communicate, first try moving them to the same non-guest network; change router-wide isolation only when that is the actual cause.
3. Set Windows to a Private network and allow LocalSend
Windows applies stricter firewall behavior to a Public network profile. Set the active connection to Private before changing individual rules.
- Open Settings and go to Network & internet.
- Select Wi‑Fi or Ethernet, then open the connected network’s properties.
- Under Network profile type, choose Private.
- Open Windows Security > Firewall & network protection > Allow an app through firewall.
- Find LocalSend and allow it on the Private network. If the app is not listed, use the advanced firewall console to create rules for the LocalSend program.
The LocalSend project README documents incoming TCP and UDP on port 53317 and allowance for outgoing traffic. In Windows Defender Firewall with Advanced Security, inspect Inbound Rules for LocalSend or rules covering TCP 53317 and UDP 53317, and inspect Outbound Rules to ensure LocalSend is not blocked. A rule that allows only incoming traffic can still fail if an antivirus suite or a custom outbound policy blocks the app’s replies.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not turn off the entire Windows firewall as a permanent fix. A narrowly scoped Private-profile rule is easier to audit and safer to reverse. If your computer is managed by an organization, policy may prevent you from changing these rules; ask the administrator to permit LocalSend’s local traffic instead.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
4. Grant Local Network permission on macOS and iOS
Apple operating systems can block local discovery until the app has Local Network permission. Internet access and Bluetooth permission do not substitute for this setting.
- macOS: Open System Settings > Privacy & Security > Local Network and enable LocalSend.
- iPhone or iPad: Open Settings > Privacy & Security > Local Network and enable LocalSend.
If LocalSend is already enabled but devices remain absent, switch the permission off, reopen the settings page, switch it on again, and relaunch LocalSend. Test with the receiver’s app open. A permission change affects only that Apple device, so repeat it on every Mac, iPhone, or iPad that should participate.
5. Test VPNs and third-party security software
A VPN can route or filter private-network traffic. Many VPN clients have an option named allow LAN traffic, local network sharing, or similar. Enable that option, or disconnect the VPN briefly and retry LocalSend. If discovery starts working only when the VPN is disconnected, keep the VPN and add a LAN-allow rule if the client supports one.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Antivirus and security suites may install their own firewall on top of Windows, macOS, or Linux rules. Check their application-control and network-protection pages for LocalSend and allow trusted local connections. A system firewall entry that looks correct can be overridden by a third-party policy, so compare results with that protection paused only long enough to diagnose the problem. Re-enable it immediately after the test.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
6. Check hotspot, port, encryption, and subnet conditions
Phone hotspots often change the network after the hotspot is enabled. Turn on the hotspot first, connect both devices, then restart LocalSend on both. If the hotspot has a setting that prevents clients from communicating with one another, LocalSend will not discover peers even though both devices have internet access.
Compare LocalSend’s connection settings on the two devices if one still cannot see the other. In particular, check the configured listening port and encryption-related options. The documented LocalSend port is 53317; a custom port must be allowed by the firewall and reachable on the receiver. Do not assume that changing a port on only one device will help.
LocalSend issue #527 warns that a subnet larger than /24 can prevent discovery. If your network uses a larger subnet, such as /23, discovery may fail even when the addresses look similar. This is a network-design limitation to discuss with whoever manages the router; manual IP sending is the practical workaround when you cannot redesign the subnet.
7. Use manual IP sending
When automatic discovery remains unavailable, send directly to the receiver’s local IP address. This bypasses the discovery layer but still requires the route, port, and firewall to work.
- Find the receiver’s private LAN address in its network settings. Use the address assigned by the same Wi‑Fi or wired network, not a public internet address.
- In LocalSend, choose Manual sending or the manual-IP option in your version.
- Enter the receiver’s IP address. If LocalSend asks for a port, use the receiver’s configured LocalSend port; the project documents 53317 for incoming TCP and UDP traffic.
- Send a small test file or message while the receiver keeps LocalSend open.
- If the transfer succeeds, save that receiver as a favorite so LocalSend can probe it directly in the future.
A successful manual transfer is strong evidence that the network path and transfer service work and that automatic discovery is the failing layer. If manual sending also fails, return to the Windows, Apple, VPN, router-isolation, port, and subnet checks rather than repeatedly restarting the app.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use the symptom to choose the next check
| What you observe | Most likely layer | Next action |
|---|---|---|
| Neither device sees any peer | Network placement, router isolation, or app state | Open LocalSend on both, leave guest Wi‑Fi, and inspect AP/client isolation. |
| Windows sees nothing, but an Apple device works on the same LAN | Windows profile or firewall | Set the active Windows network to Private and allow LocalSend’s TCP/UDP 53317 plus outgoing traffic. |
| Mac or iPhone cannot see peers, while another platform can | Apple Local Network permission | Enable LocalSend under Privacy & Security > Local Network and relaunch it. |
| Discovery works only when a VPN is disconnected | VPN route or LAN filter | Enable the VPN’s allow-LAN option or create an exception for local traffic. |
| Manual IP works but the device never appears automatically | Discovery layer, subnet, or broadcast filtering | Keep the device as a favorite and investigate isolation, subnet size, and security filtering. |
| Manual IP fails as well | Reachability, firewall, port, or incompatible settings | Check the receiver’s IP, LocalSend port, TCP/UDP rules, outgoing policy, and encryption-related settings. |
| It worked on home Wi‑Fi but not on a hotspot | Hotspot client isolation or stale app state | Activate the hotspot first, reconnect both devices, restart LocalSend, and inspect hotspot isolation. |
Why LocalSend can fail even when the settings look right
Local network names do not define reachability
Two devices can display addresses from what appears to be the same range while an access point silently blocks client-to-client packets. Conversely, a wired and wireless device can communicate normally when the router bridges them. Treat the router’s isolation policy and actual reachability as the deciding factors, not the SSID label alone.
Discovery is intentionally imperfect on complex networks
The project issue tracker notes that computer networks are complex and that an offline discovery algorithm cannot work in every environment. Firewalls, VPN routes, segmented subnets, and filtered wireless networks can all prevent announcements from reaching peers. That is why the manual-IP test is valuable: it gives you a deterministic path to distinguish discovery failure from a complete inability to connect.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsPort and encryption mismatches matter after discovery
If a peer appears and then a transfer fails, focus on the receiver’s listening port, firewall rules, and encryption-related settings rather than the device-list mechanism. Both sides must be able to reach the receiver on its configured port, and a security product must not terminate the connection. Compare settings before making changes, and change one variable at a time so you can identify the cause.
Security guidance while troubleshooting
- Use a trusted LAN: LocalSend is designed for local-network sharing. Avoid sending sensitive files from an untrusted public or hotel network.
- Keep HTTPS enabled: The project README states that transfers use HTTPS and that each device generates its own TLS certificate.
- Do not disable protection globally: Prefer a Private-profile app rule, a Local Network permission, or an allow-LAN VPN setting over turning off a firewall.
- Verify the recipient: Before accepting a transfer, confirm the displayed device is the intended computer or phone, especially on a shared network.
- Undo temporary tests: Reconnect the VPN and re-enable any security control paused for diagnosis once the test is complete.
Because LocalSend does not require cloud infrastructure or an account, a discovery failure is normally a reachability, permission, or filtering problem—not evidence that you need to register for a service.
Confirm the fix and make it durable
- Close LocalSend on both devices and reopen it after the network or permission change.
- Verify the devices are still on the intended non-guest SSID or bridged wired/Wi‑Fi LAN.
- Send a small test item in each direction. One-way operation points to a rule or permission on the device that cannot receive.
- If discovery is still absent, perform a manual-IP transfer and record whether it succeeds.
- For a successful manual transfer, save the receiver as a favorite and document its local address if the network uses stable addresses.
- Review any temporary VPN or firewall exceptions and retain only the narrow rules needed for trusted local sharing.
When these checks are complete, you have isolated the problem to one of three places: the network path, the device’s filtering and privacy permissions, or LocalSend’s discovery mechanism. The manual-IP result tells you which branch deserves further work instead of sending you through the same discovery steps repeatedly.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
