CS2 Settings Guide

Your CS2 settings are one of the few things in the game you have complete control over. Unlike matchmaking luck or server conditions, the right config is entirely on you to get right. This guide covers everything that matters: video and graphics settings for stable frames, mouse sensitivity, audio, HUD, launch options, and the config tweaks that actually move the needle. Whether you’re fine-tuning a setup that’s mostly working or starting fresh on a new PC, this is the reference.

One thing worth saying upfront: there is no single “best” settings profile that works for everyone. Hardware varies, playstyles vary, and what feels right at 400 DPI feels completely different at 800. What this guide does is explain what each setting actually does mechanically, so you can make informed choices rather than copying someone’s config blindly.

Video and graphics settings for maximum performance

In CS2, frames win fights. The goal of your graphics settings is not to make the game look good, it’s to get the highest stable frame rate your hardware can deliver while keeping the visual information you need to play well. Everything else is secondary.

Start with resolution. The two most common choices among competitive players are 1920×1080 (native 16:9) and a stretched 4:3 resolution such as 1280×960 or 1024×768. These represent a genuine trade-off rather than a simple right-or-wrong choice. Stretched 4:3 widens player models on screen without changing their hitboxes, giving a visually larger target, and it reduces GPU render load, which is why a meaningful share of professional players have used it. Native 16:9 increases your field of view, meaning more of the map is visible at once, which benefits map awareness and peripheral spotting. Higher-end players with strong PCs run native 1080p and rely on raw tracking skill rather than the visual-target-size advantage. If you learned on native resolution, switching to stretched takes real adjustment time; the changed sensitivity feel and visual habits don’t transfer immediately. Try stretched on a Workshop map before committing to it.

The settings that actually matter

Set Display Mode to Fullscreen, not Windowed or Borderless Windowed. Exclusive fullscreen gives the GPU direct output to the display, bypassing Windows desktop compositor overhead, which reduces input lag. This is one of the more meaningful changes you can make if you’re currently running in a windowed mode. One nuance worth knowing: Windows 11’s “Optimizations for Windowed Games” feature (found under Settings → System → Display → Graphics) has narrowed the input-lag gap between Borderless Windowed and true Fullscreen for players who specifically need the multitasking flexibility, but Fullscreen remains the safer default for competitive play.

Turn off V-Sync in both CS2’s video settings and your GPU control panel. V-Sync forces the GPU to wait for the display’s refresh cycle before outputting a frame, which adds input lag. Disable it at both levels, conflicting V-Sync states across in-game and driver settings can cause unexpected behavior.

Global Shadow Quality is the one in-game setting with genuine, current disagreement between sources. Several recent guides recommend Low for maximum FPS. Others specifically recommend Medium or High, arguing that shadows reveal enemy positions around corners before the player model is fully visible, particularly relevant on maps like Nuke. The case for keeping shadows higher than minimum is a tactical-information argument, not a visual-quality one. Low is not automatically the correct competitive choice; it’s a real trade-off between frame rate and positional information. Medium is a reasonable starting point for most players.

Model/Texture Detail has minimal FPS impact in CS2, broad consensus across sources agrees on this. It can be left at Medium or High without a real performance cost; dropping to Low only matters if you’re chasing every possible frame on weak hardware.

Effect Detail and Particle Detail should both be set to Low. Smoke and Molotov rendering is one of the more GPU-intensive aspects of CS2, and lowering these keeps performance stable specifically during utility-heavy rounds. Smokes still block sightlines identically regardless of the detail setting, there is no tactical downside to running these at Low.

Shader Detail guidance is mixed. Low is the safe, performance-first default. Some sources note that High shaders produce a real visual improvement with minimal FPS cost on modern GPUs, and that some professional players have moved to High. Treat this as hardware-dependent rather than a universal recommendation.

Disable Ambient Occlusion. It is GPU-heavy, and several sources argue it can make corners harder to read by adding shadow detail in exactly the spots where enemies hide, a rare case where a “quality” setting may carry a genuine competitive downside beyond just the FPS cost.

For Anti-Aliasing, CMAA2 is CS2’s modern option and a reasonable middle ground. FXAA is cheaper but blurs the image slightly. The difference between them is narrow; personal preference applies here.

Enable Multicore Rendering. This distributes engine workload across CPU cores and has no real downside on any modern multi-core processor.

Enable Boost Player Contrast. It increases visual separation between player models and the environment, which is a direct competitive visibility benefit. It’s worth noting that some individual professionals have preferred it off, citing personal feel at long distances. That is a real exception, not the default recommendation.

