CS2 launch options

How to set CS2 launch options

Launch options let you pass specific commands to Counter-Strike 2 the moment it starts. To get there, open Steam, go to your library, right-click the game, and choose Properties from the menu.

In the Properties window, stay on the General tab and find the Launch Options text box near the bottom. Type your commands there, separating each one with a single space – otherwise the engine may misread them. Steam saves everything automatically when you close the window, so you just need to launch or restart CS2 for the changes to take effect.

CS2 launch options for FPS

For competitive players, frame rate matters. Tweaking your Steam launch options can help the game boot faster, run in full-screen, and remove any artificial performance cap. These commands won’t replace proper in-game video settings, but they work well as a supplement: they help manage hardware resources, cut down on mid-match stuttering, and give your system a stable baseline to work from.

Core commands for maximum frame rates

A handful of targeted commands can make a real difference, covering CPU priority, display mode, and graphical load.

• -high: Sets the game process to high priority, giving it more CPU resources. Useful on lower-end machines, though it won’t fix every performance problem.

• +fps_max 0: Removes the default frame cap, so your hardware can run at full speed. You can also set a specific number instead of 0 if you want a consistent, locked frame rate.

• -Full-screen: Forces the game into exclusive full-screen, which tells the OS to dedicate its resources to CS2 rather than splitting them with other processes.

• +cl_force preload 1: Loads all models and maps before you spawn, so assets don’t stream in mid-round and cause stutters.

• -softparticlesdefaultoff: Disables soft particle rendering, which noticeably reduces the processing cost of explosions and smoke.

• +mat_disable_fancy_blending 1: Reduces texture blending quality to push more raw frames. Pairing it with disabled dynamic lighting can help further, though some visual effects will look noticeably worse.

Combining commands for a performance baseline

Running multiple commands at once is the fastest way to stack optimizations. A commonly used starting point is -freq 240 -no-browser +mat_queue_mode 2 +fps_max 0 +cl_force preload 1.

You can round it out with network parameters: +cl_inter_ratio 1 +cl_inter 0.031 +cl_cmd rate 128 +cl_update rate 128. After applying a long string like this, keep an eye on your in-game performance. If the client crashes, remove commands one at a time until you find the one causing the problem.

CS2 launch options for monitor refresh

Refresh rate is one of the more important factors in competitive CS2. Launch parameters tell the Source 2 engine how to handle screen settings before the game even opens. Most serious players run at 144Hz or 165Hz at minimum, with many professionals going up to 240Hz or higher.

Without the right launch option, the client can default to your desktop refresh rate, which may be lower than what your monitor supports. That means unnecessary input lag and softer visuals during fast mouse movements.

Getting this right is straightforward: you just need to enter the exact refresh rate your monitor uses. Using the wrong number can cause screen tearing or cap your rendering below what your hardware can actually do.

• -refresh [Hz]: Forces the engine to output at a specific refresh rate (for example, -refresh 144). This keeps the game properly synced with your monitor throughout a match.

• -freq [Hz]: Does the same thing as -refresh (for example, -freq 240). Players often use this version when building out longer optimization strings.

• -Full-screen: Forces the game into an exclusive display state, which prevents the OS from rendering background desktop elements and helps maintain your target refresh rate without windowed mode interfering.

Before applying any of these, check your display settings in the OS to confirm the correct value. A mismatched number won’t give you the improvement you’re after, and in some cases it can cause your monitor to go black on startup.

CS2 launch options for input lag

The gap between moving your mouse and seeing it reflected on screen is something competitive players can’t afford to ignore. Certain engine commands help close that gap by disabling features the game doesn’t need and telling the OS to treat CS2 as the priority process. The result is a shorter processing queue and fewer micro-stutters that can feel like sluggish controls.

The most direct approach is reducing system overhead. A few well-chosen variables tell the Source 2 engine to skip unused hardware and put its processing power where it counts.

• -No joy: Disables joystick and controller support. Removing the background polling for game pads gives a small performance boost and reduces input lag for mouse and keyboard players.

• -high: Sets CS2 to high priority in the OS, giving it more CPU resources, so inputs register quickly even when other programs are running.

• +cl_force preload 1: Loads all models and map assets into memory during the initial loading screen. This stops the storage drive from streaming textures mid-round, which keeps crosshair tracking smooth.

• -threads [X]: Tells the engine to use a specific number of logical processors, where X is your CPU’s thread count. Matching this to your hardware helps data flow to the GPU more efficiently and avoids processor bottlenecks that delay frame output.

Combining these settings creates a noticeably more responsive setup. Players chasing the lowest possible latency often pair -no joy with a high-priority CPU allocation as a starting point.

CS2 launch options for rendering

Controlling how the Source 2 engine draws frames comes down to a few specific parameters. These commands affect display mode, graphics API, and how the rendering workload is distributed across your hardware. Getting them right can eliminate visual inconsistencies and free up resources for the match itself.

• -Full-screen: Runs the game in an exclusive display state rather than a window. This gives CS2 full control over display output, stops the OS from rendering background desktop elements, and improves frame stability.

• -Vulcan: Switches from the default DirectX API to Vulcan. This tends to help AMD graphics cards and Linux systems in particular, often resulting in smoother frame pacing and fewer micro-stutters.

