Best CS2 Launch Options in 2026 (What Actually Works)

Last tested: July 13, 2026

Short answer: the only CS2 launch options actually worth using in 2026 are -threads (set to your physical core count plus one) and -mainthreadpriority 2. Add -noreflex only if you cap your FPS with an external frame limiter like RTSS or NVIDIA's. Paste this into Steam, adjusting the thread count to your CPU:

-threads 9 -mainthreadpriority 2

That example is for a CPU with 8 physical cores. Replace 9 with your physical core count plus one. These options are not mandatory, CS2 runs fine with none at all, but on most systems these two help frametimes and responsiveness. Everything else you see in older guides, especially -tickrate 128, is left over from CS:GO and does nothing in CS2.

How to set CS2 launch options

1. Open Steam and go to your Library.
2. Right-click Counter-Strike 2 and choose Properties.
3. On the General tab, find the Launch Options box.
4. Type your options on a single line, separated by spaces, then close the window. They apply the next time CS2 starts.

Less is more here. Clear out whatever you currently have and keep only the options below that apply to your setup.

The CS2 launch options worth using

-threads [physical cores + 1]

Sets the thread count for the game. The rule is simple: take your number of physical cores and add one. On Intel, count P-cores only and ignore E-cores. A 14900K has 8 P-cores, so use -threads 9. A 9800X3D has 8 cores, so it is also -threads 9. The same physical-cores-plus-one rule applies to AMD. The effect is more noticeable on Intel CPUs, but your mileage may vary, so test it against your average framerate.

-mainthreadpriority 2

Raises CS2's main thread to a higher priority so it gets CPU time ahead of background work. On most modern systems this smooths frame delivery. One caveat: on an older CPU it can introduce stutter, so try it, and if the game feels worse, remove it. This is the targeted, modern replacement for the old blunt -high flag.

-noreflex (only with a frame limiter)

Use this only if you cap your FPS with an external limiter such as RTSS or NVIDIA's frame limiter. In that setup it gives smoother frametimes and slightly higher 1% lows. If you rely on the in-game fps_max cap or in-game NVIDIA Reflex instead, leave -noreflex off.

Optional: convenience flags (no FPS effect)

Two harmless quality-of-life flags that do not touch performance: -console opens the developer console at launch, and -novid skips the intro animation so you reach the menu a second or two faster. Add them if you like, but do not expect frames from them.

CS2 launch options that do nothing (delete these)

These are copied straight from CS:GO guides and are dead weight in CS2's Source 2 engine. Remove them.

Option	Why it is useless in CS2
-tickrate 128	CS2 replaced fixed tickrate with sub-tick updates. There is no 64 versus 128 tick anymore, so this flag has no effect whatsoever.
-d3d9ex, -dxlevel	DirectX 9 flags for the old engine. CS2 renders with DirectX 11 and Vulkan, so these are ignored.
-processheap	A very old CS:GO stutter workaround.
-high	Still works, but it is a crude "everything at high priority" hammer. Use the more precise -mainthreadpriority 2 instead.
+cl_forcepreload 1, -noaafonts, and similar	Removed or non-functional in CS2. cl_forcepreload is no longer a valid command, and -noaafonts was a CS:GO font flag with no effect in the Source 2 engine.

Do launch options actually increase FPS in CS2?

A little, not a lot. -threads and -mainthreadpriority 2 can improve frametimes and 1% lows on many systems, which makes the game feel smoother, but they will not rescue a struggling rig or add huge average FPS. Here is the part most guides will not tell you: launch options are the smallest lever you have.

Real, repeatable FPS and frametime gains come from the layers underneath the game, your Windows configuration, GPU driver settings, power plan, BIOS and memory tuning, and background bloat. We cover all of it in our full CS2 FPS optimization guide, and it is exactly the work we do for clients at FPSHeaven. If your frames spike or your game stutters mid-fight, no launch option will fix it, but a proper PC optimization consult will. Not sure it is worth it for your rig? Start with our €5 evaluation and we will tell you honestly.

Frequently asked questions

What are the best CS2 launch options for FPS?

Use -threads set to your physical core count plus one, and -mainthreadpriority 2. Add -noreflex only if you cap FPS with an external limiter like RTSS or NVIDIA's. No launch option will transform your FPS on its own, so improve real performance through your system as well.

What should I set -threads to?

Your number of physical cores plus one. Count P-cores only on Intel and ignore E-cores. Examples: a 14900K (8 P-cores) uses -threads 9, and a 9800X3D (8 cores) also uses -threads 9.

Is -mainthreadpriority 2 safe to use?

Yes, it is safe to try. It raises the game's main thread priority and helps most modern systems, but it can cause stutter on older CPUs. Keep it only if the game feels smoother with it on.

Does -tickrate 128 work in CS2?

No. CS2 uses sub-tick updates instead of a fixed server tickrate, so -tickrate 128 has no effect. You can safely delete it.

Do I need launch options at all in CS2?

No. Launch options are optional and CS2 runs fine with none. -threads and -mainthreadpriority 2 are worth trying for smoother frametimes, but they are not required.

How do I reset CS2 launch options?

Open Steam, right-click Counter-Strike 2, choose Properties, go to General, then Launch Options, delete everything in the box, and close the window.

Bottom line

Use -threads at your physical core count plus one, add -mainthreadpriority 2, and only add -noreflex if you run an external frame limiter. Ignore every "FPS boost" launch option left over from CS:GO. Then, if you actually want more frames and cleaner frametimes, fix the system beneath the game. Read our full CS2 FPS optimization guide, see our optimization packages, or grab the €5 evaluation to find out what is really holding your rig back.