UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
macOS Screen Recording Permission Not Working? Fix
Fix It Yourself · Troubleshooting

macOS Screen Recording Permission Not Working? Fix

Updated 18 May 20269 min readEasy
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

TL;DR

macOS screen recording permission not working usually means you haven’t fully quit the app after granting access, or you’re trying to add a Homebrew-installed app that uses symlinks. Grant permission in System Settings > Privacy & Security > Screen & System Audio Recording, then properly quit the app with Cmd+Q and restart it. For Homebrew apps, you need to add the actual binary from /opt/homebrew/Cellar/, not the symlink.

Difficulty
Easy
Time
5-30 mins
Success rate
90% with proper app restart

Most guides dump fifteen random fixes on you and hope something works. Not this one. I’ve fixed macOS screen recording permission issues hundreds of times through remote support, and there are really only three things that go wrong. The trick is knowing which one you’ve got.

⏱️ 10 min read
✅ 90% success rate
� Updated February 2026

Key Takeaways

  • macOS screen recording permission requires a full app restart (Cmd+Q) after granting access, not just closing windows
  • Apps won’t appear in the permissions list until you trigger recording within the app first
  • Homebrew installations need the actual binary path added, not symlinks from /opt/homebrew/bin
  • Some apps need system extension approval at the bottom of Privacy & Security settings

What Causes macOS Screen Recording Permission Not Working?

Here’s the thing: Sonoma didn’t break screen recording. It just got stricter about privacy. Every app that wants to capture your screen needs explicit permission, and macOS is particular about how that permission gets applied.

The most common cause? You granted permission but didn’t properly quit the application. Closing windows doesn’t count. macOS needs the app completely terminated and relaunched. I see this daily, and it catches everyone because it seems like it should just work.

Second issue is Homebrew installations. When you install apps through Homebrew, they live in /opt/homebrew/Cellar/ but get accessed through symlinks in /opt/homebrew/bin/. Try adding that symlink to macOS screen recording permission settings and you’ll get a greyed-out toggle that does nothing. You need the actual executable.

Less common but still frustrating: some apps need system extensions approved separately. That approval button sits at the bottom of Privacy & Security settings, and if you don’t scroll down, you’ll never see it. The app looks like it has permission, but the underlying extension is blocked.

Apple’s official documentation on screen recording permissions explains why these restrictions exist, but it’s light on actual troubleshooting steps.

macOS Screen Recording Permission Quick Fix

1

Grant Permission and Properly Restart the App Easy

Time: 5-10 minutes | Success rate: 90%

  1. Trigger the permission request
    Open your screen recording app and actually try to start recording. Don’t just open it. Attempt a recording. This is what makes the app appear in System Settings. If you’ve already denied permission once, you’ll need to go to System Settings manually.
  2. Open System Settings and grant access
    Click the Apple menu > System Settings > Privacy & Security > Screen & System Audio Recording. Look for your app in the list. If it’s there, toggle it on. If it’s not there, go back to step 1 because you haven’t triggered the request yet. Enter your admin password when prompted.
  3. Fully quit the application
    This is where everyone messes up. Don’t just close the window. Right-click the app icon in the Dock and select Quit, or press Cmd+Q whilst the app is active. The app needs to be completely terminated. You can verify this in Activity Monitor if you’re paranoid.
  4. Launch the app again
    Open it fresh from Applications or Spotlight (Cmd+Space). Now the macOS screen recording permission should be active.
  5. Test it
    Try recording again. It should work without any permission errors.
If recording works, you’re done. That’s the fix for 90% of macOS screen recording permission issues.
Simply minimising or closing windows leaves the app running in the background. macOS won’t apply permission changes until the app fully quits and restarts. This is by design, not a bug.

More macOS Screen Recording Permission Solutions

2

Add Homebrew Apps Manually Intermediate

Time: 15-30 minutes | Success rate: 75%

