HDCP Explained: Versions, Errors and How to Fix Them

You plug a new streaming stick into your TV, open a film and get a black screen with a message like “HDCP unauthorized” or “Your display does not support HDCP”. Or 4K content quietly drops to 1080p the moment you add a soundbar. These problems have one thing in common: HDCP, the copy-protection system built into HDMI and DisplayPort. This is HDCP explained without the jargon: what it checks, why it fails and how to get the picture back.

This guide explains what HDCP is, what the version numbers mean, why errors happen, and how to fix them step by step.

What HDCP is

High-bandwidth Digital Content Protection (HDCP) is a copy-protection system that encrypts the video signal travelling over a cable between a source (a streaming stick, laptop, console or Blu-ray player) and a sink (a TV, monitor or projector). It was created by Intel in the early 2000s and is now licensed by Digital Content Protection LLC.

Where DRM such as Widevine protects video inside the device, HDCP protects it on the way out. Studios require both. A streaming licence may say, for example, “4K is allowed only on hardware-protected devices with HDCP 2.2 output”. If you want the in-device side, see Widevine L1 vs L2 vs L3.

How HDCP works, briefly

When you connect two HDCP devices, they perform a handshake:

1. Authentication. The source asks the sink to prove it holds valid HDCP keys issued by the licensing body.
2. Key exchange. Both sides agree on a session key.
3. Encryption. The source encrypts the video signal. The sink decrypts it for display.
4. Revocation checks. Devices whose keys have been leaked can be put on a revocation list delivered with protected content.
5. Repeaters. Devices in the middle, such as AV receivers, soundbars and HDMI switches, must also support HDCP and pass the handshake along. The source checks the entire chain.

If any link in the chain fails, the source either blocks protected content, shows an error, or drops to a lower resolution that has weaker requirements.

HDCP versions

The important point: HDCP 2.2 is not compatible with HDCP 1.4 at the 2.2 level. A 4K source that needs 2.2 cannot get it through a 1.4-only receiver, so it falls back or refuses.

Many 4K TVs have several HDMI ports, but only some of them support HDCP 2.2. Look for labels such as “HDCP 2.2”, “4K 60Hz” or a specific port number in the manual.

Common HDCP problems and what causes them

Black screen or “HDCP error” message

The handshake failed. Causes include a loose cable, an old receiver or switch in the chain, a port that does not support the required version, or a device that has not finished starting up.

4K content plays in 1080p only

Something in the chain supports only HDCP 1.4. The source detects it and limits protected content to HD. Soundbars and AV receivers are the usual suspects.

Protected video goes black on an external monitor

Laptops check HDCP on every connected display. A monitor, USB-C dock or cheap adapter without HDCP support causes streaming apps to block video on that screen. Sometimes only the external screen goes black while the laptop screen works.

Capture card or screen recorder shows black

Capture cards are designed not to accept HDCP content, and sources refuse to send protected video to them. This is deliberate. Game capture usually works because many consoles let you disable HDCP for games, but streaming apps will not play in that mode.

Flicker, dropouts or “no signal” every few minutes

Often a marginal cable or connector that passes 4K bandwidth sometimes but not always. The handshake repeats after each dropout, which looks like HDCP trouble.

How to fix HDCP errors, step by step

Work through these in order. Most problems are solved in the first three steps.

1. Power-cycle everything in the right order. Turn off and unplug the TV, receiver or soundbar, and the source. Wait a minute. Power on the TV first, then the receiver, then the source. This resets stuck handshakes.
2. Connect directly. Plug the source straight into the TV, bypassing receivers, switches and splitters. If it works, the device in the middle is the problem.
3. Use the right HDMI port. On 4K TVs, use the port labelled HDCP 2.2, ARC/eARC or 4K 60Hz. Enable “HDMI Enhanced Format”, “Input Signal Plus”, “UHD Color” or similar in the TV settings for that port (the name varies by brand).
4. Replace the cable. Use a certified Premium High Speed (for 4K60) or Ultra High Speed (for HDMI 2.1) cable. Long or cheap cables are a frequent cause.
5. Update firmware. TVs, receivers, soundbars and streaming devices regularly fix HDCP bugs in updates.
6. Check the receiver or soundbar specs. If it only supports HDCP 1.4, connect the source directly to the TV and send audio back to the receiver using ARC or eARC.
7. Laptops and PCs: update the graphics driver, use a direct HDMI or DisplayPort cable instead of a dock or adapter, and make sure the monitor supports HDCP (most modern monitors do; many cheap portable monitors and some adapters do not).
8. Remove splitters and HDMI extenders unless they state HDCP 2.2 compliance.

