CS2 launch options field in Steam with startup parameters for Counter-Strike 2

CS2 Launch Options 2026: What Actually Works (Tested)

Every option tested on my own PC - works, does nothing, or dead since CS:GO

Short answer: you don't need launch options to play CS2. Valve tests the game without them, and most "best launch options" lists online are copied from old CS:GO guides. Some of those flags do nothing in Source 2, others were never launch options at all.

I didn't want to repeat that list, so I tested every option myself. One by one, with and without the flag, checking sys_info, Task Manager and the game menus. I also went into the game files and pulled option names straight out of engine2.dll.

Below is what I found: which CS2 launch options still work, which ones do nothing, and the few that matter when you record, practice offline or the game won't start.

Best CS2 Launch Options: The Short Answer

My own Launch Options field in Steam is empty. I play CS2 with no launch options at all, and after testing all of them I see no reason to change that. John McDonald, one of the CS:GO and CS2 developers at Valve, put it best:

Best Launch Options are no Launch Options. They are the most heavily tested by the dev team.

Still, some options do work. Here are the ones people search for most, with what I actually saw in my tests:

OptionStatusWhat I saw
-highWorksProcess priority goes to High, main thread stays Normal. The FPS gain is small.
-threadsWorksSets the engine thread pool to the value minus 1. The default is already physical cores minus 1, so there's no reason to touch it.
-vulkanWorksSwitches the renderer from DX11 to Vulkan. Expect a slow first launch and some stutter while the game builds its Vulkan shader cache.
-noreflexWorksRemoves NVIDIA Reflex Low Latency from the video in-game menu completely.
-fullscreenWorksStarts in fullscreen even if windowed is set in the menu.
-swWorksStarts the game in a window.
-allow_third_party_softwareWorksAllows third-party software like MSI Afterburner, OBS or Fraps to work with CS2. More in Anti-Cheat Options.
-insecureWorksVAC is off - custom maps and servers only, no matchmaking.
-languageWorksForces the UI language, e.g. -language english.
-consoleWorksTurns on the developer console even if it's disabled in the menu, and locks that setting in the game. It no longer opens the console on start.
-novidNo effectCS2 has no intro video to skip.
-freq / -refreshNo effectCS2 picks up your monitor's refresh rate on its own.
-freq / -refreshNo effectCS2 picks up your monitor's refresh rate on its own. It starts at the rate set in Windows, and if your monitor supports more, it shows a warning.
-tickrate 128DeadCS2 runs 64 tick with sub-tick. The flag does nothing.

Three Launch Strings Worth Saving

  • Recording with OBS Game Capture: -allow_third_party_software - I keep it on a separate shortcut, not in Steam.
  • Offline practice on a custom map: -insecure +exec training.cfg +map cs_mansion
  • Game opens on the wrong monitor or a black screen: -sw -w 1280 -h 720 - start in a small window, then fix your video settings in the menu.

The full list, grouped by what each option does, is in the reference section. Detailed results with numbers are in my tests.

How to Set CS2 Launch Options in Steam

  1. Open Steam and go to your Library.
  2. Right-click Counter-Strike 2 and select Properties.
  3. On the General tab, find the Launch Options field.
  4. Type your options and close the window. Steam saves them right away.
Steam Properties window for Counter-Strike 2 with the Launch Options field on the General tab
The Launch Options field in my Steam - General tab of CS2 properties

How to Write Them

  • Launch options start with a dash: -sw, -language english.
  • Console commands start with a plus: +map de_dust2, +exec training.cfg.
  • Separate everything with a space. No quotes, no commas.
  • To remove an option, delete it from the field. An empty field means CS2 starts with default settings.

A lot of guides mix the two. Their "best launch options" lists are full of console commands like +fps_max 0, +cl_forcepreload 1 or +mat_queue_mode 2, sold as launch options. Some of those commands work, some don't even exist in CS2 - but none of them are launch options. A console command belongs in the console or your config. The launch line only passes it on at startup. More on that in Console Commands in Launch Options.

