High FPS does not mean smooth gameplay. CS2 can report 300 FPS and still hitch, because what you feel is the worst frames, not the average. This guide covers the fixes that actually matter, based on Valve's own recommendations and community testing.
Measure the problem first
Before changing anything, turn on the frame time and FPS readout in Settings, then Game, then Telemetry. Valve's FAQ explains the two numbers: the left one is the maximum frame time in milliseconds (the worst frame recently, and the number that matches the hitch you feel), and the right one is average FPS. You can also type cl_showfps 1 in the console for a simple FPS counter.
If the maximum frame time spikes red when the game hitches, the problem is your PC. If the frame time stays flat but players teleport, the problem is the network.
The frame pacing setup Valve recommends
Valve's Steam Support video FAQ recommends enabling G-Sync (or FreeSync), V-Sync, and NVIDIA Reflex together. That combination caps your frame rate just below your monitor's refresh rate and is, in Valve's words, usually the smoothest-looking and lowest input-latency setup. CS2 shows a settings recommendation pop-up for it.
Set your monitor to its highest refresh rate in Windows first. Use fullscreen, because G-Sync can misbehave in windowed modes. On AMD graphics, CS2 supports AMD Anti-Lag 2, the equivalent of Reflex.
The FPS caps live under Video, then Advanced Video, then Frame Pacing: Maximum FPS In Game and Maximum FPS In Menus. Since August 2025, fps_max cannot be changed while connected to a server, so set it in the menu before you queue.
Launch options that do nothing
Most "best CS2 launch options" lists are inherited from CS:GO. Here is what is actually true in CS2:
- -tickrate 128 does nothing. CS2 servers run at 64 ticks with sub-tick updates.
- -nojoy is redundant. Since May 2024, joystick input is off by default.
- -novid is unnecessary. There is no intro video to skip.
- -high and -threads have no Valve documentation that they help. Treat them as placebo.
- -autoconfig resets video settings to detected defaults. Steam Support's own suggestion when settings are broken.
Common causes and fixes
Out-of-date game or drivers. Valve has shipped stutter fixes for shader compilation and a February 2026 fix for a performance problem on Windows 10 with recent Intel CPUs. AMD users needed a driver update for an early CS2 shader issue. Update both before tweaking anything.
Background software. Overlays, capture tools, and browser tabs compete for CPU time. Close them and re-measure.
Shader compilation. After every game patch and driver update, the first session recompiles shaders. That is stutter, and it is temporary. Give it one full match before changing anything.
Texture pool too high for your VRAM. Drop texture quality one step and watch whether the hitches disappear.
Storage. Asset streaming from a HDD or a 95%-full SSD hitches in open areas. Keep 10-15% free space on the game drive.
When it is not your PC
Rubber-banding and teleporting enemies feel like stutter but often are not. Set the frame-time warning just above your normal maximum. When the game hitches, check what turned red. A frame-time spike is your PC; missed ticks are the network.
Source
[1] CS2 Stuttering and FPS Drops Fix: Settings Valve Recommends
[2] Fix stuttering in CS2: 5 fixes that actually work