How to Fix the “zsh: permission denied” Mac Terminal Error

This short article explains what the “zsh: permission denied” message means on a Mac and how to clear that roadblock so you can run a file or command without trouble.

Often this error appears when the system can’t execute a file because it lacks execute rights, the file is locked, or the command is misformatted. A quick check with ls -l shows whether a file is read-only (r) or has full rights (rwx).

You’ll see simple fixes here: add execute permission, change ownership with chown -R username:username [directorypath], or give Terminal Full Disk Access via System Settings > Privacy & Security > Full Disk Access. Dragging a file into the Terminal after typing ls -l helps avoid typos and auto-fills the path.

Follow these steps and you’ll diagnose the problem fast, update permissions safely, and prevent this denied error from interrupting your workflow.

Understand what “permission denied” means in Zsh and why it happens

You’ll see this alert when the shell blocks a script that lacks executable bits, when a locked item prevents access, or when a command points at the wrong path.

What the message signals: The shell stops an operation because your account lacks the rights needed to run a file or because the command syntax is incorrect. This protects your system from unwanted changes.

Common causes include a locked file, a missing execute bit on a script, or a command that references the wrong path. Check file permissions with ls -l in a terminal window by typing ls -l, adding a space, and dragging the file into the window.

• Use Finder’s Get Info and expand Sharing & Permissions to view who can read or write a file.
• If only an r appears in the permission string, you can read the file but not modify or run it.
• Files moved from another disk or user may keep ownership that doesn’t match your account and will cause a denied error.
• Add Terminal to Full Disk Access under System Settings > Privacy & Security > Full Disk Access when commands fail due to restricted locations on disk.

Quick tip: Confirm the exact path and validate command syntax before changing file permissions or ownership.

Quick checks before you change permissions

Run a few fast checks in your shell so you spot typos or a wrong path before altering access settings. A tiny mistake can cause a permission denied message and waste time.

Verify location and names: use pwd to confirm your directory. Then run ls -l to list items and their access bits.

• Make sure the command is spelled correctly and points at the right path; one wrong character can cause an error.
• Type ls -l, add a space, then drag the file or folder from Finder into the terminal window to insert the exact path directory.
• Check for spaces in names. Quote paths or escape spaces so the shell reads the file correctly.
• Use tab-completion and copy a full command to a fresh line if a command still fails; hidden characters can break execution.

How to Fix the “zsh: permission denied” Mac Terminal Error

You may see a block when a file lacks an execute flag, belongs to another user, or sits inside a restricted disk area. Start with a clear check before changing anything.

Check file permissions with ls -l and interpret rwx

Run ls -l [path] and read the left column. The letters rwx mean read, write, execute. A lone r is read-only. Drag a file into the shell after typing ls -l to avoid typos.

Adjust Sharing & Permissions in Finder’s Get Info

Right-click an item and open Get Info. Expand Sharing & Permissions, select your user in the name column, and set Read & Write if needed. This fixes many permission denied error cases without using the shell.

Make a file executable with chmod and verify access

Run chmod +x /path/to/file, then re-run ls -l to confirm an x appears for your account. Quote paths with spaces or escape them to keep the command correct.

Change ownership with chown and grant full access when needed

If ownership is wrong, use chown -R username:username [directorypath]. For protected folders, open System Settings > Privacy & Security > Full Disk Access, add Terminal, then quit and relaunch. These steps restore access and resolve many zsh permission denied situations.

• List first with ls -l.
• Use Get Info to set Read & Write.
• Add execute with chmod +x.
• Fix ownership with chown -R.

Step-by-step workflows for common scenarios

This short guide gives clear steps for the three routines you’ll use most often when a file or folder won’t run.

When a script or command won’t run: add execute and retry

Set execute bits: run chmod +x "/exact/path/to/script" for the target file. Use quotes when names include spaces.

Confirm the change with ls -l. Look for an x in the permissions string before you run the command again.

When a folder blocks access: apply fixes recursively

Open Get Info, set your account to Read & Write, then click Apply to enclosed items so all files inherit the update.

If you prefer the shell, use chown -R yourUser:yourUser "/path directory/that/needs/fix" and then recheck permissions with ls -l.

When ownership is wrong after moving items

Files moved between disks often keep previous ownership. Correct this by changing ownership and ensuring the correct group on shared folders.

After a chown -R, verify access for your user and run the failing command again. If a denied error remains, recheck the path for typos and confirm the file exists at that path directory.

• Set execute: chmod +x "/exact/path/to/script".
• Verify with ls -l before retrying any command.
• Use Get Info and Apply to enclosed items for folder fixes.
• Use chown -R when ownership mismatches follow a move.

Pro tips to prevent the denied error going forward

Make default file and folder rules part of every new workspace. Set sharing permissions in Finder’s Get Info for project folders, choose sensible Read & Write values, and click Apply to enclosed items. This ensures new files inherit consistent file permissions and reduces future access surprises.

Assign the right users and group for shared directories. Use the Name column when granting roles so collaborators get the access they need without opening wider rights than required.

• Standardize file permissions on main project folders so every file folder inherits Read & Write for the right users and group.
• Make a path hygiene habit: quote paths with spaces and use tab-completion to avoid typos in commands on a terminal mac.
• Grant Terminal full access under Privacy & Security only if your workflow needs protected disk areas, and document who has that capability.

Quick checklist

Conclusion

, This short recap gives a clear checklist you can follow when a blocked command halts work.

First, validate rights with ls -l. Then use Finder’s Get Info and adjust Sharing & Permissions for your user. Make scripts executable with chmod +x.

Fix ownership with chown -R username:username [directory] when files move between disks. Grant Terminal Full Disk Access from System Settings > Privacy & Security only when required.

These steps solve most zsh permission issues. For recurring permission denied error messages, run the same checks in a menu or window and repeat basic commands before deeper troubleshooting. Keep a note of why full access was enabled so system rights stay secure.