Mac Screen Recording Permission Not Working: Every Cause and Fix

Screen recording permission is on but your Mac still records a black screen? Here is every cause — stale entries, duplicate app copies, MDM — and the fix.

You flipped the switch in System Settings. The app is listed, the toggle is blue, and the recording still comes out as a black rectangle — or the app keeps showing you the same “permission required” screen you just satisfied.

This is one of the most common first-run problems on macOS, and it is almost never a bug in the recorder. macOS stores screen recording consent in a privacy database that keys on the app’s identity, not just its name, and there are a handful of specific ways that identity stops matching what you approved. Each one has a different fix.

Here is how to work through it in order, from the thirty-second fixes to the ones that need your IT department.

First, Know Which Permission You Actually Need

macOS splits what feels like one permission into four separate grants, and recorders commonly need three of them. They live in System Settings › Privacy & Security, each in its own list:

PermissionWhat it controlsSymptom when missing
Screen & System Audio RecordingCapturing display pixels and system audioBlack frame, or the app refuses to start
MicrophoneYour narrationVideo records, voice track is silent
CameraWebcam overlayWebcam area is black
AccessibilityReading window state across appsWindow picker can’t see full-screen apps

On macOS 13 Ventura the first one is simply called Screen Recording; later versions renamed it to Screen & System Audio Recording because the same toggle now covers system audio capture. If a guide tells you to look for one name and you see the other, you are in the right place.

The important consequence: granting screen recording does nothing for your microphone. A recording with perfect video and no narration is not a screen recording permission problem, and no amount of toggling that switch will fix it.

The Clean Path (Do This First)

If you have not deliberately granted permission yet, do it the way the app expects rather than hunting through System Settings yourself.

In Recorded, the first launch on macOS opens a permission window instead of the main window. It checks both Screen Recording and Accessibility at startup and only shows the main interface once both are granted. The flow is:

  1. Click Grant Permission next to Screen Recording. Recorded asks macOS to register itself in the permission list, then opens System Settings directly to the right pane.
  2. Turn the Recorded switch on. macOS asks for your password or Touch ID — this is expected; the privacy database is not user-writable without authentication.
  3. Switch back to Recorded. You do not need to click anything. The permission window re-checks status every two seconds and moves on to the main window by itself once both grants land. (There is also a Recheck button if you would rather not wait.)
  4. Click Grant Permission next to Accessibility and do the same in that list.
  5. Turn on Mic or Camera in the main window. macOS prompts for those the first time you actually use them, not at install time.

Two reasons to use the in-app buttons rather than adding the app manually: the app has to run once and ask before macOS will create a list entry for it at all, and the button takes you to the exact pane instead of a similarly named one.

Recorded also pre-registers screen capture access at startup, so macOS raises its consent dialog before you are recording rather than in the middle of a take. If you see a system dialog at launch, that is this step, and approving it is the whole point.

Cause 1: You Have Two Copies of the App

This is the single most frequent reason a correctly-enabled toggle does nothing.

macOS identifies an app by its bundle identifier and its code signature. If you launched the app once from ~/Downloads, granted permission there, then dragged it to /Applications and launched that copy, you now have consent recorded against a path and binary you are no longer running. The list in System Settings looks right. The app you are actually using was never approved.

The fix:

  1. Quit the app completely with Command-Q. Closing the window is not enough; the process has to exit.
  2. Delete every copy except the one in /Applications — check ~/Downloads, your Desktop, and any mounted .dmg in Finder’s sidebar. Eject the disk image.
  3. In System Settings › Privacy & Security › Screen & System Audio Recording, select the app’s row and click the – button to remove it entirely.
  4. Launch the copy in /Applications and grant permission again.

Removing the stale entry matters. Toggling it off and on again re-approves the same mismatched record.

Cause 2: The App Was Updated or Re-Signed

The same mismatch happens silently after some updates. If an app ships a new build with a changed signature, macOS can treat it as a different app than the one you approved, and the symptom is identical: listed, enabled, still blank.

The fix is the same removal-and-regrant from Cause 1 — remove the row with –, relaunch, grant again. It takes twenty seconds and rules out an entire class of problem, which is why it is worth doing before anything more elaborate.

If an update left you unsure which build you are running, reinstalling from the download page and deleting the old copy first is the cleanest reset.

Cause 3: You Granted It to the Wrong Thing

Look closely at the row you enabled. A few lookalikes trip people up:

  • A different recorder. If you have tried several screen recorders, the list may hold three or four entries. Enabling the wrong one is easy.
  • Your terminal or IDE. If you launched the app from a shell or a development tool, macOS may attribute the request to the parent process. The toggle you need is on Terminal, iTerm, or your editor — not on the app.
  • Your browser. Recording a web app’s own tab-sharing feature is a browser permission, and it is completely separate. Granting the recorder nothing changes what the browser can see, and vice versa.

If the row you expect is missing entirely, the app has never asked. Launch it and trigger a recording attempt so macOS has something to register.

