LocalSend keeps showing “Finished With Error” after I try to send files between devices on my local network. The transfer starts but fails at the end, and I’m not sure if the problem is with permissions, firewall settings, or device compatibility. I need help troubleshooting this LocalSend file transfer error so I can complete transfers successfully.
Why LocalSend Ends With 'Finished with error'
I ran into this a few times, and the message usually showed up when the link between both devices dropped before the file was done moving. LocalSend does a bad job here. It tells you something broke, but not what broke.
From what I saw, these are the usual causes:
- The two devices are on different networks, even if the Wi-Fi name looks similar
- A VPN, firewall, or antivirus tool is stopping local traffic
- The connection hops between 2.4 GHz and 5 GHz mid-transfer
- The receiving phone or computer goes to sleep
- The file size is large enough to expose an unstable Wi-Fi link
- Android or macOS has not given LocalSend the storage or local network permissions it needs
What Fixed It for Me Most Often
The first thing I did was close LocalSend on both devices, open it again, and make sure both were on the same Wi-Fi. Guest Wi-Fi caused issues for me once. Some mesh setups do the same thing because they keep devices separated.
Other stuff worth trying:
- Turn off VPNs for a minute and test again
- Keep both devices awake until the transfer ends
- Add LocalSend as an allowed app in your firewall
- Install the newest LocalSend version on both sides
- Start with a small file, then move up if it works
If you're on Android, check file access permissions. I missed this once and kept chasing the wrong problem. On macOS, look in Privacy & Security and confirm LocalSend has local network access if macOS asked for it.
If It Still Fails or Crawls
Large transfers seem to break first when your Wi-Fi is weak. I noticed small files went through, then a big folder would die near the end. If you're moving a lot of data, a wired method tends to be less annoying.
For Android to macOS transfers, MacDroid has been more stable over USB in my use. If you want a free option, OpenMTP is another one people try.
If LocalSend fails only on one specific network, I’d look at the router next. Some routers block device-to-device traffic on the same network, which breaks apps like this even when everything else looks fine.
3 Likes
“Finished with error” at the end usually means the data copied, but LocalSend failed on the last step, writing the file, verifying it, or closing the session. I’d look there first, not only at Wi-Fi.
Try this in order:
-
Change the save folder on the receiving device.
If LocalSend writes into Downloads, Desktop, SD card, or an external drive, switch it to a simple local folder you created yourself. I’ve seen the final write fail because the target path was protected or flaky. -
Check free space on the receiver.
You want more space than the file size. For big transfers, keep 2x free if possible. Low space often shows up as an end-of-transfer error, which is annoyng. -
Avoid weird filenames.
Zip the files first if names contain emojis, long paths, special symbols, or lots of nested folders. LocalSend sometimes chokes on metadata more than the file content. -
Test one file, then one folder, then many files.
If one large file works but a folder fails, the issue is often path length or filename handling. If folders work but many small files fail, it points to session cleanup or file indexing. -
On Windows, check Controlled Folder Access.
Windows Security, Ransomware Protection, Controlled Folder Access. If it’s on, LocalSend might transfer fine and then get blocked when saving. Add LocalSend to allowed apps. -
Watch the receiver’s disk type.
External SSD, SD card, network-mounted folder, cloud-synced folder, all of those fail more often. Save local first, move later.
I slightly disagree with @mikeappsreviewer on one part. If small files always pass and large ones fail at the exact end, I’d suspect disk write or verification before blaming Wi-Fi.
If this is Android to Mac and LocalSend keeps doing this, MacDroid is worth trying for bigger moves. USB is less fussy. Not as convienent, but more stable.
One thing I’d add to what @mikeappsreviewer and @boswandelaar said: check the time/date on both devices. Seriously. If one device clock is way off, LocalSend can act weird at the very end when it validates the transfer or closes the session. Sounds dumb, but I fixed it once that way.
Also, I would not assume it’s only permissions or firewall. If the error happens right after 100%, I’d look at these extra things:
- Disable battery optimization for LocalSend on Android. Android loves killing background network tasks at the worst possible moment.
- Turn off Private Wi-Fi Address / randomized MAC temporarily on phones/tablets. Some routers handle that badly and local discovery/session stability gets messy.
- Check hostname conflicts. If two devices on the network have similar or duplicate names, LocalSend discovery can get janky.
- Avoid cloud-synced folders on the receiver like iCloud Drive, OneDrive, Google Drive desktop sync. Save to a plain local folder first.
- Router AP isolation / client isolation can be half-enabled on some access points. Weirdly, discovery may work but file handoff fails at the end.
- Try a different network band manually instead of auto switching. I actually disagree a bit with the “Wi-Fi drop” angle being the main cause every time. Sometimes the session survives fine and the OS itself kills or blocks the last write.
If this is Android to Mac and LocalSend keeps being annoying, I’d stop burning time and use MacDroid for large transfers. USB is less cute, more boring, but usually just works. That’s been way more stable for me when LocalSend gets all dramatic and says “Finished With Error” after doing 99% of the job.