Best CS2 Settings 2026: Max FPS and Competitive Config

Counter-Strike 2 runs on a fundamentally different performance model than most modern PC games. While titles like Cyberpunk 2077 and Black Myth: Wukong are GPU-limited — throwing more geometry, lighting calculations, and shader passes at the GPU with each quality step — CS2’s Source 2 engine is almost entirely CPU-bound at competitive frame rate targets. The game’s per-frame simulation work (hit registration, entity updates, sub-tick interpolation) runs on the CPU, and the GPU is often waiting for the CPU to finish rather than the reverse. The practical consequence is that a mid-range RTX 3060 paired with an older i5-8600K frequently performs worse than a budget RX 6600 paired with a modern i5-13400 — because in CS2, CPU clock speed and IPC matter more than GPU VRAM at 1080p. This guide covers every setting that moves the needle for competitive CS2, the mechanics behind sub-tick and why it changes how you think about FPS targets, and the hardware combinations that reliably sustain 300 FPS. For the broader framework of PC settings optimisation across all games, see the complete PC game settings optimisation guide.

Full Competitive Settings Template

The following settings are used by the majority of professional and ranked competitive players in CS2 in 2026. Every value is chosen to maximise FPS, reduce input lag, or eliminate visual noise that obscures player model silhouettes. Mechanism explanations for the most impactful settings follow the table.

For a full breakdown of the best settings, see valorant settings pc.

Video Settings: The FPS Hierarchy in CS2

Not all settings are equal in CS2. The performance impact varies by an order of magnitude between settings, and understanding this hierarchy is the difference between a methodical optimisation and blindly turning everything to Low and losing 20 FPS from texture filtering while leaving shadow quality on High.

Squeeze out more FPS with the settings in settings satisfactory pc.

Global Shadow Quality is the dominant setting. In CS2’s Source 2 engine, shadows are rendered via cascaded shadow maps with a separate rendering pass for each shadow-casting light source. At Very High, every dynamic light casts per-frame shadows with high resolution shadow maps (2048×2048 or greater). At Very Low, shadow maps are disabled entirely for dynamic geometry, and only baked static light is applied. On a GTX 1660 Super at 1080p, the difference between Very High and Very Low shadows is typically 80–120 FPS — the largest single setting change available. Set it to Very Low unconditionally; the only competitive impact is that certain player model shadows used for positional cues in tight corners are removed, which is an advantage, not a disadvantage.

Ambient Occlusion is the second highest-impact setting. Screen-space ambient occlusion (SSAO) requires a full-screen depth pass each frame to calculate how much ambient light reaches each surface point. On mid-range GPUs (GTX 1070–RTX 3060 range), AO adds 15–30 FPS of overhead at 1080p. It provides no gameplay-relevant information — it darkens crevices and corners — and should be disabled regardless of GPU tier.

Particle Detail and Shader Detail are secondary but still measurable. Particle Detail controls the complexity of smoke grenades, molotov fire, and explosion effects. At High, smoke grenades use volumetric rendering with per-pixel opacity calculations; at Low, they use simplified billboard sprites. The FPS difference is most noticeable in active grenade engagements (5–15 FPS during multi-smoke executes on B Dust II). Set to Low. Shader Detail controls surface shader complexity, primarily affecting reflective surfaces and water. On Source 2, Low shader detail substitutes diffuse-only shading for full PBR surface calculations. The FPS gain is 10–20 FPS on GPUs below the RTX 3070 tier.

CS2 Launch Options for FPS and Stutter Reduction

CS2’s launch options provide configuration access that is not available in the in-game settings menu. Add these via Steam → CS2 → Properties → Launch Options:

A critical launch consideration is shader pre-compilation. CS2 moved to a per-shader compilation model in the Source 2 engine, meaning that on first launch or after driver updates, the game compiles shaders in the background while you play. This manifests as severe frame time spikes (stutter) in the first 1–3 hours of play on a new driver installation. If you experience significant stutter after a driver update, play one full deathmatch session to allow shader compilation to complete before ranking matches. The stutter does not indicate a settings problem — it resolves once the shader cache is populated.

Network Settings for Competitive Play

CS2’s sub-tick system changed the relevance of several traditional CS:GO network settings. In CS:GO, the server ran at a fixed 64 or 128 ticks per second, and network variables like cl_interp and rate were tuned around that tick rate. CS2’s sub-tick architecture records input timestamps at the moment of action rather than at the next tick boundary, which eliminates the “tick alignment” problem that made 128-tick servers so important for competitive CS:GO.

