If your monitor is 144Hz, is there any point running a game at 300 fps? It sounds wasteful, since the screen can only show 144 images per second. Yet competitive players deliberately push frame rates far above refresh, and they are not imagining the benefit. The reason is latency, not smoothness, and it is worth understanding before you cap your frames.
Refresh rate and frame rate are different clocks
Refresh rate is how many times per second the panel redraws. Frame rate is how many images per second the GPU produces. When frame rate exceeds refresh rate, the monitor still shows only its refresh number of frames, but each shown frame is fresher, generated closer to the moment it appears. That freshness lowers the delay between your input and what you see.
The latency payoff
Extra frames shrink the time a finished frame waits to be displayed. Going from 144 fps to 240+ fps on a 144Hz screen can trim total system latency by a handful of milliseconds, which competitive players value even though the visible smoothness looks the same. The table shows rough end-to-end latency trends.
| Scenario (144Hz panel) | Approx frame age when shown | Perceived benefit |
|---|---|---|
| 72 fps (below refresh) | Old, uneven | Stutter, tearing |
| 144 fps (matched) | ~6.9 ms | Smooth baseline |
| 240 fps (above refresh) | ~4.2 ms | Lower input lag |
| 360 fps (well above) | ~2.8 ms | Marginal further lag drop |
The costs of uncapped frames
Tearing and heat
Without a frame cap or sync, frames above refresh cause screen tearing, since the GPU hands over new frames mid-scan. Uncapped rendering also runs the GPU at full load, raising temperature, fan noise, and power draw for a benefit that shrinks past a point.
The sweet spot with VRR
The best of both worlds is a frame cap a few fps below your refresh rate with adaptive sync on, for example 138 fps on 144Hz, which eliminates tearing and keeps latency low. For pure competitive latency chasing without VRR, players uncap and tolerate tearing to shave those last milliseconds.
How much latency you actually save
The returns diminish quickly. Going from your refresh rate to roughly double it delivers the bulk of the latency benefit, while pushing far beyond that trims only fractions of a millisecond for a large jump in GPU load. That is why competitive titles, which are easy to run at very high frame rates, are where uncapping makes sense: the frames are almost free and the small latency gains add up over thousands of engagements. In a demanding single-player game barely hitting refresh, chasing more frames is pointless.
Measuring it yourself
Enable a latency-reduction feature such as Reflex, which caps frames intelligently to keep the GPU from queuing work, and you often get most of the responsiveness of uncapped play without the tearing and heat. For most players, that combination, a smart latency mode plus a near-refresh cap with VRR, beats brute-force uncapping.
FAQ
Can I see frames above my refresh rate?
You cannot see extra distinct images beyond the refresh count, but you can feel lower input lag because each displayed frame is newer. The benefit is responsiveness, not additional visible frames.
Should casual players uncap fps?
Usually no. A cap just below refresh with VRR gives smooth, tear-free play at lower heat and noise. Uncapping mainly helps competitive players chasing minimum latency who accept tearing to get it.
Bottom line
Rendering above your refresh rate does not add visible frames, but it lowers input latency by ensuring each displayed frame is fresher. Competitive players exploit that; everyone else is better served by capping a few fps under refresh with adaptive sync on, keeping motion clean while sparing the GPU. Match the strategy to whether you value milliseconds or a quiet, cool system.
