I don’t mind trying new apps, but I’d rather avoid something that becomes unreliable after a while. How dependable has LocalSend been in your experience?
LocalSend is handy, until the network starts acting up
I’ve used LocalSend for quick file moves on my home network, and when it works, it feels smooth. It’s free, open source, and it runs across Windows, macOS, Linux, Android, and iPhone, so people often treat it like an AirDrop replacement without the Apple-only lock-in.
The good part is simple. Your files stay on your local network instead of taking a pointless trip through some remote server. If your setup is clean, sending a photo batch, a PDF, or a short video is fast and painless.
Why it feels fast
LocalSend moves files over your Wi-Fi or LAN, so the transfer stays inside your network.
What I noticed from using it:
- You do not need internet access. If your internet is down but your router is still up, transfers still work.
- Speeds depend on your local hardware, not your ISP plan.
- Devices on the same network usually show up fast, sometimes in a second or two.
For small jobs, this setup makes sense. I’ve sent screenshots from my phone to my laptop faster than I could have opened a cloud drive tab.
Where it starts to break
The issue I ran into most was device discovery. Two devices would sit on the same Wi-Fi, both open, both waiting, and still not see each other. I’ve seen other people hit the same wall.
Most of the trouble tends to come from a few places:
- Firewall rules blocking traffic
- Router settings preventing device communication
- VPNs messing with local discovery
Once, my phone found the laptop, then lost it, then found it again. Same room, same router. No clean reason on screen. Stuff like this is what makes LocalSend feel great one day and annoying the next.
Transfer failures are another sore spot. There are reports of files stopping halfway through, and I’ve seen the app throw errors which did not tell me much. You end up retrying and hoping the second run sticks.
Folders are worse. On Windows, especially across different versions, permission errors pop up and the app does a poor job explaining what failed. You get a vague message, no useful path, no real fix.
The security side is not nothing
Some people are uneasy about LocalSend’s security, and I get why, mostly with the web app angle. Any tool like this leans hard on your network being set up right.
I would not call it unsafe by default. Still, I would not use it carelessly on public Wi-Fi or on some sketchy shared network. If your network is loose, your risk goes up. Pretty plain.
Browser tools are fine, up to a point
I used browser-based transfer tools too. For one file here and there, they’re okay. Once you start moving large videos, full photo folders, or a few hundred files, the cracks show fast.
The weak points are familiar:
- unstable internet kills transfers at the worst time
- long transfers drag on forever on weak connections
- interrupted jobs sometimes leave missing or broken files
This gets old fast if you move media often.
Why I ended up using MacDroid for bigger jobs
For Android-to-Mac transfers, I’ve had a steadier time with MacDroid.
It takes the wireless part out of the equation. You connect the Android device to the Mac with a USB cable, and the whole thing feels less fragile. No wondering if the phone will disappear from the device list halfway through. No retry loop because Wi-Fi got weird for ten seconds.
What I liked most is how Android storage shows up in Finder. From there, you move files around the same way you would with an external drive. Copy, delete, sort folders, check an SD card, done.
I found it more useful for:
- large video files
- full photo libraries
- batches with hundreds of files
- SD card access
- managing Android storage from the Mac without extra steps
A wired setup also cuts out a few common headaches:
- slow uploads
- paying for cloud storage space you did not need
- losing files after a transfer dies halfway
For quick wireless sharing, LocalSend is still nice to keep around. For large transfers, or anything you do not want to redo twice, I’d pick a wired option. That part, at least for me, has been less fussy.
3 Likes
Yes, what you’re seeing is normal with LocalSend over time, but I would not call it a sign the app is bad. I’d call it sensitive.
LocalSend depends hard on local network behavior. If anything changed, router firmware, AP band steering, firewall profile, VPN, private relay, guest isolation, battery optimization on mobile, it starts feeling flaky. The app itself often stays the same while your network enviroment drifts.
I disagree a bit with @mikeappsreviewer on one point. I don’t think LocalSend gets worse by age alone. It gets worse when your setup gets less predictable. On a plain home LAN, it tends to stay stable for months.
What to check:
- Keep both devices on the same band if possible, 5 GHz or 2.4 GHz.
- Disable VPN on both ends.
- Set Wi-Fi network profile to Private on Windows.
- Exempt LocalSend from firewall and battery saver.
- Turn off guest Wi-Fi isolation and client isolation in router settings.
- Test with fixed devices first, laptop to laptop, then phone.
If detection fails once a week, I’d still call that common. If sends fail daily, something in your network is off.
For Mac and Android, MacDroid is worth a look if you want stable large transfers. Wired beats chasing random Wi-Fi issuse every time.
I’d split the difference between @mikeappsreviewer and @mike34.
LocalSend has felt stable enough for me as a ‘keep it installed’ app, but not stable enough that I’d trust it for every important transfer without thinking about it. For quick sends, docs, pics, random files, it’s usually solid. The part that feels inconsistent over time is not always the app itself, it’s that local networking is annoyingly fragile in ways most apps can’t fully hide.
Where I kinda disagree with the doomier takes is this: LocalSend doesn’t usually decay like some abandoned app that gets worse and worse. It’s more that its reliability ceiling is tied to whatever device update, OS permission change, or weird router behavior pops up later. So month 1 can feel perfect, month 4 can feel janky, then month 5 is fine again. That’s been my expereince.
What I like:
- very fast when both devices cooperate
- no cloud middleman
- simple UI
- great for one-off transfers
What gets old:
- discovery can randomly stall
- backgrounding the app on mobile can mess things up
- bigger transfers are where I stop fully trusting it
- error feedback is kinda meh
So, dependable? Moderately. I’d call it reliable-ish, not bulletproof.
If you mostly want casual wireless sharing, LocalSend is worth trying. If your real concern is long-term consistency for larger Android-to-Mac file transfers, I’d honestly use MacDroid for that side of things. Wired transfer is just less drama, less guessing, less “why did this fail at 92%?” stuff. LocalSend is nice. MacDroid is steadier for serious jobs.
I’m closer to @techchizkid on this: LocalSend usually does not “age badly,” it just exposes every little change in your network and OS permissions. But I disagree slightly with @mikeappsreviewer on large transfers being automatically a bad fit. If your Wi-Fi is solid, LocalSend can stay dependable for months. Mine has been fine for everyday sharing, then suddenly weird after a phone OS update, then fine again after permissions got reset.
That pattern is why I’d call it conditionally reliable, not unreliable.
What makes it feel stable long term:
- active app, not abandonware
- simple job, local file transfer only
- no account system or cloud dependency to break later
What hurts consistency:
- mobile background limits
- OS updates quietly changing local network access
- mixed-device setups being less predictable than same-platform transfers
- weak error reporting when something does fail
One thing I’d add that the others didn’t stress enough: LocalSend is best treated like a convenience tool, not your “I need this to work perfectly every single time” pipeline. For casual sends, yes, dependable enough. For repeated big Android-to-Mac moves, I’d still lean wired.
That’s where MacDroid makes more sense.
MacDroid pros:
- steadier for large transfers
- Finder integration is nicer for bulk file management
- less affected by random Wi-Fi behavior
- good for folder-heavy transfers and SD card access
MacDroid cons:
- not as instant as wireless sharing
- needs a cable
- mainly useful for Android and Mac, so less universal than LocalSend
- paid features may matter depending on what you need
So my short version: LocalSend is stable enough to keep installed, but not stable enough that I’d stop having a backup option. @mike34 and @techchizkid are right that environment matters a lot. I just think if you want long-term consistency, wired tools like MacDroid usually age better because there are fewer moving parts.