The practical upshot: cl_interp_ratio and cl_interp tweaks that improved CS:GO hit registration have minimal effect in CS2. The variables still exist and are accepted in the console, but Valve’s sub-tick implementation handles interpolation internally. The most impactful network settings in CS2 are:

• rate 786432 — Sets the maximum network data rate to 786 KB/s, appropriate for connections above 6 Mbps. Default is lower; this ensures CS2 can use full available bandwidth on modern broadband connections.
• Disable Windows Network Throttling — Windows’ Network Throttling Index can delay UDP packet processing for games. Disabling it via the registry (set NetworkThrottlingIndex to ffffffff in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile) removes an intermittent source of network jitter.
• Check net_graph — Enable with net_graph 1 in the console to monitor packet loss, choke, and latency in real time. Consistent choke (packets queued at the server) indicates a network bandwidth issue; consistent loss indicates a routing or ISP issue.

Resolution: 4:3 Stretched vs Native 16:9

The stretched resolution debate in CS2 is more legitimate than in Valorant or Apex Legends, because Counter-Strike’s community has used 4:3 stretched for over fifteen years with documented competitive rationale. The most common competitive resolutions are 1280×960 (4:3), 1024×768 (4:3), and 1920×1080 (16:9 native).

The case for 4:3 stretched: player models appear horizontally wider on screen, which increases the visual target size at medium and long range. On Dust II’s long A, a player model at the far end of long doors is approximately 1.8% of screen width at 1080p native. At 1280×960 stretched to a 16:9 monitor, the same model occupies roughly 2.4% of screen width — a 33% increase in target width. This is not a placebo; it is a direct consequence of fitting 1280 horizontal pixels across a 1920-pixel-wide panel. The FPS benefit of running at lower resolution (1280×960 renders 44% fewer pixels than 1920×1080) is also meaningful on hardware below the RTX 3060 tier.

The case for 16:9 native: more of the map is visible horizontally, providing wider peripheral awareness on maps like Mirage and Inferno. Grenades arc more predictably because the FOV is wider. And above 300 FPS, the FPS gain from lower resolution becomes irrelevant since both resolutions can sustain 300+ FPS on mid-range hardware.

The practical recommendation: if you are currently on CS:GO at a 4:3 stretched resolution and your muscle memory is calibrated to that ratio, staying on stretched in CS2 is valid. If starting fresh, native 1080p provides better environmental clarity and more standard game feel. Do not switch mid-rank season, as the horizontal sensitivity ratio changes between native and stretched.

DLSS, FSR and XeSS in CS2

CS2 supports AMD FidelityFX Super Resolution (FSR) natively as of late 2024. DLSS and XeSS are not natively supported in the in-game menu, though some configurations use them via NVIDIA’s driver-level upscaling. For a full breakdown of all three upscaling technologies and their quality trade-offs, see our DLSS vs FSR vs XeSS comparison guide.

In CS2 specifically, FSR’s value is limited for competitive play. At 1080p on a 1080p monitor, FSR renders at a lower internal resolution (e.g., 720p internal with Quality mode) and upscales to 1080p output. The resulting image has softer player model edges than native rendering, which can reduce silhouette clarity at long range — exactly the scenario where visual precision matters most competitively. Disable FSR for competitive play at 1080p. FSR becomes relevant only on 1440p or 4K monitors where the internal resolution at Quality mode (1080p and 1440p internal respectively) is still a clean render target.

NVIDIA and AMD Control Panel Settings

Driver-level settings provide performance optimisations that are independent of CS2’s in-game options. For a full breakdown of every NVIDIA Control Panel setting for gaming, see our NVIDIA Control Panel optimisation guide. The settings with the most impact for CS2 specifically are:

• Low Latency Mode: Ultra — Limits the GPU’s render queue to 1 frame, reducing the pipeline latency between mouse input and on-screen result. Combined with NVIDIA Reflex in-game, this produces the lowest total system latency configuration on NVIDIA hardware.
• Power Management Mode: Prefer Maximum Performance — Prevents the GPU from throttling clock speeds during low-load frames between rounds. Without this setting, some GPU models downclock during buy phases and take 1–2 frames to ramp back up at round start.
• Texture Filtering — Quality: High Performance — Substitutes bilinear for trilinear filtering globally, consistent with the in-game bilinear setting and reducing driver-level texture sampling overhead.
• AMD users: Enable Anti-Lag+ (RDNA 2/3) in AMD Software and set Shader Cache to AMD Optimised to prevent shader recompilation on each driver update.

