Your CS2 video settings have a direct impact on how the game feels to play, not just how it looks. The difference between 80 FPS and 200 FPS is the difference between sluggish, inconsistent input response and a game that actually keeps up with you. Getting these settings right in 2026 matters more than ever because CS2’s Source 2 engine handles rendering differently from CS:GO, and a lot of old guides are still recommending options that no longer apply.
This guide covers the settings that actually move the needle on CS2 performance, from display configuration through to hardware-level tweaks. No fluff, no outdated CS:GO advice carried over unchanged.
Resolution, aspect ratio, and display mode explained
Display mode should be set to Fullscreen. Fullscreen gives the game exclusive control over the display, which reduces input latency by bypassing Windows desktop compositing, the overhead that Borderless Windowed mode still carries. Borderless Windowed has narrowed this gap on systems where Windows’ “Optimizations for windowed games” feature is enabled, but Fullscreen remains the safer default for competitive play.
Resolution and aspect ratio come down to a genuine trade-off with no single right answer. Native 1920×1080 at 16:9 gives the sharpest image and the widest horizontal field of view. Stretched 4:3 (running a 4:3 resolution such as 1280×960 or 1024×768, stretched to fill a 16:9 panel) makes player models appear wider on screen, which some players find easier to hit, and it also reduces the total pixel count the GPU has to render, useful on lower-end hardware. The cost is a narrower field of view and distorted proportions. Black bars 4:3 keeps the correct proportions but shrinks the image. Neither approach is objectively better for aim; the resolution question is covered in more depth in a dedicated CS2 settings and configuration guide, but the short version is that it is a real trade-off worth understanding rather than dismissing.
Whatever resolution is chosen, make sure the in-game refresh rate matches the monitor’s actual refresh rate. Running a 144Hz monitor capped at 60Hz in the display settings is a common mistake that makes the game feel far worse than it should.
The graphics settings that impact FPS the most
CS2 is more CPU-bound than GPU-bound at competitive frame rates, so the settings that reduce CPU overhead matter as much as the ones that reduce GPU load. A few specific settings have an outsized effect on performance.
Settings to prioritize for performance
- Global Shadow Quality: This is a genuine point of disagreement worth understanding honestly. Setting it to Low maximizes FPS, shadows are computationally expensive. However, Medium or High preserves a real tactical signal: shadows can reveal an enemy’s position around a corner before their model is visible, particularly on maps like Nuke. This is not a settled debate, and the right choice depends on whether you prioritize raw frame rate or that tactical information.
- Model/Texture Detail: The FPS impact here is minimal either way, so leaving it at Medium or High is perfectly reasonable. It will not meaningfully hurt performance on most systems.
- Effect Detail: Low. Smokes and Molotovs are among the most GPU-intensive things CS2 renders. Lowering this keeps frames stable during utility-heavy rounds without changing how smokes function tactically.
- Shader Detail: Low is the safe default. Some players run High on modern GPUs with minimal performance cost, but this is hardware-dependent, test it rather than assuming.
- Ambient Occlusion: Disabled. It is GPU-heavy, and it can actively work against visibility by shadowing the exact corners where enemies tend to hide.
- Anti-Aliasing: CMAA2 is a reasonable middle ground in CS2, it smooths edges without the heavier cost of more aggressive anti-aliasing modes.
- FSR: Off for competitive play. FSR renders at a lower internal resolution and upscales the result, which can soften distant targets, costing you exactly the clarity you need in duels.
Settings to enable
- Multicore Rendering: Enabled. This distributes the rendering workload across CPU threads. Disabling it on a modern processor leaves performance on the table with no benefit.
- Boost Player Contrast: Enabled is the more common recommendation, it increases visual separation between player models and the environment, which directly improves competitive readability. A small number of professional players reportedly run it off, citing feel at long range, but that is a genuine exception rather than the default.
The FPS cap deserves attention here. The fps_max console command sets a frame rate ceiling, and this is a genuinely unresolved debate. Running uncapped (fps_max 0) feeds CS2’s sub-tick system with the highest possible raw input sampling rate, which is the argument for leaving it open. On the other hand, a stable cap set a little above your monitor’s refresh rate can produce more consistent frame delivery than wild swings between 200 and 500 FPS, which some players find smoother in practice. Both approaches have real merit, the right choice depends on your hardware and how consistent your uncapped frame rate actually is.
Advanced video options and launch commands worth using
A handful of launch options and console commands give additional control over performance that the settings menu doesn’t expose directly. These are set in Steam via Library → CS2 → Properties → Launch Options.
- -novid: Skips the intro video on launch. Small quality-of-life change, zero downside.
- -high: Sets CS2’s process priority to High in Windows. Can reduce stutter on systems where background processes compete for CPU time. Not universally beneficial, but worth testing.
- +fps_max [number]: Sets the frame rate cap at launch rather than requiring a console command each session.
One important note: many launch options that circulated in CS:GO guides, including -tickrate and -nod3d9ex, are not relevant or functional in CS2’s Source 2 engine. Adding them does nothing at best and can cause unexpected behavior at worst. Strip out any old CS:GO launch options before applying the above.
In the console, cl_showfps 1 displays a live frame rate counter, and net_graph 1 shows a more detailed performance breakdown including ping and tick information. These are useful for diagnosing whether a performance issue is network-related or hardware-related before making changes.
Hardware and OS settings that affect CS2 performance
The in-game settings only go so far. Several hardware and operating system configurations sit outside CS2 entirely but have a meaningful effect on how the game performs.
Windows power plan: Set to High Performance or Ultimate Performance. The Balanced power plan throttles CPU clock speeds under light load, which can cause frame time inconsistencies during gameplay. High Performance keeps the CPU running at full speed. This setting is in Control Panel → Power Options.
GPU driver settings: In NVIDIA Control Panel or AMD Software, set the preferred refresh rate to “Highest Available” and confirm that the correct monitor refresh rate is active. For NVIDIA users, enabling Low Latency Mode (set to Ultra) reduces the pre-rendered frame queue, which cuts the gap between mouse input and what appears on screen.
Background processes: Close anything that competes for CPU and RAM during a session. Browser tabs with video, Discord video calls, and recording software all pull resources. If recording is needed for review, test the FPS impact before a ranked session rather than discovering it mid-game.
Storage: CS2 installed on an SSD rather than an HDD reduces level load times and can reduce stutters caused by assets streaming from disk during play. It won’t directly raise average FPS, but it eliminates one source of inconsistency.
Getting these hardware and OS settings dialed in alongside the in-game configuration is what separates a genuinely smooth CS2 experience from one that looks optimized on paper but still stutters in practice. If the inventory needs refreshing, Skinvault’s trading bots process trades in seconds with competitive pricing against the Steam Community Market.