• -Ovid: Skips the Valve intro animation on startup. It gets you to the main menu faster and avoids the resolution flicker that sometimes happens before it loads.

• +mat_queue_mode 2: Forces the material system to use multithreaded rendering, spreading the visual workload across multiple CPU cores instead of bottlenecking on one thread.

• -no-browser: Disables the embedded web browser used for in-game announcements and server messages. Shutting down that background Chromium process frees up memory and prevents CPU spikes during matches.

Testing different APIs and display modes is worth doing, since the best combination depends on your specific hardware. A clean rendering queue keeps visual updates consistent even during heavy firefights.

CS2 launch options that no longer work

Moving to Source 2 made a lot of older commands obsolete. The problem is that players keep copying old CS:GO setups and pasting them in without checking whether they still do anything. Leaving dead commands in your config doesn’t just clutter things up – it also makes troubleshooting harder if something goes wrong later.

Clearing them out means the engine only has to process instructions that actually work.

• -Tick rate 128: CS2 uses a sub-tick server architecture, so forcing a 128 tick rate does nothing. The game doesn’t rely on fixed tick intervals anymore.

• -Ovid: This was useful in CS:GO for skipping startup videos, but the updated engine ignores it entirely.

• -limitvsconst: A legacy command for older hardware limitations. It has no effect in the current rendering pipeline.

• -d3d9ex and-disable_d3d9ex: Both of these were tied to DirectX 9 optimizations. Since CS2 moved away from that API, neither command executes.

To clean things up, open Steam, right-click Counter-Strike 2, select Properties, go to the General tab, find the launch options box, and delete everything in it. Starting fresh ensures your system is only running commands that actually do something.

CS2 launch options for network settings

Getting your connection dialed in requires the right network commands applied at startup. CS2 uses a sub-tick architecture, but competitive players still fine-tune packet delivery and interpolation on the client side. The goal is to make sure your local inputs sync properly with the server, which cuts down on hit registration delays in fast-paced situations.

• +cl_cmd rate 128: Sets the maximum number of command packets sent to the server per second, keeping your outgoing updates as frequent as possible.

• +cl_update rate 128: Sets the maximum number of update packets requested from the server per second, so you’re getting the most current positional data for tracking enemies.

• +cl_inter 0.031: Sets the base interpolation time in seconds. This smooths out player model movement while keeping artificial rendering delay to a minimum.

• +cl_inter_ratio 1: Divides the base interpolation by the update rate for a tighter sync. Works best for players on wired connections with low packet loss.

Adding these to your Steam properties gives you a more responsive online experience. Managing both incoming and outgoing packet behavior helps keep your connection stable across different servers.

CS2 launch options with autoexec

To load your personal config automatically, right-click Counter-Strike 2 in your Steam Library, select Properties, and type +exec autoexec.cfg into the launch options field. That single command tells the engine to read your config file at startup, pulling in all your saved binds, crosshair settings, and performance tweaks without you having to do anything manually.

Using a dedicated config file keeps your setup consistent every time you launch the game.

A useful addition is -console, which opens the developer console as soon as the game starts. With it open, you can check whether your autoexec ran correctly by looking for any custom text outputs or error messages. Combining both options gives you full visibility into what’s actually loading on startup.

Keeping complex scripts in an external file also means your Steam properties field stays clean, which makes it much easier to manage and troubleshoot your settings over time.

CS2 launch options for language and streaming

A few specific commands cover two fairly different needs: adjusting the interface language and reducing system load for streaming. Both are simple to set up and can make a meaningful difference depending on how you use the game.

Interface Language Customization

To force CS2 to display in a specific language regardless of your Steam client’s default, use -language English (or replace “English” with your preferred localization string, such as “Spanish” or “German”). Content creators often use this to keep the HUD and menus readable for their audience during a live broadcast, even if their OS is set to a different language.

Optimizations for Streamers

Broadcasters need every bit of headroom they can get to keep their video feed clean. A few commands help with that.

• -Ovid skips the Valve startup animation, getting you to the main menu faster and avoiding any sudden audio spikes at the start of your stream.

• -no-browser disables the background web browser rendering engine, freeing up memory and CPU cycles for your recording software.

• -full-screen forces the game into an exclusive full-screen state, which capture cards and streaming software tend to handle more efficiently than windowed modes.

These adjustments reduce the load on your system while the game is running. Your streaming software will have more to work with, and your viewers get a cleaner, properly localized broadcast.

CS2 launch options and common risks

Launch options are useful, but pushing too many aggressive settings at once can create instability and make problems harder to diagnose.

Recommended Command Combinations

Pasting a long string of commands all at once makes it nearly impossible to figure out what’s causing an issue if something breaks. A better approach is to add parameters one at a time and test between each addition. Some settings have side effects worth knowing about: -high, for instance, can put extra load on your CPU and slow down background apps like Discord or OBS.

If the game starts crashing, clearing the launch options box entirely is the quickest way to reset and start troubleshooting from scratch.

Valve Anti-Cheat and Safety Concerns

Using launch options carries no risk of a VAC ban. Valve officially supports adjusting these settings through the Steam interface, and they don’t touch protected game memory or inject any unauthorized code. The only real account risk comes from third-party software that forces graphical changes outside of Steam. Sticking to the native Steam properties keeps everything safe.