Set FSR (FidelityFX Super Resolution) to Off for competitive play. FSR renders at a lower internal resolution and upscales, which can make distant enemies harder to read clearly, a real cost in a game where clarity at range matters.

Frame rate, refresh rate, and fps_max

CS2 leans heavily on the CPU rather than the GPU. Source 2 handles hit registration, physics, sub-tick calculation, and player simulation primarily on the processor. This is a meaningful distinction from many other modern titles and explains why adjusting graphics settings alone won’t fix CPU-bound stutter.

Your monitor’s refresh rate must be correctly set in both Windows Display Settings and confirmed in-game. Running a 240Hz monitor at a default 60Hz is a surprisingly common and easily-missed misconfiguration. The jump from 60Hz to 144Hz is the single largest perceptible upgrade in competitive play, substantially larger than the step from 144Hz to 240Hz, or from 240Hz to 360Hz. 144Hz is the practical 2026 baseline for competitive CS2; 240Hz is the common upgrade tier; 360Hz exists but the perceptible difference above 240Hz is small for most players.

For fps_max, there is a genuine and currently unresolved community debate between leaving it at 0 (uncapped) and setting an explicit cap. The case for capping: a frame rate that bounces wildly between 200 and 500 FPS can feel less consistent than a flat, stable 300, and capping prevents the GPU and CPU from working harder than necessary once you’re well past your monitor’s refresh rate. The case for uncapped: CS2’s sub-tick system processes input the moment it happens rather than at tick boundaries, so consistently higher raw frame rates feed cleaner, more frequent input sampling regardless of monitor refresh rate. Neither position is definitively settled. If you choose to cap, the more common middle-ground recommendation is to set the cap modestly above your monitor’s refresh rate, not equal to it.

Mouse settings and sensitivity explained

Mouse settings are the most personal part of your config, and getting them wrong makes everything else irrelevant. The standardized metric for comparing sensitivities across different setups is eDPI (effective DPI), your mouse DPI multiplied by your in-game sensitivity. Raw DPI and raw in-game sensitivity numbers alone aren’t directly comparable between players, but eDPI is.

The commonly cited professional eDPI range sits roughly between 600 and 1,200, with various sources citing slightly different bands within that window. The reasonable framing: most competitive players land somewhere in that range, and going meaningfully outside it in either direction trades off precision (too high) or speed (too low). There is no single correct number, only the sensitivity you can control consistently.

Raw Input and mouse acceleration

Enable Raw Input in CS2’s mouse settings. This is mandatory, not optional, it is one of the only points with zero disagreement across every source. Raw input bypasses Windows mouse acceleration and pointer speed settings entirely, pulling positional data directly from the mouse. Without it, your Windows pointer speed setting affects your in-game sensitivity and introduces inconsistency.

Disable Mouse Acceleration in CS2. Also disable “Enhance Pointer Precision” in Windows Mouse Settings — this is Windows’ built-in acceleration, found under Control Panel → Mouse → Pointer Options. Acceleration breaks the consistent, repeatable muscle memory that spray control and flick aim depend on. This is treated as close to a hard rule across every source reviewed.

Set your mouse polling rate to 1000Hz or the highest your mouse supports. A 1000Hz polling rate reports position 1,000 times per second versus the 125Hz default, which directly reduces positional reporting delay. Current guides commonly cite lightweight options such as the Logitech G Pro X Superlight series or the Zowie EC series as popular professional choices, though hardware preference is separate from settings configuration.

Finding your sensitivity

A widely used starting point is 400 DPI at 2.0 in-game sensitivity, which gives you 800 eDPI, within the competitive range. Load into Aim Botz on the Workshop and spend 15 minutes tracking moving targets. If you’re consistently overshooting, go lower. If you’re struggling to reach targets without repositioning your arm, go higher. Make one change at a time and give yourself at least a few sessions before evaluating.

400 DPI is the most common hardware DPI among competitive players, paired with an in-game sensitivity roughly between 1.0 and 2.5 to land in the 600–1,200 eDPI range. eDPI calculators are widely available and can help you find the equivalent in-game sensitivity when switching DPI values so you’re not starting from scratch.

Audio and HUD settings that give you an edge

Audio in CS2 is a competitive tool. Positional audio, footsteps, reload sounds, bomb plant audio, utility pulls, carries information you need to make decisions. Your audio settings should be configured to make those sounds as clear and directionally accurate as possible.

Use headphones, not speakers, for competitive play. Set your audio output to Headphones in CS2’s audio settings even if you’re using a headset, the game’s HRTF (head-related transfer function) processing is designed for headphone output and affects how accurately sounds are positioned in three-dimensional space.

Volume levels and key audio settings

