'Permission Denied' on a Folder on Mac? Here's How to Fix It

You try to drop a file into a folder and Finder pushes back: “The folder can’t be opened because you don’t have permission to see its contents.” Or you save from an app and get “You don’t have permission to save the file in the folder.” Or in Terminal, the blunt version: Permission denied. The folder is yours, on your Mac, and yet macOS says no.

Permission errors come from a Unix model bolted under the macOS GUI. The model is precise; the error message is vague. Knowing how the layers stack helps you fix it without making things worse.

How macOS permissions actually work

Every file and folder has three permission attributes per principal:

• Owner — usually a user.
• Group — usually staff or wheel.
• Other — everyone else.

For each, you can grant Read, Write, Execute. On folders, “execute” means “list contents.”

Plus, on top of the Unix layer, macOS has:

• Access Control Lists (ACLs) — additional fine-grained permissions, often invisible in Finder.
• TCC (Transparency, Consent, and Control) — privacy gates around specific folders like Documents, Desktop, Photos.
• System Integrity Protection (SIP) — protects system folders from any modification, even by root.

The “Permission denied” error can come from any of those layers.

Check what you’ve actually got

In Finder, click the folder → File → Get Info (Cmd+I). Scroll to Sharing & Permissions at the bottom. You’ll see:

• Your username with Read & Write, Read only, or No Access.
• A staff or wheel group entry.
• An everyone entry.

In Terminal:

ls -le /path/to/folder

The -e flag shows ACLs. Output looks like:

drwxr-xr-x@ 5 you staff 160 Apr 12 14:32 myfolder
 0: group:everyone deny delete

The first column is permissions. The @ after it means extended attributes. ACLs appear on numbered lines below.

Quick fixes for the common cases

1. Grant yourself Read & Write through Get Info

Get Info → Sharing & Permissions → click the lock → authenticate → set your user to Read & Write. If you’re not in the list, click + and add yourself.

This handles permission errors on folders you legitimately own.

2. Apply to enclosed items

After fixing permissions on a folder, click the gear menu → Apply to enclosed items. This propagates the change recursively. Useful for folders restored from backup with broken inherited permissions.

3. Check ownership

If the folder is owned by a user that doesn’t exist on this Mac (e.g., you migrated from another machine), you might lack any access at all.

sudo chown -R $USER:staff /path/to/folder

Replace the path. This claims ownership of the folder and everything in it.

Skip the manual huntSweep clears the cruft that triggers most of these errors — caches, logs, leftover daemons. Download Sweep free →

Fix Terminal Permission denied errors

In Terminal, Permission denied usually means one of:

1. You don’t have read/write permission on the file.
2. The folder containing the file lacks execute (list) permission for you.
3. You’re trying to write to a system-protected path (SIP blocks it even from root).

For your own files:

chmod u+rw /path/to/file
chmod u+rwx /path/to/folder

For folders where you’re missing the listing permission:

chmod u+x /path/to/folder

For paths owned by another user where you have legitimate access (uncommon outside multi-user systems):

sudo -u othheruser command

Use sudo only when you need to. Casual use of sudo rm -rf is how people accidentally destroy their data.

Reset Library or Application Support permissions

If an app fails saving its preferences, settings, or cache, your ~/Library may have permission damage:

diskutil resetUserPermissions / `id -u`

This resets permissions on your home folder back to macOS defaults. Doesn’t touch your data — just permission metadata.

In modern macOS (Catalina+), this command may not work or may have been replaced. The alternative is targeted:

sudo chown -R $USER:staff ~/Library
chmod -R u+rw ~/Library

After running these, restart and try the failing app again.

Fix permission errors from app sandboxing (TCC)

If you get permission denied in apps trying to access Documents, Desktop, Downloads, or external volumes, that’s TCC, not Unix permissions.

System Settings → Privacy & Security → scroll through:

• Files and Folders — per-folder, per-app permissions.
• Full Disk Access — broad read access for tools that need it.
• Desktop & Documents — per-app.

