What fps_max to Set in CS2 for Your Refresh Rate (2026)
Uncapped is not the best setting. The right fps_max value depends on your monitor and whether you run G-Sync — here is the cap matrix for 60/144/240/360 Hz, and whether to cap in-game or in the driver.
"More FPS is always better" is half-true. An uncapped frame rate that swings wildly produces uneven frametimes, extra heat, and — when frames pile up faster than the GPU can present them — added input latency from a growing render queue. The right fps_max isn't the biggest number; it's the one that keeps frametimes flat for your monitor. Here's how to pick it.
Why cap at all?
A cap does three things: it flattens frametimes (the thing you actually feel as "smooth"), keeps the GPU from running flat-out for frames you'll never see above your refresh rate, and — paired with the right latency settings — keeps the render queue short. The goal is a stable cap a little above your refresh, or exactly tuned to it if you run G-Sync.
The fps_max value for your monitor
| Monitor | Sync | fps_max | Where to cap |
|---|---|---|---|
| 60 Hz | None | 240 (or 60 for image quality) | In-game |
| 144 Hz | None | 300 | In-game or NVIDIA App |
| 240 Hz | None | 400 | NVIDIA App / RTSS preferred |
| 360 Hz+ | None | 500+ or 0 (uncap) | NVIDIA App |
| Any | G-Sync + V-Sync + Reflex | (refresh − 3), e.g. 237 for 240 Hz | In-game (Reflex) or driver |
In-game fps_max vs driver cap
On low- and mid-refresh monitors the in-game fps_max is fine. But at 240 Hz and above, the in-game limiter is less accurate — a driver-level cap (NVIDIA App or RTSS) holds the number more precisely and frametimes come out flatter. Set one cap, in one place — don't stack an in-game cap and a driver cap at different values, or they fight.
G-Sync: the lowest-latency tear-free combo
If you have a G-Sync (or G-Sync Compatible) monitor, the community-favourite tear-free setup is: G-Sync On + V-Sync On in the driver + NVIDIA Reflex On in-game + fps_max at (refresh − 3). The cap keeps you inside the G-Sync range so V-Sync never actually engages — you get no tearing and near-minimum latency. For the Reflex-off camp, see CS2 input lag: Reflex on or off.
Bottom line
Don't chase an uncapped number — cap a few frames above your refresh (or at refresh − 3 with G-Sync), set the cap in one place, and use the driver cap at 240 Hz+. Let the Optimizer confirm the value for your hardware, and if frames still feel uneven, work through the stuttering fixes.
FAQ
What is the best fps_max for CS2?
It depends on your monitor: about 300 for 144 Hz, 400 for 240 Hz, and 500+ or uncapped for 360 Hz. With a G-Sync monitor, cap at your refresh minus 3 (e.g. 237 for 240 Hz).
Should I cap FPS or leave it uncapped in CS2?
Cap it. An uncapped, swinging frame rate gives uneven frametimes and can grow the render queue, adding latency. A stable cap a little above your refresh feels smoother than a higher, unstable number.
Should I cap FPS in-game or in the NVIDIA App?
In-game is fine up to ~144 Hz. At 240 Hz and above, a driver-level cap (NVIDIA App or RTSS) is more accurate and gives flatter frametimes. Use one cap in one place, not both.
What fps_max should I use with G-Sync?
Set fps_max to your refresh rate minus 3, with G-Sync On, driver V-Sync On and in-game Reflex On. That keeps you inside the G-Sync range for tear-free, near-minimum-latency frames.
Does a higher FPS cap reduce input lag?
Up to a point. Higher frames can lower latency, but past your refresh the gains shrink and an unstable, uncapped rate can hurt frametimes. A stable cap plus Reflex or Ultra Low Latency Mode matters more than a huge number.