Refresh rate describes how often the display timing updates. FPS describes how many frames an application produces. They interact, but one does not automatically determine the other.
Hz belongs to the display timing; FPS belongs to the content
A 144 Hz output schedules up to 144 display refresh cycles each second. A game running at 90 FPS produces about 90 new frames per second. The monitor can continue refreshing at 144 Hz while some refreshes show the same game frame again.
Likewise, a GPU may render more frames than a fixed-refresh display can present as complete updates. Depending on synchronization, extra frames may reduce input latency, be discarded, or appear as portions of different frames.
Frame pacing matters as much as the average
An average of 120 FPS can hide uneven delivery. Alternating fast and slow frame times produces visible stutter even when the average number looks high. Consistent pacing usually feels smoother than an unstable rate with the same average.
Browser animation timing has the same limitation: one headline Hz estimate cannot explain every delayed callback. DisplayCheck reports stability and confidence instead of treating every sample as a perfect physical refresh.
Synchronization decides when frames are presented
V-Sync coordinates presentation with a fixed display cycle to avoid partial frames, but it may add latency or produce a step down when performance misses a target. Variable refresh rate allows a compatible display to adapt its refresh timing within a supported range.
Neither setting guarantees stable game performance. CPU load, GPU load, frame caps, power modes, and the game engine still determine when frames are ready.
- Refresh rate: active output timing, expressed in hertz.
- FPS: frames produced by an application each second.
- Frame time: duration of one rendered or presented frame.
- Frame pacing: consistency of those durations over time.
How to check each value
Use the game’s performance overlay or a trusted frame-time tool for application FPS. Use operating-system display settings for the selected output mode. Then run the browser refresh rate test as a practical confirmation on the target screen.
If the result remains near 60 Hz on a high-refresh monitor, follow the 60 Hz troubleshooting checklist. For visible split frames, compare synchronization settings with the screen tearing test.
Try the tools
Check the behavior on your display.
DisplayCheck provides visual checks and browser capability reports. Objective color, luminance, physical response time, contrast, and gamut measurements require suitable instruments.