How to Optimize CS2 for Performance (2026) Optimization Guides

Quick Answers

Common questions answered at a glance

How much FPS can I realistically gain in CS2?

Most players squeeze out 30–70% more FPS through a combination of the optimum in-game settings plus Windows and driver tweaks. CS2 is heavily CPU-bound on the Source 2 engine — the bottleneck is almost always your processor, not your GPU — so budget systems and laptops see the biggest gains.

What’s the single biggest change I can make?

Will I get banned using any of this?

Why CS2 Runs Worse Than CS:GO Did

If you played CS:GO and effortlessly hit 300+ FPS, CS2 probably felt like a downgrade. That’s because Source 2 is a more high-maintenance lady – it compiles shaders in real-time (hence those first-match stutters), needs more Processor threads / cores, and approaches lighting and physics differently. Community testing confirms CS2 is 30–40% more demanding than CS:GO and still struggles with frametime consistency even on high-end rigs like the 9950X3D + 5090.On top of that, Windows is running things such as telemetry, Game Bar, Copilot and various other bandwidth wasting slobs that didn’t exist at CS:GO’s launch. Your hardware didn’t suddenly get worse, everything else piled on it is simply heavier.

IQON's automatic optimizations can help resolve many of these issues with one click.

Learn more

Our guide to improve CS2 FPS lowers the load on everything so your hardware is free to do what it’s meant to do.

Step 1: In-Game Video Settings That Actually Save FPS

Because some of CS2’s settings affect performance differently depending on whether you’re optimizing for pure FPS or competitive performance, the same settings will also have different uses. Some, such as Shadow Quality, actually have useful information embedded in them for competitive play, even at a cost of FPS. Here’s what to tinker with, based on benchmarked FPS impact data from Tradeit.gg:Global Shadow Quality — Low if you need FPS, High if you want competitive. 10–20% FPS difference between Low and Very High. Shadows in CS2 indicate enemy footsteps around corners, so many pros keep them on high just for the competitive relevance with the FPS cost. If you’re starving for fps you can go down to low, otherwise keep them up if you have the budget.Shader Detail — Low. 5–15% more FPS. Governs how many polygons surface shading uses. Low looks fine enough in actual gameplay and eats up no resources.Particle Detail — Low. 5–10% more FPS. Controls how many particles aren’t smoke dusts and explosions, lower means less total pixels on screen for spray battles.Ambient Occlusion — Disabled. 5–10% more FPS. Adds some shadows on edges and corners. Looks great in screenshots. Costs you babes. Not worth it at all in competitive play.Multisampling Anti-Aliasing — The pros don’t drop to the lowest setting here. “None” adds 10–15% more FPS but makes the edges of things jagged and makes enemies blend into geometry more likely. Most pros use 4x or 8x MSAA for cleaner edges. If you’re on a budget system you can drop to CMAA2 as a lighter alternative.Boost Player Contrast — Enabled. This costs 1–2% FPS but allows enemy character models much easier to see on backgrounds. Almost every professional enables this. It’s worth the trade.Texture Filtering Mode — Bilinear. 3–5% more FPS. This controls how textures look on extreme angles and the like. Bilinear is the lightest option. The difference here is slight and you likely won’t even notice the difference in-game.Model/Texture Detail — Low to Medium. 5–10% more FPS. The quality of your weapon models, player models, and environmental textures are controlled here. Low is perfectly sufficient. Medium, if you have Video Card memory to spare is just fine also.FidelityFX Super Resolution (FSR) — Disabled. Unlike Warzone or Fortnite, the FSR implementation introduced to CS2 feels sluggish and blurry. Disable it in CS2 and select “Highest Quality” for a native-resolution image.V-Sync — Disabled. Always. Never turn this on. You are adding so much input delay to a game that exponentially rewards players for having lower latencies to win duels against enemies. You know this already!

Step 2: Resolution — The 4:3 Stretched Debate

The majority of CS2 professionals currently play at 1280x960 in 4:3 stretched, an age-old Competitive resolution in the legacy title. ProSettings.net confirms both s1mple (1280x960) and ZywOo (1024x768) use 4:3 stretched — for more than a decade now of consistent comp play, stretched resolution reveals player models as wider (easier to hit). The extra FPS gain is staggering and many simply prefer the “feel” of the movement playing at this resolution and style.You lose on your peripheral vision though, and 16:9 at least at 1920x1080 gives you a wider field of view. If you’re just starting at CS2, use 1080p at native first. If you want to try what the professionals like to use, switch to 1280x960 4:3 and set your Video Card to stretch it to fullscreen (NVIDIA Control Panel → Adjust Desktop Size and Position → Scaling: Full-screen, Perform scaling on: GPU).

Step 3: Launch Options That Work