Cause 4: The Process Is Holding a Stale Answer

A running process can cache the “denied” answer it received before you flipped the switch. Modern capture APIs mostly handle a live grant, which is why Recorded can detect the change within about two seconds and continue — but if a recording attempt still fails right after you grant, give the app a clean restart with Command-Q and relaunch.

A quick way to tell the difference: if the in-app permission screen moves on by itself, the grant registered. If it keeps showing “required” for more than a few seconds with the toggle visibly on, you have a mismatch from Cause 1 or 2, not a caching issue.

Cause 5: The Toggle Won’t Stay On, or Is Greyed Out

If the switch bounces back off, refuses to accept your password, or the whole row is dimmed, the privacy database is not the problem — something above it is overriding you:

  • A managed Mac. Work laptops often carry a configuration profile that pre-approves or blocks specific apps. Check System Settings › General › Device Management. If a profile is listed, your IT team controls that list through an MDM policy and has to add the app for you; no amount of local clicking will stick.
  • A standard (non-admin) account. Changing privacy settings requires administrator credentials.
  • A database that needs clearing. As a last resort you can reset consent for one app from Terminal and start the grant from scratch:
tccutil reset ScreenCapture app.recorded
tccutil reset Microphone app.recorded
tccutil reset Camera app.recorded
tccutil reset Accessibility app.recorded

app.recorded is Recorded’s bundle identifier; substitute your own app’s if you are debugging something else. Each command clears that one permission for that one app, so you will be asked again on next launch. Running tccutil reset ScreenCapture with no identifier resets it for every app on the Mac, which means re-approving your conferencing tools too — avoid that unless you mean it.

Cause 6: It Isn’t a Permission Problem at All

Some black frames have nothing to do with consent. Before you keep digging:

  • DRM-protected video. Streaming apps and protected browser playback deliberately render black to any capture path. This is working as designed and cannot be configured away.
  • A window that isn’t drawing. A minimized window, or one on another Space, may hand the capture API nothing to copy. Bring it forward before you start.
  • The wrong capture target. Picking a monitor you are not looking at produces a perfectly valid recording of an idle screen. If you are not sure which target you selected, choosing the right capture mode walks through monitor, window, and area.
  • An unsupported system. Recorded’s macOS build requires macOS 12 or later on an Apple silicon Mac, and system audio capture needs macOS 13 Ventura or later, because that is when the capture framework gained audio. There is no Intel build, so an Intel Mac will not get there no matter what you toggle.

For symptoms beyond a black frame — dropped frames, sync drift, failed exports — the broader screen recording troubleshooting guide covers the rest of the pipeline.

Microphone and Camera: Separate Lists, Separate Prompts

Once video works, audio is its own short checklist. macOS asks for the microphone the first time an app actually opens an input, so the prompt arrives when you enable Mic, not at install.

If you dismissed that prompt, there is no second chance from the app — the denial is recorded and you have to re-enable it manually in System Settings › Privacy & Security › Microphone. Same for Camera and your webcam overlay.

Two things worth checking at the same time:

  • Input device, not just permission. Permission is granted per app; which microphone it uses is a separate choice in the app. Watch the level meter move before you record a take.
  • Bluetooth inputs. A headset’s microphone can be granted and connected and still sound wrong. That is a different problem with a different fix.

And if the missing audio is app sound rather than your voice, you want system audio capture, not a microphone — recording internal audio on a Mac covers that specifically.

Windows Doesn’t Work This Way

If you move between platforms, the mental model does not transfer. Windows has no per-app screen recording consent at all — the capture API is available to any app, which is why a Windows recorder starts working the moment you install it.

Windows does gate the microphone and camera, in Settings › Privacy & security › Microphone and › Camera. Two switches matter there: the global Microphone access toggle and the separate Let desktop apps access your microphone switch further down the same page. Desktop apps are controlled by that second switch, and plenty of people turn the first one on, scroll no further, and conclude their mic is broken. A side-by-side of the platforms is in macOS vs. Windows screen recording.

The Five-Minute Resolution Order

When you are stuck, run this in sequence rather than changing several things at once:

[ ] Confirm which permission the symptom points to (video / mic / camera)
[ ] Command-Q the app, not just close the window
[ ] Delete every copy of the app except /Applications; eject any .dmg
[ ] Remove the app's row in Privacy & Security with the – button
[ ] Relaunch and grant from the app's own button, not from System Settings
[ ] Check General › Device Management for a managed profile
[ ] Only then, tccutil reset for that one app
[ ] Record a 10-second test and play it back before the real take

That last line is the one that saves the most time. A ten-second test recording confirms video, narration, and webcam in one pass, and it costs nothing compared with discovering a silent track at the end of a twelve-minute walkthrough.

Once permissions are settled they stay settled — this is a first-run problem, not a recurring one. If you are setting up a new Mac, you can download Recorded here, grant both permissions in the first minute, and not think about the privacy database again.

Happy recording!