Optimization guide · Updated on May 20, 2026

How to improve FPS in Counter-Strike 2 (PC)

Counter-Strike 2 migrated to Source 2 in 2023 and while the game looks better, performance regressed compared to CS:GO on the same hardware. CS2 is notoriously CPU-intensive, especially on maps with dense foliage and during volumetric smoke grenades. With the right settings you can recover much of those lost FPS and reach the high framerates needed for competitive play.

⚠️ Known for: Worse performance than CS:GO on the same hardware (Source 2 overhead). Volumetric smoke grenades are particularly CPU-heavy. Poorly calibrated shadow settings can cost 30-50 FPS.

Example with your hardware

This is what you'd gain with a NVIDIA RTX 3060

Without optimization (Ultra)

75 FPS

1080p · Ultra · no DLSS

With this guide applied

~132 FPS

1080p · Recommended settings

+ DLSS Quality

~169 FPS

1080p · Settings + DLSS

Calculations based on our FPS model combined with the % gain of each setting (measured in public benchmarks). Calculate your exact FPS with your own hardware →

1. Quick wins (no visual loss)

Start here. Each one adds a little, but together they give +38% free FPS.

Multicore Rendering

Recommended: Enabled · Visual impact: Imperceptible · Consensus: 10/10 fuentes

+30% FPS

Like Multithreaded Rendering in Valorant, this switch activates all CPU cores for rendering. ALWAYS enabled — without it CS2 underutilizes the processor.

V-Sync

Recommended: Off · Visual impact: Imperceptible · Consensus: 10/10 fuentes

+8% FPS

V-Sync in a competitive FPS is unacceptable. Always off. Use G-Sync/FreeSync on your monitor if you want to eliminate tearing without latency.

fps_max (consola)

Recommended: fps_max 0 o límite = Hz monitor + 20 · Visual impact: Imperceptible · Consensus: 9/10 fuentes

+0% FPS

fps_max 0 unlocks the framerate completely. Alternatively, cap at Hz+20 for stability. It's a console variable, not a graphics option.

Raw Input

Recommended: 1 (activado) · Visual impact: Imperceptible · Consensus: 10/10 fuentes

+0% FPS

Raw Input 1 makes the game read directly from the mouse hardware, bypassing OS acceleration. Doesn't affect FPS but is the competitive standard.

2. Medium impact settings

Here's where most of the FPS is. Minor visual impact, major performance impact.

Shadow Quality

Recommended: Very Low (modo competitivo) · Visual impact: Medium · Consensus: 10/10 fuentes

+18% FPS

Shadows in CS2 are especially CPU-expensive. Very Low is the competitive standard: removes visual distractions AND gives the biggest single-setting FPS jump available.

Ambient Occlusion

Recommended: Off · Visual impact: Low · Consensus: 9/10 fuentes

+8% FPS

Ambient Occlusion in CS2 has significant cost. Off is the competitive standard.

Shader Detail

Recommended: Low · Visual impact: Low · Consensus: 8/10 fuentes

+6% FPS

Shaders at Low reduce material complexity. In competitive CS2, visual clarity matters more than material quality.

Particle Detail

Recommended: Low · Visual impact: Low · Consensus: 8/10 fuentes

+5% FPS

Particles (bullet impacts, explosions, fire) at Low save GPU during the most critical moments of combat.

High Dynamic Range

Recommended: Performance · Visual impact: Low · Consensus: 8/10 fuentes

+4% FPS

HDR Performance mode in CS2 gives a competitively clear image (appropriate contrast) without the Quality mode cost.

Boost Player Contrast

Recommended: Enabled · Visual impact: Medium · Consensus: 9/10 fuentes

+0% FPS

Does not affect FPS but improves enemy player visibility in complex environments. Always enabled in competitive.

3. Upscaling (DLSS / FSR / XeSS)

The biggest gain in the game. Compatible with almost any modern GPU.

DLSS Quality (NVIDIA RTX)

+25% FPS

CS2 supports DLSS. For competitive play use Balanced or Performance to maximize FPS. Quality if you want better image without as much sacrifice.

No upscaling (recomendado para competitivo)

+0% FPS

Most pro players prefer native resolution without upscaling in CS2 — the game is light enough at 1080p and upscaling can add artifacts that affect enemy visibility.

4. Tips by GPU

NVIDIA

•NVIDIA Reflex + Boost: enable it in CS2 settings. Dramatically reduces input latency with no FPS cost.
•Launch option '-threads X' (X = number of physical CPU cores): helps multi-core CPUs distribute load better.
•In NVIDIA Control Panel, set 'Low Latency Mode' to 'Ultra' for CS2.
•DSR/DLDSR not needed in CS2 — keep native resolution.

