Fix macOS 'You don't have permission' Error in 3 Steps

Why This Happens

You click a file or open an app, and macOS tells you "You don't have permission to view it." Or maybe it's a -36 error when copying files. This usually shows up after a system update, when you moved an external drive between Macs, or when you restored files from Time Machine. The permission flags on the file got scrambled.

Here's the good news: you don't need to reinstall macOS or nuke your hard drive. Most permission errors are fixable in under a minute. Let's walk through the fixes in order — start with the first one, and only move down if you're still stuck.

Fix 1: The 30-Second Check — Privacy Settings

Before you touch anything in Terminal, check if macOS is blocking the app from accessing your files. This is the #1 cause of permission errors in modern macOS (Mojave and later).

Open System Settings (Sonoma and Ventura) or System Preferences (Monterey and earlier).
Go to Privacy & Security.
Look at the left sidebar for Files and Folders (or Full Disk Access if the app needs that).
Find the app that's throwing the error. Make sure the toggle next to it is ON.
If it's already on, try turning it OFF, then ON again.

After you toggle it, quit the app completely (press Cmd+Q) and reopen it. You should see the file or folder now. If the toggle wasn't there at all, that means the app never asked for permission — that's a different problem, so move to Fix 2.

This fix works because macOS treats file access as a privacy permission. If the checkbox isn't on, the app literally can't read the file, no matter what the file permissions say. I've seen this drive people crazy after they upgraded from Catalina to Big Sur.

Fix 2: The 5-Minute Fix — Get Info & Change Permissions

If privacy settings didn't do it, the file or folder itself has wrong permissions. This happens a lot with files you copied from a Windows machine or an old backup. Here's the direct approach:

Right-click the file or folder that's giving you trouble.
Select Get Info.
Scroll to the bottom, where it says Sharing & Permissions.
Click the lock icon in the bottom-right corner and enter your password.
Next to your username, change the privilege from Read only to Read & Write.
Close the window, then reopen it to confirm the change stuck.

That fixes single files. But what if you have a whole folder full of stubborn files? You could repeat this for each one, but that's a waste of time. Instead,

Open Terminal (search for it in Spotlight).
Type this, but replace drag_folder_path with the actual folder — you can drag the folder from Finder into the Terminal window and it will fill in the path automatically:

chmod -R u+rwx drag_folder_path

Hit Enter. You won't see any output if it works. Then try opening the folder again. If you still get the error, the problem might be that you're not the owner of those files. That brings us to Fix 3.

Fix 3: The Advanced Fix — Reset Ownership with Terminal (15+ minutes)

This one's for when you've tried everything above and you're still locked out. It's also the fix for that weird case where you see a red circle with a minus sign on your files.

First, let's confirm you're actually the owner. In Terminal, run:

ls -le@ drag_folder_path

You'll see a list of files with letters like -rw-r--r-- and an owner name. If the owner isn't your username, that's the problem. To take ownership back, run:

sudo chown -R $(whoami):staff drag_folder_path

You'll be asked for your password. Type it (you won't see characters as you type — that's normal). After it runs, you're the owner. Now also reset the permissions to the standard ones:

chmod -R u+rwX,g+rwX,o-w drag_folder_path

That X capital letter is important — it only adds execute permission to directories, not regular files. Run those two commands, then close Terminal and try the file again.

When to Use the Nuclear Option

If the folder is on your home folder or Desktop, and you're still locked out after these steps, you might have a corrupted ACL (access control list). That's rare, but when it happens, you'll want to clear the ACLs. Here's the command:

sudo chmod -RN drag_folder_path

This strips every ACL entry from the folder and its contents. It's a blunt instrument — your custom sharing permissions vanish, but the default permissions stay. Use it only if nothing else worked, and only on folders you don't share with other users.

One more thing: if you're getting permission errors on an external drive, don't bother with the above. The drive is probably formatted with NTFS (Windows format) or has a filesystem macOS can't fully write to. In that case, backup your data, then reformat the drive to APFS or exFAT using Disk Utility. You'll lose the data, so make sure you copy it somewhere else first.

What If Nothing Works?

If you've gone through all three fixes and the error is still there, you're dealing with something else. Check if the file is actually corrupted — try copying it to a new location. If it copies fine, the issue is Finder's cache; restart your Mac, and it usually clears.

Also, check if the file has a @ symbol next to the permissions in Terminal output. That means it has extended attributes, like quarantine flags from downloads. Remove them with:

xattr -cr drag_folder_path

That clears all extended attributes. This fixes that "You don't have permission" error you get right after downloading an app from the internet and opening it for the first time. I've seen it fix a stuck .dmg mount too.

You should be back in business now. If you're still stuck, leave a comment with the exact error message and what you tried — I'll help you narrow it down.