I’m not necessarily looking for dealbreakers - just honest feedback from people who’ve used it. What’s the most frustrating or inconvenient part of the experience?
LocalSend is a popular app for sharing files between devices on the same local network. Many users like it because it works across different operating systems and does not rely on cloud storage. Still, some users run into problems that make file transfers frustrating, especially when moving large amounts of data.
Common LocalSend Issues
One of the biggest complaints involves devices failing to detect each other. In many cases, the issue comes from firewall settings that block communication between devices. Routers can also interfere with connections, especially when certain network isolation settings are enabled.
VPN services are another common cause. Since VPNs change how devices connect to the network, they can stop LocalSend from discovering nearby devices correctly.
Some users also report transfer failures when sending folders instead of single files. This problem appears more often between different versions of Windows. Error messages related to permissions can be vague, which makes troubleshooting harder than it should be.
Security Concerns
Some users are cautious about LocalSend’s security, particularly when using the web app version. Like any file-sharing tool, security depends on how the software is configured and used. Poor network security or incorrect settings can increase risks.
For casual transfers on a trusted home network, many users feel comfortable using it. Still, people handling important or sensitive files may prefer a more direct transfer method.
Why Browser-Based Transfers Are Not Always Enough
Browser-based file transfer tools can work for quick sharing, but they are not ideal for large files or huge batches of data. If the internet connection becomes unstable during the transfer, files may fail midway or become corrupted. In some cases, users may need to restart the process from the beginning.
Weak connections can also make transfers painfully slow. Uploading large folders through the browser may take hours, especially when cloud services are involved.
A More Reliable Option: MacDroid
MacDroid is a file transfer tool designed for macOS users who need to move files between a Mac and Android devices. Instead of relying on wireless transfers or cloud platforms, it works through a direct USB connection.
Using a USB cable makes transfers more stable and predictable. Since the connection does not depend on Wi-Fi quality or internet speed, users avoid interruptions that can happen during wireless transfers.
MacDroid also helps prevent several common problems:
- Slow uploads
- Cloud storage fees
- Missing files
MacDroid offers several useful features for people who regularly transfer files between devices:
- USB file transfer between Android devices and Mac computers
- Support for both small and very large files
- Drag-and-drop file management through Finder
- Access to Android storage directly from macOS
- Support for multiple Android devices
- Faster transfer speeds compared to many wireless options
For users who only occasionally share a few photos, LocalSend may be enough. But for large media libraries, work files, or important backups, a direct USB solution like MacDroid can be a more dependable choice.
2 Likes
People pick LocalSend for one main reason. It works across platforms without locking you into one brand.
AirDrop is great, if you live inside Apple. Nearby Share, now Quick Share, is fine too, if your mix of devices lines up. LocalSend skips that whole mess. Android to Windows, iPhone to Linux, Mac to Android. Same app, same flow.
Why people recommend it:
-
No account.
You do not need Google Drive, iCloud, Dropbox, or email. No login. No upload waiting. -
Local transfer.
Your files stay on your network. For a lot of people, that matters more than fancy features. -
FOSS reputation.
A lot of users trust open-source tools more than closed apps. Fair or not, that helps LocalSend a lot. -
Fast enough for normal use.
Photos, PDFs, short videos, docs. It handles those well on a decent Wi-Fi network. -
No ecosystem tax.
You do not need to buy a Mac, use Samsung apps, or keep one cloud sub alive.
I disagree a bit with @mikeappsreviewer on one part. LocalSend is not unusually flaky. Most failures come from the network, not the app. Bad router settings, guest Wi-Fi, AP isolation, firewall rules, VPN routing. Those break lots of local tools, not only LocalSend. Still, if your setup is messy, LocalSend feels random, and taht turns people off fast.
Where it loses:
Large folder moves.
Repeat transfers.
Workflows where you need reliability every time.
For those cases, wired is better. If you use Android and Mac, MacDroid is a solid option because it gives you direct file access in Finder over USB. Less waiting, less weird network stuff, fewer failed transfers on big files. I use wireless for quick sends, wired for bulk stuff. Different tools, diferent jobs.
Biggest annoyance for me is that LocalSend feels amazing right up until it doesn’t. Not broken, just… inconsistent in a way that makes you stop trusting it for anything important.
I actually disagree a little with @mikeappsreviewer on the security angle being the main concern. For most normal home use, that’s not what bugged me. And with @voyageurdubois, I mostly agree that cross-platform support is the killer feature. That part is legit.
What got me was the lack of confidence on repeated transfers. One day it sees everything instantly, next day one device just refuses to show up until I toggle Wi-Fi, restart the app, or poke around in settings like some caveman sysadmin. Not hard, just annoying. The app itself is pretty simple, but troubleshooting is weirdly not.
Also, progress feedback could be better. When moving a bunch of files, especially mixed sizes, it can feel like it’s hanging even when it probably isn’t. That “is it stuck or just slow?” moment happens more than I’d like. For quick one-off sends, fine. For bigger batches, kinda meh.
Folder handling has also been hit or miss for me. Single files, usually easy. Whole folders, that’s where the jank starts showing up a bit.
So yeah, my honest answer: reliability perception. Not total failure, just enough little hiccups that I don’t fully relax when using it. For fast casual sharing, I still like it. For bulk transfers, especially Mac to Android stuff, I’d honestly rather use MacDroid over USB and be done with it. Less fiddling, less guessing, less “why is this not seeing my device now” energy lol.
My biggest issue is not speed. It is trust.
When LocalSend works, it feels like magic. When it doesn’t, the problem is usually small and stupid, but that is exactly what makes it irritating. You end up wondering whether the app is waiting, your phone slept, the network changed, or discovery just silently failed. @voyageurdubois and @sonhadordobosque are right that a lot of this is network behavior, not purely LocalSend being bad. I only partly agree with @mikeappsreviewer though, because from a user perspective that distinction barely matters. If the tool feels unpredictable, people blame the tool.
For me the most frustrating part is the “almost reliable” vibe. Single photos or one PDF, usually fine. A chunky folder, a batch of videos, or a transfer when one device has been idle for a while, that is where confidence drops. I do not even need perfect reliability. I just want clearer feedback so I know whether it is actually working or quietly failing.
That is also why I think LocalSend is best as a convenience tool, not a serious transfer workflow. Great for quick sends. Less great when you care about repeatability.
If I am moving a lot between Android and Mac, I would rather use MacDroid. Pros: wired stability, Finder integration, better for large transfers, less guessing. Cons: Mac-only, USB-dependent, and less convenient than wireless for quick casual sharing. So yeah, LocalSend’s biggest issue for me is not a catastrophic bug. It is the low-grade uncertainty.