AMD

•Anti-Lag+ (RDNA 3): enable it for reduced input latency, comparable to NVIDIA Reflex.
•FSR in CS2 is unnecessary for most AMD GPUs — the game is light enough.
•Enable SAM (Smart Access Memory) in BIOS if you have a compatible board.

Sistema

•Launch option '-novid' skips the intro and speeds up startup. No in-game FPS effect.
•High Performance power plan in Windows — clear benefit in CS2 due to its single-core demands.
•CPUs older than Intel 12th gen or Ryzen 5000 can be the bottleneck in CS2 Source 2. If you're under 200 FPS with a modern GPU, the CPU is the problem.

5. Known game issues

FPS regression compared to CS:GO

Source 2 has more overhead than Source 1. CS2 on the same hardware gives ~20-30% fewer FPS than CS:GO. This is a structural engine limitation, not a bug — Valve has been gradually improving it.

Estado: Continuously improving since launch (2023-2024)

Stuttering with volumetric smoke grenades

CS2's smoke grenades are volumetric and CPU-calculated. In areas with multiple simultaneous smokes there are noticeable FPS drops. Partially improved in 2024 patches.

Estado: Improved in 2024 patches (partial)

CPU bottleneck on pre-12th gen CPUs

CS2 is very demanding on CPU single-core performance. An i7-8700K, Ryzen 5 3600, and similar chips cannot maintain 200+ FPS stably even with an RTX 3080. Upgrading the CPU is the only solution.

6. Frequently asked questions

How many FPS does an RTX 3060 get in CS2?▾

At 1080p with competitive Low/Very Low settings, an RTX 3060 reaches 200-280 FPS stably as long as the CPU isn't the bottleneck. With an i5-12400 or Ryzen 5 5600, expect the higher end of that range.

Why does CS2 run worse than CS:GO?▾

Source 2 is more modern but also heavier than Source 1. The extra engine overhead costs ~20-30% FPS on the same hardware. Valve improves it gradually but CS2 will likely never match CS:GO's framerates.

Why do smoke grenades drop FPS so much?▾

CS2's volumetric smokes are calculated on the CPU in real time (that's why they can be shot through and redirected). It's a computationally expensive system. Partially improved in 2024 patches.

Is DLSS worth it in CS2?▾

For competitive play at 1080p, prefer native resolution. DLSS can add edge artifacts on player models that affect visual readability. If you're below 144 FPS, DLSS Balanced can help.

Want to know exactly how many FPS YOUR PC will get?

Enter your GPU and CPU in our calculator and measure the real impact of each setting.

Calculate FPS for Counter-Strike 2 →

Calculations based on consensus of technical sources and our own FPS model. More about our methodology →

Optimization guide · Updated on May 20, 2026

How to improve FPS in Counter-Strike 2 (PC)

Example with your hardware

This is what you'd gain with a NVIDIA RTX 3060

Without optimization (Ultra)

75 FPS

1080p · Ultra · no DLSS

With this guide applied

~132 FPS

1080p · Recommended settings

+ DLSS Quality

~169 FPS

1080p · Settings + DLSS

Calculations based on our FPS model combined with the % gain of each setting (measured in public benchmarks). Calculate your exact FPS with your own hardware →

1. Quick wins (no visual loss)

Start here. Each one adds a little, but together they give +38% free FPS.

Multicore Rendering

Recommended: Enabled · Visual impact: Imperceptible · Consensus: 10/10 fuentes

+30% FPS

Like Multithreaded Rendering in Valorant, this switch activates all CPU cores for rendering. ALWAYS enabled — without it CS2 underutilizes the processor.

V-Sync

Recommended: Off · Visual impact: Imperceptible · Consensus: 10/10 fuentes

+8% FPS

V-Sync in a competitive FPS is unacceptable. Always off. Use G-Sync/FreeSync on your monitor if you want to eliminate tearing without latency.

fps_max (consola)

Recommended: fps_max 0 o límite = Hz monitor + 20 · Visual impact: Imperceptible · Consensus: 9/10 fuentes

+0% FPS

fps_max 0 unlocks the framerate completely. Alternatively, cap at Hz+20 for stability. It's a console variable, not a graphics option.

Raw Input

Recommended: 1 (activado) · Visual impact: Imperceptible · Consensus: 10/10 fuentes

+0% FPS

Raw Input 1 makes the game read directly from the mouse hardware, bypassing OS acceleration. Doesn't affect FPS but is the competitive standard.

2. Medium impact settings

Here's where most of the FPS is. Minor visual impact, major performance impact.

Shadow Quality

Recommended: Very Low (modo competitivo) · Visual impact: Medium · Consensus: 10/10 fuentes