Understanding how these settings interact with CS2’s CPU-GPU pipeline is covered in detail in our PC game settings explained guide, including why power management mode affects frame pacing more than raw FPS numbers suggest.

Minimum Hardware for 300 FPS in CS2

CS2’s CPU-bound performance profile means the hardware combinations required for 300 FPS are weighted heavily toward CPU single-core performance and IPC (instructions per clock), not GPU tier. The following combinations reliably sustain 300 FPS at 1080p with the competitive settings template above:

We cover the exact settings in overwatch settings 2026: max fps to maximise performance.

The Ryzen 7 5800X3D’s 96 MB L3 cache (3D V-Cache) produces disproportionately high CS2 performance relative to its base clock speed, because CS2’s game simulation data fits within the expanded cache, dramatically reducing cache miss penalties on per-frame entity lookups. The 5800X3D frequently outperforms the i9-12900K in CS2 FPS benchmarks despite lower clock speeds — a hardware quirk specific to Source 2’s memory access pattern.

RAM configuration matters more in CS2 than in almost any other game. Single-channel memory (one DIMM) versus dual-channel (two DIMMs of the same size) can reduce CS2 FPS by 20–40% on Ryzen platforms, because Ryzen’s memory controller bandwidth is cut in half in single-channel mode. If you are building for CS2 specifically, two 8 GB sticks are always preferable to one 16 GB stick.

Frequently Asked Questions

What are the best CS2 settings for a GTX 1060 or RX 580?

Run the full competitive template with Global Shadow Quality at Very Low, Ambient Occlusion disabled, and all other settings at Low. At 1920×1080 with these settings, a GTX 1060 6 GB typically delivers 180–240 FPS depending on CPU pairing. If paired with an older quad-core (i5-7400 or below), the CPU is likely the bottleneck — check GPU utilisation in MSI Afterburner; if GPU is below 80% at your FPS target, a CPU upgrade delivers more frames than a GPU upgrade. Consider switching to 1280×960 stretched to reduce GPU load by ~44% and potentially unlock 280–300 FPS on higher-end CPU pairings.

Why is CS2 stuttering even with high FPS?

The four most common causes: (1) Shader pre-compilation — if you recently updated drivers or installed CS2 fresh, play one full deathmatch session for shader compilation to complete. (2) VSync enabled — disable it immediately; VSync adds a frame queue that causes periodic stutter as the buffer fills. (3) Windows power plan — ensure it is set to High Performance or Balanced; Power Saver throttles CPU and GPU clocks mid-game. (4) Background CPU load — Discord hardware acceleration, RGB software (iCUE, Synapse), and GeForce Experience overlay all consume CPU cycles that CS2’s simulation needs. Disable unnecessary background applications.

Does CS2 use more than 4 CPU cores?

CS2’s Source 2 engine uses multiple threads, but its main game simulation loop is largely single-threaded. Rendering (draw call submission) runs on a secondary thread, and audio processing uses additional threads. In practice, CS2 saturates 2–3 cores heavily and uses 4–6 cores at partial load. The implication for hardware selection: single-core clock speed and IPC matter more than core count in CS2. An 8-core CPU at 3.6 GHz performs worse than a 6-core CPU at 5.0 GHz in CS2 FPS benchmarks. Prioritise clock speed and modern architecture (Intel 12th/13th/14th gen or AMD Zen 3/4) over core count.

Should I use fps_max in CS2?

Set fps_max to match your monitor’s refresh rate, not to 0 (uncapped). Uncapped FPS in CS2 causes the GPU to spike to 99–100% utilisation, generating heat and increasing frame time variance (micro-stutter). Setting fps_max 300 on a 240Hz monitor or fps_max 144 on a 144Hz monitor stabilises GPU frame pacing and typically produces lower perceived stutter than uncapped, even at a marginally lower peak FPS number. A common competitive trick: set fps_max to 1.5× the monitor refresh rate (e.g., fps_max 360 on a 240Hz monitor) to maintain GPU headroom while keeping frame pacing controlled.

Sources

1. Valve Corporation. Counter-Strike 2 — Official Site and Patch Notes. Valve Corporation.
2. NVIDIA Corporation. NVIDIA Reflex Low Latency Technology Overview. NVIDIA Corporation.
3. Tom’s Hardware. CPU and GPU Benchmarks, CS2 Performance Analysis. Future Publishing.
4. PC Gamer. CS2 Settings Guides and Competitive Coverage. Future Publishing.