Best CS2 Launch Options: What They Do and Which to Use

Launch options are command-line parameters Steam passes to Counter-Strike 2 when it starts, before the game is even on screen. A few of them are genuinely useful for skipping intros, enabling the console, or forcing your monitor's refresh rate; many popular ones do nothing in CS2 or can even hurt performance. This guide separates the useful from the useless so you add only what helps.

These launch options and their effects were checked in October 2026 against Steam's launch options field, the Counter-Strike 2 console, and community discussion on r/GlobalOffensive. Some options that existed in earlier Counter-Strike versions behave differently or no longer apply in CS2, so this guide notes where that is the case.

How to set launch options

In your Steam library, right-click Counter-Strike 2, choose Properties, and in the General tab you will find the launch options field. Type the options there separated by spaces. They take effect the next time the game starts. Because they run before the game loads, launch options are the right place for things that need to be set early — like enabling the console or forcing a display mode — while everything else is better handled in your in-game config. A good habit is to write out the field somewhere you can read it, with each option on its own mental line and a note of what it does, rather than pasting a dense string you will not remember the meaning of later. Launch options are easy to set and then forget about for months, so a little clarity now saves confusion the next time you look.

A good rule is to keep this field minimal. The temptation is to paste a long string of options promising more FPS, but most of those are placebo or outdated, and a bloated launch line is just more to go wrong. Add only options whose effect you can explain.

There is a simple reason launch options are the wrong home for most tweaks: they are static text applied once at startup, they do not autocomplete or validate the way the in-game console does, and a single typo in the field can stop an option working with no obvious error. The console, by contrast, tells you immediately whether a command exists and what its current value is, and a config file keeps those commands organized and commented. So the mental model is to use launch options only for the few things that genuinely must happen before the game window exists — enabling the console, forcing a display mode or refresh rate, skipping the intro — and to treat everything about how the game plays as the console and config's job.

The genuinely useful options

• -novid — skips the intro video on launch. Harmless and saves a few seconds every start. Widely recommended.
• -console — opens the developer console automatically on launch. Useful if you rely on the console, though you can also just enable it in Settings.
• -freq (or -refresh) followed by your refresh rate — forces the game to output at your monitor's refresh rate. Valuable if the game ever defaults to 60Hz on a high-refresh monitor, which is a common and frustrating issue.
• -fullscreen — forces fullscreen mode, useful if the game keeps launching windowed.
• -tickrate — only relevant for certain offline/practice servers; in CS2's subtick world it does not change matchmaking, so most players do not need it.

For the large majority of players, -novid plus the refresh-rate option is the entire list worth having. Everything you want to tune about gameplay belongs in your config, not here — see our config guide for that.

The refresh-rate option deserves emphasis because of how common and invisible the problem it solves is. Modern monitors frequently run at 120Hz, 144Hz, 240Hz or higher, but a game can launch at 60Hz if it misreads the display or a driver setting is off, and the game will still look perfectly fine to the eye at a glance — it is just quietly rendering far fewer frames than your monitor can show. Players sometimes spend hours chasing a "laggy" feeling that is nothing more than the game stuck at 60Hz on a high-refresh panel. Forcing the refresh rate in the launch options, and confirming in Windows display settings that the desktop itself is set to the monitor's full rate, resolves it. If the game ever feels less smooth than you expect, this is one of the first things to check.

Options to avoid or skip

Several famous launch options are either useless in CS2 or actively counterproductive:

• -high — sets the process priority to high. It can seem to help but often causes stutters and input issues by starving other system processes, so it is generally not recommended.
• +fps_max and other in-game cvars — these work, but they belong in your config, not the launch line, where they are harder to manage.
• -nod3d9ex, -nojoy, various "FPS boost" strings — many of these are carried over from older engines or myths and have no real effect in CS2. Adding them just clutters your launch options.
• -threads — manually setting thread counts usually performs worse than letting the engine decide. Leave it alone.

The pattern here is that modern CS2 handles most optimization itself. The era of long FPS-boosting launch strings is largely over, and copying one from an old guide can do more harm than good.

It helps to understand why these myths persist. Many of the famous "FPS boost" launch options date from much older engines, where they genuinely did something, and they were copied forward from guide to guide for years after they stopped applying. Others produce a placebo effect: a player adds a long string, restarts, pays closer attention than usual, and feels an improvement that is really just attention and a fresh launch. The engine and your graphics drivers have become very good at managing threads, memory, and priority on their own, and overriding those decisions by hand usually interferes rather than helps. The honest takeaway is that if an option's purpose cannot be explained in one plain sentence, it almost certainly does not belong in your launch line, and removing it costs you nothing.

Auto-running a config at launch

One powerful use of launch options is +exec followed by a config file name, which runs that config automatically when the game starts. This is a clean way to guarantee your autoexec applies every launch without relying on the menu to remember your settings. If some of your settings keep resetting after updates, pairing +exec with a well-maintained autoexec is the most reliable fix. The practice server commands, by contrast, should stay in a separate config you run manually — our practice commands guide explains why.

One caveat with +exec is that it depends on the config file name and location being correct, so if you rely on it, test once that the game actually runs your config at launch rather than assuming it does. A quick way to verify is to put a harmless, visible setting — like a distinctive crosshair color — in the config and confirm it is applied the moment you load in. If it is not, the file name, extension, or folder is wrong, and you can fix that once rather than wondering for weeks why your settings keep drifting. This small check turns +exec from a hopeful line into a guarantee that your preferences load every single time.

A sensible default launch line

For most players, a short launch line of -novid, -console, and the refresh-rate option for your monitor covers everything launch options should do, with +exec added if you want to force your autoexec. Resist adding more. Then put your real tuning — frame cap, crosshair, viewmodel, sensitivity — into your config, which is easier to edit and far more capable than the launch field. Keeping the two separate, with launch options minimal and config comprehensive, is the setup that stays stable and easy to troubleshoot.

If you are ever debugging a problem — stutters, a setting that will not stick, the game launching oddly — a minimal launch line is a gift to your future self, because there is almost nothing in it to suspect. When your launch options are three well-understood entries, you can rule them out instantly and look elsewhere; when they are a fifteen-item string copied from a forum, any one of them could be the culprit and you have no idea which. Simplicity here is not just tidiness, it is a troubleshooting strategy. Strip the field back to what you can justify, keep a note of why each entry is there, and you will spend far less time chasing problems that a bloated launch line quietly created.

Counter-Strike 2 accounts and services

Launch options and configs get the game running the way you want, but they will not move an account that is stuck at the wrong level or lacks Prime. If that is the blocker, our Counter-Strike 2 accounts and services page offers accounts and boosting as a service so your optimized setup gets tested in matches that count. Launch options are Steam's own feature, and nothing on the storefront involves cheats or anything that risks your account.

Frequently Asked Questions