CS2 Launch Options in 2026: What Works and What Is a Myth

Of the fifteen or so flags that have been passed around in guides since CS:GO, seven still do anything in Counter-Strike 2: -novid, -console, -fullscreen/-windowed, -w/-h, -freq, +fps_max and -allow_third_party_software. The rest are either ignored by Source 2 or actively harmful — Valve called -processheap harmful back in 2013. And none of the working flags adds frames on its own: FPS only goes up where you ask the game to draw fewer pixels.

Start from an empty box. It lives in Steam: right-click CS2 → Properties → General → Launch Options.

Short answer

A sensible 2026 line: -novid -console -freq 240 +fps_max 400, where 240 is your monitor's refresh rate and 400 is a cap slightly below the FPS you actually get.
-tickrate 128, +exec autoexec, -high, -threads, -processheap and -dxlevel do nothing for matchmaking. If you copied them from an old guide, delete them.
Four of the six top players in the ProSettings list run a completely empty box.
Add -allow_third_party_software only if a program you need won't work without it, or the game won't start at all.
Judge a flag by your frame dips using cl_showfps 3, never by the average FPS number.

Where to type them

The Steam Support page describes the path: open your Library, right-click the game, choose Properties, and on the General tab find the Launch Options box. Flags go on one line, separated by single spaces.

There is no Apply button. Closing the window saves the line, and the game picks it up on the next launch — not on the next match.

An empty launch options box in the game properties window — One box holds every flag. Their order does not matter, and the separator is an ordinary space.

Two kinds of entries behave differently. A flag with a hyphen is an engine switch read before the game loads: -novid. A flag with a plus is a console command that runs once the engine is up: +fps_max 400. They coexist happily on the same line.

Which flags still work in 2026

Option	What it does	Verdict for 2026
`-novid`	Skips the Valve intro	Harmless. In CS2 the "video" is part of the loading screen, and testers in the February 2026 r/GlobalOffensive thread found no change in time-to-menu. Keep it if you prefer a black screen to the logo.
`-console`	Opens the developer console at launch	Not required if the console is enabled in Settings and bound to a key. u/aveyo points out the one real benefit: without it the console starts blank, so engine initialisation errors never reach your eyes.
`-fullscreen` / `-windowed`	Forces the display mode	Works. Useful when the in-game setting is stuck after a resolution change.
`-w 1280 -h 960`	Forces the resolution	Works. The only flag that genuinely changes FPS, because fewer pixels get rendered. Most pros play 1280×960 stretched, by ProSettings data.
`-freq 240` / `-refresh 240`	Forces the monitor refresh rate	Works, and it is what s1mple runs (`-freq 360`). Only needed when Windows or the game refuses to pick your monitor's maximum.
`+fps_max 400`	Caps the frame rate	Works; identical to typing `fps_max` in console. A cap slightly below your average gives steadier frame times.
`-allow_third_party_software`	Lets overlays and capture tools hook the game	Works, and it is official. Some setups need it just to open — the May 2026 thread describes exactly that case. Opinions on side effects are split.
`-autoconfig`	Resets video settings to hardware defaults and ignores .cfg files	Works. A repair tool for exactly one launch.
`-language english`	Forces the interface language	Accepted by the engine; shows up in 2026 troubleshooting threads.

If this table sends you off to rebuild your reticle too, ready-made strings sit in our CS2 crosshair codes guide, which also explains which crosshair settings a code actually carries.

Which flags are myths now

-tickrate 128. The Counter-Strike 2 page states it plainly: tick rate no longer matters for moving, shooting or throwing, because sub-tick handles it. In the 2026 thread u/Starbuckz42 adds that the flag did nothing unless you host the game yourself. It only governs a listen server you spin up for practice. In pro configs it survives out of habit.

+exec autoexec.cfg. Not needed — CS2 loads autoexec.cfg from the cfg folder on its own, as u/Expadable confirms in the same thread. The recurring "my autoexec won't run" posts almost always end at a wrong file extension rather than a missing flag.

-high. Raises the process priority. The old r/GlobalOffensive wiki says some users reported performance increases, but it was written for CS:GO. In a January 2026 thread about "Processing SDL events" stutter, the author lists -high among the things that did not help.

-threads N. The wiki describes it as setting the number of threads for the game. A January 2026 investigation into the engine thread pool showed CS2 reading the CPU layout by itself: sys_info reported 24 CPUs and an 8P+8E arrangement with no launch options at all. The "-threads 9 for 8-core Intel" advice is a CS:GO leftover.

-processheap. Valve's mattwood answered this one back in 2013: it was a band-aid for a long-fixed issue, and running with it now will make your system perform worse. Delete it if you inherited it from someone else's config.

-nojoy, -nod3d9ex, -noforcemaccel, -noforcemspd, -dxlevel. Source 1 switches from the old wiki. Neither the 2026 threads nor pro configs show them doing anything in CS2.

-vulkan. It exists and switches the renderer to Vulkan. A July 2026 thread shows players trying it to fix a launch crash, without success. It is a troubleshooting switch, not a performance one: no source in our list measures it raising FPS on Windows.

What the pros actually run

Player	Launch options
donk	none
NiKo (Falcons)	none
m0NESY (Falcons)	none
ropz (Vitality)	none
ZywOo (Vitality)	`-novid -tickrate 128 -allow_third_party_software`
s1mple (BC.Game)	`-freq 360 -novid -console +fps_max 999`

ProSettings data as of September 2026.

