Quick answer: DisplayPort 1.2 runs four lanes at HBR2, 5.4 Gbit/s each, for 21.6 Gbit/s raw and 17.28 Gbit/s of payload after 8b/10b encoding. That carries 4K60 at 8 bit 4:4:4, or two 1080p60 screens through multi-stream transport, and it supports audio and daisy chaining. It cannot do 4K60 at 10 bit without subsampling, and it predates display stream compression, so 4K120 is out of reach. Any cable rated for HBR2, which includes most DisplayPort cables sold today, is sufficient.
Version numbers on monitors and cables are marketing shorthand; what matters is the link rate the two ends negotiate. A DP 1.2 source and a DP 1.4 monitor will run at HBR2 and behave exactly like a 1.2 link, which is fine for 4K60 and frustrating for anyone expecting 4K120 from the newer label.
The link budget
HBR2 and its payload
HBR2 is 5.4 Gbit/s per lane over four lanes. The 8b/10b encoding costs 20 percent, leaving 17.28 Gbit/s for video, audio and protocol overhead. A 4K60 8-bit 4:4:4 signal needs 12.54 Gbit/s, so there is room for audio and for a second stream at lower resolution.
What does not fit
4K60 at 10 bit 4:4:4 needs 15.68 Gbit/s, which fits, but 4K60 at 12 bit or 4K120 does not. Without DSC, the only way to keep 10 bit at 4K60 is chroma subsampling, which some monitors accept and others refuse. That is why 10-bit panels often report 4K60 at 4:2:2 on a 1.2 link.
Configurations and what they carry
| Configuration | Payload | Typical use | Limitation |
|---|
| 4 lanes, HBR2 | 17.28 Gbit/s | 4K60 8 bit | No 4K120 |
| 2 lanes, HBR2 plus USB 3 | 8.64 Gbit/s | 1440p60 | 4K60 needs subsampling |
| MST, two sinks | Shared | 2 x 1080p60 | Hub required |
| MST with one 4K | Shared | 4K30 plus 1080p60 | Budget split |
MST and daisy chaining
Multi-stream transport packs several video streams into one link, each addressed to a different monitor. On a monitor with a DisplayPort output, this allows daisy chaining, but the first monitor must stay powered for the second to work, and the total payload is shared. Two 4K60 screens therefore need a 1.4 link with DSC, while two 1080p60 screens fit comfortably on 1.2.
A hub behaves the same way and adds a power supply. Hubs are more reliable than daisy chaining for a fixed desk, because a monitor that sleeps does not take the second screen with it.
Cables and adapters
DP 1.2 does not need a special cable. Any cable rated for HBR2, which is almost every DisplayPort cable, carries it, and passive adapters to HDMI work up to the adapter’s output stage. Where the source is USB-C, a USB-C to DisplayPort cable negotiates four lanes and gives the same 4K60 result.
Long runs need care: at 5.4 Gbit/s per lane, a passive copper cable is reliable to about 3 m, and beyond that an active cable or a fiber version is safer. The DisplayPort 1.4 cable page covers the higher-rate cabling, and the DisplayPort cables overview covers connector and length options.
Practical scenarios
- Office dual-screen setup: one DP 1.2 port with an MST hub drives two 1080p60 screens; 4K on both would need 1.4 and DSC.
- 4K60 monitor on an older laptop: check that the laptop port is DP 1.2 or better and that the cable is not a passive HDMI adapter limited to 4K30.
- Daisy-chained monitors in a row: keep the chain to two screens and power both, because the first must stay awake for the second.
- Long cable to a wall-mounted display: use an active or fiber cable beyond 3 m, since HBR2 margin disappears quickly with thin copper.
FAQ
Is DisplayPort 1.2 enough for 4K60?
Yes at 8 bit 4:4:4, which is what most monitors use. At 10 bit it fits with little margin, and some systems fall back to 4:2:2. If the panel is 10 bit and the work depends on colour accuracy, a 1.4 link removes the compromise.
Do I need a special cable for DP 1.2?
No. Cables rated for HBR2 are standard, and the certification programme covers them. What matters is length: keep passive copper under 3 m for full rate, and choose an active cable for longer runs or for routing through conduit.
Why does my monitor show 4K30 on a 1.2 port?
Either the link trained at two lanes because the port shares pairs with USB, or the cable cannot sustain HBR2. Check the reported lane count and rate, then test with a short cable. A hub in the path is the usual cause of a two-lane link.
