ls: .: Operation Not Permitted

What does “ls: .: operation not permitted” mean on Mac?

“ls: .: operation not permitted” means Terminal doesn’t have permission to look inside the file or directory you asked about. macOS guards certain areas of every Macintosh, and when an app tries to access without the right access, you’ll see the error every time instead of a result. In short, the system has denied Terminal what it needs.

Two security layers are usually behind it. Full Disk Access controls which apps can reach protected folders, while System Integrity Protection (SIP) shields core system files from changes. Both are simply doing their job—keeping your data safe—even when they get in your way.

If your window looks cluttered while you troubleshoot, a clear Terminal command on Mac tidies things up, making each message easier to read.

How to fix the “operation not permitted” error on Mac?

There’s no single switch here—the right approach depends on what’s blocking access. Most of the time, it comes down to permissions or system settings, both shaped by the security features of macOS that protect your machine.

In most cases, the culprit is one of a few things—Terminal lacking disk access, a locked file or folder, a restricted directory you’ve wandered into, settings that haven’t refreshed yet, or SIP guarding core files. Enabling full disk access, adjusting permissions, switching to a user directory, restarting, or briefly disabling SIP each tackles one of those causes.

If you’re running a Unix command and the issue is related to file permissions, you can also try running the command with administrator privileges using sudo.

A note from our experts: 

 

As you can guess already, it’s not always easy to determine the cause behind the “ls: .: operation not permitted” issue from the first attempt. To support you on the way, we suggest contacting our Premium Services within the MacKeeper app and getting professional help with both identifying the issue and finding a solution. 

 

To try our support service, do the following:

1. Download and install MacKeeper on your Mac.
2. Find the Premium Services feature and click the Chat Now button.
3. Use the text box to explain your issue, then try our specific advice.

We’ve lined up the methods that work most often below, so start at the top and work your way down.

1. Enable Full Disk Access for Terminal

Granting Full Disk Access lets Terminal read the protected directories it’s currently locked out of, which clears the error in many cases. It’s the first thing we reach for.

Here’s how to turn it on:

1. Open the Apple menu and choose System Settings.
2. Click Privacy & Security, then select Full Disk Access.
3. Switch on the toggle next to Terminal. If it isn’t listed, click the Add button (+) and pick it from Utilities.
4. Quit and reopen Terminal so the change takes effect.

2. Check file and folder permissions

Sometimes the block isn’t system-wide—a single file or folder simply has access rights that shut you out. You can review and adjust those rights from Finder in a few clicks.

Follow these steps:

1. Select the file or folder in Finder, then press Command-I to open Get Info.
2. Scroll down to Sharing & Permissions at the bottom of the window.
3. Click the lock icon and enter your password to allow changes.
4. Set your account’s privilege to Read & Write, then quit and reopen Terminal.

3. Make sure you’re working in the correct directory

It’s not a real solution to your problem, but a necessary checkup to be done, as our practice shows that it’s easy to land in a folder macOS keeps off-limits without realizing it. If the error only shows up in certain spots, the directory itself may be the culprit—not your permissions.  

Follow our guidelines below:

1. Type pwd in Terminal and press Return to see which directory you’re in.
2. If it’s a protected system folder, head somewhere user-friendly—your Home or Documents folder works well.
3. Run cd ~/Documents to switch there, then try your command again.

4. Restart Terminal or your Mac

Permission changes don’t always kick in right away. Quitting Terminal usually helps, and when it doesn’t, you may need to restart Mac so those settings load properly and any temporary glitch clears out.

Here’s the quick version from us:

1. Press Control-C to stop any running command, then quit Terminal with Command-Q.
2. Reopen Terminal and run your command once more.
3. Still stuck? Restart your Mac from the Apple menu ▸ Restart, then test again.

5. Temporarily disable System Integrity Protection (advanced)

This one’s for stubborn cases only. System Integrity Protection (SIP) is a core protection layer that stops even administrators from changing protected system files. Turning it off can lift the block, but it leaves your Mac more exposed—so treat it as a last resort and switch it back on as soon as you’re done.

Here’s the process, and please go slowly:

1. Restart your Mac and hold the power button (Apple Silicon) or Command-R (Intel) to enter Recovery Mode.
2. Open Utilities ▸ Terminal from the menu bar.
3. Type csrutil disable and press Return.
4. Restart, make your change, then return to Recovery Mode and run csrutil enable to switch protection back on.

Can you permanently disable protections to bypass “ls: .: operation not permitted”?

Technically, yes—you can leave SIP off. But we don’t recommend it. With that protection gone, malware and unwanted apps can reach the very system files macOS works hard to guard, and a single bad install could do real harm.

Think of SIP as a seatbelt. You can unbuckle it for a moment if you truly need to, but riding around without it isn’t worth the gamble. Re-enable protection as soon as your task is finished, and you’ll keep your Mac on safe footing.

You might also run into “ls: .: operation not permitted” inside a Docker container, where the same permission rules apply—another reason to keep your system’s defenses intact.

What to do if “ls: .: operation not permitted” keeps appearing?

If the error sticks around after every method above, something deeper may be going on. Don’t worry—a few broader checks usually sort it out, whether you’re on a MacBook, an iMac, or a Mac mini. We recommend doing the following:

• Revisit System Settings ▸ Privacy & Security to confirm Terminal still has the access you granted.
• Think back to any recent changes—a new app, a system update, or a tweaked setting can quietly reset permissions.
• As a final step, back up your files and reinstall macOS to give the machine a clean slate. A clean reinstall sounds drastic, but it’s a reliable way to clear lingering permission issues without losing your data when you’ve backed up first.

Conclusion

Nearly every time, “ls: .: operation not permitted” comes down to permissions—macOS simply protecting a file or folder behind its security layers. Grant Terminal the right access, double-check your directory, and the message usually disappears.

If you’d rather not manage all this by hand, MacKeeper’s Premium Services keep your Mac clean, secure, and running smoothly, with a 24/7 Help Center ready whenever a question pops up. Let our team handle the heavy lifting!