Four of the six run an empty box. The two who don't use flags for the things a launch option genuinely controls: the intro, the console, the refresh rate, the frame cap and overlay access. Nobody is running a ten-key string.

Notice also that ZywOo's -tickrate 128 sits there doing nothing measurable. Someone else's config is not proof that a flag works. If the mouse numbers behind these names interest you more than the flags, they are broken down in our guide to pro player eDPI in CS2 and Valorant.

Which line to use and what really raises FPS

-novid -console -freq 240 +fps_max 400

Swap 240 for your monitor's refresh rate and 400 for a cap a little below the FPS you actually get. Add -w 1280 -h 960 -fullscreen if you play stretched and the in-game menu keeps forgetting it.

Test any flag honestly, or you will end up arguing with someone else's hardware instead of measuring your own:

Load the same map every time. A deathmatch on Mirage, or something picked with the random CS2 map tool for variety. Type cl_showfps 3 in console.
Play for two minutes. Write down the average FPS and, more importantly, the lowest readings.
Add exactly one flag. One. Restart the game and repeat the run on the same map.
Keep the flag only if the lows improved. The average barely matters; stutter lives in the dips.

A jagged frame-time graph next to a smooth one — The left shape is what stutter feels like; the right one is the same average with no dips. Flags are judged on the right-hand picture.

Launch options are the smallest lever available. In order of real effect: a lower resolution, Shadow Quality and Model/Texture Detail on Low, MSAA at 2x instead of 8x, Nvidia Reflex or AMD Anti-Lag switched on, an FPS cap for steady frame times, and current GPU drivers. donk, by ProSettings data, runs Model/Texture Detail and Shader Detail on Low with a 600-frame cap — on top-tier hardware, because in a shooter readability beats eye candy.

Switching from 16:9 to 4:3 stretched is its own trap. The sensitivity number stays identical while the mouse starts to feel different. Check your cm per 360 before and after: the physical distance is unchanged, but the horizontal stretch makes the same turn look faster on screen. If you also play Valorant, the sensitivity converter keeps that distance the same across both games.

What usually goes wrong

The line was copied from a CS:GO-era guide. Symptom: ten keys in the box and worse performance than the friend running nothing. Cause: -processheap, -threads and -dxlevel ride along with the working flags. Fix: clear the box completely, then add flags back one at a time, testing each.

-autoconfig was never removed. Symptom: graphics settings reset to defaults on every launch and autoexec.cfg appears to be ignored. Cause: that is precisely the flag's job — it overrides .cfg files. Fix: take it out as soon as the game has started cleanly once.

The autoexec "won't work", so +exec goes into the box. Symptom: commands from the file never apply. Cause: in the overwhelming majority of cases the file is named autoexec.cfg.txt or sits in the wrong folder. Fix: turn on file extensions in Explorer, verify the name and the cfg path, and leave the flag out — CS2 loads the file itself.

The game doesn't open at all. Symptom: the process starts and dies silently. Cause, per the May 2026 thread: some setups won't launch without third-party software allowed. Fix: try -allow_third_party_software on its own, with nothing else in the box. If that isn't it, you are into Steam-side failures, covered in our Steam error codes guide, with the VAC case handled separately in VAC was unable to verify your game session.

A flag was "confirmed" by watching the average FPS. Symptom: the counter gained ten frames but nothing feels smoother. Cause: the average moves for all sorts of reasons, including standing somewhere else on the map. Fix: read the low values and repeat the run along an identical route.

Is -allow_third_party_software risky for Trust Factor

This is the one live flag with a genuine disagreement attached. In the May 2026 "CS2 refuses to open" thread the original poster says allowing third-party software badly worsens matchmaking. Another commenter replies that it does nothing for trust factor.

Valve has published nothing either way. We checked the official pages and found no statement supporting or denying it.

What is certain: the flag exists so overlays and recording software can hook the game, and without it some setups never start. That makes the practical call an easy one. If you don't need it, leave it out. If a specific program or the launch itself depends on it, use it — there is no confirmed evidence of a penalty, and equally no guarantee from anyone.

If tuning the config leaves you wondering which role suits you in the first place, the which CS2 role fits you quiz takes a couple of minutes, and the keys for that role are easier to lay out with our gaming keybinds guide.

FAQ

Do launch options give more FPS in CS2?

Almost none of them. The only options that change performance are the ones that change what the game renders (-w, -h, -fullscreen, +fps_max). -high and -threads sometimes help on specific machines, sometimes make things worse; test with cl_showfps and keep only what measurably improves your 1% lows.

Does -tickrate 128 work in CS2?

Not for matchmaking. CS2 uses sub-tick updates and Valve states that tick rate no longer matters for moving, shooting or throwing. The flag only affects servers you host yourself.

Do I still need +exec autoexec.cfg?

No. In CS2 an autoexec.cfg placed in the game's cfg folder loads by itself. If yours does not, check the file name (autoexec.cfg, not autoexec.cfg.txt) and the folder path first.

Is -allow_third_party_software safe?

It is an official Valve flag that lets overlay and capture software hook the game. Some players report it changes their matchmaking experience, others say it does nothing; Valve has not published a statement either way. Use it only if a program you need refuses to work without it.

What launch options do CS2 pros use?

Mostly none. By ProSettings data (September 2026) donk, NiKo, m0NESY and ropz run no launch options at all; ZywOo lists -novid -tickrate 128 -allow_third_party_software and s1mple -freq 360 -novid -console +fps_max 999.