HDCP on computers

On Windows and macOS, the operating system and graphics driver handle HDCP. Browser DRM and streaming apps ask the system whether the current output is protected. Things that commonly break it:

• USB display adapters that use DisplayLink-style drivers.
• Very old monitors connected by DVI or VGA adapters. VGA has no HDCP at all.
• Virtual machines and remote desktop sessions, which are treated as unprotected outputs.
• Screen-mirroring software.

If protected video works on the laptop screen but not on the external display, the external chain lacks HDCP. The fix is usually a direct cable to a modern monitor.

What this means for streaming developers

If you build players or streaming services, HDCP shows up through DRM licence policies and key status:

• In Widevine, PlayReady and FairPlay licences, you can require a minimum HDCP version per track. A typical policy is: SD with no HDCP requirement, HD with HDCP 1.4, UHD with HDCP 2.2.
• In browsers, EME reports a key status of output-restricted when the current output does not meet the licence’s HDCP requirement. Handle it by switching to a lower rendition rather than showing an error. The EME guide shows how.
• The HDCP Policy Check API, proposed for EME, lets a player ask in advance which HDCP version is available. Support is limited, so do not rely on it alone.
• Always give users a clear message, such as “Your external display does not support the protection needed for HD. Try a direct HDMI connection.” It saves support time.

HDCP and wireless casting

Chromecast, AirPlay and Miracast handle protection differently from a cable. Chromecast and AirPlay devices receive the stream or keys directly and then output over their own HDMI connection with HDCP. That means the Chromecast or Apple TV’s own HDMI chain to the TV must pass HDCP checks. Miracast screen mirroring from Windows or Android often cannot carry protected content at full quality, which is why some apps block playback when mirroring.

A quick HDCP checklist by device

Streaming sticks (Fire TV, Chromecast, Roku, Apple TV): plug directly into a TV HDMI port that supports HDCP 2.2 for 4K. Avoid HDMI extenders unless you need them. If the stick came with an HDMI extender cable, use the one from the box.

Game consoles: PlayStation and Xbox use HDCP for streaming apps and protected discs. Most let you disable HDCP for games only, which is useful for game capture, but you must re-enable it to use streaming apps.

Laptops: use a direct HDMI or DisplayPort cable to the monitor. If you rely on a USB-C dock, check the dock maker’s page for HDCP support.

Projectors: older and budget projectors may only support HDCP 1.4, which limits streaming to 1080p. That is usually fine given their resolution.

AV receivers and soundbars: check the spec sheet for HDCP 2.2 or 2.3 on every HDMI input you plan to use. If not supported, connect the source to the TV and use eARC for audio.

Why HDCP still matters

Some people see HDCP as an annoyance that punishes paying customers. The fact is that studios will not license 4K content without it, and the rules are written into contracts. For viewers, understanding the chain makes errors easy to fix. For developers, handling HDCP gracefully in your player turns a frustrating black screen into a lower-quality stream with a clear explanation.

Related reading

HDCP is the last link in a longer protection chain. To see how the rest of it works, read what is Widevine DRM for the licence side, why Netflix plays in low quality on PC for browser-specific limits, and how to check your Widevine security level if a phone or TV box is the device in question. Our DRM support checker is a quick way to see what a computer’s browser supports before you start swapping cables.

Summary

HDCP encrypts video on the cable between your device and your screen, and every device in the chain has to support the version the content requires. HDCP 2.2 or newer is needed for 4K streaming. Most errors come from older receivers, the wrong HDMI port, poor cables, adapters and capture devices. Power-cycle, connect directly, use the right port and cable, and update firmware, and nearly every HDCP problem goes away.