The most common audio mistake is running Master Volume too high. When Master Volume is maxed, quiet sounds like distant footsteps get compressed against louder sounds like gunfire. Set Master Volume to around 60–70% and bring overall volume up through your system volume or headset amplifier instead. This preserves dynamic range and makes quiet audio cues easier to distinguish.

Turn Music Volume to zero. The CS2 music kit plays during rounds and can mask audio cues. Disable Round End Music and Death Camera Music as well, these are atmospheric features with no competitive value that actively interfere with information gathering.

CS2’s L/R Isolation setting has no strong consensus on the ideal value. A reasonable starting point is around 50%, adjusting from there based on personal feel. At 100%, the center of the audio field collapses into hard left/right, which some players find clearer and others find disorienting for sounds directly ahead or behind. At 0%, audio blends more naturally but may carry less precise directional information.

Perspective Correction is a newer CS2 feature intended to make audio direction match the player’s actual in-game perspective more accurately. Players who learned audio cues under the older CS:GO-style system sometimes prefer disabling it to keep familiar audio behavior.

Raise the 10-second bomb timer volume. This is consistently flagged across sources as a specific setting worth increasing, commonly suggested around 10–30%. Missing this audio cue in a clutch round has an outsized real cost relative to how small a settings change it is.

Use a flat or neutral EQ preset rather than bass-boosted or “cinematic” presets. Boosted bass can mask or distort the precise footstep frequencies competitive players rely on.

HUD settings

The HUD gives you real-time information about your health, armor, ammo, and economy. The default HUD is functional, but a few adjustments make it cleaner and more readable under pressure.

Set HUD Scale to a value where the radar and health bar are readable without drawing your eye away from center screen. Most players sit between 0.85 and 1.0.

For radar settings: enable Radar Centers the Player, this keeps your own position fixed at the radar’s center, which several sources suggest helps faster spatial parsing during movement. Enable Radar Rotates with Player as well, so “up” on the radar always matches the direction you’re currently facing rather than a fixed compass orientation, reducing the mental translation step between radar and screen. Adjust cl_radar_scale to a zoom level where you can read teammate positions clearly, lower values show more map area at the cost of detail, and the right value is personal preference.

Enable Show Team Positions When Dead in the radar settings. When you’re dead, your radar becomes one of your most useful tools for calling positions to teammates. Having it active and readable is a small habit that compounds over time in Premier.

Launch options and config file tweaks

Launch options and config files let you set parameters that either aren’t available in the in-game menus or that you want locked in place every session. These go in Steam: right-click CS2, Properties, Launch Options.

An important caveat: CS2 has deprecated a large number of CS:GO-era launch options. Several no longer function at all. -tickrate is dead, CS2 uses a sub-tick system that processes input timing independently of server tick boundaries, and this cannot be set via launch option. Any guide still listing -tickrate 128 as a useful CS2 launch option is using stale CS:GO-era advice. Legacy DirectX flags such as -nod3d9ex and similar options are also obsolete since CS2 doesn’t run on the old engine version they were built for. Launch options in CS2 provide marginal, mostly convenience-level gains rather than the meaningful FPS impact they sometimes had in older Source engine games. The actual performance levers live in driver settings, Windows configuration, and in-game video settings.

The launch options that still function and are commonly recommended in 2026 are:

• -novid — skips the intro video on launch (minor convenience, not a performance gain)
• -console — opens the developer console automatically on launch
• -high — sets CS2 to high process priority in Windows Task Manager; impact is debated and considered minor by more rigorous current sources, but costs nothing
• -fullscreen — forces fullscreen mode
• -refresh [your monitor’s refresh rate] — sets refresh rate; CS2 should detect this correctly by default in most cases, making this redundant but harmless as a safety net
• +fps_max 0 — removes the frame cap at the launch level, paired with whatever explicit cap strategy you choose in-game
• -allow_third_party_software — needed specifically to allow OBS or similar capture software to hook into the game
• +exec autoexec — runs your autoexec.cfg on launch

The autoexec.cfg

Your autoexec.cfg is a plain text file that runs console commands every time the game starts. It lives in Steam/steamapps/common/Counter-Strike Global Offensive/game/csgo/cfg. Create it if it doesn’t exist.

Useful commands to include:

