macOS Error -50: Fix the 'File Not Found' Code Fast

Cause 1: Finder Permission Problem (Most Common)

You're trying to move, copy, or delete a file and hit error -50. That happens when macOS thinks you don't have the right to touch that file. It's not that the file is gone—it's that the system blocked you.

This pops up a lot when you've downloaded a file from Safari or Mail and then try to drag it to the Desktop. The quarantine attribute sticks to it, and Finder gets confused.

Fix: Reset Permissions on the File

1. Right-click the file in Finder. Select Get Info (or press Cmd+I).
2. Look at the Sharing & Permissions section at the bottom. If it's collapsed, click the arrow to expand it.
3. If the padlock icon is locked, click it and enter your admin password.
4. Next to your username, set the privilege to Read & Write using the dropdown menu.
5. Close the Get Info window. Then try moving or copying the file again.

After you change the permission, you should see the file act normal—dragging works, and no error message appears.

If one file is fixed but others still fail, you can batch-fix a folder. Select the folder, press Cmd+I, then click Apply to enclosed items at the bottom. That takes a few seconds, so don't panic if it looks frozen.

Cause 2: Cloud File Stuck in Limbo

If you use iCloud Drive, Dropbox, or OneDrive, error -50 often shows up when you try to open a file that hasn't downloaded yet. The file looks solid, but it's just a placeholder that can't wake up.

I see this with Pages documents and large media files that were uploaded from another device. You click to open, and boom—error -50.

Fix: Force the Download or Re-link

1. Open Finder and go to the folder where the file is (like iCloud Drive).
2. Right-click the file. Look for a menu item that says Download Now (iCloud) or Make Available Offline (Dropbox). If you see it, click it and wait for the cloud icon to disappear.
3. If there's no such option, the file might be a placeholder. Click the file once, then press the spacebar to Quick Look. That sometimes triggers a download.

If Quick Look also fails, you need to remove the file from the cloud folder entirely. Move it to your Desktop (if you can), then drag it back to iCloud Drive. That forces a re-upload and clears the bad pointer.

After re-downloading, the file should open normally. If it still throws -50, the file itself might be corrupt—try downloading a fresh copy from the web if it came from a website.

Cause 3: Corrupted LaunchServices Database

Less common, but I've seen it in macOS Monterey and Ventura. Error -50 shows up when you try to open any file after a system update, and it's not just one file—everything fails.

That's the LaunchServices database getting corrupted. It's the system's index of which apps open which files. When it's broken, Finder can't resolve file types and throws -50.

Fix: Reset LaunchServices

You'll need the Terminal for this one. Don't worry, it's safe if you copy-paste exactly.

1. Open Terminal (found in Applications > Utilities).
2. Paste this command and press Enter:

   sudo launchctl unload /System/Library/LaunchDaemons/com.apple.launchd.plist

   You'll be asked for your password. Type it in (it won't show, that's normal) and press Enter.
3. Now paste this and press Enter:

   sudo launchctl load /System/Library/LaunchDaemons/com.apple.launchd.plist

4. Restart your Mac. Not just log out—a full restart from the Apple menu.

After the restart, the system rebuilds the database automatically. This takes a couple of minutes. When you log back in, try opening a file that gave you -50. It should work.

If that command doesn't work on your macOS version (Sonoma or later), here's an alternative that's newer:

lsregister -kill -r -domain local -domain system -domain user

Run that in Terminal, then restart. Same effect.

Quick Reference: Your Fix at a Glance