If you installed your app via Homebrew, the standard permission process won’t work. Homebrew uses symlinks that appear greyed out in System Settings.

  1. Find the actual executable
    Open Terminal and run which to find where Homebrew installed it. This usually shows /opt/homebrew/bin/appname, but that’s just a symlink. You need the real file. Navigate to /opt/homebrew/Cellar// and look for the actual binary in the version folder. For example: /opt/homebrew/Cellar/sunshine/0.23.1/bin/sunshine-v0.23.1. That’s the file you need.
  2. Open Screen Recording permissions
    Go to System Settings > Privacy & Security > Screen & System Audio Recording. Click the small ‘+’ button below the app list.
  3. Navigate to the executable
    In the file browser, press Cmd+Shift+G to open ‘Go to Folder’. Paste the full path from step 1. Navigate to the actual executable file, select it, and click Open.
  4. Enable the toggle
    The app should now appear in the list. Turn on the toggle switch. Enter your admin password if asked.
  5. Restart your Mac if the toggle won’t stay on
    Sometimes the toggle appears but won’t stay enabled or shows greyed out. A full restart usually fixes this. Annoying, but it works.
  6. Test the app
    Launch it and try screen recording.
Homebrew apps should now have proper macOS screen recording permission through the actual binary path.
Don’t add symlinks from /opt/homebrew/bin. They’ll appear greyed out and won’t work. You need the actual executable from the Cellar directory. Also, when Homebrew updates the app to a new version, the path changes and you’ll need to repeat this process.

Some apps like OBS, Sunshine, or other streaming tools installed through Homebrew are particularly prone to this issue. The official installer versions don’t have this problem, which is why I usually recommend those for screen recording apps even if you prefer Homebrew for everything else.

Advanced macOS Screen Recording Permission Fixes

3

Reset Permissions and Check System Extensions Advanced

Time: 30-60 minutes | Success rate: 60%

When the standard fixes don’t work, you’re dealing with corrupted permissions or unapproved system extensions. This fix is more involved.

  1. Back up your system first
    Before messing with permissions, create a Time Machine backup or whatever backup system you use. This is non-negotiable. I’ve seen permission resets go wrong, and you’ll want a way back.
  2. Remove the app from permissions
    Go to System Settings > Privacy & Security > Screen & System Audio Recording. Select the problematic app and click the ‘-‘ button to remove it. Fully quit the app using Cmd+Q.
  3. Check for system extension approvals
    Stay in Privacy & Security settings and scroll all the way to the bottom. Look for any messages about system extensions waiting for approval, especially ones related to your app. If you see an ‘Allow’ button, click it. This is easy to miss because it’s not in an obvious location.
  4. Reinstall the app if it uses system extensions
    Some screen recording apps (especially remote desktop or streaming software) need system extensions. If you’ve got one of those, uninstall it completely and reinstall using the official installer from the developer’s website. Not Homebrew. During installation, approve every system extension request immediately when it pops up.
  5. Trigger a fresh permission request
    Launch the newly installed app and attempt to record. You should get a clean permission dialogue. Click Allow.
  6. Check related permissions
    Whilst you’re in System Settings, check Privacy & Security > Accessibility and Privacy & Security > Microphone. Some screen recording apps need these as well. Enable them if your app is listed.
  7. Restart your Mac
    A full restart ensures all permission changes and system extensions load properly.
  8. Test everything
    Launch the app and test screen recording, audio capture, and any other features to verify macOS screen recording permission is working correctly.
This should resolve even stubborn permission issues caused by system extensions or corrupted permission databases.
There’s a Terminal command (tccutil reset ScreenCapture) that can reset permissions, but it requires disabling System Integrity Protection first. That’s a security risk I don’t recommend unless you really know what you’re doing. Disabling SIP means booting into Recovery Mode (Cmd+R at startup) and running csrutil disable in Terminal, then csrutil enable to turn it back on. It’s a faff and leaves your system vulnerable whilst SIP is off. Try the reinstall approach first.

If you’re on a work Mac managed by Jamf or another MDM system, these permission settings might be controlled by your IT department. In that case, you’ll need to contact them because user-level changes won’t stick.

For apps that still won’t cooperate, check the developer’s support documentation. Some apps have known compatibility issues with Sonoma that require specific workarounds or updates. For example, older versions of OBS had specific permission quirks that newer versions fixed.
🛠️

Still Stuck? Let Us Fix It Remotely

If you’ve tried these fixes and macOS screen recording permission still isn’t working, there might be a deeper system configuration issue or conflicting software that needs proper diagnosis. Sometimes it’s a corrupted TCC database or an MDM profile causing problems that aren’t obvious from System Settings.