CS2 launch options are fraught with myth. Many options that worked in CS:GO no longer function in CS2. As cyber-sport.io explains, CS2’s Sub-Tick system makes legacy network commands irrelevant. That being said, there’s a few that do help.Recommended launch options: +fps_max 0 -nojoy -high -console -softparticlesdefaultoff+fps_max 0 removes FPS cap altogether. Use this always.-nojoy disables joystick support, freeing up a minuscule amount of RAM and Processor overhead.-high tells CS2 to run as a high process priority. This helps on most systems, since it tells Windows there’s no use deprioritizing it.-softparticlesdefaultoff disables soft particle blending, enabling a small FPS gain.Options that DON’T work in CS2: -tickrate 128 (we’re using sub-tick, not traditional tickrates), -novid (this flag is no longer supported), -threads (CS2 runs on its own threading now, and this can cause instability), -d3d9ex (we’re using DirectX 11, not 9).Notable: Most professionals use few to no launch options. s1mple uses just -freq 360 -novid -console +fps_max 999. ZywOo, m0NESY, and donk all use similarly minimal options. If it’s good enough for them, it’s good enough for you.

Step 4: NVIDIA Reflex — The One That Might Start A Fight

This one deserved being made into its own section, because we’re genuinely split on this. This technology from NVIDIA, is designed to reduce input latency. NVIDIA’s own collaboration with Valve achieved up to a 70% reduction in latency when using Reflex in Counter-Strike. Enabling it in most games we get a free win. To put it simply, CS2 is a mess of a game like that.Option A — Enable Reflex in-game (default recommendation). You’re going to set NVIDIA Reflex to “Enabled + Boost” in the video settings of CS2. This is what NVIDIA recommends and works great on a lot of systems.Option B — Disable Reflex completely, you can use the NVIDIA Control Panel instead. Thorough latency testing by CS2 Kitchen (using Arduino + photodiode measurements) has shown that on specific systems (in particular AMD X3D Processors), adding -noreflex to your launch options and the Low Latency Mode to “On” or “Ultra” mode in NVIDIA Control Panel can produce lower frame times and faster input response.The takeaway: test both of these in CapFrameX (a free frame time analysis tool) and take your actual frame time, and 1% lows, not your average FPS counter, and see what you can get. The performance of the two varies wildly across pretty much every hardware setup.

Step 5: Windows Settings That Are Robbing You of Frames

CS2 is very sensitive to Windows background processes. Because Source 2 is more Processor-intensive than most games, it means that anything it ingests and fights for CPU time has a larger impact.Disable Memory Integrity (VBS). You likely have this feature enabled by default on your Windows 11 setup, and it’s going to cost you 5–10% of your FPS. Head over to Settings → Privacy & Security → Windows Security → Device Security → Core Isolation → Turn off Memory Integrity and reboot.Disable Xbox Game Bar and Game DVR. It consumes 200–400MB of RAM and adds 18–23ms of input latency. Settings → Gaming → Game Bar → Off.Enable Game Mode. Windows Game Mode prevents Windows Update and other background processes from running while you’re playing. Settings → Gaming → Game Mode → On.Switch to Ultimate Performance power plan. Open command prompt as admin and enter: powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61. Then go to Power Options and select “Ultimate Performance.” Desktop only — laptops should use “High Performance.”Disable startup programs. Task Manager → Startup Tab. Disable anything that doesn’t need to start with Windows. Spotify, Discord, RGB software, cloud sync apps — all of it loads at boot and stays in RAM forever. Cleaning up startup programs can free up 1–4GB of RAM.Enable Hardware-Accelerated GPU Scheduling (HAGS). Allows your Video Card to handle its own scheduling instead of your CPU. Settings → System → Display → Graphics → Change Default Graphics Settings → Toggle On. Reboot required.

Step 6: NVIDIA Control Panel Settings

Right click your desktop → NVIDIA Control Panel → Manage 3D Settings → Program Settings → Add CS2.Power Management Mode — Prefer Maximum Performance. Prevents your Video Card from reducing its clock speed during gameplay.Low Latency Mode — On. If Reflex is enabled in-game, set this to “On”. If you’re using Option B (no Reflex), set this to “Ultra.”Shader Cache Size — 10 GB or Unlimited. CS2 compiles shaders in real-time. A larger cache means less micro-stutter when loading new areas or effects for the first time.Texture Filtering Quality — High Performance. Minimal visual difference, measurable FPS gain.Vertical Sync — Off. Same as in-game. Never stack VSync in two places.AMD users, the equivalent options in Radeon Software are: Anti-Lag → Enabled, Tessellation Mode → Override → Off, Texture Filtering Quality → Performance, Wait for V-Sync → Off.

Step 7: Networking and Competitive Advantage

