Best CS2 Launch Options and Config for FPS and Ranked

The best CS2 launch options are, for almost everyone, no launch options. That is not a cop-out, it is the accurate answer for Source 2. Most of the flags floating around in “best cs2 launch options” videos are copied straight from CSGO, and a big chunk of them are dead, redundant, or actively harmful in CS2. The short version: enable the console, point the game at your autoexec if you use one, set fps_max, and stop there. This guide lists exactly which launch options still work, which ones are deprecated in Source 2, and the config and net settings that actually matter, so you are not running 20 flags that do nothing.

A Valve developer said it cleanly years ago: the best launch options are no launch options, because the default config is the most-used and most-tested path in the game. That is even truer in CS2 than it was in CSGO. Settings smooth out how the game feels, but they do not win rounds on their own – if you want the thing that actually moves your rating, that is aim, positioning, and the utility that actually wins you rounds. Config first here, then go be good.

What sub-tick changed (and why half your launch options are dead)

The reason so much old advice is wrong is one system: sub-tick. CS2 threw out CSGO’s fixed 64-tick and 128-tick model and replaced it with a sub-tick system that timestamps your inputs between server frames. Check the current behavior against the Counter-Strike update notes if you want the primary source, but the practical fallout is huge for configs.

Because there is no tickrate anymore, -tickrate 128 does absolutely nothing. It does not give you a 128-tick matchmaking server, because 128-tick servers are not a concept in CS2. We see this one constantly on account handoffs – a client swears their FPS and “hit registration” got better after they added -tickrate 128, and it is pure placebo, because the flag is inert. Same story for the old rate cvars: cl_updaterate and cl_cmdrate were removed, since the client now sends updates tied to your frame rate. There is nothing to tune, and pasting them in just clutters your config. (The one upside of sub-tick: you can finally stop arguing about tickrate in the lobby. Small mercies.)

CS2 launch options that still work

The list of genuinely useful launch options in CS2 is short. Here is what still functions and is worth considering.

• -console opens developer console access on launch. The one flag almost everyone should have (you can also toggle it in settings).
• +exec autoexec.cfg forces your autoexec to run. CS2 does not reliably auto-run it, so this is the honest fix if you use a config file.
• -fullscreen or -windowed -noborder sets display mode. Redundant with the video menu, but handy if the game keeps launching in the wrong mode.
• -w 1920 -h 1080 forces a resolution. Again redundant with settings; useful only to recover from a broken config.
• -refresh 240 forces a refresh rate. Set your monitor’s actual Hz; also settable in-game.
• -high launches at high CPU priority. This is the one people fight about: it helps on some systems and causes stutter on others. Test it, do not cargo-cult it.
• -language english forces UI language independent of your Steam language.
• -vulkan forces the Vulkan renderer. Mostly relevant on Linux; on Windows the default DX11 path is fine for most.

Notice what is not on that list: any flag that promises free FPS. There isn’t one. Your frame rate lives in the video settings and fps_max, not in a launch string.

Launch options that are dead or pointless in CS2

These get pasted into configs constantly and do nothing (or worse). Cut them.

If your launch string has more than three or four things in it, you almost certainly copied a 2019 CSGO video and are running a museum of dead flags. Trim it to -console plus, if you use one, +exec autoexec.cfg, and you have lost nothing.

fps_max and the settings that actually change your FPS

Your FPS comes from the in-game video settings and one cvar, not from launch options. The cvar is fps_max. Set to 0 it uncaps your frame rate entirely; set to a number it caps there. On a strong PC plenty of players uncap it, but a stable cap at or above your monitor’s refresh rate often feels smoother than a jittery uncapped number bouncing between 400 and 700. There is also fps_max_ui, which caps the menu – no reason to render 900 FPS on a settings screen and cook your GPU for nothing (your case fans will thank you).

Defaults for these have shifted across builds, so check them in the console rather than trusting an old guide. The honest hierarchy for real FPS gains: lower the heavy video settings (shadows, model/texture detail, MSAA), set a sane fps_max, and only then argue about -high. If you want to know whether a change actually helped instead of feeling like it did, Leetify tracks your performance across matches so you can compare before and after with real numbers.