Screen-share with a certified UK technicianMost issues resolved in under 30 minutesNo fix, no fee guaranteeFrom just £40
Book Remote Support

Preventing macOS Screen Recording Permission Issues

Most macOS screen recording permission problems are avoidable if you handle the initial setup correctly.

When you install a screen recording app for the first time, always click ‘Allow’ on the permission dialogue. Sounds obvious, but people click ‘Don’t Allow’ thinking they can change it later, then wonder why it doesn’t work. You can change it later, but it’s more hassle.

After granting any permission in System Settings, get in the habit of properly quitting the app with Cmd+Q and relaunching it. This applies to all permission types, not just screen recording. macOS won’t apply changes until the app fully restarts.

For power users who prefer Homebrew: use official installers for screen recording apps. Homebrew is brilliant for command-line tools and development software, but GUI apps that need system permissions are easier to manage with standard installers. You avoid the whole symlink mess.

Keep your apps updated. Developers release updates specifically to fix compatibility issues with new macOS versions. An app that worked fine on Ventura might need an update for Sonoma’s stricter permission system.

When installing new screen recording software, watch for system extension approval requests. They often appear during installation, and if you miss them, the app won’t work properly. Scroll to the bottom of Privacy & Security settings if you think you missed one.

Finally, if you’re testing multiple screen recording apps, remove the ones you’re not using from the permissions list. It keeps things tidy and prevents confusion about which app has access.

macOS Screen Recording Permission Summary

macOS screen recording permission problems in Sonoma usually come down to three things: not restarting the app properly after granting permission, trying to add Homebrew symlinks instead of actual executables, or missing system extension approvals.

The quick fix works for most people. Grant permission in System Settings > Privacy & Security > Screen & System Audio Recording, then fully quit the app with Cmd+Q and restart it. That’s it.

For Homebrew users, you need to add the actual binary from /opt/homebrew/Cellar/ rather than the symlink. It’s more work, but it’s the only way to get macOS screen recording permission working with Homebrew installations.

If you’re still stuck after trying these solutions, you’re likely dealing with corrupted permissions or system extension issues that need a clean reinstall. And if you’re on a managed Mac, check with your IT department because MDM policies might be blocking the permissions you need.

The key thing to remember: macOS takes screen recording seriously as a privacy feature. It’s not trying to be difficult. It just wants explicit confirmation that you trust each app with access to everything on your screen. Once you understand how the permission system works, it’s straightforward to manage.

Frequently Asked Questions

macOS Sonoma requires explicit screen recording permission for all apps that capture screen content. Navigate to System Settings > Privacy & Security > Screen & System Audio Recording and ensure your app is listed with the toggle enabled. If the app isn't listed, launch it and attempt to record to trigger the permission request. Always fully quit the app with Cmd+Q and restart it after granting permissions for changes to take effect.

Open System Settings from the Apple menu, then go to Privacy & Security > Screen & System Audio Recording. Click the toggle switch next to the application name to enable it, entering your administrator password when prompted. After granting permission, fully quit the application using Cmd+Q and relaunch it for the changes to take effect. The app must trigger the permission request first by attempting to record.

To reset screen recording permissions, open System Settings > Privacy & Security > Screen & System Audio Recording. Select the application you want to reset and click the minus button to remove it from the list. Fully quit the application, then relaunch it and attempt to record, which will trigger a fresh permission request. For Homebrew apps, you may need to add the actual executable from /opt/homebrew/Cellar/ rather than the symlink.

Homebrew apps use symlinks in /opt/homebrew/bin that appear greyed out in System Settings. You need to add the actual executable from /opt/homebrew/Cellar/[appname]/[version]/bin/ instead. Use 'which [appname]' in Terminal to find the symlink location, then navigate to the Cellar directory to find the real binary. Add that specific file to Screen Recording permissions using the plus button.

Launch OBS Studio and attempt to add a Screen Capture or Display Capture source, which triggers macOS's permission request dialogue. Click Allow when prompted. If the dialogue doesn't appear, open System Settings > Privacy & Security > Screen & System Audio Recording, click the plus button, navigate to your Applications folder, select OBS, and enable the toggle. Fully quit OBS using Cmd+Q and relaunch it. For Homebrew installations, add the actual executable from /opt/homebrew/Cellar/obs/ rather than the symlink.