Options in this field stay active every time you start the game. I've forgotten -insecure there more than once, then wondered why matchmaking wouldn't let me in. That's why I keep test options on separate shortcuts - see CS2 Shortcuts vs. Launch Options.

Steam stores the field in Steam\userdata\<SteamID>\config\localconfig.vdf. Steam rewrites this file while it's running, so a manual edit made with Steam open gets lost. Use the Properties window.

How I Tested CS2 Launch Options

Every option in this guide was tested on my own PC, on CS2 version 1.41.9.0/14190 (October 2026). One option at a time, always compared with a clean launch without it.

Test PC

  • CPU: AMD Ryzen 7 7800X3D (8 cores, 16 threads)
  • GPU: NVIDIA GeForce RTX 3070 Ti
  • RAM: 32 GB
  • Monitor: 240 Hz
  • OS: Windows 11
  • Renderer: DX11 (CS2 default)

How I Checked Each Option

  • Console. sys_info shows the renderer, process priority and engine thread pool, so I used it for -high, -threads, -dx11 and -vulkan.
  • Task Manager. A second check for process priority.
  • Game menus. Display mode, resolution and video options like NVIDIA Reflex.
  • Files. For logging options I checked if console.log actually appears.
  • FPS benchmark. For FPS tests I use the CS2 FPS Benchmark Dust2 workshop map. The same route every run, so results are comparable.

FPS numbers in this guide come from my PC. On yours they'll be different - the status of an option won't.

What the Statuses Mean

Works
The option does something visible, and it repeats every launch.
No effect
CS2 starts fine with it, but nothing changes.
Dead
A CS:GO-era option with no place in CS2, like -tickrate or -d3d9ex.

CS2 Launch Options: Full List

Every option I tested, grouped by what it does. Old CS:GO flags that have no place in CS2 are collected separately in Dead CS:GO Launch Options.

Display and Window

OptionStatusWhat I saw
-fullscreenWorksStarts in fullscreen even if the menu is set to windowed.
-fullNo effectThe game stays windowed. Only the full name -fullscreen works.
-swWorksStarts the game in a window. The only windowed-mode option that works in CS2.
-windowed / -startwindowedNo effectThe game still starts in fullscreen. Use -sw instead.
-noborderNo effectChanges nothing, alone or together with -sw.
-w / -hWorksSets the resolution at startup, e.g. -w 1280 -h 720. Works in both window and fullscreen.
-x / -yWorksMoves the window on screen, e.g. -x 100 -y 100. Only together with -sw.
-freq / -refresh / -refreshrateNo effectCS2 picks up your monitor's refresh rate on its own. See below.

Here's how display options behaved against the setting in the game menu:

In-game settingLaunch optionsResult
Windowed-fullscreenFullscreen
Windowed-fullWindowed
Fullscreen-swWindowed
Fullscreen-windowedFullscreen
Fullscreen-startwindowedFullscreen
Fullscreen-noborderFullscreen
Fullscreen-sw -noborderWindowed, same as -sw
1920x1080-w 1280 -h 7201280x720
1920x1080-w 1280 -h 720 -sw1280x720, windowed
1920x1080-w 1280 -h 720 -fullscreen1280x720, fullscreen

Why -freq Is No Longer Needed

-freq 144 and -freq 240 are probably the most copied CS2 launch options. The habit comes from older games, where the game took the refresh rate from Windows and a high-Hz monitor could end up running at a lower rate. Adding -freq forced the right number.

CS2 doesn't need that. It picks up your monitor's refresh rate on its own - the game detects your display and knows its highest mode. It still starts at the rate set in Windows, but if your monitor supports more, CS2 shows a warning right in the game:

