What Screen Capture Can and Cannot Do

You drag a rectangle around a video, press record, play it, and stop. The recording is a black box with audio. Nothing crashed, no error appeared, and the app did exactly what macOS told it to do.

Screen capture on a Mac looks simple from the outside and is full of rules that only show up when you hit them. Here is an honest account of what the system permits, what it refuses, and why a tool that is upfront about the refusals is more useful than one that pretends they do not exist.

The permissions the system actually requires

macOS does not let an app read your screen because the app asked nicely in code. The user grants it, in System Settings, per app, and the app cannot grant it to itself.

• Screen and System Audio Recording: required to capture anything on screen or the audio the system is playing. Without it there is no capture at all, not a degraded one.
• Automation: a separate grant, required for an app to ask a browser what page is open in the active tab. Reading a window's title is not the same as reading its content, and macOS treats the second as a different level of trust.
• A recent OS: the capture APIs move. Reel's window and area recording requires macOS 15 or later, which is a real constraint rather than a preference.

The practical consequence is that setup is not optional and cannot be skipped by a clever installer. If a capture tool works on the first launch with no prompts, it is either already been granted access or it is not doing what you think.

Protected video can refuse to be recorded

This is the one that surprises people. Some video is protected at a layer below the app. When it is, the system can hand back a black frame instead of the picture, and no amount of application logic changes that outcome.

It is not a bug, and it is not an app that needs a better version. It is the protection working. The honest response from a tool is to tell you that capture may be blocked and let you find out quickly, rather than producing a file you discover is useless an hour later.

If you are evaluating capture software, treat any claim of universal capture as a red flag. The claim is either false or describes something you should not be doing.

A page address is not a promise

Browser page detection works by matching a window title and reading the active tab's URL. That gives an app a link. A link is not a downloadable file.

Whether the original can actually be retrieved depends on the site's restrictions, whether the content sits behind a login, and whether the player has changed since the downloading tool last understood it. All three are outside the app's control and all three change without notice.

The design question is what to do about that. Reel checks whether a source can be downloaded before it queues the job, and if it cannot, your selection stays ready to record instead. The check is quick and the fallback is honest. The alternative, queuing everything and failing later, wastes the one thing you were trying to save.

What the app can and cannot see on screen

A capture tool sees pixels and window boundaries. It does not see structure. Reel does not recognize video boundaries from screen pixels, which means it cannot look at a page and decide by itself which rectangle is the player.

That matters on a page with several videos. The desktop picker can select a window or a rectangle you draw, which is enough most of the time. For picking one specific player element, Reel offers an optional companion extension for Chrome-family browsers that can select an HTML video player, a YouTube watch or Shorts link, or an embedded YouTube or Vimeo player. There is no Safari companion.

Two capture modes behave differently once recording starts. Window capture follows the window you selected, so moving it is fine. Region capture stays in the rectangle you drew, so anything that moves out of the rectangle is gone. Neither one goes back in time: a recording includes only what plays after you start it.

System audio is not the same as "this video's audio"

macOS gives an app the system's audio output. It does not give an app one application's audio stream isolated from the rest. If a notification chimes, a song is playing in another tab, or a call is open in the background, that goes into the recording with everything else.

The fix is unglamorous and reliable: pause unrelated audio before you record. Worth stating clearly in the other direction too, because people assume the worst about capture tools. In Reel the microphone stays off. A snapshot of the screen is taken when you open the picker so you can choose a target, and recording begins only when you choose to record.

Limits, and how to judge a tool by them

Capture has ceilings, and finding them at hour three is an unpleasant way to learn. In Reel, downloads target up to 1080p with a 5 GB limit. Recordings stop at four hours or roughly 5 GB, whichever comes first.

Numbers like these are a feature of a tool's documentation, not a weakness of the tool. Every capture system has them. The difference is whether you were told.

Given all of that, the useful questions to ask of any capture tool are not about feature lists. They are:

• Does it tell you what it cannot do, before you try? Checking a link before queuing a download is a small thing that reflects a larger attitude.
• Does it degrade sensibly? When a download is impossible, does recording remain available as a path, or do you start over?
• Is it clear about permissions? A tool that explains why it needs Automation access is easier to trust than one that prompts and moves on.
• Does it state its limits in units? Resolutions, size caps, and durations in plain numbers are a sign that someone measured.

The takeaway

Screen capture is a negotiation with the operating system, the browser, and the site, and you will lose some of those negotiations. The tools worth using are the ones that tell you which negotiation failed and leave you a working second option, rather than the ones that imply the negotiation never happens. If you want to talk through whether a capture workflow fits what you are trying to keep, start here.