• cl_crosshairsize, cl_crosshairgap, cl_crosshairthickness, cl_crosshaircolor — lock your crosshair settings so they don’t reset between sessions or after updates
• cl_crosshairstyle 4 — sets a static crosshair, which is overwhelmingly preferred over dynamic at competitive level; dynamic crosshairs expand on movement and firing, which functions as visual noise once muscle memory already internalizes movement-accuracy penalties
• cl_righthand 1 (or 0 for left-hand viewmodel)
• viewmodel_fov 68 — widens the viewmodel field of view, reducing how much of the screen the weapon occupies
• cl_bob_lower_amt 0, cl_bobamt_lat 0, cl_bobamt_vert 0 — removes weapon bob while moving
• net_graph 1 — displays your ping, packet loss, and frame rate in-game, useful for diagnosing connection issues
• bind “key” “buy ak47; buy m4a1” — buy binds for faster purchases on eco rounds

For crosshair color, cyan, light green, and yellow are the most commonly recommended options for visibility against CS2’s color palette. Red is specifically a poor choice since it blends with blood and hit-effect colors. Very dark colors risk being invisible against dark map geometry. A thin, tight crosshair, size roughly 1–3, gap around -3 to -1, thickness 0–0.5, is the common competitive default: large enough to find quickly, small enough not to obscure a head-sized target at range. An outline of around 0.5–1 helps maintain visibility against both bright and dark backgrounds simultaneously.

End the file with host_writeconfig to save the settings to your main config. Use // before any line to add a comment explaining what a command does.

GPU driver settings: NVIDIA and AMD

In-game settings alone don’t tell the full story. Your GPU driver software has its own settings that directly affect input lag and frame consistency in CS2, and the defaults are not always correct for competitive play.

NVIDIA Control Panel / NVIDIA App

Low Latency Mode is the single most consistently recommended NVIDIA setting for competitive play. Set it to Ultra. This minimizes the GPU’s render queue so frames are processed just before they’re needed rather than buffered ahead of time, directly cutting input lag. One important nuance: if CS2 ships with native NVIDIA Reflex support, in-game Reflex should take priority over driver-level Low Latency Mode, some sources specifically recommend setting the Control Panel Low Latency Mode to Off in that case, since Reflex operates with more complete pipeline control. Verify CS2’s current Reflex support status, as it has been inconsistently reported across sources.

Set Power Management Mode to Prefer Maximum Performance for desktop gaming setups. The “Optimal Power” default allows the GPU to downclock during lighter load moments such as menus and loading screens, which can cause stutter as it ramps back up mid-match.

Set Texture Filtering – Quality to High Performance or Performance. This trades a small, usually imperceptible amount of image sharpness for a real, if modest, FPS gain, a reasonable trade for a competitive title where raw frame rate matters more than texture fidelity.

Set V-Sync to Off in the NVIDIA Control Panel as well as in-game, consistent with the in-game guidance above. If you are using a G-Sync monitor, the more advanced configuration, G-Sync on, V-Sync on in the Control Panel but off in-game, paired with a frame cap a few frames below the monitor’s refresh rate (commonly cited as refresh rate minus 3, e.g., 141 on a 144Hz panel), eliminates tearing without the latency cost of conventional V-Sync. This is a more advanced setup, not the simple default.

Leave Anti-Aliasing overrides at Application Controlled. The NVIDIA Control Panel’s AA override settings were designed for older DirectX 9 and early DX11 titles. Modern games including CS2 handle their own anti-aliasing internally, and forcing driver-level AA on a modern title generally does nothing or causes conflicts.

AMD Radeon Software (Adrenalin)

Enable Radeon Anti-Lag. This is AMD’s direct equivalent to NVIDIA’s Low Latency Mode, reducing the CPU-to-GPU frame queue depth to cut input lag. If AMD’s newer Anti-Lag 2 is specifically available for CS2, support varies by title and is still being rolled out, it is the preferred version over the original Anti-Lag.

Disable Radeon Chill for competitive play. Chill dynamically varies the frame rate cap based on how much on-screen motion is happening, which changes mouse feel moment-to-moment in a way that’s specifically undesirable for competitive consistency. It is also worth noting as a hard technical constraint: Chill and Anti-Lag cannot be enabled simultaneously on most driver versions, enabling one disables the other, so this is a forced choice, not just a preference.

Disable Radeon Boost for competitive play. Boost dynamically lowers render resolution during fast camera movement to maintain frame rate, exactly the wrong moment for reduced clarity in a game where fast crosshair movement during a duel is when you most need a clear target.

Set Wait for Vertical Refresh (AMD’s V-Sync setting) to Off. Use FreeSync if available, paired with an in-game or driver frame cap, rather than traditional V-Sync.

Set Texture Filtering Quality to Performance for the same small FPS gain with minimal visual cost as the NVIDIA equivalent.

Do not enable HYPR-RX for competitive play. This single-toggle bundle activates several AMD features together, including Boost and Chill alongside Anti-Lag, in a way that can’t be selectively disabled. Configure each setting individually for a competitive title like CS2 rather than using this convenience toggle.

