Permission Denied on Mac: How to Fix It

A “Permission denied” message on a Mac usually means your account or an app cannot read, change, or run a file. These steps help you identify what is blocked and correct the access setting without weakening permissions across your Mac. Have the exact file or folder path and, if possible, the full error message ready.

What You’ll Need

Access to the Mac account that owns or manages the affected files. Some changes require an administrator password.
The name and location of the affected file, folder, app, or external drive.
A current backup if you plan to change permissions on important files or folders.

Step-by-Step

Identify what action failed. Note whether the message appeared while opening, editing, deleting, installing, or running something in Terminal. Check that you are working with the intended file and that it still exists. If the item is on an external drive, server, or shared folder, its owner or administrator may control access.
Try a simple restart and retry. Save your work, restart the Mac, and repeat the action once. If an app is involved, quit and reopen it. A restart can clear a temporary process or mount issue, but it will not change a genuine access restriction.
Check Finder’s Sharing & Permissions. In Finder, select the affected file or folder and choose File > Get Info (or press Command-I). Expand Sharing & Permissions near the bottom. Find your account in the list and read its privilege: Read & Write allows changes, while Read only does not. If your account is absent, use the add button, if available, to add it and set the appropriate privilege. Click the lock and authenticate if macOS asks for an administrator password. Change only the specific item you need.
Check the enclosing folder. A file may inherit practical access limitations from its parent folder. Use Get Info on the folder containing the item and inspect its permissions too. If several items in a folder are meant to have the same access, the gear menu may offer Apply to enclosed items. Use this only when you understand that it changes permissions for everything inside; avoid applying it to your home folder, the whole startup disk, or system folders.
Check app privacy access. If an app cannot access Documents, Desktop, Downloads, a removable volume, or another protected location, open System Settings > Privacy & Security. Review the relevant category, such as Files and Folders or Full Disk Access, and allow access only if the app needs it and you trust it. The available categories and controls can differ by macOS version and app. Quit and reopen the app after changing access.
Check the volume and its state. If the item is on an external disk, confirm the drive is connected, appears in Finder, and is not mounted read-only. In Disk Utility, select the volume and use First Aid if you suspect a file-system problem. Do not erase or reformat the drive unless you have a backup and intend to remove its contents. For a work, school, network, or shared drive, ask its administrator whether your account has access.
If the error is in Terminal, confirm the command and path. Check spelling, capitalization where relevant, spaces, and the current folder. Dragging a file or folder from Finder into Terminal can insert its path accurately. Use ls -l followed by the path to inspect a file’s owner and permission bits. Do not run a command with sudo just to make an error disappear: it runs with elevated privileges and can damage files or expose data if used incorrectly.
Make a narrow permission change only if needed. If you know the correct owner and intended access, an administrator can use chmod for permissions or chown for ownership in Terminal. These commands are easy to misuse: apply them only to the exact file or folder, verify the path first, and do not use recursive options such as -R unless you fully understand the scope. For ordinary personal files, Finder’s Get Info controls are usually the safer option.
Retry and note what changed. Reopen the item or repeat the original action. If it still fails, record the exact message, the app or command, the file location, and what you changed. Restore an earlier setting if the change caused a new problem, and use the troubleshooting checks below.

Common Mistakes

Changing permissions on too much. A recursive command or “Apply to enclosed items” can alter thousands of files. Limit changes to the one item that needs access.
Making everything readable or writable. Broad settings such as allowing every user to write can expose private files or break expected protections. Grant only the access your account or trusted app needs.
Using sudo without checking the command. Administrator privileges do not make a command safe. A wrong path can affect unrelated files or system components.
Confusing app privacy with file permissions. A file may allow your account, while macOS separately blocks an app from accessing its location. Check both when the problem is app-specific.
Assuming every “permission” error is fixable locally. A shared-drive owner, organization administrator, or external-drive format may control access. Changing local settings may not help.

Tips

Use Finder’s Get Info to check one item at a time before changing anything.
Keep a backup before making broad changes, especially on folders containing work or personal documents.
When Terminal is involved, quote paths with spaces or use the path inserted by dragging from Finder. Verify the target before pressing Return.
After granting an app access in Privacy & Security, quit and reopen it; some apps do not recognize the new permission immediately.
If a file came from another account or device, ask its owner to share it properly rather than taking ownership blindly.

Troubleshooting

The Sharing & Permissions controls are dimmed: Click the lock at the bottom of Get Info and authenticate if you are an administrator. If the lock cannot be unlocked or your account is not an administrator, contact the Mac’s administrator or the file owner.

Your account already has Read & Write: Check the parent folder and the app’s Privacy & Security access. Also check whether the disk is read-only, full, disconnected, or experiencing errors. A file may be locked: select it in Finder, choose Get Info, and check whether Locked is selected.

Only one app is affected: Confirm the app is allowed to access the relevant folder in Privacy & Security, then restart the app. If it is a downloaded or managed app, consult its help resources or your administrator rather than granting broad disk access automatically.

A Terminal command still fails: Recheck the full path, spelling, and ownership with a read-only inspection such as ls -l. If the file belongs to another user, is on a shared volume, or is protected by macOS, stop rather than trying increasingly broad commands. Ask the owner or administrator for the correct access.

The error began after a permissions change: Avoid further recursive edits. If you have a backup, restore the affected files or settings from it. For system files or a Mac managed by an organization, contact Apple Support or the administrator for help appropriate to the Mac and macOS version.

Frequently Asked Questions

Why does my Mac say “Permission denied”?
Usually, the current account or app lacks the access needed for that file, folder, drive, or protected location. The error can also come from a read-only volume or a shared resource’s access rules.

How do I give an app permission to access a folder?
Open System Settings > Privacy & Security, inspect the relevant access category, and allow the trusted app if it is listed. Quit and reopen the app afterward.

Should I use chmod 777 to fix it?
No. It grants broad read, write, and execute permissions and can expose or damage files. Set only the specific access required, preferably through Finder for ordinary files.

Can I fix permission denied without an administrator account?
You can inspect settings and access files you own, but changing protected ownership or permissions may require an administrator. Ask the Mac’s administrator or file owner rather than trying to bypass the restriction.

Why does Terminal deny access when Finder can open the file?
Terminal may be blocked separately by macOS privacy controls, or the command may use a different path or account context. Check Terminal’s relevant Privacy & Security access and verify the path.

Will changing permissions delete my files?
Changing access settings does not normally delete files, but a mistaken command can alter or damage many items. Back up important data and verify the exact target before making changes.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →