How to grant screen recording permission on a Mac

The request to grant screen recording permission on a Mac almost never arrives on its own. It arrives in the middle of something else: a meeting that will not share a window, a screenshot tool that captures a grey rectangle, a recorder that produces a black video with working audio. The permission itself takes about fifteen seconds to give. The parts that waste time are the app that refuses to appear in the list, the app that appears but stays switched off, and the prompt that comes back weeks later.

Worth knowing before opening anything: the pane involved has changed name, and on current macOS it covers system audio as well as the screen. Searching for a pane called Screen Recording will not find it.

Where the switch lives now

The permission is in Privacy and Security, and it governs two things at once.

Choose Apple menu > System Settings, then click Privacy & Security in the sidebar. (You may need to scroll down.) Click Screen & System Audio Recording. For each app listed, turn the ability to record on or off. You can allow apps to record both your screen and audio, or just your audio. Source: support.apple.com, read September 27, 2026

The split between screen and audio is the part that catches people out. An app can be allowed to capture what the speakers are playing without being allowed to see the screen, which is exactly the configuration that produces a recording with clean sound and a black picture. When a capture looks like a permissions problem but audio is present, this pane is the first place to look rather than the last.

The settings reference for the pane states the same thing in one line and adds the detail that matters for a missing app.

Screen & System Audio Recording: Allow apps to record your screen and audio, or just your audio. The listed apps have access. To add an app, click below a list, select the app, then click Open. Source: support.apple.com, read September 27, 2026

Note the wording: the listed apps have access. Several neighbouring panes in the same list are described as showing apps that have requested access. This pane is a list of what has been granted, which is why an app that has never successfully asked is simply absent rather than present and switched off.

Why the app is not in the list

An app appears in this list when macOS has seen it attempt a screen capture, or when it has been added by hand. Absence therefore means one of a small number of things.

The app has not tried yet. Plenty of apps only request screen access at the moment the feature is used, so an app launched and left idle never triggers the prompt. Starting a share, starting a recording or opening the window picker is often all that is needed.

The prompt was dismissed rather than answered. Clicking outside the dialog, or pressing Escape, can leave the request unresolved without recording a denial, and some apps will not ask a second time in the same session.

The app is not the thing doing the capture. Helper processes, browser based meeting tools and command line utilities are common cases. A meeting held in a browser needs the browser to hold the permission, not the meeting service. A script run from a terminal needs the terminal app or the terminal emulator in the list, not the script.

The app was moved or replaced after being granted. The permission is tied to the app's identity and location, so a copy dragged to a different folder, or a build replaced by hand rather than by an updater, can read as a different app.

Adding the app by hand is the fix in all of those cases. Click the button below the list, navigate to the app in Applications, and select it. The switch then appears and can be turned on directly.

Granting it, then making the app notice

Turning the switch on is not always the end of it, and this is where most of the remaining confusion lives.

macOS decides what an app is allowed to do when the app starts. An app that was already running when the permission was granted often keeps behaving as though it has nothing, which produces the familiar loop of switching the toggle, testing, seeing the same failure, and switching it again. Current macOS versions usually offer to quit and reopen the app at the moment the switch is flipped. When that offer is not shown, quitting the app completely and opening it again does the same job.

Quitting means quitting, not closing the window. An app with a menu bar icon and no window is still running after its last window is closed, so the reliable route is Quit from the app menu, or a check in Activity Monitor that the process has actually gone.

There is a visible confirmation that a capture is really happening, which saves a lot of guesswork about whether a permission took effect.

An orange dot next to the Control Center icon in the menu bar indicates the microphone on your Mac is in use; a green dot indicates a camera is in use; a purple dot indicates the system audio is being recorded. Source: support.apple.com, read September 27, 2026

Only one indicator is shown at a time, so a green dot during a call does not mean audio is not being captured as well. Opening Control Center shows which apps are using the microphone, camera or system audio, and that panel is the fastest way to answer whether the app that claims to be recording actually is.

The three panes that get confused with each other

Three separate permissions cover things people describe as screen sharing, and granting the wrong one explains a good share of the time lost here.

Pane What it allows Typical need
Screen & System Audio Recording Capturing the screen, or the system audio, or both Recorders, screenshot tools, meeting apps sharing a screen
Remote Desktop Access to the screen and audio through Remote Desktop Remote support and administration tools
Accessibility Running scripts and system commands to control the Mac Remote control, window managers, automation

A remote support session that shows a picture but cannot click needs Accessibility in addition to screen access. A tool that can click but shows a black screen has the reverse problem. Checking which of the two symptoms is present identifies the pane without any trial and error.

There is also a distinction between recording the screen and reading what is on it. Some window management and capture tools need the screen permission simply to learn the titles and positions of other apps' windows, because that information comes from the same interface as a capture. An app asking for screen recording is not necessarily asking to record anything, and the pane cannot express that difference.

Managed Macs behave differently

On a Mac issued by an employer or a school, this pane can stop being the place where the answer is decided.

Apple's own help page for the pane makes the split explicit. The instructions describe the switches for one person on one Mac, and then send administrators somewhere else entirely.

If you're a system administrator and want information about deploying security settings, see Apple Platform Deployment. Source: support.apple.com, read September 27, 2026

The practical meaning of that sentence is that the state of this pane on a managed Mac may have been decided by whoever deployed it, rather than by the person sitting in front of it. That explains both of the confusing outcomes people report on work machines: a meeting tool that already has access with no memory of anyone granting it, and an app that cannot be made to stick no matter how often the switch is set.

The observable check is whether the Mac carries a configuration profile, which is listed in Privacy and Security. If one is present, the useful next step is a request to whoever manages the Mac rather than further attempts at the pane. The same applies to a Mac that belongs to a household but was set up under Screen Time restrictions, since those are also decided outside this list.

On a machine where adding an app by hand does not hold, the only route left is to let the app ask for itself. That means starting the feature that needs the screen while the app is in front, and answering the dialog when it appears instead of dismissing it to deal with later.

Revoking it, and starting over

Turning a switch off in the same pane withdraws the permission, and again the app usually has to be restarted before it stops behaving as though it still has access. Removing the app from the list entirely is done with the button next to the add button, which is the cleaner option when an app has been uninstalled.

There is also a documented way to clear the answers themselves so that apps ask again from a blank slate. The privacy database that stores these decisions has a command line tool, and its manual page is short enough to be worth reading before use.

The tccutil command manages the privacy database, which stores decisions the user has made about whether apps may access personal data. One command is currently supported: reset. Reset all decisions for the specified service, causing apps to prompt again the next time they access the service. If a bundle identifier is specified, the service will be reset for that bundle only. Source: man tccutil, read September 27, 2026

The manual page's own example resets every decision for a single app by bundle identifier, which is the narrow form worth preferring. A reset that names no app clears that permission for everything on the Mac, and every app that had it will prompt again the next time it is used. On a Mac with a dozen tools involved in meetings and capture, that turns one broken app into an afternoon of dialogs.

Try the ordinary route first. Remove the single app from the list, quit it, open it, and let it ask again. That achieves what most people want from a reset without touching anything else.

The menu bar side of the same problem

Screen capture tools are, almost without exception, menu bar apps. They have no Dock presence, no window most of the time, and a single icon at the top right of the screen that holds the record button, the stop button and the recent files.

That makes the state of the menu bar part of the workflow rather than a cosmetic matter. An icon pushed off the visible strip by an app with long menus means no stop button, which during a recording is a genuine problem rather than an annoyance. Apple's own controls help to a point: the Menu Bar pane in System Settings turns the built in icons on and off, and holding Command while dragging removes or rearranges an icon.

Add an icon from System Settings: Choose Apple menu > System Settings, click Menu Bar in the sidebar (you may need to scroll down), then select the icon you want to appear in the menu bar. Source: support.apple.com, read September 27, 2026

What those controls cannot do is keep a third party icon available while taking it out of the visible row. That is the job of a menu bar organizer, and the ones worth using let a hidden icon be clicked without unfolding the whole strip, which is the difference between a recorder that can be stopped in one click and one that takes three. The comparison page sets out which tools behave that way.

What to change first

Open Privacy and Security, click Screen and System Audio Recording, and check whether the app is listed at all before touching any switch. If it is missing, add it with the button below the list, then quit the app and open it again so the new permission is read at launch. If the tool doing the recording is a menu bar app whose icon keeps disappearing behind app menus, Koffret keeps it reachable.

Frequently asked questions

Why is my app not showing in the Screen and System Audio Recording list?

The list shows apps that have been granted access, so an app that has never successfully requested it is absent rather than switched off. Start the feature that needs the screen so the request is made, or add the app by hand with the button below the list and turn the switch on there.

I granted permission but the app still records a black screen. What now?

macOS reads permissions when an app starts, so an app that was already running usually has to be restarted. Quit it from its app menu rather than just closing the window, then open it again. If the picture is still black while the sound is fine, check that the screen switch is on and not only the audio one.

Why does the prompt come back for an app that was already allowed?

The permission is tied to the identity and location of the app, so a build replaced by hand, a copy dragged to another folder, or an update applied outside the app's own updater can read as a different app. Checking the pane usually shows the older entry still listed while the new copy is absent.

Does a screenshot tool need this permission as well?

Anything that captures the screen outside the built in screenshot keys needs it, and so does anything that reads other apps' window titles and positions, because that information comes from the same interface. An app requesting screen access is therefore not always about to record anything.

Should I use tccutil to reset the permission?

Only as a last resort, and only for one app. The manual page documents resetting a single bundle identifier, which makes that app ask again. A reset that names no app clears the decision for everything on the Mac, so every capture and meeting tool will prompt again the next time it runs.

Back to all posts