macOS Error 50: The Finder Copy Fix That Actually Works

The Most Common Cause: File Permissions on the Destination

I know this error is infuriating—you drag a folder, it copies halfway, then bam, error 50. The #1 culprit is the destination folder or drive lacking proper permissions. This happens a lot when copying to an external drive formatted for Windows (exFAT) or a network share.

The fix is dead simple: adjust the permissions on the destination.

1. Right-click the destination folder or drive in Finder.
2. Select Get Info.
3. At the bottom, expand Sharing & Permissions.
4. If the lock icon is closed, click it and enter your admin password.
5. Set the everyone privilege to Read & Write.

Still stuck? If you're copying to an external drive, check its format. If it's NTFS, macOS can't write natively. You'd think Apple would've made this clearer, but here we are. Download a free NTFS driver like Mounty or reformat the drive to exFAT—just back up first.

Second Cause: Finder's Cache Is Corrupted

Sometimes permissions are fine, but Finder trips over its own shoelaces. A corrupted cache can cause error 50 on random files, especially after a big update like macOS Sonoma 14.4. You don't need to restart your entire Mac—just kill the Finder cache.

Here's the command that's saved my bacon more than once:

sudo find /private/var/folders -name "com.apple.finder" -exec rm -rf {} \; && killall Finder

This nukes Finder's temporary cache. It'll rebuild automatically. Run it in Terminal (yes, you need admin rights), then try your copy again. If that doesn't work, also clear the system cache—but only if you're comfortable in Terminal.

I've seen this fix work after hours of troubleshooting, so don't skip it.

Third Cause: Disk Errors or Full Storage

No one wants to hear "your disk is failing," but if the first two fixes didn't help, error 50 might just be a symptom of a deeper storage issue. Check your available space first—if the destination has fewer than 10 GB free, that's often the trigger.

Disk errors, especially on older spinning hard drives, can also throw error 50 mid-copy. Run First Aid in Disk Utility. Pick the drive, click First Aid, and let it do its thing. It's not a perfect fix, but it catches most logical errors.

If you're still seeing the error after all this, it's time to look at the source folder too. Corrupted file names (the ones with weird characters or too-long names) can cause this. Rename the file to something simple like test.txt and try copying again. If it works, you've found your problem.

Quick Reference Summary

Start with the first fix. In my experience, 70% of error 50 cases are permissions, and the other 30% split between the cache and disk health. If you've tried all three and it's still happening, you might be dealing with a failing drive—back up now, not later.