FHD (1920×1080) at 360 Hz — 17.92 Gbps

Share of the limit used

• HDMI 1.48.16 Gbps · 219.6%too much
• DisplayPort 1.217.28 Gbps · 103.7%too much
• HDMI 2.014.4 Gbps · 124.4%too much
• DisplayPort 1.425.92 Gbps · 69.1%fits
• HDMI 2.142.67 Gbps · 42%fits
• DisplayPort 2.177.37 Gbps · 23.2%fits

Of HDMI 2.0’s 18 Gbps, video gets 14.4. The link ships eight bits inside ten (8b/10b). HDMI 2.1 packs sixteen bits into eighteen, DisplayPort 2.1 packs 128 into 132. This table therefore compares against the usable video share, not the headline figure.

Borderline cases are not called a pass

A real signal does not carry only the visible pixels: blanking intervals sit between lines and between frames, and in current timings they add about 5 %. So when a figure lands above 95 % of a limit it is marked borderline rather than a pass — that is the range where cable quality and specific hardware start to decide.

Compression changes the answer

Display Stream Compression cuts the payload to roughly a third and the standards call it visually lossless. These figures assume no compression, so a combination marked as too much will often work anyway if both ends support DSC — support varies by device.

Nearby refresh rates

Same resolution, other rates

Same rate, other resolutions

A new cable alone may not do it

The bandwidth you get is the narrowest of three: source, display, and cable. A graphics card that speaks HDMI 2.1 still stops at 2.0 if the monitor input is 2.0. For the cable itself, look at the certification tier rather than a version number — Ultra High Speed for HDMI, DP80 and similar for DisplayPort.

How to read this

• Data per second = width × height × refresh rate × bits per pixel (24 at 8-bit).
• The comparison is against the usable video share, not the headline bandwidth.
• Above 95 % of a limit it is marked borderline, since blanking can push it over.
• These figures assume no DSC. With compression the payload drops to about a third.