Visibility first, then FPS
In CS2 not every setting is about looks. Some decide whether you see a player's shadow around a corner or a model in a dark spot. Keep those, and lower the settings that only cost frames.
Set your monitor to its highest refresh rate in Windows first, and use exclusive fullscreen.
Display
| Setting | Set to | Why |
|---|---|---|
| Display mode | Fullscreen | Lowest latency and most stable frame pacing. |
| Refresh rate | Your monitor's highest | CS2 sometimes picks a lower one. |
| Brightness | Raise it until dark corners are readable | Pure visibility. |
Advanced video
| Setting | Set to | Why |
|---|---|---|
| Boost player contrast | Enabled | Makes player models stand out from the map. |
| Wait for vertical sync | Disabled | V-Sync adds input lag. With G-SYNC, see the NVIDIA guide. |
| Multisampling anti-aliasing | 2x or 4x MSAA | Cleaner edges help spot players at a distance. Use CMAA2 on weaker GPUs. |
| Global shadow quality | Medium or High | Shadows give away player positions. Don't go lowest. |
| Model, texture and shader detail | Low | Costs frames, doesn't help you see players. |
| Texture filtering | Anisotropic 4x | Barely costs anything. |
| Particle detail | Low | Less clutter in smokes and molotovs. |
| Ambient occlusion | Disabled | Costs frames, darkens corners. |
| High dynamic range | Performance | Higher FPS, no visibility loss. |
| FidelityFX Super Resolution | Disabled (highest quality) | Upscaling blurs small targets. |
| NVIDIA Reflex Low Latency | Enabled + Boost | Lowers input lag when the GPU is busy. |
Capping FPS
CS2's frame times get uneven when the CPU is the limit, which happens a lot in busy rounds. Set Max frames per second in the video settings, or fps_max in the console, to a number your PC holds in heavy fights. With Reflex on, that keeps input lag low and frames even.
With G-SYNC, cap a few FPS below your refresh rate.
VAC and FACEIT
Valve's own anti-cheat (VAC) doesn't need special Windows settings. If you play on FACEIT, its client is a kernel anti-cheat that checks Windows security features, much like Vanguard. If it won't start after a debloat, see the anti-cheat guide.
PC settings that help CS2
- CS2 is CPU-heavy: turn on XMP or EXPO and use a high-performance power plan.
- The first matches after a driver update can stutter while shaders compile. See fix stutter.
- Turn off mouse acceleration in Windows. See the mouse guide.
Questions
Should I play CS2 on all low settings?
No. Keep shadows at medium or high and use some anti-aliasing, because they help you see players. Lower the rest.
Is stretched 4:3 better in CS2?
It's a preference. Models look wider, but you see less of the sides. It doesn't give more FPS on a modern GPU.
Why does CS2 stutter after an update?
Game and driver updates make CS2 compile shaders again. It usually settles after a few matches.
On PatroneOS, part of this guide is already set. The rest is up to you.