CS2 refresh rate warning showing a 240 Hz monitor running at 144 Hz
My monitor supports 240 Hz, Windows was set to 144 Hz - CS2 noticed and warned me

I tested -freq, -refresh and -refreshrate - CS2 ignores all three. If you see this warning, fix it in Windows: right-click the desktop > Display settings > Advanced display > Choose a refresh rate.

Renderer and Performance

OptionStatusWhat I saw
-dx11WorksForces DX11. It's already the default, so on most PCs nothing changes.
-vulkanWorksSwitches the renderer from DX11 to Vulkan. Expect a slow first launch and some stutter while the game builds its Vulkan shader cache.
-noreflexWorksRemoves NVIDIA Reflex Low Latency from the video menu completely.
-forcenovsyncNo effectWith V-Sync forced in the NVIDIA driver, FPS stays capped at the monitor's refresh rate. Neither this option nor the in-game V-Sync setting changes that.
-highWorksProcess priority goes to High, main thread stays Normal.
-threadsWorksSets the engine thread pool to the value minus 1. The default is physical cores minus 1 - 7 on my 8-core CPU.
-limitvsconstNo effectSource 1 leftover. Nothing changes.
-nopreloadNo effectNothing changes in loading or FPS.
-softparticlesdefaultoffNo effectSource 1 leftover. Nothing changes.

Startup and Tools

OptionStatusWhat I saw
-languageWorksForces the UI language, e.g. -language english.
-devWorksDeveloper mode with the full console log. A good tool when you hunt a startup error - see how I use it to check configs.
-condebugWorksWrites console output to console.log in the game folder.
-consolelogWorksSame as -condebug - also writes console.log.
-consoleNo effectThe console doesn't open on start. Turn it on in Settings > Game instead.
-autoconfigNo effectSupposed to reset video settings. Nothing changed in my test.
-nosoundNo effectSound still works.
-novidNo effectCS2 has no intro video to skip.
-joyNot testedTurns joystick input back on. Valve switched it off by default on May 29, 2024, and named this option to restore it. I don't have a gamepad to test it.

Anti-Cheat and Third-Party Software

OptionStatusWhat I saw
-insecureWorksTurns VAC off. Custom maps and servers only - matchmaking is blocked.
-allow_third_party_softwareWorksAllows third-party software like MSI Afterburner, OBS or Fraps to work with CS2. More in Trusted Mode.

A few more options I found inside the game files - -tools, -playtest, -nohltv and others - are in Inside engine2.dll.

My Test Results: Options That Actually Do Something

The full list above gives a status for each option. Here are the ones worth a closer look - what exactly changed, and what I saw in the console.

-noreflex: Removes NVIDIA Reflex from the Menu

Without the option, Settings > Video > Advanced Video has the NVIDIA Reflex Low Latency setting. With -noreflex, the setting is gone from the menu completely.

CS2 Advanced Video settings showing NVIDIA Reflex Low Latency available without the -noreflex launch option
Default launch - NVIDIA Reflex Low Latency is in the menu
CS2 Advanced Video settings with NVIDIA Reflex Low Latency missing after launching with -noreflex
Launched with -noreflex - the Reflex option is gone

Most players have no reason to use it. It only makes sense if you're troubleshooting and want Reflex fully out of the picture.

-high: Process Priority

With -high, sys_info shows Process priority: high and main thread priority: normal. Task Manager confirms cs2.exe runs at High. Without the option, both show Normal.

CS2 console sys_info output with process priority high after launching with -high
sys_info output with -high in the launch options

So the option works. On my old laptop (Ryzen 5 3550H, GTX 1650), the FPS gain was small, and setting high priority through the Windows Registry gave better results than -high:

MethodAverage FPS1% Low
Default114.353.8
-high117.459.0
Registry121.562.5

The full test with screenshots and the Registry method is in my guide: Is -high Worth It in CS2?

-threads: The "+1 Core" Myth