Windows-level settings for competitive CS2

CS2 performance is affected by your Windows configuration in ways that in-game settings cannot compensate for. Several Windows settings have a direct, measurable impact on frame consistency and input latency.

Set your Power Plan to High Performance at minimum. Ultimate Performance, a hidden Windows power plan not visible by default, unlocked via a one-time Command Prompt command (powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61) and then selected from Power Options, is cited as a further step that prevents the CPU from downclocking between frames. Several sources specifically link this to improved 1% low frame rates, which reflects the consistency of worst-case frames during a session and is often more impactful to actual feel than average FPS. Laptop users should keep Ultimate Performance active only while gaming and plugged in, as it negatively affects battery life and increases heat.

Enable Game Mode (Settings → Gaming → Game Mode). Modern Windows 11 Game Mode prevents Windows Update from installing mid-session, deprioritizes background processes, and several sources report measurable improvements to frame consistency specifically in competitive titles. The earlier Windows 10-era reputation of Game Mode causing problems in some games is specifically noted as resolved in current versions.

Hardware-Accelerated GPU Scheduling (HAGS) is hardware-dependent. It is beneficial on modern GPUs — RTX 30-series, RX 6000-series, and newer, but can increase frametimes on older cards such as GTX 10-series, GTX 16-series, and RX 5000-series. Check your GPU generation before enabling this.

Disable Xbox Game Bar and Game DVR background recording if you are not actively using them for clipping or recording. The background capture buffer consumes resources continuously even when not in active use, with a more noticeable impact on systems with 16GB RAM or less.

If playing in Borderless Windowed mode for streaming or multitasking convenience, enable Optimizations for Windowed Games (Settings → System → Display → Graphics). This allows the borderless window to bypass the Desktop Window Manager’s compositing pass and access the display more directly, meaningfully closing the input-lag gap between Borderless Windowed and true Fullscreen. It does not make Borderless equal to Fullscreen, but it substantially narrows the difference.

If your monitor supports G-Sync, FreeSync, or HDMI VRR, enable the Variable Refresh Rate (VRR) toggle in Windows (Settings → System → Display → Graphics → Variable Refresh Rate), working alongside the equivalent driver-level setting rather than replacing it.

Keep your GPU drivers current, and use a clean installation method. Display Driver Uninstaller (DDU) fully removes old driver remnants before installing a new version, which is cited as meaningfully reducing stutter and instability compared to simply installing over an existing driver. Old shader caches and conflicting registry entries from incomplete driver transitions are a commonly cited but easy-to-overlook stability issue.

Common CS2 settings mistakes to avoid

Most settings problems come from a handful of the same mistakes. Knowing what to look for makes diagnosing a bad config much faster.

Copying a pro’s config without understanding it. Pro configs are optimized for specific hardware, specific sensitivities, and specific playstyles. A 400 DPI config from a player using a large mousepad on a dedicated gaming rig may feel completely wrong on your setup. Use pro configs as a reference, not a template.

Running V-Sync without realizing it. V-Sync can be enabled in your GPU control panel even if it’s disabled in CS2. Check both. Input latency from V-Sync is immediately noticeable once you’ve played without it.

Ignoring Windows-level settings. CS2 performance is affected by your Windows power plan, background applications, and GPU driver settings. A well-configured in-game setup running on a power-saving Windows plan will underperform. Set the power plan to High Performance or Ultimate Performance before evaluating any other changes.

Changing sensitivity too frequently. Muscle memory takes time to build. Changing sensitivity after every bad session prevents you from ever adapting to any setting. Commit to a sensitivity for at least a week of regular play before evaluating.

Setting shadow quality to Very Low. This is one of the most common graphics mistakes. Very Low shadows remove the dynamic shadows that show enemy positions in gaps and around corners. The frame rate gain rarely justifies the loss of positional information. Medium is the floor for competitive play.

Using outdated CS:GO launch options in CS2. Options like -tickrate 128, -nod3d9ex, and -d3d9ex do nothing in CS2 and in some cases cause issues. If your launch options string was copied from a CS:GO guide, audit it against the current list above.

Not using an autoexec. If your settings reset between sessions or after updates, an autoexec.cfg fixes that permanently. It also lets you share your exact config across machines without manually re-entering every command.

Once your settings are dialed in, the next thing worth thinking about is your loadout. A clean config deserves skins that match. Skinvault lists float values on every item and inventory rotates regularly, so if you’re looking to pick up something specific for your loadout, it’s worth checking what’s currently available.