CS2 launch options are command-line flags you pass to the game through Steam before it starts. The right combination removes your FPS cap, reduces input overhead, and forces the game to use your monitor’s full refresh rate — all before the first round loads. For a full PC-wide FPS strategy, see our PC optimization guide for better FPS.
What Are CS2 Launch Options?
Launch options are flags passed to the CS2 executable at startup via Steam. They configure the game at the engine level — below the in-game video menu — which means some settings (like process priority and monitor refresh rate) can only be changed here, not inside CS2 itself.
Unlike CSGO, CS2 runs on the Source 2 engine and uses DirectX 11 by default. Many CSGO launch options (like -nod3d9ex and -processheap) do nothing in CS2 or cause instability. Keep your launch string clean and only use options confirmed to work on Source 2.
How to Set CS2 Launch Options
- Open Steam and go to your Library.
- Right-click Counter-Strike 2 and select Properties.
- Under the General tab, find the Launch Options field.
- Paste your options as a single space-separated string (e.g.
-novid -high -freq 144). - Close the window — Steam saves automatically. Changes apply on the next game launch.
There is no need to restart Steam. If an option causes crashes or stutters, remove flags one at a time and re-launch to isolate the culprit.
Best CS2 Launch Options for FPS in 2026
These are the launch options that produce measurable FPS gains or reduce input lag in CS2 as of 2026. Use them as your baseline configuration:
| Launch Option | What It Does | FPS Impact |
|---|---|---|
-novid | Skips the Valve intro video on every launch | No FPS change — saves 5–10 seconds at boot |
-high | Sets CS2 process priority to High in Windows Task Manager | +5–15 FPS on systems with active background processes |
-freq 144 | Forces the game to target your monitor’s refresh rate. Replace 144 with your actual Hz (e.g. -freq 240 for 240Hz panels) | Required for 144Hz or 240Hz output to render correctly |
+fps_max 0 | Removes CS2’s FPS cap entirely for uncapped output | +20–40 FPS if the default engine cap was throttling your GPU |
-nojoy | Disables joystick and gamepad input polling on launch | Reduces input thread overhead; minor gain on CPU-bound systems |
-fullscreen | Forces exclusive fullscreen mode instead of borderless windowed | +5–10 FPS vs windowed borderless on some NVIDIA configurations |
-console | Opens the developer console automatically on game launch | No FPS impact — quality-of-life only |
-allow_third_party_software | Required for NVIDIA GeForce Overlay, AMD Adrenalin HUD, and some screen capture tools to work in-game | No FPS impact |
Recommended launch string: -novid -high -freq 144 +fps_max 0 -nojoy -console
Replace 144 with your monitor’s actual refresh rate. Players on 60Hz monitors can omit -freq entirely — it defaults correctly in most cases on standard refresh rates.
Additional Options Worth Testing
These options are not universally beneficial. Test them individually on your system before keeping them in your launch string:
| Launch Option | When to Use It |
|---|---|
-tickrate 128 | Only affects offline and local practice servers. Has zero effect on official Valve matchmaking tick rate |
+cl_forcepreload 1 | Preloads all map assets before the round begins. Reduces mid-match texture pop-in at the cost of longer initial load time |
+mat_queue_mode 2 | Forces multi-threaded rendering. Can help on 6-core or better CPUs; causes stutters on some systems — test before keeping |
-threads [n] | Manually allocates CPU threads to CS2. Only worth testing on 8+ core CPUs. Use your physical core count minus 2 |
CS2 Launch Options That No Longer Work
These CSGO launch options were widely used but have no effect in CS2 or actively cause crashes. Remove them from your string if they are still there:
| Dead Option | Why It No Longer Works in CS2 |
|---|---|
-nod3d9ex | CS2 does not use DirectX 9. This flag is not recognised by Source 2 |
-processheap | Source 1 memory allocation flag. Not present in Source 2’s memory model |
-noaafonts | CS2 handles font rendering differently. No effect |
-noforcemparms / -noforcemaccel / -noforcemspd | CS2 manages raw mouse input natively through in-game settings. These Source 1 flags do nothing |
-limitvscontrast | Deprecated post-Source 2 migration. No effect in CS2 |
-softparticlesdefaultoff | CS2’s particle system changed in Source 2. Use the in-game Particle Quality slider instead |
Understanding the technical reason each setting matters — not just what to set — makes it easier to adapt when game updates change defaults. The Game Settings Explained guide covers the render pipeline terminology and hardware concepts behind CS2 and other PC shooter settings.
Frequently Asked Questions
Do CS2 launch options affect VAC or risk a ban?
No. All options listed in this guide are Valve-approved. The only option that disables VAC is -insecure, which also locks you out of official servers entirely. Standard performance flags like -high, -freq, and +fps_max have no effect on VAC status.
Should I use -high on Windows 11?
Yes, on most systems. Windows 11 already prioritises foreground applications, but -high pushes CS2 above background services including antivirus scans, browser rendering threads, and Windows Update processes. The gain is most visible on Ryzen 5 or Core i5-class CPUs running under moderate background load.
Does +fps_max 0 cause overheating?
Uncapped FPS drives your GPU and CPU harder, especially in menus where frame rates can spike above 1,000 FPS. If temperatures are a concern, set +fps_max 300 as a reasonable upper bound rather than fully uncapping. This still eliminates the default engine cap while preventing thermal spikes on idle screens.
Can I use these launch options with Faceit or ESEA?
Yes. All options in this guide are fully compatible with Faceit and ESEA. Third-party anti-cheat platforms flag cheat software, not performance configuration flags. You can use this full launch string on any ranked or third-party competitive platform without risk.
Why is -freq important for 144Hz monitors?
Without -freq, CS2 may initialise its render loop at 60Hz even on a 144Hz or 240Hz display, capping effective frame output regardless of GPU capability. Always set -freq to your monitor’s native refresh rate to ensure the engine uses the full capability of your panel.