CS2 FPS Boost: 9 Fixes for Low FPS

Low FPS in CS2 is almost always a settings problem, not a hardware death sentence. The fixes below are ordered by how much framerate they typically recover — work through them top to bottom and measure the difference with cl_showfps 1 after each change. Type it in the console, or check our cl_showfps command page for the display modes.

Fix 1: Update Your GPU Driver

Valve ships CS2 updates that rely on driver-side optimizations, and both NVIDIA and AMD have released multiple driver versions with CS2-specific performance fixes. If your driver is more than a couple of months old, update it before touching anything else: the NVIDIA App(which replaced GeForce Experience as NVIDIA's driver and settings hub) for GeForce cards, AMD Software: Adrenalin Editionfor Radeon. On a troubled install, choose the clean/custom install option so old driver settings don't carry over.

Fix 2: Sort Out the Expensive Video Settings

In Settings → Video → Advanced Video, four settings decide most of your GPU cost:

• Shader Detail → Low. Often worth 15–25% on mid-range GPUs.
• Global Shadow Quality → Low. Disables most dynamic shadow work. Note that Medium is the minimum for seeing enemy shadows at full distance, so competitive players often compromise on Medium.
• Multisampling Anti-Aliasing → CMAA2 or None. MSAA 4x/8x is the single most expensive toggle in the menu.
• FidelityFX Super Resolution → Disabled (Highest Quality). FSR renders at a lower internal resolution and upscales, which sounds like free FPS — but CS2's spatial upscaler visibly softens distant enemies. Treat it as a last resort for genuinely underpowered GPUs, and prefer simply dropping resolution (Fix 3), which keeps the image sharp.

Also set V-Sync → Disabled (it adds input lag and caps FPS) and Boost Player Contrast → Enabled (cheap and improves visibility). For the full settings table with FPS impact ratings, see our FPS optimization guide.

Fix 3: Drop Your Resolution

Rendering fewer pixels is the most reliable FPS gain there is. Moving from 1920×1080 to 1280×960 (4:3) cuts pixel count by 44% and typically buys 30–50% more frames — it's why a large share of professionals still play 4:3 stretched. Use our resolution calculator to compare aspect ratios, and check what the pros run on our pro player settings pages.

Fix 4: Set Launch Options

Right-click CS2 in Steam → Properties → Launch Options and add:

-fullscreen +fps_max 0

-fullscreen forces exclusive fullscreen (the lowest-latency display mode) and +fps_max 0 uncaps the framerate (see the fps_max command page for capping strategies). -high (high CPU priority) still functions but its benefit is debated — test it and drop it if you measure no difference. Delete legacy CS:GO options: -novid (CS2 has no intro video), -threads, -d3d9ex, and -tickrate 128 do nothing in CS2 or actively hurt. Our launch options optimizer builds a clean, current string for you, and the FPS optimization guide covers the full list of live and dead flags.

Fix 5: NVIDIA / AMD Control Panel Settings

NVIDIA Control Panel → Manage 3D Settings → Program Settings → cs2.exe: set Power management mode to "Prefer maximum performance", Low Latency Modeto "Ultra" (or enable NVIDIA Reflex in-game instead, which supersedes it), and Texture filtering qualityto "High performance".

AMD Adrenalin → Gaming → CS2: enable Radeon Anti-Lag, set Texture Filtering Quality to Performance, and make sure Radeon Chill (an FPS limiter) is off.

Fix 6: Windows Power Plan and Game Mode

In Settings → System → Power, set the power mode to Best performance — the balanced plan downclocks your CPU between rounds. Windows Game Mode (Settings → Gaming) is worth testing both ways: it helps on some systems by deprioritizing background tasks and hurts on others. Change one thing at a time and measure.

Fix 7: Close Background Apps and Overlays

Chrome tabs, Discord (especially its overlay), Wallpaper Engine, RGB software, and capture tools like the NVIDIA App's Instant Replay all steal CPU time from a CPU-bound game. Close what you can and disable overlays you don't use — each overlay hooks into the game's rendering pipeline and costs frames.

Fix 8: Trim In-Game Extras with an Autoexec

Be picky here: most CS:GO-era "FPS commands" (cl_forcepreload, r_drawtracers_firstperson) were removed from the Source 2 engine entirely — any guide still recommending them is stale. What still works: engine_low_latency_sleep_after_client_tick true (shifts the engine's low-latency sleep to after client simulation, trimming input latency) and a deliberate fps_max cap if your frametimes are spiky. Put them in an autoexec so they apply every session — our autoexec generator writes the file for you, and the console commands index documents every performance command that survived the engine switch.

Fix 9: Check Your Hardware Bottleneck

If nothing above gets you to a stable framerate, identify the bottleneck: open Task Manager's performance tab while playing. CPU pinned near 100% with the GPU loafing means CS2's real constraint — CPU single-core speed — is your limit. Sixteen GB of RAM in dual-channel and an SSD are effectively mandatory; beyond that, a modern mid-range CPU moves the needle more than a GPU upgrade for this game.

Frequently Asked Questions

Why is my FPS so low in CS2 compared to CS:GO?

CS2 runs on Source 2 with more demanding lighting, smoke simulation, and rendering. It is also more CPU-bound than CS:GO, so older quad-core CPUs that handled CS:GO fine can bottleneck CS2. Lowering shader detail, shadow quality, and resolution recovers most of the difference.

What launch options give the biggest FPS boost in CS2?

Honestly, none give a big boost. +fps_max 0 uncaps your framerate from launch and -fullscreen forces exclusive fullscreen, the lowest-latency display mode. -high (high CPU priority) is worth testing but its benefit is debated. Skip CS:GO-era flags like -novid — CS2 has no intro video, so it does nothing. Video settings and GPU driver configuration matter far more.

Does capping FPS improve performance in CS2?

An uncapped framerate (fps_max 0) gives the lowest input latency, but on some systems a cap slightly below your average FPS produces more stable frametimes. Try uncapped first; if your frametime graph is spiky, experiment with a cap around your 1% low FPS.