This is one of the most repeated tips in CS2 guides: set -threads to your core count plus one - -threads 9 for an 8-core CPU - and the game will "use all your cores" and give you more FPS. It doesn't work that way.

CS2 sets the engine thread pool on its own: physical cores minus 1. Here's my sys_info with no launch options:

CPUs: 16 CPUs (8 cores), Frequency: 4.2 GHz
CPU brand information: AMD Ryzen 7 7800X3D 8-Core Processor
Engine thread pool: 7 thread(s)

With -threads, the pool becomes the value you set minus 1. So the famous -threads 9 on my CPU gives a pool of 8 - one extra worker thread, nothing more. It doesn't unlock any cores. Windows spreads the game's threads across your CPU either way. The engine takes any number, by the way: -threads 999 gives me 998 threads, and the game runs exactly the same.

The tip itself comes from early 2024, when people used -threads as a workaround for freezes on Intel 12th-14th gen hybrid CPUs. Valve fixed that with an update, but the "+1" advice kept going from guide to guide as a general FPS boost.

Source 2 handles multithreading by itself. Leave -threads out of your launch options.

-vulkan and -dx11: Renderer Switch

CS2 on Windows runs on DX11 by default - sys_info shows Render system: DX11. -dx11 forces the same thing, so on most PCs it changes nothing.

-vulkan switches the renderer, and sys_info shows Render system: Vulkan. It's a switch, not a performance tweak. On the first launch the game loaded noticeably longer and the menu stuttered - Vulkan builds its shader cache from scratch, and the game has to get through that first.

On NVIDIA cards Vulkan is slower. On my RTX 3070 Ti I got 340 FPS with Vulkan instead of 450 on DX11 - about 24% less. That's a big drop, but that's what I got.

Other tests point the same way, with a smaller gap. Gaming Style tested after the November 19, 2025 update on a Ryzen 5 7600 with an RTX 4070: DX11 gave about 3.7% more average FPS, but Vulkan kept frame times much more even. They also found that some Intel Arc cards, like the B580, run CS2 20% faster or more on Vulkan.

I don't have an AMD card, so I can't test that side. My take: stay on DX11, unless you have Intel Arc or you've tested Vulkan on your own PC and it works better for you.

If you see stutter and freezes in general, not only after switching renderers, start here: How to Fix FPS Drops, Stuttering, and Input Lag in CS2.

-condebug, -consolelog and -dev: Console Logs

-condebug and -consolelog both work the same way - they write everything from the console to a console.log file in the game folder. Handy when the game crashes before you can read the console.

-dev turns on developer mode and keeps the full startup log in the console. I use it to check which configs load and in what order - see how I do it.

Anti-Cheat Options: -insecure and -allow_third_party_software

Two launch options in CS2 change how the game deals with its own protection. They do different things, and people mix them up all the time.

-insecure: VAC Off

-insecure starts CS2 without Valve Anti-Cheat. It doesn't put your account at risk - it simply locks you out of everything that's VAC-secured, including matchmaking. You'll see it in the console too: with this option, the status command shows insecure in the version line.

It's meant for local servers with plugins or modified files, and for community servers that run without VAC. For normal play you don't need it.

The classic mistake: you add -insecure for one test, forget about it, and a week later matchmaking won't let you in. That's exactly why I keep it on a separate shortcut and never in the Steam field.

-allow_third_party_software: Trusted Mode Off

CS2 runs in Trusted Mode by default. In this mode the game blocks third-party programs that try to load into the CS2 process. That's a security measure: cheats work the same way.

-allow_third_party_software turns Trusted Mode off. VAC stays on, you can still play matchmaking, and programs that hook into the game start working again:

  • OBS Studio with Game Capture
  • MSI Afterburner with the RTSS overlay (FPS, temps, frametime graph)
  • Fraps

Not everything needs the flag. OBS Display Capture and Window Capture record the screen from outside the game and work in Trusted Mode without any launch options. If that's enough for you, don't add the flag at all.

