macOS Error 36: Fix Finder Copy Failures on Mac

Quick Fix (30 seconds): Kill Finder & Reconnect

Half the time, Error 36 is just Finder being stupid. Do this first:

1. Press Option + Command + Escape to force quit Finder.
2. Select Finder in the list and click Relaunch.
3. If you were copying to a network drive or external disk, eject it and plug it back in.

This clears whatever tiny glitch hung the copy process. Doesn't work? Move on.

Moderate Fix (5 minutes): Run dot_clean on the Source or Destination

Error 36 is almost always caused by Apple Double files — those hidden ._ files that macOS adds to store extended attributes. When these get corrupt or cross filesystems wrong, Finder throws -36.

The fix is dot_clean. It merges those ._ files back into the parent file.

1. Open Terminal (Applications > Utilities).
2. Type:

   dot_clean -v /path/to/problem/folder

   — replace the path with the actual folder that's failing. You can drag the folder from Finder into the Terminal window to paste the path.
3. Hit Enter. Wait a few seconds.
4. Try the copy again.

That's the #1 fix I've used on hundreds of Macs. It works on any macOS version from High Sierra through Sonoma. The -v flag shows what it's processing. Leave it out if you want quiet mode.

Still broken? That means the issue is deeper — probably permissions or actual file system corruption.

Advanced Fix (15+ minutes): Use Terminal to Copy With rsync

When Finder fails, bypass it. rsync is a rock-solid command-line tool that doesn't care about Finder's metadata hangups.

1. Open Terminal.
2. Run:

   rsync -av --progress /path/to/source/ /path/to/destination/

   • -a preserves permissions, timestamps, and most metadata.
   • -v makes it talk to you so you know it's working.
   • --progress shows each file as it copies.
   • Important: the trailing slash on the source path matters — it means 'copy the contents of this folder', not the folder itself.
3. Watch the output. If rsync throws errors, it'll tell you exactly which file and why.

Common rsync error on macOS: rsync: mkstemp failed: Permission denied — that's macOS security blocking writes. Fix it by running the command with sudo:

sudo rsync -av --progress /path/to/source/ /path/to/destination/

You'll need your admin password. Don't forget the trailing slash.

When rsync Still Fails: Check Disk Permissions

If even rsync complains about permissions, the file or folder has gotten locked up. Check in Finder:

• Right-click the folder, choose Get Info.
• At the bottom, look at Sharing & Permissions. Your user should have Read & Write.
• If it says Read only, click the lock icon, then change it to Read & Write.

Also check the destination drive. If it's an external drive formatted as NTFS, macOS can't write to it without third-party drivers. Error 36 shows up there too. Reformat the drive as exFAT or APFS if you own it, or install Paragon NTFS.

Final Nuke Option: First Aid in Disk Utility

If none of the above helps, the drive itself might have file system corruption.

1. Open Disk Utility.
2. Select the drive (not the volume) on the left sidebar.
3. Click First Aid and run it. This can take 10-30 minutes on large drives.
4. After it finishes, try the copy again.

Real-world trigger I see most: Someone copies a folder full of photos from a Mac-formatted drive to a FAT32 USB stick. FAT32 doesn't support extended attributes, macOS chokes, and boom — Error 36. dot_clean fixes it every time.

That's it. Start with dot_clean. That resolves 90% of cases. The other 10% are permissions or drive issues. You don't need to reboot, reinstall macOS, or call Apple Support for this one.