How to Improve FPS in CS2 (2026): Settings, Launch Options & Config

Counter-Strike 2 runs on Source 2, and while it's better optimized than CS:GO ever was, plenty of players still can't hit the 240+ FPS needed for high-refresh competitive play. The good news: CS2 responds well to targeted tweaks — video settings, launch options, and autoexec commands that most guides gloss over.

This guide breaks down the exact settings that matter for FPS in CS2 as of 2026, ordered by impact. We cite measured benchmarks from independent reviewers — OpenBenchmarking.org shows an RTX 4070 SUPER at 166 FPS average on high settings (1080p), while an RTX 4080 SUPER pushes 228 FPS in the same scenario. The gap between those cards is hardware, but the gap between 166 FPS and 300+ on the same card is settings and config. If you want a hardware-specific playbook that accounts for your exact GPU, CPU, and RAM, run a free optimization at BetterFPS — it builds a step-by-step guide in 60 seconds.

Video Settings by FPS Impact

CS2's video menu has 15+ sliders, but only five settings account for most of the framerate cost. Start here and work down the list until you hit your target FPS.

Shadow Quality — the biggest offender

Shadow Quality is the single most expensive setting in CS2. High to Low typically frees 20–30% framerate on mid-tier GPUs (RTX 4070, RX 7800 XT class). The visual difference is minimal in competitive play — you're not admiring shadow softness when you're holding an angle. Set it to Low unless you have a top-end card and framerate to spare.

Global Shadow Quality — secondary hit

Global Shadow Quality controls the resolution of the shadow map. Medium to Low adds another 8–12% FPS. Combined with Shadow Quality on Low, you're looking at a 30–40% total gain over maxed shadows — that's the difference between 160 FPS and 220 FPS on many cards.

Model / Texture Detail — VRAM-bound

Model and Texture Detail load higher-res assets into VRAM. If you have 8 GB or more, High is fine. If you're on 6 GB (RTX 3060 class), Medium prevents stuttering without a major visual downgrade. The FPS cost is modest (5–8%) unless you're memory-starved, in which case it cascades into frame pacing issues.

Effect Detail — smoke and fire

Effect Detail governs particle rendering for smokes, molotovs, and gunfire. High looks better in replays, but in a live match the difference is negligible. Medium saves 6–10% framerate. Low is overkill unless you're chasing every last frame on weak hardware.

Anti-Aliasing — clean up or speed up

CS2 offers MSAA and FXAA. MSAA 4x costs 10–15% FPS but eliminates jaggies on edges. FXAA is nearly free (1–2% cost) but blurs the image slightly. Most competitive players run FXAA or None — the minor shimmer is worth the framerate headroom. If you're on a 1440p or 4K display, None is often acceptable because pixel density masks aliasing.

Launch Options That Actually Matter

CS2 launch options are entered in Steam (right-click Counter-Strike 2 > Properties > Launch Options). Half the options floating around forums are placebo or deprecated; here are the ones that work in 2026.