Does It Affect Trust Factor?

It can. Valve's own FAQ says that when you launch with -allow_third_party_software, your Trust Factor "may be negatively affected". Not "will", but "may" - Valve doesn't say more than that, and neither will I. Read it yourself: Steam Support - CS2 Trusted Mode.

Neither of these options lives in my Steam field. When I need to record with Game Capture or test something on a local server, I start CS2 from a separate shortcut. Matchmaking always runs clean. How to set that up: CS2 Shortcuts vs. Launch Options.

Console Commands in Launch Options

Anything with a plus in front is not a launch option. It's a regular console command that Steam passes to the game at startup - the same as typing it in the console right after the game loads. A few of them are actually handy:

+exec name.cfg
Runs one of your configs on startup, e.g. a practice config.
+map de_dust2
Loads a map right after the game starts, no menus.
+fps_max 0
Works, but pointless. The value is saved in your settings anyway, so there's no reason to pass it on every launch. More in Video and Performance commands.
CS2 launch options in Steam with the +exec config.cfg command
A config passed through the launch line with +exec

A practice launch line I use looks like this:

-insecure +exec training.cfg +map cs_mansion

What goes into a training config and how to set up bots is in my CS2 Bot Commands Guide.

You Don't Need +exec autoexec.cfg

This one is in almost every launch options list, and it's useless. CS2 treats autoexec.cfg like a system file - if it's in your cfg folder, the game runs it on every start by itself, before any config from the launch line.

You can check it yourself. Put echo "autoexec loaded" at the top of the file, start the game with -dev, and look for the line in the console. -dev keeps the full startup log, so you'll see exactly which configs ran and in what order.

The full load order and where every config file lives: CS2 Config Location Guide. Creating and organizing your own configs: CS2 Config: How to Create, Load, and Manage CFG Files.

What I Found Inside engine2.dll

Testing options one by one only tells you what happens on screen. I wanted to see which option names the game itself knows about, so I searched the game files directly. Here's how, and what came out of it.

How I Searched

First, a search across every .dll and .exe in the game folder. I ran it in cmd from the Counter-Strike Global Offensive folder, with the list of options I wanted to check:

(for %o in (novid nojoy noreflex vulkan threads noborder forcenovsync) do @(echo === %o === & findstr /s /m /i /c:"-%o" *.dll *.exe)) > cs2_flags.txt

The result is a text file that lists, for each option, every game file containing that name. In a .bat file, write %%o instead of %o.

Second, I pulled all readable text out of the main engine file with Strings from Microsoft Sysinternals:

strings64.exe game\bin\win64\engine2.dll > engine2_strings.txt

That gives a long text file with every message, setting and option name the engine has inside. This is where the descriptions in the table below come from.

What a File Search Can and Can't Prove

Finding an option name in a game file doesn't prove the engine accepts it. It only gives you something to investigate. But it doesn't work the other way. -noreflex, -threads, -condebug, -high, -fullscreen and -sw all work in my tests, yet neither method found them. My guess is that Source 2 stores many of these names in a form a text search can't see.

So a file search can confirm an option exists. It can never prove an option is dead - for that, you have to test it.

Options Found in the Game Files

OptionTestedFound in / what the files show
-vulkan, -dx11, -emptyYesengine2.dll and the three renderer files: rendersystemvulkan.dll, rendersystemdx11.dll, rendersystemempty.dll. One option per renderer. I tested the first two.
-insecureYescs2.exe, engine2.dll, tier0.dll, client.dll.
-allow_third_party_softwareYescs2.exe.
-consolelog, -con_logfileYesengine2.dll. -consolelog writes console.log like -condebug. -con_logfile sits right next to it and looks like another name for the same thing - I haven't tested it.
-nohltvYesengine2.dll, with the message "Not creating socket NS_HLTV due to -nohltv". It skips the GOTV network socket. In my test nothing changed or broke.
-playtestYesengine2_strings.txt. The engine text ties it to not reading and writing the user config. In my test I saw no difference.
-perfectworld, -worldwideNoengine2.dll. Perfect World runs the Chinese version of CS2, so these choose between the Chinese and the worldwide version.
-trusted, -untrustedNocs2.exe, client.dll. Most likely related to Trusted Mode.
-toolsNoStarts CS2 with the Workshop Tools for map and mod makers.

