Protected Content Can't Be Recorded: Why

You start a screen recording, play something on Netflix or ESPN+, and stop. The file plays back as a black rectangle where the video should be — sometimes with audio, usually without. Or the recorder refuses outright: "Protected content can't be recorded due to copyright or privacy restrictions."

Nothing is broken. The recording worked exactly as designed. A content protection system detected the capture and replaced the protected frames with black before they ever reached your recorder.

This explains the machinery, what each error message actually means, and where the line sits legally. It does not explain how to get around it, because the honest answer to that question is that you should not, and the second-honest answer is that the methods circulating online largely do not work.

The one-paragraph version

Streaming services encrypt video and hand decryption to a DRM system built into your operating system and GPU. That system will only decrypt into a protected memory path the OS refuses to expose to screen capture. When capture is detected, the compositor substitutes black for those pixels. The recorder never sees the frame. There is nothing to recover, no setting to flip, no quality tradeoff to accept — the data is simply not in the buffer you are recording from.

The four systems you will meet

Different platforms use different DRM, and the error you see depends on which one is in play.

FairPlay — Apple

Apple's DRM, used by Apple TV+, Apple Music video, and any app that adopts it. On macOS and iOS it hooks into the window server: a video layer can be marked as protected, and ScreenCaptureKit (and everything built on it) receives black for that layer's region. The rest of the screen records normally, which is why you get a black rectangle rather than a black file.

Widevine — Google

Used by Netflix, Disney+, Amazon Prime Video, Spotify and most services on Android and in Chrome. Widevine has three security levels:

• L1 — decryption and decoding happen inside the device's trusted execution environment. Frames never touch memory the OS can read. This is what phones and modern Macs use.
• L2 — decryption in the TEE, decoding outside it.
• L3 — everything in software. Content owners typically cap L3 playback at 480p, which is why Netflix in some browsers looks soft.

Queries like widevine protected content screen capture black screen land here. The black screen at L1 is not a policy applied after the fact; it is a consequence of the frames living somewhere the capture API cannot reach.

PlayReady — Microsoft

Microsoft's equivalent, used by some services on Windows and Xbox. Windows exposes an explicit "protected content" flag through the Windows Graphics Capture API; a window carrying it captures as black. Developer documentation covers this directly, which is why windows graphics capture protected content black screen documentation is a real search.

HDCP — the cable

The odd one out, because it protects the wire rather than the software. High-bandwidth Digital Content Protection encrypts the signal between your device and your display. It is why an external monitor or a capture card sometimes shows black while the built-in display is fine, and why some HDMI splitters break playback entirely.

HDCP failures produce their own distinct symptom: playback works on the laptop screen but not on the external monitor, or a "drm restricted output" style error appears when you connect a second display.

What each error message actually means

The audio row is worth dwelling on. A surprising share of "DRM blocked my recording" reports turn out to be a missing audio permission on a recording that was never protected at all. Test with a non-protected video first — a YouTube clip, a local file. If that also records silent, the problem is permissions, not DRM.

Why the usual suggestions do not work

Search results promise fixes. Here is what each actually does.

Turning off hardware acceleration. This can drop a browser from Widevine L1 to L3, and L3 playback is decoded in software. It sometimes changes the symptom. It also caps resolution at 480p on most services, and services increasingly detect and refuse the downgrade. It is not a fix; it is a downgrade that occasionally leaks.

A different recorder. Every screen recorder on macOS uses ScreenCaptureKit or an older equivalent. Every one on Windows goes through the graphics capture stack. They all receive the same black frames, because the substitution happens below all of them. An app claiming otherwise is either recording something else or lying.

A capture card. This moves the problem to HDCP, which is the layer specifically designed to stop it. Devices marketed as "HDCP strippers" exist; buying one to circumvent protection is precisely the activity anti-circumvention law prohibits.

Filming the screen with a phone. Not a technical circumvention, so the DMCA anti-circumvention provision does not apply — but the recording is still a reproduction of a copyrighted work, and redistributing it is still infringement. Legal for a personal reference clip in many places, not legal to publish.

Browser extensions and downloader sites. The functional ones circumvent DRM, which is the illegal part. The rest are ineffective, or malware, or subscription traps. This category has an unusually high concentration of scams precisely because the demand is high and the honest supply is zero.

The legal line, briefly

This is not legal advice, and jurisdictions differ. But the shape is consistent enough to state.

In the United States, DMCA §1201 prohibits circumventing a technological measure that controls access to a copyrighted work. Notably, it prohibits the act of circumvention itself — separately from any infringement that follows. You can violate §1201 without ever sharing the file.

The EU Copyright Directive Article 6 and the UK CDPA §296ZA take the same structure. Australia, Canada and Japan all have analogous provisions.