• **-high** — sets CS2 process priority to High in Windows. Marginal FPS gain (2–4%), but reduces background app interference. Safe to use.
• **-threads [N]** — forces CS2 to use N CPU threads. Only useful if you have 6+ cores and the game isn't auto-detecting them. Modern CPUs (Ryzen 7000, Intel 13th/14th/15th-gen) don't need this.
• **-novid** — skips intro videos. Doesn't boost FPS but saves 10 seconds on launch. Quality-of-life win.
• **-nojoy** — disables joystick polling. Frees a tiny bit of CPU overhead. No downside unless you use a controller (you don't in CS2).
• **-freq [Hz]** — forces monitor refresh rate. Use `-freq 240` if Windows is capping you at 144 Hz. Check your desktop refresh first; if it's already correct, omit this.
• **+fps_max 0** — uncaps framerate. CS2 defaults to unlimited, but some configs or autoexecs override it. This ensures no cap.

A clean 2026 launch string for competitive CS2 looks like: `-high -novid -nojoy +fps_max 0`. Add `-freq 240` only if needed.

Autoexec Commands for Maximum FPS

An autoexec.cfg file runs every time CS2 launches, letting you enforce FPS-friendly settings that aren't exposed in the GUI. Create a text file named `autoexec.cfg` in your CS2 `cfg` folder (usually `Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg`). Paste these commands:

• `fps_max 0` — uncap framerate (redundant with launch option, but ensures no override)
• `mat_queue_mode 2` — forces multi-threaded rendering. Source 2 usually auto-sets this, but explicit is better.
• `cl_forcepreload 1` — preloads map assets into RAM at load time. Reduces mid-match stutters at the cost of 5–10 seconds longer load screens. Worth it on 16 GB+ RAM.
• `r_drawtracers_firstperson 0` — disables first-person bullet tracers. Tiny FPS gain (1–2%) and reduces visual clutter in spray fights.
• `cl_showfps 1` — displays framerate counter in top-left corner. Use `cl_showfps 2` for more detailed stats (frame time, GPU/CPU bottleneck indicator).
• `rate 786432` — sets max network bandwidth. Not an FPS command, but prevents packet loss from choking framerate on high-tick servers.

Save the file, then add `+exec autoexec` to your launch options to ensure it runs. Or type `exec autoexec` in console after each launch (less reliable).

NVIDIA and AMD Control Panel Tweaks

Driver-level settings apply to CS2 before the game's own options kick in. These are low-effort, high-return changes you set once and forget.

NVIDIA Control Panel

• **Power Management Mode** → Prefer Maximum Performance. Keeps the GPU clocked high even during light scenes (buy rounds, warm-up). Adds 5–10% framerate consistency.
• **Low Latency Mode** → On or Ultra (if you have a Reflex-compatible GPU). Reduces input lag by 5–15ms. Doesn't boost FPS directly, but makes high FPS feel smoother.
• **Texture Filtering - Quality** → Performance. Trades a negligible visual difference for 3–5% FPS.
• **Shader Cache** → On. Reduces stutter on map loads. No FPS cost.

AMD Radeon Software

• **Radeon Anti-Lag** → Enabled. AMD's equivalent to NVIDIA Reflex; cuts input latency. Minimal FPS cost (1–2%).
• **Radeon Boost** → Disabled for CS2. Dynamically lowers resolution during fast motion, which hurts precision aiming.
• **Texture Filtering Quality** → Performance. Same logic as NVIDIA — free 3–5% FPS.
• **Wait for Vertical Refresh** → Off unless you prefer locked FPS. CS2 competitive players want uncapped frames.

For Intel Arc users (A750, A770), the control panel is still maturing as of 2026. Stick to in-game settings and avoid experimental driver toggles — stability matters more than 2% FPS in competitive CS2.

Resolution Scaling: The Nuclear Option

If you've applied every setting above and still can't hit your target FPS, resolution scaling is the last lever. CS2's dynamic resolution slider lets you render at a lower internal resolution (e.g. 80% of 1080p) and upscale to native. The FPS gain is proportional to the reduction: 90% scaling adds ~20% FPS, 80% scaling adds ~40% FPS.

The tradeoff is clarity. At 90%, most players can't tell. At 80%, distant enemies get slightly blurrier. Below 75%, you're sacrificing competitive edge. Benchmarks show an RX 7800 XT at 161 FPS (1080p high, measured by OpenBenchmarking.org) can push 220+ FPS at 80% scaling with Low shadows — that's the difference between 144 Hz and 240 Hz playable.

When Settings Aren't Enough: Hardware Bottlenecks

CS2 is CPU-sensitive in competitive 5v5 matches, especially on maps like Inferno and Nuke with dense geometry. If you're on a 4-core CPU (older i5, Ryzen 5 3600 or below), you'll struggle to sustain 200+ FPS in late-round utility spam. Measured benchmarks show the ceiling: an RTX 5090 hits 341 FPS at 1080p high, while an RTX 4090 hits 303 FPS — but pair either card with a weak CPU and you'll see 180 FPS instead.

RAM speed also matters. CS2 on Source 2 favors DDR4-3200 or DDR5-5600 and above. If you're running 2400 MHz DDR4, a RAM upgrade can add 8–12% framerate. It's one of the cheapest upgrades with measurable CS2 impact.

If you're unsure where your bottleneck is, run a free playbook at BetterFPS — it analyzes your CPU, GPU, and RAM together and tells you which component is holding you back in CS2 specifically. You'll get a step-by-step optimization guide that prioritizes the changes with the biggest return for your exact hardware.

CS2 performance in 2026 is predictable: Shadow Quality and Global Shadow Quality account for 30–40% of the framerate range, launch options add another 5–10%, and autoexec commands lock in consistency. Apply these changes in order, test with `cl_showfps 2`, and adjust until your FPS floor stays above your monitor's refresh rate. The gap between 160 FPS and 250+ FPS on the same hardware is configuration, not luck.

Frequently asked questions