One more thing I found in engine2_strings.txt: the names enable_priority_boost and disable_priority_boost. It looks like the engine manages its own priority, but I haven't confirmed what these do. That's a test for the next update of this guide.

False Matches

A plain text search also finds names that have nothing to do with launch options. These four fooled me at first:

freq
Only in steamaudio.dll and valve_webm.dll - audio and video libraries, not the engine.
refresh
Only in Qt5Widgets.dll, a UI library.
heapsize
A standard Windows function called HeapSize that sits in most DLLs. Not a launch option.
threads
An ordinary word that shows up everywhere. The search says nothing about the option.

That's why "I found it in the game files" proves nothing by itself. Every result needs a look at which file it came from.

Digging Deeper: An Old Trick from CS 1.6

This isn't the first time I've gone looking inside game files. Back in CS 1.6 we loaded all kinds of client DLLs - protectors, SteamID changers and so on. Start the game, open the console, and there's a line like "Protected by Ostrog Loaded", the one that stopped servers from changing your config.

I wanted to change that text. I opened the DLL and found nothing - no message, no command names, just noise. It took some digging to understand why: the file was packed. If I remember right, it was UPX, a packer that squeezes the whole file so nothing inside is readable. The tool I had only took .exe files, so I renamed the DLL to .exe and unpacked it. And there it all was - every message and every command name in plain text. I changed what I wanted, packed the file again, renamed it back to .dll, and it worked.

So the first question when a file shows you nothing is: is it packed? A tool like Detect It Easy tells you that in seconds.

CS2 files are not packed - strings64 pulled thousands of readable lines out of engine2.dll. So packing isn't why -noreflex and the others don't show up. Finding them would take a disassembler like Ghidra and reading the engine's code, not just its text.

One warning: reading CS2 files is harmless, changing them is not. A modified game file can get you banned on VAC-secured servers, and VAC doesn't care why you changed it. Look, but don't touch.

Dead CS:GO Launch Options

These options still float around in "best launch options" lists, but they come from GoldSrc, Source 1 or CS:GO. Each one controlled something CS2 simply doesn't have - DirectX 9, OpenGL, IPX networking, the old mouse code. I didn't test every single one, and there's no need to: an option can't switch off a system that isn't there.

-tickrate 128
Set the tickrate of a local CS:GO server. CS2 runs 64 tick with sub-tick, and the option does nothing.
-d3d9ex, -nod3d9ex, -dxlevel
DirectX 9 modes and levels from CS:GO and Source 1. CS2 has no DirectX 9 renderer - only DX11 and Vulkan.
-d3d, -gl, -soft, -r_emulate_gl
Forced Direct3D, OpenGL or software rendering in GoldSrc and Source 1. CS2 has none of these renderers.
-noforcemparms, -noforcemaccel, -noforcemspd
Stopped the game from changing your Windows mouse settings. Still a must-have in CS 1.6, useless in CS2 - its mouse input doesn't touch Windows mouse settings.
-nomouse
Switched off the mouse for debugging in older engines.
-heapsize, -zone
Manual memory settings from the GoldSrc and Source 1 days. CS2 manages memory on its own.
-noipx
Disabled the IPX network protocol, which games stopped using in the early 2000s.
-nosse4
Turned off SSE4 instructions for old CPUs in Source 1.
-noaafonts
Font smoothing switch from Source 1. CS2's interface is built differently.
-stretchaspect
Stretched the image in older engines. In CS2 aspect ratio and stretching are set in the video menu.
-lv
Low-violence mode from CS:GO.
-safe
Safe mode with minimal settings in Source 1.
-nocrashdialog
Hid crash pop-ups in Source 1, mostly on test machines and servers.
-no-browser
Turned off the in-game browser of old Source games. There's nothing to turn off in CS2.
-nojoy
Disabled joystick input. Since the May 29, 2024 update CS2 ignores joysticks by default, so there's nothing left to disable. To turn them back on, Valve's option is -joy.

