/
/
Settings & Config
Settings & Config
CS2 Stuttering With High FPS: Why It Happens
Frames above your refresh rate cause microstutter. Valve's own explanation, the three settings it recommends, and the eight stutters it fixed.

Your overlay says 400 FPS. The game still jumps. Someone tells you to buy a better CPU, someone else tells you to uncap everything, and nothing gets better.
Valve wrote an explanation of exactly this on a support page almost nobody opens, and the conclusion is the opposite of what the community repeats: frames above your refresh rate are not free, they are the cause.
Why high FPS stutters

There are two problems and only one of them is visible.
Screen tearing is the obvious one. The display receives a new frame in the middle of refreshing, so the top half of your screen shows one frame and the bottom half shows another.
Microstutter is the one that ruins your aim without ever looking broken. In Valve's words, when the frame rate is above the refresh rate the game renders a frame before the display is able to show it, the two drift apart, and eventually the game renders two frames in a row before the display shows you one. The result looks like the game jumping forward.
That is the answer to the question. It is not your network and it is not a weak GPU. It happens because you are rendering faster than your monitor can display, which is precisely the state people chase.
If you want to separate this from an actual network hitch, the telemetry HUD does it in thirty seconds, and that is covered in our net jitter guide.
Valve's own recommended settings

Valve recommends enabling G-Sync, V-Sync and NVIDIA Reflex together whenever all three are available, and says plainly that this will limit your frame rate to slightly below your monitor's refresh rate. Their words: this is by design, and is usually the smoothest-looking and lowest input latency settings combination.
Each piece does one job.
G-Sync, or FreeSync on AMD, lets the display change its refresh rate on the fly to match the game, so a drop from 60 does not become a jarring 30.
V-Sync makes the game sleep until the next display refresh, which removes tearing and microstutter. On its own it costs you input latency, because a sleeping game is not reading your mouse, and those inputs queue up for the next frame.
Reflex pays that back by moving the sleep to before input processing instead of after, so the game collects your latest input before rendering. On its own Reflex can cause a stutter, because its sleep interval is an estimate and can miss a refresh deadline. G-Sync absorbs that miss.
Which is the point. The three settings cancel each other's downsides, and only all three together give you the full result.
CS2 checks for this at startup. If the combination is available and you are not using it, you get a popup with an Apply Changes button that sets it for you.
Before any of it, make sure your monitor is actually running at its highest refresh rate. Valve lists that first for a reason, and our refresh rate guide covers what the jump is actually worth.
The stutters that were the game's fault

Not all of it was ever your setup. Valve shipped eight separate stutter and hitch fixes, and every one of them landed in 2024.
Shader compilation, two different threading bugs that were worse when all your CPU cores were busy, HUD elements appearing, in-game voice chat, end of round, the sniper scope, and one bug simply described as causing excessive stuttering for some players.
Two things from that period are still settings you control rather than bugs that got fixed.
Streamlined Push to Talk. Valve eliminated most voice chat hitching in June 2024 but said some users may still get a hitch the first time they push to talk. This setting avoids it. If your stutter happens the moment you first talk in a round, that is the one.
CPU Cores Usage Preference. Added in December 2024 to control how performance and efficiency cores are used on CPUs that have both. If you are on a recent Intel chip with E-cores, this setting exists specifically for you, and Valve separately mitigated a performance issue affecting Windows 10 users with recent Intel CPUs in February 2026.
What to do, in order
Set your monitor to its highest refresh rate in Windows, not just in CS2. Then turn on G-Sync or FreeSync in your driver control panel, restart the game, and enable V-Sync and Reflex in CS2. Accept the frame cap.
If you still stutter, check whether it has a trigger. First push to talk, end of round, scope in, or the first time you see a new effect on a map all point at different causes, and all four are things Valve has worked on.
Then confirm it is actually your PC rather than your connection, and if frames are the real problem our CS2 FPS guide and launch options guide cover what still moves the number and what does nothing.
And if the game is not stuttering but closing, that is a different problem with a different list, in our CS2 crashing guide.
The uncomfortable part is the first step. Capping your frame rate feels like losing something after years of being told the number is the goal. Valve's position is that a stable 240 beats an unstable 400, and they built the startup popup because enough people had it wrong.

WRITTEN BY
Brian Sirbu
CS2 COACH // GAMESENSELAB
MORE CS2 GUIDES