If you would rather not spend a Saturday A/B testing config files, that is a fair call – let our CS2 team climb the account while you dial in the config at your own pace. Real players on the maps you queue, clean handoff, and you come back to a higher CS Rating with your settings exactly how you left them.

The autoexec: how to actually make a config stick

An autoexec is just a text file of cvars the game runs on launch: crosshair, viewmodel, volume, radar, sensitivity. In CS2 the catch is that the game does not reliably auto-run autoexec.cfg on its own, which is why people swear their settings “keep resetting.” The fix is two steps.

• Put your file at ...\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\autoexec.cfg (yes, the folder is still named for the old game – that is the correct Source 2 path).
• Add +exec autoexec.cfg to your launch options so it actually loads.

Keep the file lean: the cvars you genuinely want pinned, not a 200-line dump. If you want your crosshair, viewmodel, and HUD identical every session, the autoexec is where that lives, and a clean crosshair setup is worth more to your consistency than any launch flag. Optionally end the file with host_writeconfig to save state, though many players leave it out to avoid overwrite quirks.

Net settings for ranked and Premier

The net settings that survived sub-tick are few, and the ranked-relevant one is rate, your maximum bandwidth in bytes per second. CS2 raised the ceiling over CSGO, so on a decent connection there is no reason to run a low cap; set it high enough that your connection, not the game, is the limit. Leave cl_interp and interp ratio at default. The old “cl_interp 0” ritual is legacy CSGO advice and sub-tick handles timing differently now, so forcing it just risks making things worse.

The one net setting with a real tradeoff is mm_dedicated_search_maxping, which caps the ping of servers matchmaking will put you on. Lower it for better servers at the cost of longer queues; raise it if you are stuck waiting forever. None of this moves your rating, though – how CS Rating actually moves is about round wins and the strength of who you beat, not your netgraph. A perfect config on a Silver’s aim is still a Silver. Settings remove excuses; they do not add skill.

Frequently asked questions

What are the best CS2 launch options?

For most players, almost none: -console to enable the console, and +exec autoexec.cfg if you run a config file. Everything else that mattered in CSGO is either handled by the in-game menu now or dead in Source 2. A Valve developer summed it up years ago – the best launch options are no launch options, because the default path is the most tested.

Does -tickrate 128 work in CS2?

No. CS2 replaced fixed tickrate with sub-tick, so -tickrate 128 does nothing at all. It will not give you a 128-tick matchmaking server, because that concept no longer exists in the game. It is the single most common dead flag people still paste into their launch options.

What launch options increase FPS in CS2?

None reliably. -high can help on some systems and cause stutter on others, so test it rather than trusting it. Your real FPS levers are the in-game video settings and fps_max – no launch flag hands out free frames the way old guides imply.

Do I still need an autoexec in CS2?

Only if you want specific cvars applied every launch. CS2 does not reliably auto-run autoexec.cfg, so if you use one, add +exec autoexec.cfg to your launch options or it simply will not load, which is why so many players think their settings keep resetting.

Are -novid and -d3d9ex still useful?

No. -novid is redundant because CS2 has no startup movie to skip, and -d3d9ex is dead because Source 2 runs on DX11 and Vulkan, not DirectX 9. Both are pure leftovers from CSGO configs.

What should I set fps_max and rate to?

Set fps_max to 0 to uncap, or to a stable value at or above your monitor’s refresh rate if uncapped feels jittery; use fps_max_ui to cap the menu. Set rate high enough that your connection is the limit rather than the game – CS2 raised the cap over CSGO, so a low value only holds you back.

Strip your launch options down to -console and, if you use a config, +exec autoexec.cfg; put your crosshair, viewmodel, and fps_max in an autoexec; leave the net cvars near default and trust sub-tick. That is the entire honest optimization for CS2, and the rest is aim and reps. The community agrees, if you scroll the recurring r/cs2 launch-options threads: the consensus is that most legacy flags do nothing in Source 2. If you want the rating without the grind while you tune all this, our CS2 boosting team runs clean Premier and competitive climbs on the maps you actually play, and hands the account back with your config untouched.