CS2 FPS Boost: Best Settings and Launch Options for 2026
SHORT ANSWER
For maximum CS2 FPS, set Shader Detail, Model/Texture Detail and Particle Detail to Low, Ambient Occlusion to Disabled, Global Shadow Quality to High, High Dynamic Range to Performance and NVIDIA Reflex to Enabled + Boost, then use the launch options -novid -nojoy -fullscreen. Keep Boost Player Contrast on and shadows above Low - both cost a little performance and materially improve your ability to see enemies.
At a glance
| Engine | Source 2 |
|---|---|
| Primary bottleneck | CPU (single-thread heavy) |
| Target frame rate | At or above your refresh rate, capped for VRR |
| Biggest single win | Shader Detail and Particle Detail to Low |
| Do not lower | Shadows, Boost Player Contrast |
Key takeaways
- CS2 is heavily CPU-bound at competitive frame rates. If your GPU sits at 60% usage, that is normal and lowering graphics settings will not help much.
- Shader Detail and Particle Detail are the two settings with the worst cost-to-benefit ratio - drop both to Low first.
- Do not lower Global Shadow Quality below High. Shadows in CS2 render enemy silhouettes around corners and are a genuine information source.
- Boost Player Contrast costs a small amount of performance and is worth every frame it takes.
- Most CS:GO-era launch options no longer exist in Source 2. -threads, -high and -tickrate do nothing or actively hurt.
Quick setup
- 1
Set the launch options
Right-click Counter-Strike 2 in Steam, choose Properties, and paste -novid -nojoy -fullscreen into Launch Options. Ignore the longer strings shared in CS:GO-era guides; the rest are Source 1 leftovers that do nothing here.
- 2
Drop Shader Detail and Particle Detail to Low
Advanced Video settings. These two are the largest wins in the menu and neither costs you competitive information - particle detail in particular pays out during smokes and molotovs, where frame rate normally collapses.
- 3
Leave the shadows alone
Keep Global Shadow Quality at High and Dynamic Shadows on All. CS2 renders enemy shadows that reveal players around corners, so lowering these trades information for a small number of frames.
- 4
Enable Reflex and cap your frame rate
Set NVIDIA Reflex Low Latency to Enabled + Boost, and set fps_max about three below your refresh rate if you use G-Sync or FreeSync.
- 5
Free up CPU time
Enable XMP or EXPO in BIOS, set the Windows power mode to Best performance, and close hardware-accelerated browser tabs. CS2 is CPU-bound, so this is where most of the remaining gain lives.
Why CS2 does not respond to graphics settings the way you expect
CS2 runs on Source 2 and, at the frame rates competitive players target, it is almost always limited by your CPU rather than your GPU. This surprises people who open Task Manager, see the GPU at 55% and assume something is broken. It is not - the CPU is finishing its work on each frame before the GPU has anything left to do.
The practical consequence is that dropping from 1440p to 1080p, or turning texture quality down, often changes almost nothing. What does help is reducing the per-frame CPU work: particle detail, shader complexity, and the number of background processes competing for cores. That is why the system-level section further down matters more in CS2 than in most other games.
The CS2 video settings, one by one
| Setting | Recommended | Why |
|---|---|---|
| Boost Player Contrast | Enabled | Brightens player models relative to the environment. Costs a small amount of GPU time and is the most valuable visibility setting in the game. Never turn this off for frames. |
| Wait for Vertical Sync | Disabled | V-Sync adds a full frame of latency. Use a frame cap plus G-Sync or FreeSync instead. |
| Multisampling Anti-Aliasing Mode | 2x MSAA (or CMAA2 on weaker GPUs) | 8x MSAA is very expensive for a marginal edge-quality gain. Going to None makes distant player models shimmer and harder to track. |
| Global Shadow Quality | High | Deliberately not Low. CS2 renders enemy shadows that reveal players around corners and above you. Lowering this removes information, and the frame cost is modest. |
| Dynamic Shadows | All | Same reasoning - shadows cast by other players are competitively useful. |
| Model / Texture Detail | Low | Meaningful CPU and memory saving with essentially no impact on your ability to identify a player at range. |
| Texture Filtering Mode | Bilinear or Anisotropic 2x | Anisotropic 16x costs frames for surface detail on floors you are not looking at. |
| Shader Detail | Low | One of the two largest wins in the menu. Reduces per-pixel shader complexity across the whole scene. |
| Particle Detail | Low | The other large win, and it pays out exactly when you need it - smokes, molotovs and flashbangs are where frame rate collapses. |
| Ambient Occlusion | Disabled | Subtle contact shadowing that costs real GPU time and adds no competitive information. |
| High Dynamic Range | Performance | The Quality setting costs frames for tone-mapping fidelity that does not help you win rounds. |
| FidelityFX Super Resolution | Disabled, or Ultra Quality if GPU-bound | Because CS2 is usually CPU-bound, upscaling often returns nothing. If your GPU is genuinely at 99%, Ultra Quality is the only preset that does not soften player models unacceptably. |
| NVIDIA Reflex Low Latency | Enabled + Boost | Shortens the render queue. Costs a small number of frames and returns a larger reduction in click-to-photon latency, which is the thing you actually feel. |
Launch options: what still works in Source 2
Right-click Counter-Strike 2 in Steam, choose Properties, and paste into the Launch Options box. Most of the long strings shared in CS:GO-era guides are inherited from a different engine and either do nothing or hurt.
-novid -nojoy -fullscreen| Setting | Recommended | Why |
|---|---|---|
| -novid | Keep | Skips the intro video. Saves a few seconds per launch, no downside. |
| -nojoy | Keep | Skips controller subsystem initialisation. Small memory saving, faster startup. |
| -fullscreen | Keep | Forces exclusive fullscreen, which is the lowest-latency presentation path. Windowed and borderless both add a compositor step. |
| -high | Avoid | Raises process priority above other system threads. On modern schedulers this causes audio and input stutter more often than it helps. |
| -threads N | Avoid | A Source 1 option. In Source 2 it either does nothing or interferes with the engine's own thread allocation. |
| -tickrate 128 | Does nothing | CS2 uses sub-tick timing. Tickrate launch options are meaningless in this engine. |
| -d3d9ex / -softparticlesdefaultoff | Does nothing | Source 1 leftovers. CS2 does not use DirectX 9 and does not recognise these. |
Console commands worth setting
Enable the console in Settings > Game > Enable Developer Console, then open it with the tilde key.
// Uncapped, or set to 3 below your refresh rate if you use G-Sync/FreeSync
fps_max 0
// Maximum bandwidth - use this unless you are on a very constrained connection
rate 786432
// Lightweight on-screen performance readout
cl_showfps 1
// Full network graph while diagnosing stutter (0 to turn off)
cq_netgraph 1On a variable-refresh display, uncapped frame rate is not what you want. Set fps_max to roughly three below your refresh rate - 237 on a 240 Hz panel, 141 on 144 Hz - so you stay inside the VRR window and avoid the latency spike that occurs when frames queue at the refresh ceiling.
System changes that matter more in CS2 than elsewhere
Because CS2 is CPU-bound, anything competing for CPU time shows up directly in your 1% lows. This is where most of the remaining gain lives.
- Close browser windows and Discord streams before playing. Hardware-accelerated browser tabs are the most common cause of unexplained CS2 frame drops.
- Disable the Steam overlay for CS2 specifically if you do not use it - Properties > General > Enable the Steam Overlay.
- Enable XMP or EXPO in BIOS. Memory bandwidth and latency matter more in CS2 than in almost any other competitive title, and a machine running JEDEC fallback speeds gives up a large amount of headroom.
- Set the Windows power mode to Best performance so cores are not parked between rounds.
- Prune startup applications. RGB software, capture utilities and vendor updaters all take CPU slices during a round.
- Keep the game on an SSD. Map load and round transitions are the only disk-heavy moments, but they are where hitching appears.
Frequently asked questions
Why is my GPU usage low in CS2?
Because CS2 is CPU-bound at high frame rates. The CPU finishes preparing each frame before the GPU is saturated, so GPU utilisation sits well below 100% while your frame rate is limited by single-thread CPU performance. This is normal and expected. It also means lowering resolution or texture quality will do very little - focus on particle and shader detail, background CPU load, and memory speed instead.
Should I lower shadows in CS2 for more FPS?
No. Keep Global Shadow Quality at High and Dynamic Shadows on All. CS2 renders shadows cast by other players, which reveals enemies around corners and on levels above you. The frames you gain by lowering shadows are worth less than the information you lose. Lower Shader Detail and Particle Detail instead - they cost more and tell you nothing.
What are the best CS2 launch options in 2026?
-novid -nojoy -fullscreen. That is the complete useful set. Most longer strings circulating online are inherited from CS:GO and Source 1: -threads, -d3d9ex and -softparticlesdefaultoff do nothing in Source 2, -tickrate is meaningless because CS2 uses sub-tick timing, and -high causes audio and input stutter more often than it helps.
Does FSR help FPS in CS2?
Usually not, because the bottleneck is your CPU rather than your GPU, and upscaling only reduces GPU work. Check GPU utilisation first: if it is genuinely pinned at 98-99%, FidelityFX Super Resolution at Ultra Quality will help. Below that, it costs you image clarity on player models for no frame-rate return.
What FPS should I cap CS2 at?
If you have a G-Sync or FreeSync monitor, set fps_max to about three below your refresh rate (237 on 240 Hz, 141 on 144 Hz) so you stay inside the variable-refresh window. On a fixed-refresh monitor without VRR, leaving fps_max at 0 gives the lowest input latency at the cost of tearing. A stable capped frame rate consistently feels better than a higher but fluctuating one.
WRITTEN BY
Frost Live
Frost Live is the founder of Frozen Tweaks and the creator behind the FrozenTweaks optimization guides. He has spent years testing Windows, GPU driver and in-game settings on competitive titles including Counter-Strike 2, Valorant, Fortnite, Apex Legends and Call of Duty, and turned the tweaks that survived that testing into the Frozen Tweaks optimizer.
Related guides
Read this guide as plain markdown
Stop re-doing this after every update
Frozen Tweaks applies the system-level optimizations in our guides, logs every change so you can roll any of it back, and re-applies your configuration after Windows and driver updates revert it.
Download Frozen Tweaks