Fair use and fair dealing are defences to infringement. They are not exemptions from anti-circumvention rules. This surprises people: you can have a legitimate fair-use purpose for the clip and still be liable for the technical act of getting it. Courts have generally not accepted personal-use copying of streaming video as an exemption.

The practical read: for personal, private viewing the enforcement risk is low, but the act is prohibited, and the tooling to do it is where the actual danger lives.

What you can record

The frustrating part of a black rectangle is that the legitimate use case is usually mundane. Here is what works.

Your own content. Anything you produced, uploaded, or hold the rights to. Your own Vimeo uploads, your own course videos, your own footage in a streaming app's preview.

Non-protected video on the same services. Trailers, previews, and promotional clips are typically unprotected. If you need a reference frame from a show, the trailer often contains it.

Screenshots via official features. Some services provide share/clip features precisely because people want them. Spotify Canvas, YouTube clips, Twitch clips. These exist and are sanctioned.

Everything that is not a streaming app. This is the one people forget. The black rectangle covers a protected layer, not the screen. Your app, your terminal, your browser on a normal page, a video call, a game — all record normally, in the same session, even while a protected window is open elsewhere.

Licensed footage. For a commercial project, licensing from the rights holder or a stock library is cheaper than the alternative and does not carry the risk.

Recording everything that is not protected

If you landed here because a recording came out black and the actual job was a demo, tutorial or bug report, the practical move is to record the thing you need and leave the protected window out of frame.

Screenify Studio is a macOS recorder built for that kind of capture — pick a window or region rather than the whole display, so a protected surface elsewhere on screen never enters the recording. Auto-zoom follows your clicks so small UI stays readable, captions are generated on-device, and the mockup layer stages the result without a second app. Free tier covers 1080p up to five minutes with a watermark.

It cannot record protected content either. No recorder can, and any that claims to should be treated with suspicion.

Troubleshooting: is it actually DRM?

Work through this before assuming protection.

Record a non-protected video first. A local MP4 or a YouTube page. If that is also black, it is not DRM — it is a permission or GPU issue.

Check screen recording permission. On macOS, System Settings → Privacy & Security → Screen & System Audio Recording. A revoked permission produces a black or empty recording that looks identical to DRM blocking. See our guide on fixing macOS screen recording permission.

Try the built-in display only. Disconnect external monitors. If it works, the problem was HDCP on the output, not DRM on the content.

Test in a different browser. A black recording in Chrome but not Safari points at Widevine level differences rather than a universal block.

Check whether the recording stops rather than blacks. A recording that ends early is a different failure — see screen recording stops by itself.

Look at file size. A black recording that is tiny suggests the encoder saw uniform frames — consistent with DRM. A normal-sized black file suggests something else, like a wrong display captured.

FAQ

Why does my screen recording of Netflix show black? Netflix uses Widevine DRM. At security level L1 the decrypted frames live in protected memory that screen capture APIs cannot read, so the compositor substitutes black. This is intended behaviour, not a bug in your recorder.

Is it illegal to screen record Netflix? Circumventing the DRM to do it is prohibited under DMCA §1201 in the US and equivalent laws elsewhere, independent of what you do with the file. Recording your screen in general is perfectly legal; the protection layer is what changes the analysis.

Why can I record on my laptop screen but not an external monitor? That is HDCP, not the content DRM. The protection applies to the display link. Some adapters, splitters and older monitors fail HDCP negotiation and the source blacks the output.

Does turning off hardware acceleration fix it? It changes the Widevine security level in some browsers, which changes the symptom. It also caps playback resolution and is increasingly detected. It is not a reliable fix and it is not a legitimate one.

Can any screen recorder capture DRM content? No. Recorders on macOS all go through ScreenCaptureKit; on Windows through the graphics capture stack. Both receive the substituted black frames. Software advertising otherwise is generally ineffective or malicious.

Why is my recording black but the audio is there? Video and audio are protected separately, and some services protect only the video path. It can also mean the video failed for an unrelated reason while audio recorded normally.

What does "protected content can't be recorded due to copyright or privacy restrictions" mean? The operating system told the recording app up front that the target contains a protected surface, so the app refused rather than producing a black file. Same cause, earlier and clearer failure.

Can I record a streaming service for a class or review? Fair use may cover the use, but it does not exempt the circumvention. Where possible, use official clip features, licensed footage, or trailers, which are typically unprotected.

The short version

The black rectangle is the system working. Frames are decrypted into memory your recorder is not permitted to read, and no setting, recorder or codec changes that. The fixes circulating online are downgrades, scams, or illegal, usually in that order of likelihood.

What is worth your time is the other 95% of your screen, which records fine. If the actual task was a demo or a walkthrough, capture the window you need and let the protected one stay out of frame.

Related reading: iPhone screen recording shows black? DRM explained · Fix macOS screen recording permission · Why screen recordings are so large