“HDMI 2.1” on a spec sheet tells you a port uses a newer signaling scheme capable of up to 48 Gbps — it does not tell you what rate that specific port, cable, or monitor actually implements. Two devices can both be labeled HDMI 2.1 and support genuinely different maximum bandwidths, because the HDMI Forum allows partial adoption of the 2.1 feature set.
Two different encoding schemes, not just a faster HDMI 2.0
HDMI up through version 2.0 uses TMDS (Transition-Minimized Differential Signaling) encoding, which packages every 8 bits of data into a 10-bit symbol for transmission — a fixed 20% overhead. HDMI 2.0’s raw link capacity is 18 Gbps, which works out to 14.4 Gbps of actual usable payload after that overhead.
HDMI 2.1 introduced FRL (Fixed Rate Link), a different encoding scheme (16b/18b) with roughly 11% overhead instead of 20%, running across up to 4 lanes at several selectable per-lane rates. This is the mechanism that makes the 48 Gbps ceiling possible — it’s not the same TMDS scheme just clocked faster.
The HDMI Forum does not require every “HDMI 2.1” device to implement the maximum FRL rate — a device can be legitimately labeled HDMI 2.1 while implementing a lower FRL lane count or rate than the 48 Gbps ceiling, or in some cases, none of FRL’s higher tiers at all beyond baseline compliance. Unless a specific device’s documentation states its exact implemented FRL rate, there’s no reliable way to back that number out from the version label alone. CompatSense has not found a verified, device-specific FRL rate for any monitor in its current dataset — not because the devices don’t have one, but because manufacturers routinely don’t publish it.
What CompatSense does when the FRL rate isn’t documented
Rather than assume a device gets the full 48 Gbps just because it’s labeled HDMI 2.1, CompatSense’s engine falls back to the verified HDMI 2.0 TMDS floor (14.4 Gbps payload) — because HDMI’s backward-compatibility requirement guarantees that floor for any HDMI 2.1 device, regardless of what higher FRL tier it may or may not implement. If a mode fits within that floor, it’s shown as fully compatible whether you request “HDMI 2.0” or “HDMI 2.1,” because the actual computation is identical either way. If a mode needs more than the TMDS floor and no higher verified rate exists for that device, the result says so explicitly instead of guessing.
A Gigabyte M32U at 3840×2160@60Hz, 8-bit RGB (594 MHz pixel clock, CTA-861 VIC 97) requires 14.26 Gbps — which fits inside HDMI 2.0’s verified 14.4 Gbps TMDS payload floor (18 Gbps raw link capacity, minus 20% 8b/10b encoding overhead). Asking whether this works over “HDMI 2.0” or “HDMI 2.1” produces the identical fully-compatible result, because without a verified FRL rate for this device, both requests are evaluated against the same verified floor.
Working through real numbers
These figures come directly from the bandwidth calculator — the same engine code, not a separate estimate.
| Mode | Required (uncompressed) | HDMI 2.0 payload (14.4 Gbps) | Result |
|---|---|---|---|
| 1920×1080@60, 8bpc RGB | 3.56 Gbps | Fits | Fully compatible over HDMI 2.0 or 2.1 |
| 3840×2160@60, 8bpc RGB | 14.26 Gbps | Fits (just) | Fully compatible over HDMI 2.0 or 2.1 (Gigabyte M32U, verified) |
| 3840×2160@60, 12bpc RGB (HDR) | 21.38 Gbps | Doesn’t fit | Needs FRL or DSC — see below |
| 3840×2160@120, 8bpc RGB (standard-derived estimate) | ≈25.8 Gbps | Doesn’t fit | Needs FRL or DSC |
The 12-bit HDR case above is a real, verified device scenario: the LG 27GP950-B at 3840×2160@60Hz 12-bit color exceeds the HDMI 2.0 TMDS floor. Its uncompressed requirement (21.38 Gbps) would fit within HDMI 2.0’s floor if DSC could reduce it — the compressed figure works out to well under 14.4 Gbps — but LG’s own specifications document DSC support on this monitor’s DisplayPort input only, not its HDMI 2.1 input. With no DSC fallback on HDMI and no verified FRL rate for this model, the honest result is that CompatSense can’t currently confirm this exact mode over this monitor’s HDMI input — not “incompatible,” but “not enough verified information to say.”
What this means practically
- An “HDMI 2.1” label on a cable, port, or monitor is not by itself proof that a specific high-bandwidth mode (4K120, 4K144, high-bit-depth HDR) will work.
- 4K at 60Hz with standard 8-bit color comfortably fits within the verified HDMI 2.0 floor on real hardware — the “you need HDMI 2.1 for basic 4K60” claim is often overstated for typical desktop use.
- 4K at 120Hz or higher, or high-bit-depth HDR at 4K60, genuinely needs either a verified higher FRL rate or DSC support across the whole chain — and DSC support is not universal even within a single monitor’s inputs, as the 27GP950-B shows.
- If a manufacturer publishes the exact FRL lane count/rate their port implements, that changes what can be verified — this is a documentation gap in the industry, not a limitation specific to any one product.
Enter your own resolution, refresh rate, and color depth to see exactly where it lands against HDMI’s verified transport floor.
Open the bandwidth calculatorSources
- HDMI Specification Technology Overview / HDMI Forum Releases Version 2.1 of the HDMI Specification
- HDMI TMDS vs FRL: What’s The Difference And Why It Matters
- Gigabyte M32U official specifications; CTA-861 (VIC 97)
- LG 27GP950-B official specifications