Why this matters
A small rate table prevents DP40/DP80 cable labels and UHBR endpoint labels from being compared as if they were identical naming systems.
Decision sequence
- Identify the endpoint UHBR class
- Translate it to the four-lane raw rate
- Apply encoding, video timing, and compression rules before judging a display mode
What Heliacal Dawn adds
This page connects 3 primary/originator sources to a bounded engineering decision. The analysis separates mechanism, worked examples, failure boundaries, and verification steps; it does not imply hands-on testing unless that evidence is explicitly declared.
Engineering depth
6 evidence-led sectionsTerminology and scope
For “DisplayPort UHBR10 vs UHBR13.5 vs UHBR20: raw link-rate reference”, the useful model is not a single feature flag. Treat the system as source timing/link capability → transport mode and lane rate → cable/link class → display input and decoding capability. The question “Translate a DisplayPort UHBR label into its per-lane and four-lane raw signaling rate” is answered only after the relevant capability survives every layer. This prevents a common category error: promoting a connector shape, certification mark, protocol generation, or maximum number into an end-to-end guarantee.
Worked reading of a real specification claim
Consider a buyer following this page's sequence: first “Identify the endpoint UHBR class”, then “Translate it to the four-lane raw rate”, then “Apply encoding, video timing, and compression rules before judging a display mode”. Suppose the first check passes and the product headline looks ideal, but the second check exposes a lower capability in the transport path. The correct conclusion is not “almost compatible”; the second layer is the current bottleneck, so the headline ceiling is unavailable until that layer changes. For this page, apply that boundary specifically to “Translate a DisplayPort UHBR label into its per-lane and four-lane raw signaling rate” and do not generalize it to an unrelated capability axis.
Historical wording versus current capability
A useful counterexample is a configuration in which the most impressive label is real but irrelevant. The source can legitimately advertise the higher class while the receiving endpoint supports only the lower class, or the endpoint can support the higher class while the path between them does not. In both cases every individual marketing statement can be true while the combined system still operates below the headline maximum. For this page, apply that boundary specifically to “Translate a DisplayPort UHBR label into its per-lane and four-lane raw signaling rate” and do not generalize it to an unrelated capability axis.
UHBR13.5 — This class is the reason a DP54 label can matter independently from DP40 or DP80.
Where a reference ceiling stops predicting product behavior
The primary-source evidence on this page narrows the technical possibility space, but product-specific implementation can still change the outcome. Firmware policy, thermal limits, optional feature support, region-specific spectrum or SKU differences, cable length and signal integrity, and vendor power-management choices are examples of factors that can sit outside a standards body's high-level capability statement. For this page, apply that boundary specifically to “Translate a DisplayPort UHBR label into its per-lane and four-lane raw signaling rate” and do not generalize it to an unrelated capability axis.
UHBR20 — A cable or endpoint that does not support UHBR20 prevents an end-to-end UHBR20 link.
How to verify a current product or document
Use an evidence ladder. Start with the exact receiving requirement, then verify identify the endpoint uhbr class. Next verify translate it to the four-lane raw rate, using the model or certification record that matches the exact product rather than a family name. Only then verify apply encoding, video timing, and compression rules before judging a display mode. This order makes the first failing layer visible instead of burying it under a successful fallback. For this page, apply that boundary specifically to “Translate a DisplayPort UHBR label into its per-lane and four-lane raw signaling rate” and do not generalize it to an unrelated capability axis.
Raw rate vs display payload — Display transport consumes capacity for encoding and timing, and DSC can change the required payload.
Reference boundary: specification fact versus product behavior
The source set for this page contains 3 primary/originator references. Together they support the specification and certification statements summarized here; they do not represent a bench test of every commercial implementation. Heliacal Dawn's contribution is the mapping from those sources into a decision sequence and explicit uncertainty boundary, not a claim of first-hand measurement. For this page, apply that boundary specifically to “Translate a DisplayPort UHBR label into its per-lane and four-lane raw signaling rate” and do not generalize it to an unrelated capability axis.
Raw rate vs display payload — Use the table as the first layer of a display-mode calculation, not the final compatibility answer.
Primary sources reviewed
- VESA — DisplayPort UHBR cable certification
VESA UHBR certification material provides the UHBR10/UHBR13.5/UHBR20 and DP40/DP80 context. - VESA — DisplayPort 2.1a / DP54 announcement
VESA DisplayPort update material provides DP54 and current link-class context. - VESA — DisplayPort Alt Mode 2.0 for USB-C
DisplayPort Alt Mode material is used to keep USB-C transport context separate from the raw DisplayPort link class.
Related next questions
Change history
2026-08-29 — Materially reworked to improve decision usefulness: canonical titles were separated from distribution hooks, page structures were diversified by user job, original decision visuals were added, and selected pages gained deterministic interactive utilities.