If you want to skip straight to the commands, here are the two setups worth using in 2026. Copy either one into Steam’s Launch Options field and you are done.
Recommended (most players): -novid -fullscreen +fps_max 0 -allow_third_party_software
Low-end PC (stability first): -novid -fullscreen +fps_max 60
Everything below explains what each flag does, which old CS:GO commands to stop using, and how to build an autoexec that handles the rest. Launch options are a small piece of the puzzle — your real gains come from CS2 settings and GPU configuration. Set that expectation now and this guide will be more useful.
How to set launch options in CS2
Setting launch options takes about thirty seconds. Here is the exact process:
- Open Steam and go to your Library.
- Right-click Counter-Strike 2 and select Properties.
- Stay on the General tab and find the Launch Options field near the bottom.
- Type your commands directly into the field, separated by spaces.
- Close the window. Steam saves automatically and applies the commands every time CS2 starts.
No restart is needed after saving. The commands run before the game engine initializes, which is why some flags work here rather than through in-game menus. Keep the field clean: only add commands you understand and have a reason to use. A cluttered string of outdated flags does nothing except make troubleshooting harder.
What actually works in CS2 in 2026
The list of genuinely useful CS2 launch options is short. [VERIFY: confirm each command still functions in the current CS2 build before publishing.]
| Option | What it does | Use it? |
|---|---|---|
| -novid | Skips the Valve intro video on launch. No performance impact, zero downsides. | Yes |
| +fps_max 0 | Removes the frame cap entirely. Pair with your preferred capping strategy — see the FPS section below. | Yes, on high-end hardware |
| +fps_max 144 / +fps_max 240 | Caps frames at your monitor’s refresh rate for a stable ceiling instead of running uncapped. | Yes, on mid-range hardware |
| -fullscreen | Forces fullscreen mode at launch. Redundant if Display Mode is already set to Fullscreen in-game, but useful if Steam ever resets your settings. | Yes |
| -refresh [Hz] | Forces a specific refresh rate, e.g. -refresh 144 or -refresh 240. CS2 detects this correctly in most cases, but forcing it does not hurt if you have had detection issues. | Optional |
| -allow_third_party_software | Required for OBS or similar capture tools to hook into the game for recording or streaming. | Yes, if you stream or record |
| -autoexec [filename] | Loads a custom config file on launch. Useful because some console values reset after game updates — your autoexec reloads them every time. | Yes, if you use a config |
| -high | Sets CS2 to High priority in Windows Task Manager. Current testing puts this closer to placebo for most systems. It does not hurt to include, but do not expect a measurable gain. | Optional |
Launch options to avoid in CS2
Many launch option lists circulating in 2026 are copy-pasted from CS:GO guides written years ago. Several of those commands do nothing in CS2’s Source 2 engine — or were never meaningful to begin with. If a guide still has CS:GO screenshots, its recommendations do not apply to CS2.
| Option | What people claim | Reality in CS2 | Use it? |
|---|---|---|---|
| -tickrate 128 | Forces 128-tick servers | Completely dead. CS2 uses a sub-tick system that processes input timing independently of tick boundaries. There is nothing for this flag to set. | No |
| -nod3d9ex / -d3d9ex | DirectX 9 optimizations | CS:GO-era DirectX 9 flags. CS2 runs on a different rendering pipeline entirely. No effect. | No |
| -threads [number] | Assigns more CPU threads | Overriding thread count on modern multi-core CPUs can hurt performance by disrupting how CS2 allocates work across cores. CS2 handles thread distribution well on its own. | No |
| -nojoy | Disables joystick input to free memory | Had minimal effect in CS:GO and has no confirmed benefit in CS2. Leave it out. | No |
| -lv | Low-violence mode | Region-specific flag from CS:GO. Not applicable to CS2 in most markets. | No |
The rule is simple: if a command comes from a CS:GO guide and you cannot find confirmation it functions in CS2 specifically, leave it out. Dead flags add visual noise and make it harder to diagnose actual issues.
Recommended launch option setups by use case
There is no single perfect setup, but these starting points cover the most common hardware situations.
| Setup | Launch options string | Notes |
|---|---|---|
| High-end PC (144 Hz+ monitor, strong CPU) | -novid -fullscreen +fps_max 0 -allow_third_party_software | Uncapped FPS, forced fullscreen, no intro. Clean and minimal. Let the hardware do the work. |
| Mid-range PC (targeting stable 144 FPS) | -novid -fullscreen +fps_max 144 | Capping at the monitor’s refresh rate keeps frame times consistent and avoids the GPU running hotter than necessary. More stable than uncapped on hardware that swings between 130 and 180. |
| Low-end PC (stability over peak FPS) | -novid -fullscreen +fps_max 60 | A stable 60 is more playable than an unstable 90. Cap at a number your system can hold consistently, then adjust upward once you have confirmed headroom. |
| Streamer / content creator | -novid -fullscreen +fps_max 0 -allow_third_party_software | The -allow_third_party_software flag is required for OBS and similar tools to hook into the game correctly. |
A note on FPS caps and input feel
Input lag — the delay between a mouse movement and the game responding — is worth thinking about separately from raw frame rate. Higher FPS means more frequent frame samples, which shortens the window between your input and the next rendered frame. Dropping below your monitor’s refresh rate causes stutter that is often more disruptive than a stable lower frame rate.
On the mouse side, make sure mouse_raw_input 1 is set either in the console or via your autoexec. This bypasses Windows pointer acceleration entirely, so the only variable affecting cursor movement is your in-game sensitivity. Pair this with disabling Enhance Pointer Precision in Windows mouse settings. Both need to be correct — raw input in CS2 alone does not fix Windows-level acceleration if it is still active at the OS level.
For a deeper look at how video and graphics settings affect frame rate and frame time, that guide covers Global Shadow Quality, Effect Detail, and Boost Player Contrast — settings that have a larger combined impact on competitive performance than any launch flag.
CS2 autoexec: what belongs there vs in launch options
Launch options run once when the game starts and control engine-level behavior. Your autoexec is a text file full of console commands that loads every time CS2 launches — it is the right place for anything that resets after a game update or that you want applied consistently without typing it manually.
To use one, create a file called autoexec.cfg and place it in:
steamapps/common/Counter-Strike Global Offensive/game/csgo/cfg
Then add -autoexec autoexec to your launch options field (or use the +exec autoexec command). CS2 will load the file on every startup.
Good candidates for your autoexec include:
- mouse_raw_input 1 — Bypasses Windows pointer acceleration. Set this here so it never gets reset.
- volume and snd_musicvolume — Persistent audio levels. Check the audio settings guide for recommended values.
- Viewmodel commands — Position, FOV, and offset values. These are covered in detail in the viewmodel settings guide.
- Crosshair commands — Style, size, color, and gap. The crosshair guide has a full breakdown of every relevant command.
- cl_showfps or net_graph equivalents — Persistent performance overlays if you want them on by default.
Keep launch options for engine-level flags and use the autoexec for everything else. That separation makes both easier to maintain and debug.
FAQ
Do launch options increase FPS in CS2?
Marginally, and only in specific cases. Removing a frame cap with +fps_max 0 lets the GPU run freely, which can raise your ceiling. But the meaningful FPS gains in CS2 come from in-game video settings and GPU driver configuration, not launch flags. Treat launch options as housekeeping, not a performance unlock.
Is -novid still needed in CS2?
It still works and still skips the intro video. It has no effect on performance — it just saves a few seconds at startup. There is no downside to including it, so most players keep it in. It is not essential, just convenient.
What does -high do in CS2?
-high sets the CS2 process to High priority in Windows Task Manager, theoretically giving it more CPU time. In practice, current testing on modern hardware puts the effect close to zero for most systems. It is not harmful, but do not include it expecting a real improvement. It is one of the most overhyped flags in circulation.
How do I remove launch options in CS2?
Open Steam, right-click CS2, select Properties, and go to the General tab. Highlight everything in the Launch Options field and delete it. Close the window. Steam saves the empty field automatically and the game will launch with no extra flags from that point on.
Should I use +fps_max in CS2?
Yes, but the right value depends on your hardware. Uncapped (+fps_max 0) works well if your system consistently exceeds your monitor’s refresh rate. If your frame rate fluctuates, capping at your refresh rate — for example +fps_max 144 — produces more consistent frame times and often feels smoother, even if the peak number is lower.
Once your settings are dialed in, the next step is your loadout. If you are looking to refresh your inventory without overspending, the best budget loadouts in CS2 guide covers solid options at every price point — and you can trade CS2 skins instantly with SkinVault’s trade bots to swap out anything you no longer use.