HDCP (High-bandwidth Digital Content Protection) is a copy protection technology that encrypts video and audio as it travels over a cable between a source and a display. It is a specification originally developed by Intel Corporation to protect digital entertainment content across digital interfaces, and it is licensed by Digital Content Protection LLC (DCP). If EDID is the handshake that tells a source what a display can do, HDCP is the handshake that decides whether protected content is allowed to appear on that display at all.

What HDCP Actually Does

The specification defines three mechanisms: authentication of HDCP receivers to their upstream transmitter, revocation of receivers that DCP LLC determines to be invalid, and encryption of the audiovisual content flowing over the protected interface. In plain terms, your streaming box (transmitter) challenges your monitor (receiver) to prove it holds valid licensed keys. Only after both sides derive a shared secret does the encrypted video start flowing. HDCP is applied when connecting sources such as set-top boxes, streaming devices, and Blu-ray players to sinks such as TVs and monitors over digital interfaces including HDMI, DVI, DisplayPort, MHL, and Miracast.

The Version Landscape

This is where most real-world confusion (and most support tickets) originate:

1. HDCP 1.4: the legacy version tied to the DVI and early HDMI era, still fine for 1080p content.
2. HDCP 2.2: the jump to a stronger cryptosystem for the 4K era. The 2.x family uses standards-based RSA public-key authentication and AES-128 encryption, and every device in the HDMI chain, including the TV, AV receiver, and anything in between, must support HDCP 2.2 to stream 4K Ultra HD or HDR content. If even one device does not, playback drops to 720p or 1080p.
3. HDCP 2.3: the latest version, succeeding 1.4 and 2.2. HDCP 1.4 roughly tracked HDMI 1.3/1.4, HDCP 2.2 arrived alongside HDMI 2.0, and HDCP 2.3 is the relevant version in the HDMI 2.1 era.

An important engineering nuance: HDCP 2.2 support cannot be added via firmware update because it requires dedicated hardware in the transmitter and receiver silicon. This is why "why won't my older 4K TV play Netflix in 4K" is usually a silicon problem, not a settings problem.

The Locality Check

HDCP 2.x added a feature that matters a lot in pro-AV and extender scenarios: a locality check, where the source must receive a response from the receiver within 20 milliseconds. The intent is to block long-distance retransmission of protected content, but the side effect is that poorly designed HDMI-over-IP extenders and wireless links can fail authentication purely on latency.

Why HDCP Matters in Real-World Engineering

From production and field-support experience, HDCP failures cluster into predictable patterns:

1. The weakest-link rule: every component in the chain, including the source, cables with active electronics, splitters, and the display, must be certified. One non-compliant link results in error messages or a blank screen.
2. Version mismatch downgrades: a 2.2 source into a 1.4-only monitor typically means 1080p output or a black screen, depending on how the content is flagged.
3. Repeater complexity: HDCP receivers may also act as repeaters, serving as downstream transmitters passing content to additional receivers, which is exactly what docks, AVRs, and KVM switches do. Each hop is another authentication that can fail.
4. Key provisioning at the factory: like EDID, HDCP keys are programmed into device silicon or secure storage during manufacturing, and key handling is governed by the DCP license, so this step is audited far more strictly than typical firmware flashing.

Bottom line: HDCP is the gatekeeper for protected content on digital displays. It does not improve picture quality; it decides whether the picture appears at all. When a screen goes black only on Netflix or a Blu-ray but works fine on a desktop, the HDCP handshake is the first suspect any display engineer will investigate.