If you still play CS:GO through the legacy branch, many of these options work there just like they used to: How to Play CS:GO After CS2 on Steam.

When CS2 Won't Start: Launch Options That Help

If CS2 crashes on start, shows a black screen or opens on the wrong monitor, go through these steps in order:

  1. Clear the Launch Options field. Start with an empty field. An old flag you forgot about is a more common problem than it sounds - -vulkan on a driver it doesn't like, or a leftover from some "FPS boost" list.
  2. Force DX11. If the game crashes after a driver update or after you tried Vulkan, add -dx11. It makes CS2 start on its default renderer.
  3. Start in a small window. Black screen, wrong monitor, or a resolution your screen doesn't support - use -sw -w 1280 -h 720. Once the game is up, fix the video settings in the menu and remove the options.
  4. Reset the video settings. -autoconfig did nothing in my test, so don't count on it. Delete cs2_video.txt instead - CS2 creates a new one with default values on the next launch. Where to find it: CS2 Config Location Guide. Full reset: How to Reset All Settings in CS2.
  5. Verify the game files. In Steam: right-click Counter-Strike 2 > Properties > Installed Files > Verify integrity of game files.
  6. Get a log. If nothing helps, start with -condebug. The console.log file in the game folder shows the last thing the game did before it crashed. Add -dev for the full log.

CS2 starts, but matchmaking won't let you in? Check the field for -insecure. It switches off VAC, and VAC-secured servers won't accept you until you remove it.

I Googled "CS2 Launch Options" - Here's What I Found

I took the launch strings from the top search results and checked them against my tests. Two typical examples below. The rest look pretty much the same.

Example #1: "Best Launch Options"

-freq 240 -d3d9ex -novid -no-browser +mat_queue_mode 2 +fps_max 0 +cl_interp_ratio 1 +cl_interp 0.031 -tickrate 128 +cl_cmdrate 128 +cl_updaterate 128 +cl_forcepreload 1
  • -freq 240 - no effect. CS2 picks up your monitor's refresh rate on its own.
  • -d3d9ex - dead. CS2 has no DirectX 9.
  • -novid - no effect. There's no intro video to skip.
  • -no-browser - dead. Nothing to turn off.
  • +mat_queue_mode 2, +cl_forcepreload 1 - Source 1 console commands that don't exist in CS2.
  • +cl_interp_ratio, +cl_interp, +cl_cmdrate, +cl_updaterate - network commands from CS:GO, not launch options. And no combination of them turns a 64-tick server into 128.
  • -tickrate 128 - dead.
  • +fps_max 0 - works, but it's a console command, and the value is saved in your settings anyway.

Result: twelve items, one that works - and that one isn't even a launch option.

Example #2: "Balanced Performance"

-novid -console -nojoy -tickrate 128 +fps_max 240 +cl_forcepreload 1 -high +exec autoexec.cfg
  • -novid - no effect, again.
  • -console - works, it turns on the developer console. But an open console doesn't add FPS.
  • -nojoy - dead. CS2 ignores joysticks by default since May 2024.
  • -tickrate 128 - dead.
  • +fps_max 240 - works, but it's a console command, same as above.
  • +cl_forcepreload 1 - doesn't exist in CS2.
  • -high - works. The gain is small, details in my tests.
  • +exec autoexec.cfg - useless. The game runs autoexec on its own, see why.