In CS2, every millisecond of latency matters. A 20ms ping advantage in a duel can be the difference between trading kills and getting a clean entry. Here’s how to optimize your connection.Use Ethernet, not WiFi. This is non-negotiable for competitive players. WiFi introduces jitter, packet loss, and inconsistency. A cheap Ethernet cable beats a $300 gaming router every time.Switch your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8). Your ISP’s default DNS is slower than either of these. Settings → Network → Your Connection → Edit → DNS → Manual.Set your max matchmaking ping. In CS2 settings, set your maximum acceptable matchmaking ping to 50–80ms depending on your region. This prevents you from being placed on servers halfway across the continent.Rate command. Open console and type “rate 786432” which sets your maximum bandwidth. This allows CS2 to send and receive the maximum amount of data per tick.

Step 8: Hardware-Specific Tips

If you’re on a budget or older PC: Set everything to Low. Use 1280x960 4:3 stretched for a massive FPS boost. Disable Ambient Occlusion and drop Shader Detail to Low first — those two alone can net you 20–25% combined. Use CMAA2 for anti-aliasing instead of MSAA.If you’ve only got 8GB of RAM: Close everything before you launch CS2. Chrome alone can eat 2–4GB. Make sure your pagefile is system managed on an SSD. Upgrade to 16GB if possible — 8GB is the minimum spec and you’ll have constant stuttering during round transitions.If you’re on a laptop: Always play plugged in. Set both Windows and your manufacturer’s software to High Performance mode. Prop the back of your laptop up — thermal throttling kicks in at 90–95°C and your FPS will tank.Enable XMP/DOCP/EXPO in your BIOS. Your RAM is probably running at 2133MHz instead of its rated speed. Enabling the speed profile in BIOS can give you 15–20% better performance. CS2 especially benefits from fast memory since Source 2 is CPU-bound.Consider 32GB of RAM. CS2 itself doesn’t need 32GB, but if you’re running Discord, a browser, and music in the background, 16GB fills up fast. 32GB gives you headroom so nothing fights for memory.

Step 9: What the Pros Actually Use

If you look at the top CS2 professionals, the pattern is crystal clear: almost everyone plays on 4:3 stretched at either 1280x960 or 1024x768, Shader Detail on Low, Particle Detail on Low, Shadows on High (for competitive info), and everything else stripped back.s1mple (BC.Game) plays on 1280x960 4:3 stretched with 8x MSAA, Shader Detail Low, and High Shadows. He keeps Model Detail on Low and Texture Filtering on Bilinear. Interesting note: he has NVIDIA Reflex disabled, preferring his own latency stack.ZywOo (Team Vitality, HLTV #1 2023) goes even lower at 1024x768 4:3 stretched with Reflex Enabled, 4x MSAA, and keeps Boost Player Contrast on. His settings are more “balanced” than s1mple’s — higher Shader and Texture Detail but at the cost of a lower resolution. Both approaches work at the highest level.The lesson: pros don’t chase beautiful graphics. They chase consistent frames, clean edges, and the lowest possible input latency. Copy their structure, then tune to your hardware.

Common CS2 Issues and Fixes

Stuttering on first match after updates. This is shader compilation. CS2 compiles shaders the first time it encounters new effects. Let the game sit in a deathmatch or workshop map for 5–10 minutes after each update to pre-compile. Also clear your old shader cache: NVIDIA Control Panel → Manage 3D Settings → set Shader Cache to Unlimited to avoid this filling up.FPS drops during smokes and molotovs. CS2’s volumetric smokes are beautiful but expensive. This is a CPU problem, not GPU. Lower Particle Detail to Low, reduce Shadow Quality if needed. If you’ve got an older quad-core, these drops are unfortunately inherent to Source 2’s smoke rendering.Micro-stutters with high average FPS. You’ve got a frametime problem, not an FPS problem. Check your 1% lows in CapFrameX. Common causes: Memory Integrity (VBS) enabled, Xbox Game Bar running, NVIDIA Shader Cache too small, or your RAM not running at XMP speed.Game crashes with “VAC was unable to verify” error. This isn’t a ban. It’s usually caused by antivirus software interfering with VAC. Whitelist CS2 in your antivirus, verify game files through Steam, and try restarting Steam as administrator.High ping despite fast internet. Lower your max matchmaking ping setting. Switch DNS to 1.1.1.1. Make sure nothing else on your network is hogging bandwidth. If you’re on WiFi, switch to Ethernet immediately.

The Short Version

If you’ve only got 5 minutes, do these in order:1. Set Shader Detail to Low, Particle Detail to Low, Ambient Occlusion to Disabled2. Disable V-Sync, enable NVIDIA Reflex On + Boost (or test Option B)3. Try 1280x960 4:3 stretched if you’re comfortable with it4. Disable Xbox Game Bar (Settings → Gaming → Game Bar → Off)5. Disable Memory Integrity (Settings → Device Security → Core Isolation → Off)6. Enable XMP/DOCP in BIOS for your RAM speedThat’s 80% of the benefit in 5 minutes. Everything else in this guide is the remaining 20%.See you on Mirage. Or Dust 2. Or Inferno. Or… you know the drill.