“More FPS” is usually a sensible PC-gaming goal, but it is not the only goal. A game rendering as many frames as possible can also push a graphics card harder than necessary, make its fans louder, consume more power and still produce an ugly visual defect: screen tearing. In the right setup, an FPS cap is less about settling for lower performance than asking the PC to deliver a steadier, better-matched output.
The most useful reason to limit frame rate is to keep it aligned with the display. This matters particularly for monitors with variable refresh rate, or VRR, support through NVIDIA G-Sync-compatible technology or AMD FreeSync. It can also help on conventional displays when combined with V-Sync. The best setting is not universal, though: the monitor’s maximum refresh rate, the game’s performance level and a player’s tolerance for latency all matter.
The short answer: cap frames when stability and clean motion matter
For many PC games, an FPS limit is worth considering. A cap can reduce the likelihood of tearing, lower GPU workload, curb fan noise and reduce overall power output. Crucially, it can keep performance at a consistent target if the hardware can sustain that target. It does not turn an unstable game into a stable one; if the GPU regularly falls beneath the selected limit, the result will still fluctuate. But it prevents the card from spending resources on frames the display may not be able to present cleanly.
That distinction is important. Frames per second (FPS) describes how many images the GPU renders in one second. Refresh rate, measured in hertz (Hz), describes how many times per second a monitor or TV updates its image. A 120Hz screen refreshes 120 times per second. When a game’s frame output and the display’s update cycle are poorly aligned, part of one frame can be visible alongside part of another.
For more context, explore Kelly Rowland and Tina Knowles to Captain birthFUND Team at Houston’s Third Ward Mile.
What screen tearing is, and why a cap can help
Screen tearing happens when the graphics card sends a new frame while the monitor or television is still showing the old one. Rather than seeing one complete image, the viewer may see portions of two different frames at once. In motion, it tends to appear as distracting horizontal breaks or flickering lines.
An FPS cap alone is not a universal guarantee against tearing, but it is a useful part of a coordinated setup. Capping output below the display’s ceiling avoids repeatedly colliding with that ceiling, while V-Sync can synchronize delivery with the display’s refresh cycle. On a VRR display, staying below the maximum refresh rate also helps the screen operate inside its intended variable-refresh window.
For a second perspective on the practical settings involved, see this guide to deciding when to cap FPS in PC games.
VRR: the setup where a frame cap is especially useful
Variable refresh rate means the display can adjust its refresh behavior to match the GPU’s frame output. G-Sync and FreeSync are examples. This can make changes in frame rate look smoother because the display is not fixed to one rigid cadence while the GPU varies.
The effective VRR range is generally understood to begin around 48 FPS and extend to the panel’s maximum refresh rate. A cap gives the GPU an upper boundary just beneath that maximum, helping to keep gameplay within the range instead of allowing frame output to strike the top limit. The potential latency benefit is described as small, but avoiding the ceiling is still a practical reason to set the limit a few frames below the panel maximum.
This is also why a player with a 120Hz VRR screen should not necessarily chase an unlimited result well above 120 FPS. A stable 117 FPS target, if the system can hold it, can be a cleaner fit for the display than letting output surge past its refresh limit. Likewise, small dips around a high target may be difficult to perceive: a movement from 120 FPS to 110 FPS is not automatically visible or tangible to every player.
A practical cap target: three or four frames below refresh rate
A straightforward starting point is a cap three or four FPS below the display’s maximum refresh rate, used alongside V-Sync. That approach aims to avoid hitting the refresh ceiling while preserving nearly all of the panel’s available frame-rate range.
- For a 60Hz display, try 57 FPS.
- For a 120Hz display, try 117 FPS.
- For a 240Hz display, try 237 FPS.
On paper, surrendering three frames can sound counterproductive. In practice, the gap between 57 and 60 FPS, or between 237 and 240 FPS, is unlikely to be noticeable for most players. The more meaningful requirement is that the PC can stay at or above the selected cap in the game being played. If it cannot, the cap remains an upper limit rather than a promise of consistent performance.
V-Sync explained: clean output with a latency trade-off
V-Sync, short for vertical synchronization, coordinates game output with the monitor or TV’s refresh rate. With standard V-Sync enabled, a game will not exceed the display’s maximum refresh rate. On a 120Hz monitor, for example, output is prevented from going beyond 120 FPS.
Its central advantage is clear: V-Sync greatly reduces the chance of tearing. The drawback is input lag. Before the GPU delivers a fresh frame, V-Sync makes it wait for the display’s current refresh cycle to finish. That waiting introduces delay between an input and the resulting screen update.
The duration of one refresh cycle gets shorter as refresh rate climbs:
- A 60Hz display completes a cycle in about 16.7ms.
- A 120Hz display completes a cycle in about 8.33ms.
- A 240Hz display completes a cycle in about 4.17ms.
A useful rule of thumb is that V-Sync can add about one additional refresh cycle of latency, although the actual amount can differ between games. If the GPU cannot render quickly enough, frames can queue up and add even more delay. That makes standard V-Sync a compromise rather than a blanket best setting. Players who prioritize a tear-free image may accept it readily; players focused on the lowest possible input delay may prefer to experiment carefully, especially in competitive shooters.
When Fast V-Sync may be relevant
NVIDIA users whose games commonly run far above their monitor’s refresh rate have another option to investigate: Fast V-Sync. It is available in the NVIDIA Control Panel’s 3D settings and is intended to provide lower-tear output while reducing some of the lag associated with ordinary V-Sync.
Unlike standard V-Sync, Fast V-Sync allows the GPU to continue rendering rather than forcing it to wait for each refresh cycle. It therefore does not impose the same conventional FPS cap. Its usefulness is conditional: it is an option for games where frame rate normally exceeds the display refresh rate by a wide margin, and it does not work equally well in every game. It is not a substitute for testing the combination of settings that suits a particular title and display.
How to set a system-wide FPS cap
Many games include an in-game frame limiter in their graphics menus. That is the simplest place to begin, though built-in limiters are not always dependable. GPU software offers a system-wide alternative that can apply a defined limit more consistently.
NVIDIA graphics cards
In the NVIDIA Control Panel, open Manage 3D Settings, select Global Settings, then choose Max Frame Rate. Enter the FPS target appropriate for the display. NVIDIA users can also use the NVIDIA app.
AMD graphics cards
In AMD Adrenalin, go to Gaming, then Radeon Chill. Set the minimum and maximum frame-rate fields to the same desired value to create a fixed cap.
Third-party route
Guru3D RTSS RivaTuner is another available option for setting a frame limit. Whichever route is chosen, it is sensible to check that an in-game limiter is not competing with the driver-level or third-party setting. The goal is one deliberate target, not several overlapping limits with unclear behavior.
Choosing the right approach for your setup
A sensible configuration begins with the display rather than with the highest number a benchmark can produce. Identify the panel’s maximum refresh rate, decide whether VRR is in use, then select a cap a few frames below that maximum if the system can reliably sustain it. With a VRR display, this keeps output beneath the top of the working range. Adding V-Sync can further address tearing, with the known possibility of added latency.
If a game is demanding enough that it cannot consistently reach the near-maximum target, choose a lower figure that the hardware can maintain more reliably. The value of a cap is stable frame pacing and appropriate GPU workload, not an arbitrary number. Conversely, if a game routinely runs vastly faster than the display can refresh, an uncapped configuration may expend extra GPU power without providing a proportionate visual gain.
There is no need to treat an FPS cap as a permanent, all-games rule. A slower-paced game, a visually demanding game and a competitive shooter may justify different priorities. But for players using VRR displays, or anyone bothered by tearing and unnecessary graphics-card noise, a carefully chosen cap is a practical tool—not an admission that the PC has lost the frame-rate race.