Result: two options that work - -high and -console - and neither of them is an FPS boost. Everything else does nothing or is already handled by the game.

Why These Lists Keep Coming Back

Guides copy older guides, and nobody tests anything. A long launch string looks like expert knowledge, and when the game feels smoother after a driver update, the "FPS boost" gets the credit.

If you want more FPS, launch options are the wrong place to look. Windows, drivers and in-game settings are where the real numbers come from - I tested all of that here: How to Increase FPS in CS2.

CS2 Launch Options FAQ

A glowing FAQ sign on a futuristic holographic panel surrounded by floating question marks
What are the best launch options for CS2?

For most players - none. My own Launch Options field is empty. A few options are useful for specific jobs: -allow_third_party_software for recording with OBS Game Capture, -insecure for local servers, -sw when the game won't start properly. None of them is a performance boost.

Do launch options increase FPS in CS2?

No. The only one with a measurable effect in my tests was -high, and the gain was small. -vulkan actually lowered my FPS. Real FPS gains come from Windows, drivers and in-game settings.

Should I set -threads to my core count plus one?

No. CS2 already sets its thread pool to physical cores minus 1. -threads 9 on an 8-core CPU just adds one worker thread, it doesn't "unlock" anything. The "+1" tip comes from an old workaround for freezes on Intel hybrid CPUs that Valve has since fixed.

How do I enable the console in CS2?

In Settings > Game, or with -console. The option turns the console on even if it's disabled in the menu, and locks that setting. It doesn't open the console on start anymore - press ~.

Does -tickrate 128 work in CS2?

No. CS2 runs 64 tick with sub-tick, and the option does nothing - not in matchmaking, not on a local server.

Is -novid still needed?

No. CS2 has no intro video, so there's nothing to skip.

How do I open the console on startup?

-console doesn't work in CS2. Turn the console on in Settings > Game and open it with the ~ key.

Why doesn't -windowed work?

In CS2 only -sw starts the game in a window. -windowed, -startwindowed and -noborder do nothing. For fullscreen use -fullscreen - the short -full doesn't work either.

Should I use -vulkan or stay on DX11?

On NVIDIA, stay on DX11 - it's the default and it was faster in my tests. Vulkan makes sense on Intel Arc cards, or if you've tested it on your own PC and it works better for you.

Does -allow_third_party_software affect Trust Factor?

It can. Valve's FAQ says Trust Factor "may be negatively affected" when you launch with it. I keep it on a separate shortcut and use it only for recording.

Can launch options get me VAC banned?

The options in this guide don't change the game, so no. -insecure doesn't ban you - it keeps you off VAC-secured servers until you remove it. Modifying game files is a different story, and that can get you banned.

Do I need +exec autoexec.cfg in my launch options?

No. CS2 runs autoexec.cfg from your cfg folder on every start by itself. Adding it to the launch line does nothing useful.

How do I set my refresh rate if -freq doesn't work?

In Windows: right-click the desktop > Display settings > Advanced display > Choose a refresh rate. CS2 picks it up on its own, and if your monitor supports more, the game shows a warning.

How do I remove launch options?

Open Properties of CS2 in Steam and clear the Launch Options field. An empty field means the game starts with default settings.

More CS2 Guides

3 Responses

    1. Hi! This is a valid CS2 launch option. It disables NVIDIA Reflex / NVIDIA Low Latency technology at the game launch level.
      Personally, I do not use it because I have NVIDIA Reflex Enabled + Boost turned on in my CS2 settings. If you do not need to disable Reflex, do not use this launch option just because someone wrote somewhere that it supposedly helps. The best option is to test CS2 with -noreflex and without it. Compare FPS, frametime, and how the input lag feels. If there is no noticeable difference, you do not need to use -noreflex.

Leave a Reply

Your email address will not be published. Required fields are marked *