+18% FPS

Shadows in CS2 are especially CPU-expensive. Very Low is the competitive standard: removes visual distractions AND gives the biggest single-setting FPS jump available.

Ambient Occlusion

Recommended: Off · Visual impact: Low · Consensus: 9/10 fuentes

+8% FPS

Ambient Occlusion in CS2 has significant cost. Off is the competitive standard.

Shader Detail

Recommended: Low · Visual impact: Low · Consensus: 8/10 fuentes

+6% FPS

Shaders at Low reduce material complexity. In competitive CS2, visual clarity matters more than material quality.

Particle Detail

Recommended: Low · Visual impact: Low · Consensus: 8/10 fuentes

+5% FPS

Particles (bullet impacts, explosions, fire) at Low save GPU during the most critical moments of combat.

High Dynamic Range

Recommended: Performance · Visual impact: Low · Consensus: 8/10 fuentes

+4% FPS

HDR Performance mode in CS2 gives a competitively clear image (appropriate contrast) without the Quality mode cost.

Boost Player Contrast

Recommended: Enabled · Visual impact: Medium · Consensus: 9/10 fuentes

+0% FPS

Does not affect FPS but improves enemy player visibility in complex environments. Always enabled in competitive.

3. Upscaling (DLSS / FSR / XeSS)

The biggest gain in the game. Compatible with almost any modern GPU.

DLSS Quality (NVIDIA RTX)

+25% FPS

CS2 supports DLSS. For competitive play use Balanced or Performance to maximize FPS. Quality if you want better image without as much sacrifice.

No upscaling (recomendado para competitivo)

+0% FPS

Most pro players prefer native resolution without upscaling in CS2 — the game is light enough at 1080p and upscaling can add artifacts that affect enemy visibility.

4. Tips by GPU

NVIDIA

•NVIDIA Reflex + Boost: enable it in CS2 settings. Dramatically reduces input latency with no FPS cost.
•Launch option '-threads X' (X = number of physical CPU cores): helps multi-core CPUs distribute load better.
•In NVIDIA Control Panel, set 'Low Latency Mode' to 'Ultra' for CS2.
•DSR/DLDSR not needed in CS2 — keep native resolution.

AMD

•Anti-Lag+ (RDNA 3): enable it for reduced input latency, comparable to NVIDIA Reflex.
•FSR in CS2 is unnecessary for most AMD GPUs — the game is light enough.
•Enable SAM (Smart Access Memory) in BIOS if you have a compatible board.

Sistema

•Launch option '-novid' skips the intro and speeds up startup. No in-game FPS effect.
•High Performance power plan in Windows — clear benefit in CS2 due to its single-core demands.
•CPUs older than Intel 12th gen or Ryzen 5000 can be the bottleneck in CS2 Source 2. If you're under 200 FPS with a modern GPU, the CPU is the problem.

5. Known game issues

FPS regression compared to CS:GO

Source 2 has more overhead than Source 1. CS2 on the same hardware gives ~20-30% fewer FPS than CS:GO. This is a structural engine limitation, not a bug — Valve has been gradually improving it.

Estado: Continuously improving since launch (2023-2024)

Stuttering with volumetric smoke grenades

CS2's smoke grenades are volumetric and CPU-calculated. In areas with multiple simultaneous smokes there are noticeable FPS drops. Partially improved in 2024 patches.

Estado: Improved in 2024 patches (partial)

CPU bottleneck on pre-12th gen CPUs

CS2 is very demanding on CPU single-core performance. An i7-8700K, Ryzen 5 3600, and similar chips cannot maintain 200+ FPS stably even with an RTX 3080. Upgrading the CPU is the only solution.

6. Frequently asked questions

How many FPS does an RTX 3060 get in CS2?▾

At 1080p with competitive Low/Very Low settings, an RTX 3060 reaches 200-280 FPS stably as long as the CPU isn't the bottleneck. With an i5-12400 or Ryzen 5 5600, expect the higher end of that range.

Why does CS2 run worse than CS:GO?▾

Why do smoke grenades drop FPS so much?▾

CS2's volumetric smokes are calculated on the CPU in real time (that's why they can be shot through and redirected). It's a computationally expensive system. Partially improved in 2024 patches.

Is DLSS worth it in CS2?▾

For competitive play at 1080p, prefer native resolution. DLSS can add edge artifacts on player models that affect visual readability. If you're below 144 FPS, DLSS Balanced can help.

Want to know exactly how many FPS YOUR PC will get?

Enter your GPU and CPU in our calculator and measure the real impact of each setting.

Calculate FPS for Counter-Strike 2 →

Calculations based on consensus of technical sources and our own FPS model. More about our methodology →