600Hz and 1040Hz Monitors: Dual-Mode Goes to Extremes
Samsung's 27-inch G60H advertises 600Hz at its native QHD resolution and 1040Hz at 720p. That is the dual-mode trade — spend fixed panel bandwidth on pixels or on refresh rate — pushed well past the 4K-at-240Hz generation. Whether it helps you depends almost entirely on the frame rate you can actually sustain.
What dual-mode actually does
A display has a fixed bandwidth budget. Resolution, refresh rate and colour depth all draw from it. Dual-mode displays let you reallocate that budget at runtime: drop from QHD to 720p and the pixels you stop sending become refresh rate headroom.
The 27-inch G60H is the clearest current example, at 600Hz native and 1040Hz at the reduced resolution. Samsung's 32-inch G80SH takes the other path, running 4K at 240Hz over 80Gbps DisplayPort 2.1.
Why the second number is mostly theoretical
A display cannot show more distinct images than your system renders. A 1040Hz panel fed 200fps shows each rendered frame roughly five times. You do not get 1040 distinct images; you get 200, held for a shorter interval each.
That shorter interval is the real benefit, and it is worth being precise about it. Less time showing each frame means less sample-and-hold motion blur, so moving objects look sharper even when your frame rate is far below the panel maximum. It is a genuine improvement — it just is not the improvement the headline number implies.
The returns also compress fast. Going from 60Hz to 120Hz halves frame persistence. Going from 500Hz to 1040Hz halves an interval that was already about 2ms. The second change is real and much harder to see.
Check what you are actually getting
Buying a high-refresh display does not guarantee you are running at its rated speed — cables, ports and display settings all cap it silently. Measure rather than assume: the refresh rate test reports the rate your browser is actually receiving, and the FPS test shows the frame rate your machine can sustain.
Run both. If the refresh rate reads lower than the panel specification, the problem is a cable, a port or a display setting. If the refresh rate is correct but your frame rate is far below it, the panel is not your bottleneck and a faster display will not help.
The cable is part of the specification
These rates depend on link bandwidth. DisplayPort 2.1b carries UHBR20 — 20Gbps per lane across four lanes for 80Gbps total — and adds the DP80LL low-loss cable specification for longer runs. HDMI 2.2 raises its ceiling to 96Gbps and needs the new Ultra96 cable to reach it.
An under-specified cable does not error. It negotiates a lower rate and leaves you capped, which is exactly the symptom covered in monitor stuck at 60Hz. If you want the background on what refresh rate does and does not buy you, refresh rate explained covers the fundamentals.
Sources: VESA — DisplayPort · Microsoft — View display settings in Windows
Frequently asked questions
How can one monitor run at both 600Hz and 1040Hz?
A display has a fixed bandwidth budget shared between resolution, refresh rate and colour depth. Dual-mode panels let you reallocate it at runtime: drop the resolution and the pixels you stop sending become refresh rate headroom.
Will I actually see 1040 distinct frames?
No. A display cannot show more distinct images than your system renders, so a 1040Hz panel fed 200fps shows each rendered frame roughly five times. The real benefit is the shorter interval each frame is held, which reduces sample-and-hold motion blur.
Are the gains still meaningful at these rates?
They compress fast. Going from 60Hz to 120Hz halves frame persistence; going from 500Hz to 1040Hz halves an interval that was already about 2ms. The second change is real and much harder to see.
How do I confirm I am getting the rated refresh rate?
Measure rather than assume. If the reported rate is lower than the panel specification, the cause is a cable, a port or a display setting — an under-specified cable does not error, it negotiates a lower rate and leaves you capped.