Every app has some drawbacks, so I’m wondering what users usually complain about when it comes to LocalSend. Anything that becomes frustrating after regular use?
I used LocalSend for a while because it keeps file sharing on your own network and skips cloud accounts. For quick transfers, it felt clean and low-friction. Still, after enough use, a few weak spots showed up, and they matter if you plan to depend on it.
Connectivity and Firewall Issues
The issue I saw most often was simple and annoying. Devices would sit there and fail to detect each other, or a transfer would start and then stall out. Plenty of people report the same thing here, failing to complete transfers.
In a lot of cases, the culprit is your firewall. I ran into this on a Windows machine where the app looked fine on the surface, but the network rules were blocking it. Routers do this too if client isolation or stricter local traffic settings are turned on. VPNs are another common mess. I had one enabled once and LocalSend stopped seeing anything on the LAN. Turned the VPN off, retried, and it worked.
If your setup is refusing to connect, the first things I would check are your firewall rules, router settings, and whether a VPN is hijacking local discovery.
File Transfer Limitations
Single files usually move over without much drama. Folders are where it gets shakier. I kept seeing reports like users report error messages tied to missing permissions, especially when the transfer involved different Windows versions.
The rough part is the wording of the errors. You get a complaint, but not much help. So you end up checking folder access, app permissions, destination paths, and OS-level restrictions one by one. If you're moving a folder tree with mixed file types and nested directories, this gets old fast.
Security
I would not treat a local network tool as harmless by default. LocalSend is no exception. Some people have pointed at the web version as an area worth reviewing, see some users raise concerns.
If you use it on a trusted home network, the risk profile feels different than using it in a shared office, school, or lab. I would still look through permissions, confirm what is exposed on the network, and avoid being sloppy with sensitive files. Local traffic is still traffic.
When LocalSend Stops Being the Easy Option
For a couple photos or a PDF, browser-based or local network sharing is fine. Once you get into large batches, bigger video files, or a ton of folders, the weak points show up. A flaky wireless connection slows everything down. A dropped transfer wastes time. In the worst cases, you get incomplete copies and need to verify what made it over. I had one transfer drag way longer than expected because the signal dipped in and out. It was a dumb waste of time.
That is where a cable starts making more sense. MacDroid takes this route, with support for both USB and Wi-Fi. If you want the steadier path, USB is the one I would pick first. If you need less clutter on your desk, Wi-Fi is still there.
It supports photos, video, music, documents, and full folders. It also works with internal phone storage and SD cards when your device allows access that way.
One part I liked is direct file access through Finder. You open the item on your Mac and edit it without copying it over first. On a crowded drive, that saves space and cuts one extra step.
Using a USB connection with MacDroid avoids a few problems I kept running into with network transfers:
- Slow transfers when Wi-Fi strength drops
- Paying for cloud storage space you did not need
- Incomplete transfers after a disconnect
If you move files between Android and Mac often, and you are tired of troubleshooting local network weirdness, a wired option like MacDroid makes more sense to me than hoping Wi-Fi behaves that day.
1 Like
Yeah. A few limits get annoying after regular use.
First, LocalSend depends too much on both devices behaving nicely at the same time. If one phone sleeps, changes Wi-Fi bands, or puts the app in battery saver mode, the transfer can hang. This is common on Samsung, Xiaomi, and some Oppo phones. Android background limits are a pain.
Second, there is no great resume flow. If a big video fails at 85 percent, you often restart from zero. For small files, who cares. For 20 GB of clips, it gets old fast.
Third, duplicate handling is weak. If you send the same folder twice, cleanup gets messy. You spend time checking what copied and what overwrote. LocalSend feels best for quick one-off sends, not repeat file management.
I slightly disagree with @mikeappsreviewer on one point. Security is not the thing most users complain about day to day. Reliability and friction are. People notice failed transfers first.
Also, there is no real deep library sync or mounted storage workflow. It sends files. That’s it. If your goal is ongoing Android to Mac file access, MacDroid is less annoying because you browse phone storage in Finder and move stuff in a more normal way. Less poking at both screens, fewer retries. Not perfct, but better for heavy use.
So yeah, LocalSend is nice. Then you use it for a few months and the small cracks start showing.
Biggest long-term annoyance for me is that LocalSend feels awesome right up until you start using it like a real workflow instead of a quick share tool.
@caminantenocturno is right about repeat use exposing the cracks, but I’d push it a bit further: the UI is almost too simple. Nice at first, kinda limiting later. There’s not much history, not much control, not much visibility into what exactly happened when something goes wrong. You get “send file” and “hope the network gods are in a decent mood today.”
A few things that get old fast:
- no real file management feel
- weak feedback during failed transfers
- not ideal for giant batches
- not great if you need predictable, repeatable transfers
- can be annoying across mixed devices/OS behavior
I slightly disagree with @mikeappsreviewer on the security angle being a major everyday complaint. Most normal users are not sitting there auditing LAN exposure. They’re just annoyed that a transfer stalled for no obvious reason lol.
If you only send photos, PDFs, random clips, LocalSend is fine. Pretty great, even. If you move folders a lot or want Android-to-Mac access that feels less temporary, that’s where something like MacDroid starts making more sense. It’s less “send and pray,” more direct file access. Diffrent tool, but for heavier use it can feel way less fussy.
My take is the most annoying LocalSend limitation is not speed, it is state. It does not really remember, track, or organize transfers in a way that helps once sharing becomes routine.
So while @caminantenocturno, @espritlibre, and @mikeappsreviewer are right about stalls, discovery issues, and failed big transfers, I’d add these:
- weak transfer history, so auditing what already moved is annoying
- limited conflict handling, especially with similarly named files
- no “workflow” layer like queue management or smarter batching
- too dependent on both devices staying awake and foreground-friendly
- not great for people who want ongoing access, not one-time sending
I slightly disagree with the idea that it becomes bad after a few months. For many people it stays great if they only use it as a drop tool. The frustration starts when expectations shift toward file management.
That is where MacDroid is worth considering on Mac. Pros: Finder integration, direct Android storage access, USB option for stability, better for repeated drag-and-drop work. Cons: Mac-only, not as instant for device-to-device sharing, and some features depend on the connection mode and device behavior.
So yeah, LocalSend is excellent at “send this now.” Less excellent at “this is my regular system.”