Add the failing app to the appropriate list. Apps that need to read the whole filesystem (backup tools, antivirus, search tools) need Full Disk Access. After granting, restart the app.

Diagnose AND clean in one appSweep finds the buildup behind the error and clears it. Try Sweep free →

Specific scenarios

Permission denied on a folder you copied from another Mac

The owner UID from the other Mac doesn’t match your UID here. sudo chown -R $USER:staff /path/to/copied-folder claims ownership.

Permission denied on Time Machine backup contents

Time Machine sets ACLs that block direct access. Don’t try to read or modify the backup directly — use Migration Assistant or browse via Time Machine’s UI. Modifying TM backup files manually breaks them.

Permission denied on a network share

SMB and AFP shares enforce permissions from the server. If the server says no, you can’t override locally. Talk to whoever runs the share.

”Operation not permitted” instead of “Permission denied”

This is TCC speaking, not Unix. The app needs a Privacy & Security grant. Check System Settings → Privacy & Security.

Permission denied trying to delete .DS_Store files

The deeper folder owns them. Get Info on the parent, fix permissions, apply to enclosed items.

Reset the user’s home folder permissions

For widespread permission damage in your home folder:

1. Boot into Recovery Mode (Apple Silicon: hold power, choose Options; Intel: Cmd+R).
2. Utilities → Terminal.
3. Run resetpassword (yes, despite the name, this also exposes the user permissions reset).
4. From the menu in the resetpassword tool, choose your user and apply the home folder permission reset option.

The exact menu item varies by macOS version but the function is consistent. This is the official way to fix systemic permission damage on your home folder.

Don’t override SIP

System folders like /System, /usr (mostly), /sbin, parts of /private, and others are protected by System Integrity Protection. Permission denied there means SIP is doing its job.

The right answer is virtually never to disable SIP. If a tool requires writing to a SIP-protected path, the tool is wrong or out of date. Look for an alternative or contact the developer.

Specific Library folder repairs

Common folders that get permission-damaged:

chmod -R u+rw ~/Library/Caches
chmod -R u+rw ~/Library/Application\ Support
chmod -R u+rw ~/Library/Preferences

Restart afterward — many running processes won’t pick up new permissions until relaunched.

Bulk-fix permissions on a backup folder

If you’ve restored from an external backup and permissions are wrong everywhere:

sudo chown -R $USER:staff ~/RestoredFolder
sudo chmod -R u+rw ~/RestoredFolder
sudo xattr -cr ~/RestoredFolder

The third line clears extended attributes (including any quarantine flags) that may have come along.

When the folder genuinely shouldn’t be writable

Sometimes the answer is “you’re trying to write somewhere you shouldn’t”:

• App bundles (/Applications/AppName.app/Contents/...) — modifying breaks the code signature.
• Other users’ home folders — you shouldn’t have write access by default.
• System folders — protected on purpose.
• Mounted disk images marked read-only — copy contents out, then modify.

If the permissions are correct and the system is telling you no for a good reason, find a different path.

When you have to factory-reset your user

In rare cases, permission damage is so widespread that the cleanest fix is creating a new user account, copying your data over, and abandoning the broken one:

1. System Settings → Users & Groups → add a new admin user.
2. Log in as the new user.
3. Copy /Users/old/Documents, /Users/old/Desktop, /Users/old/Pictures, /Users/old/Movies into the new user’s home (you may need to use Get Info → Sharing & Permissions on the source first).
4. Re-set up apps and preferences in the new account.
5. Once verified, delete the old user account.

This loses preferences and saved sessions but rebuilds permissions cleanly.

Prevent permission errors

• Don’t run sudo casually. Most permission errors should be fixed without it.
• Don’t manually edit files inside /System or /Applications/<app>.app.
• If you migrate, use Migration Assistant rather than dragging folders directly.
• Don’t change permissions on folders inside ~/Library unless you know which one.

Permission denied is one of the most common macOS errors and one of the most fixable. Identify the layer (Unix, ACL, TCC, SIP), apply the right fix, and you’re back to writing where you should.