Counter-Strike 2 launch options let you change certain startup settings before the game opens. You can use them to request fullscreen mode, set a specific resolution, open the developer console or select the Vulkan renderer. They are useful tools for specific tasks, but they are not a hidden switch that makes every PC faster.
Many supposed “best CS2 launch options” lists are still packed with commands copied from Counter-Strike: Global Offensive. Some refer to outdated DirectX features, some belong to the old networking model, and others change a setting without delivering the performance boost claimed alongside them. A long command line is not automatically better than a short one.
The key is to distinguish what an option actually changes from whether that change benefits your setup. Here are three simple configurations you can copy, an explanation of the commands worth knowing, and a reliable way to compare them without inventing FPS gains.
Which CS2 launch options should you use?
If CS2 starts correctly and already uses your preferred display mode, resolution and frame-rate settings, leave the launch options field empty. That is a valid configuration, not a missed optimization step. Steam and CS2 can handle ordinary startup settings without custom arguments.
Add an option when you need its specific function. For example, -fullscreen requests fullscreen mode, -w 1280 -h 960 supplies an explicit resolution, -vulkan switches the graphics API on Windows, and +fps_max 0 removes the limit controlled by the fps_max variable.
There is no universal CS2 launch string that increases FPS on every computer. Start with an empty field or use
-fullscreenif you specifically want fullscreen at startup.+fps_max 0removes a frame-rate cap; it does not make the hardware more powerful.-vulkanselects a different renderer; it is a comparison to run, not a guaranteed upgrade.
Steam's official launch options guide explains how launch arguments work and how they can help recover from incompatible video settings. Its general command reference also covers older GoldSrc and Source games, however, so do not assume every historical command applies to CS2's Source 2 engine.
How to set CS2 launch options in Steam
Close Counter-Strike 2 if it is running.
Open Steam and select Library.
Find Counter-Strike 2 in your list of games.
Right-click the game and select Properties.
Open the General tab and locate the Launch Options field.
Enter your chosen command line, close the Properties window and start CS2.
You usually do not need an Apply button. Steam retains the line entered in the field. The next time you launch CS2, the game receives those arguments. To cancel the change, delete the line and restart the game.
How to enter multiple launch options correctly
Put the options on one line separated by spaces. Keep the hyphen or plus sign that belongs to each argument. When an option requires a value, add that value after a space.
-fullscreen -w 1280 -h 960This requests fullscreen mode at 1280 × 960. There is no need to wrap the entire line in quotation marks or separate commands with commas, semicolons or line breaks. Do not combine contradictory display options, such as forcing fullscreen and windowed mode at the same time.
What is the difference between a hyphen and a plus sign?
Arguments beginning with a hyphen, such as -fullscreen and -vulkan, are interpreted as startup options. A plus sign normally passes a console command to the engine on startup. For example, +fps_max 300 requests a value of 300 for the fps_max console variable.
These forms are not interchangeable. -fullscreen is not the same as +fullscreen, and +fps_max 0 is not written as -fps_max 0. A console command also has to exist in CS2 and be permitted at startup; putting a plus sign before an obsolete command does not revive it.
Save your current settings before making changes
If the field already contains a line, copy it into a note before replacing anything. Record your current display resolution, fullscreen setting and FPS cap, too, because some of these values are saved inside the game rather than only in Steam. Keeping the original configuration makes it easy to undo a change without guessing what the previous settings were.
Change launch options while CS2 is closed, then restart it. Test one meaningful change at a time. If you simultaneously modify the rendering API, resolution, FPS cap and CPU priority, you will not know which setting produced the result.
Three ready-to-copy CS2 launch option presets
These are three alternatives, not three pieces of one longer command line. Start by deleting your existing arguments. Test one option set, record what happens, then replace it with the next. Run an initial test with the field empty so that you have a proper baseline.
Preset 1 – Standard fullscreen startup
-fullscreenThis is the simplest practical preset. It tells CS2 to open in fullscreen mode without changing the renderer, worker thread configuration or FPS limit. It is useful when you want the game to start fullscreen consistently after switching between display modes.
What to expect. If CS2 was already running in fullscreen mode, the command does not provide an extra FPS boost. Check that the game starts in the intended mode; there is nothing else to optimize with this flag.
Preset 2 – Fullscreen with an uncapped FPS limit
-fullscreen +fps_max 0The extra command sets the fps_max limit to zero, removing the cap imposed by that variable. Suppose CS2 was locked to 144 FPS but your PC could render considerably more in the same scene. After removing that cap, the displayed frame rate could rise above 144. If your PC was struggling to reach 110 FPS, removing a higher cap would not solve the underlying performance limit.
Uncapping the frame rate can keep the GPU working harder, raise power consumption and produce large peak numbers that say little about consistency. It is useful for a controlled comparison, but not automatically the best everyday setting. You can restore a comfortable cap in CS2's video settings or use a specific value such as +fps_max 300 if a 300 FPS ceiling is appropriate for your setup.
What to expect. A change only where the previous cap was limiting the output. Evaluate smoothness and frame times alongside the FPS counter, not just the biggest number it reaches.
Preset 3 – Fullscreen with Vulkan
-fullscreen -vulkanThis instructs the Windows version of CS2 to use Vulkan rather than its standard DirectX 11 rendering path. Vulkan is a real renderer choice; it is not an instruction to “unlock” GPU performance. Its effect on frame rate depends on the graphics card, driver, CPU and game build.
Test it against DirectX 11 with the same graphics settings and FPS limit. The first run after switching an API can involve shader preparation, so allow the game to settle before measuring. For the DirectX 11 comparison, remove -vulkan and restart CS2 completely.
What to expect. A different rendering path, not a guaranteed faster one. The right choice is the version that measures and feels better on your system.
Do not merge these three presets into one line. The Vulkan preset is not a more powerful version of the uncapped-FPS preset; they change different things. If the game is stable and smooth with no launch options, you can keep the field blank permanently.
CS2 launch options that work and what they actually do
Use a startup argument because it solves a particular problem, not because it appears in a popular “FPS config.” A command can be fully functional and still have no effect on your frame rate. For instance, selecting a language or launching at a certain resolution is a real change, but it does not increase the processing power of your CPU or GPU.
The following commands cover the most practical jobs that players try to accomplish through Steam. Some settings can also be changed from within CS2, where they are often easier to manage.
Common CS2 launch options and their intended functions
Command | What it does | When to use it |
|---|---|---|
| Requests fullscreen mode during startup. | When you want a predictable fullscreen launch. |
| Requests a startup resolution of 1920 × 1080. | When specifying a supported resolution or recovering from an unsuitable display mode. |
| Requests developer console access at startup in the Valve engine launch-option convention. | Only if you specifically want startup-console behavior; otherwise enable the console in the CS2 menu. |
| Selects the Vulkan renderer instead of DirectX 11 on Windows. | For a direct, measured rendering-API comparison. |
| Sets the in-game | When measuring performance without that particular FPS cap. |
| Sets the game's | If you intentionally want that limit and prefer applying it at launch. |
| Requests English localization. | When you want to override the current language choice. |
| Requests execution of the named configuration file. | When that file exists and you want its commands loaded. |
None of these commands overclocks hardware, unlocks additional CPU cores or magically allocates more VRAM. You can check their legitimate functions by looking at the display mode, selected renderer, applied console variable or resulting configuration.
Do you need -console?
The reliable way to enable the developer console is inside CS2. Open Settings → Game → Enable Developer Console (~) and set it to Yes. You can then assign or use the console key, commonly ~ on US keyboard layouts. This is also the method described in Steam's official developer console instructions.
Some Source-era launch option lists recommend -console to bring up the console as soon as the game starts. That distinction matters. It is not a performance setting, and you do not need it merely to have a usable console in a match. Enabling the console in the game's menu is the straightforward setup.
Should you add +exec autoexec.cfg?
An autoexec.cfg file is a place to store commands such as custom key bindings, crosshair settings or preferences you want to load consistently. In a correctly set up CS2 configuration, a proper autoexec file can run automatically. Adding +exec autoexec.cfg to Steam is not an essential performance trick, and repeatedly executing the same configuration usually solves nothing.
The command becomes useful when you deliberately want to run a separately named file. For example, +exec practice.cfg requests execution of practice.cfg during startup. The file needs to be in a location where CS2 can find it, and the commands inside must still be valid in Source 2.
Keep lengthy key binds and individual gameplay preferences in configuration files or the game settings. The Steam launch options field is most useful for startup behavior.
Can you change the CS2 language through launch options?
-language english requests an English-language interface. This can help if the language you want is different from the one currently being used. Steam also has language-related game properties, so check those first when you want a permanent change.
Do not set one language in Steam's game properties and a conflicting language through launch arguments. Pick one method, restart CS2 and confirm that the interface changed. Language selection is unrelated to frame rate or network latency.
Best CS2 launch options for FPS and performance
A search for “CS2 launch options for FPS” often produces a command line promising an instant boost. The problem is that CS2 performance can be limited by the CPU, GPU, memory behavior, rendering pipeline or an intentional frame-rate cap. Launch options can change some software choices, but they do not remove those hardware limits.
Before changing anything, work out whether the game is capped below what your system can render or already running as quickly as it can. Those are very different situations.
What does +fps_max 0 actually do?
The console variable fps_max defines a frame-rate ceiling for gameplay. Setting it to 0 removes the restriction imposed by that variable. If a previous cap was holding the game at 144 FPS and the hardware can render 200 FPS in the same scene, the counter may increase after the cap is removed.
If a low-end PC is already limited to around 95 FPS by its processor or graphics card, +fps_max 0 will not turn that into 200 FPS. The distinction is between lifting an artificial ceiling and improving actual rendering capacity. +fps_max 300, by contrast, introduces a ceiling of 300 FPS; it does not make the system target or guarantee 300.
CS2 already provides controls for this in its own menus. Valve's official video-settings update notes explain that the Maximum FPS In Game and Maximum FPS In Menus controls map to fps_max and fps_max_ui respectively. For normal use, the in-game settings are often preferable to a permanent Steam override.
FPS cap versus FPS result. A cap is a maximum permitted value, not an instruction for the GPU to reach it. Setting
+fps_max 300will not create 300 FPS if the computer cannot render that many frames.
Is unlimited FPS better than an FPS cap?
Removing the cap is useful when benchmarking the upper performance limit of your hardware. For regular play, however, maximum average FPS is only part of the picture. Frame-time consistency, input latency, screen tearing, fan noise and GPU load matter as well.
Valve's official CS2 video settings recommendations discuss refresh rates, adaptive sync and frame pacing. For systems with compatible NVIDIA hardware and monitors, Valve recommends a coordinated G-Sync, V-Sync and Reflex configuration. It can deliberately keep frame rate a little below the display's refresh rate to improve consistency and latency. An unconditional instruction to uncap FPS therefore conflicts with a legitimate, officially recommended setup for some players.
For an FPS-cap experiment, change only the cap, measure a repeatable scene, and then choose the limit that best suits your display and hardware. Do not judge a configuration by one unusually high number recorded while looking at a wall.
Does -high improve CS2 FPS?
The point of -high is process scheduling priority, not extra CPU performance. Higher priority affects how Windows allocates processor time when tasks compete for it. It does not create cores, increase clock frequency or speed up memory.
Individual benchmark results for this parameter vary with the test system and background workloads. That is not evidence of a general-purpose FPS improvement. A computer with an already well-scheduled game process cannot gain substantial rendering capacity merely from a priority change. On some systems, aggressive scheduling can also interfere with other tasks you need running normally.
Recommendation. Keep -high out of your default CS2 launch string. Consider process scheduling only if you have identified a specific scheduling problem and can demonstrate an improvement with controlled measurements.
What about -threads 4, -threads 8 or CPU core count plus one?
The common advice to type your CPU's total thread count plus one is misleading. This option concerns the engine's worker-thread pool; it is not a switch that unlocks all logical processors. The operating system already schedules work across available CPU resources, and Source 2 handles its own parallel tasks.
Technical inspections of CS2 have shown that specifying -threads can change the reported worker-thread configuration. That makes it inaccurate to claim the parameter is always completely ignored. But a changed thread-pool number is not proof that a game renders more frames, and increasing the number can be counterproductive.
For example, a published controlled comparison on a Ryzen 7 7800X3D reported a default engine pool of seven workers on an eight-core CPU; overriding the parameter changed the pool size rather than unlocking any hidden cores. The important conclusion is not a magic number for that processor. It is that the engine has a default allocation, and manually changing it needs a demonstrated reason.
Recommendation. Leave -threads unset unless you are diagnosing a measurable problem on your particular system. Neither -threads 4 nor -threads 9 nor “logical cores plus one” is an all-purpose performance preset.
Is -vulkan faster than DirectX 11 in CS2?
-vulkan genuinely switches the renderer. You can inspect the active renderer using CS2's diagnostic output rather than trusting the presence of the command in Steam. Whether Vulkan performs better is a separate question, and controlled tests do not all point in the same direction.
Published benchmark comparisons illustrate the difference. One tester using an Intel Arc B580 with an Intel Core i5-14400F reported average frame rates of approximately 324.6 FPS on DirectX 11 and 350.2 FPS on Vulkan in their chosen benchmark. A separate multi-run comparison on an NVIDIA GeForce RTX 5070 Ti with an AMD Ryzen 7 9700X reported approximately 732.3 FPS on DirectX 11 and 706.1 FPS on Vulkan on that system. These are independent, hardware-specific published measurements, not results measured by 555Drop and not guarantees for other PCs.
Both outcomes are consistent with the same technical explanation. API performance depends on the GPU architecture, driver, CPU bottlenecks, graphics settings and the particular version of CS2. On a system where Vulkan is ahead, switching can help. On a system where DirectX 11 is ahead, switching can hurt. You cannot predict the winner solely from the word “Vulkan.”
How to judge the result. Compare average FPS alongside 1% low FPS and frame times where you have a tool capable of measuring them. A configuration with slightly lower average FPS but fewer sharp frame-time spikes can feel smoother. Let shader preparation finish before recording Vulkan results, then rerun the same test on DirectX 11.
How to change CS2 resolution with launch options
The -w and -h arguments request a screen width and height when CS2 starts. They are especially helpful if you want to restore a supported display mode after a bad setting or specify a particular resolution before the game opens.
Copy-ready CS2 resolution launch options
Goal | Launch options | Requested resolution |
|---|---|---|
1080p fullscreen |
| 1920 × 1080, 16:9 |
1280 × 960 fullscreen |
| 1280 × 960, 4:3 |
1024 × 768 fullscreen |
| 1024 × 768, 4:3 |
1440p fullscreen |
| 2560 × 1440, 16:9 |
Only select display modes supported by your monitor or driver. You can normally choose the same settings from CS2's Video menu, where the available options are visible and easier to reverse. Keeping the resolution in launch options is most helpful when you have a specific startup requirement or are trying to recover from a bad display setting.
How to set 4:3 stretched resolution in CS2
A popular search is “CS2 launch options 4:3 stretched.” The critical distinction is that a 4:3 resolution and a stretched image are not the same setting. A line such as -w 1280 -h 960 requests the 4:3 pixel dimensions. It does not independently instruct the GPU to stretch that image across a wider monitor.
Select a 4:3 aspect ratio in CS2, then choose a supported resolution such as 1280 × 960.
Choose fullscreen mode.
Open the scaling controls in your graphics driver's software, if your display needs a separate scaling setting.
Select full-screen scaling or the equivalent setting if you specifically want the 4:3 image stretched to fill a 16:9 display.
Return to CS2 and confirm that the display looks correct. Undo the scaling change if you prefer black bars or the result is distorted.
There is no special Steam argument that turns a 4:3 resolution into guaranteed stretched scaling on every driver and monitor. Width and height describe the rendered image; scaling determines how that image is presented on the physical screen.
Can launch options force 144 Hz, 240 Hz or another refresh rate?
You may see -freq 144, -refresh 144 or -refresh 240 in legacy Source guides. These are not a reliable general-purpose substitute for confirming the actual refresh rate in modern CS2. First set the correct refresh rate in your operating system and verify the active video mode in the game.
Valve's CS2 display recommendations encourage using the highest refresh rate supported by the monitor and explain that windowed and fullscreen-windowed modes follow the operating system's display configuration. Check the screen's real operating mode instead of assuming a Steam parameter has changed it.
Also remember that 240 Hz is not the same as 240 FPS. Hertz describes how often the display can refresh. FPS describes how many frames the game renders. Neither figure guarantees the other.
Outdated CS2 launch options you should not copy from CS:GO guides
Counter-Strike 2 uses Source 2, and many old Counter-Strike: Global Offensive startup and console settings refer to systems that are no longer present. Others are still recognized in some form but do not deliver the widely advertised benefit. Mixing them all into one “FPS boost” command line makes troubleshooting harder and can introduce unnecessary overrides.
Common legacy launch options and why they do not belong in a universal CS2 setup
Option | What is wrong with the usual recommendation | Practical advice |
|---|---|---|
| Historically skipped an introductory movie in older Source games. CS2 does not use that old intro sequence as a loading bottleneck. | Remove it. It does not increase in-match FPS. |
| Old advice presents disabling joystick support as a memory and FPS boost, without repeatable proof of a worthwhile CS2 performance gain. | Do not add it for supposed FPS savings. |
| Does not switch CS2 matchmaking to the older CS:GO-style 128-tick setup. | Remove it. |
| Relate to the old DirectX 9 renderer that CS2 does not use. | Remove both. |
| Legacy DirectX selection for previous Valve engines, not a CS2 low-end graphics preset. | Do not use. |
| Old preload command, not an applicable modern CS2 optimization variable. | Remove it. |
| Source 1 material-system setting. Does not unlock hidden multithreading in Source 2. | Remove it. |
| Old memory-allocation argument, not a supported way to reserve more useful RAM for CS2. | Do not use. |
| Can affect engine worker-thread configuration, but there is no universally faster value. | Leave it unset without a measured reason. |
| Changes scheduling priority rather than the CPU's processing capacity. | Exclude it from default FPS presets. |
| Old display arguments are a poor replacement for selecting and verifying the actual refresh rate in the OS and CS2. | Use the display and game settings instead. |
Why a command can appear to work even when it changes nothing
Steam passes arguments to the game executable. CS2 can still start normally when some of those arguments are irrelevant or unrecognized. The absence of an error message is not evidence that every command was successfully applied.
To confirm a real effect, check the thing the command claims to change. A resolution option should produce the specified display mode. An FPS limiter should affect the reported variable and frame ceiling. A graphics API switch should be visible in renderer diagnostics. A claimed FPS increase requires repeatable measurements, not just a successful launch.
Can -tickrate 128 enable 128-tick CS2 matchmaking?
No. The old debates around 64-tick and 128-tick Counter-Strike: Global Offensive servers cannot be resolved by inserting this flag into CS2's Steam properties. Counter-Strike 2 uses a subtick-based system, and a client launch argument does not change the official server's networking schedule. Do not confuse a local startup flag with control over matchmaking infrastructure.
If you want background on the legacy engine networking model, Valve's technical multiplayer networking documentation provides useful context. It should not be interpreted as a recommendation to force old tickrate parameters in Source 2.
Does -novid make CS2 launch faster?
The old -novid flag existed to skip a startup video in earlier Valve games. It does not remove the real work CS2 performs while loading resources, preparing shaders or initializing hardware. If launch time is unusually long, investigate the actual startup bottleneck rather than relying on an intro-skipping flag copied from CS:GO.
Similarly, replacing a modern video mode with a DirectX 9 argument will not reduce the actual hardware requirements of CS2. Outdated flags are not a substitute for supported in-game settings.
Should you copy the launch options used by pro players?
Professional players' settings can be useful examples of individual preferences, but they are not universal performance profiles. A pro player's line may reflect their monitor refresh rate, chosen resolution, peripheral setup or simply a personal habit carried over from an older game.
If you want to use 1280 × 960 after seeing a professional player use it, configure that resolution deliberately. If you want fullscreen, set fullscreen. Avoid blindly copying unrelated startup flags just because the source has a recognizable name.
Avoid “ultimate FPS configs.” Ten launch arguments are not automatically better than one. Some old commands are irrelevant, some duplicate ordinary menu settings, and others override working defaults. Keep your launch line limited to changes you understand and can verify.
How to test CS2 launch options without misleading FPS results
Verifying a display setting is straightforward. -fullscreen should produce the intended window mode. A resolution line should produce a supported resolution. -vulkan should select a different rendering API. Proving a performance benefit requires more discipline, because FPS can fluctuate even when the game and your hardware are unchanged.
Test FPS under the same conditions
Record a baseline. Clear the Steam launch options field. Start CS2 with your usual video settings and note the FPS cap, display mode and renderer.
Use a repeatable scenario. A consistent benchmark route or the same controlled scene is better than comparing unrelated multiplayer rounds. Player activity, smoke, effects and server behavior can change the workload dramatically.
Warm up the game. Allow maps and shaders to finish their initial loading work. Do not treat a loading hitch as ordinary gameplay performance.
Measure more than once. Record several runs, including average FPS. Where your tool supports it, record 1% lows and frame times so that large stutters do not disappear behind a high average.
Change one setting. Close the game, add exactly one option or preset and repeat the same scenario with all other settings unchanged.
Recheck the original setup. Clear the field and run the baseline again. This helps identify temporary fluctuations that are unrelated to the command you tested.
CS2's own telemetry and FPS readouts are useful for checking simple changes. For a rigorous 1% low or frame-time comparison, use a measurement method that actually records those metrics. Do not label a simple instantaneous FPS display as a full frame-time benchmark.
How to check whether Vulkan is active
Start CS2 with -vulkan. Open the developer console and enter:
sys_infoInspect the reported system information for the active graphics renderer. When Vulkan is selected and initialized, the renderer details should reflect it. Then close CS2, remove -vulkan, relaunch under the usual Windows rendering path and inspect the information again. This verifies the actual API change rather than merely confirming that Steam accepted the typed string.
For any FPS comparison between Vulkan and DirectX 11, keep your frame cap and graphics settings equivalent. If one renderer has an FPS cap and the other does not, the results do not isolate the renderer's performance.
Compare all three presets with a clean baseline
Start with no custom launch options, then test each of the three short strings in turn. They represent different questions.
-fullscreen. Does CS2 start in the desired fullscreen mode? If it already did, performance should not be assumed to improve.-fullscreen +fps_max 0. Was the previous gameplay FPS limit preventing higher output? Check FPS along with smoothness, GPU usage and whether uncapping introduces unwanted heat or noise.-fullscreen -vulkan. After shader warm-up, how does Vulkan compare against DirectX 11 at the same FPS cap and graphics settings? Confirm the renderer withsys_info.
Do not compare a capped DirectX 11 baseline to an uncapped Vulkan test and conclude that the rendering API caused the difference. The test conditions must be comparable.
Use the following table to note the changes you observe. The illustration for this section intentionally contains no fabricated benchmark numbers.
Test | What changes | What to record |
|---|---|---|
Empty field | No startup override | Baseline FPS, frame-time behavior and display mode |
| Startup display mode | Whether fullscreen works and whether any new issues appear |
| Gameplay FPS ceiling | Average FPS, consistency, GPU load and temperatures |
| Renderer | Average FPS, 1% lows and frame times after warm-up at the same cap |
Does every working option have to increase FPS?
No. An option to change the interface language can function perfectly and leave game performance unchanged. A fullscreen setting can be applied successfully even when fullscreen was already selected. An explicit resolution can change the GPU's workload, but if performance is limited by the CPU, the resulting FPS change may be small.
It is more useful to ask whether the argument achieved its stated purpose. Only claim a frame-rate improvement if the measured frame rate improved under comparable conditions. That distinction prevents unnecessary startup changes and avoids confusing a settings adjustment with a performance breakthrough.
CS2 launch options not working – fixes for black screens, crashes and ignored commands
If CS2 launches with a black screen, unexpectedly changes resolution or becomes unstable immediately after a new startup argument, the most effective first check is to remove the argument. Do not try to repair a potentially bad command line by adding more unknown commands on top.
How to reset CS2 launch options
Close Counter-Strike 2.
Open Steam → Library → Counter-Strike 2 → Properties → General.
Delete the entire contents of the Launch Options field.
Close the Properties window and launch CS2 again.
Clearing this field resets the launch arguments, not every saved game setting. Your crosshair, binds, mouse sensitivity and other preferences are not automatically deleted just because you removed the Steam arguments.
Black screen after changing resolution or display mode
First remove the recent launch options, especially forced resolutions, unusual display modes, refresh-rate arguments and Vulkan. Test the default startup. If the issue began immediately after selecting a resolution your current display does not handle correctly, you can try requesting a widely supported temporary resolution:
-w 1280 -h 720Once the game opens successfully, select a proper display mode in CS2's Video settings and remove the temporary recovery line. A troubleshooting resolution is not an everyday performance preset. Steam's official video-mode recovery guidance describes recovery approaches for Valve games; treat its older-engine commands carefully rather than importing obsolete DirectX settings into CS2.
CS2 crashes after adding -vulkan
Close the game, delete -vulkan and restart. On Windows, this returns the game to its usual DirectX 11 rendering path. If CS2 still crashes with no launch options, the problem is no longer explained by that argument alone. Verify game files through Steam and check whether your graphics driver and display mode are functioning normally.
Do not layer -high, -threads or legacy DirectX flags onto a crashing Vulkan setup. They do not address the underlying API initialization issue.
Launch options are ignored or do not change FPS
Check that the commands are in the Properties of Counter-Strike 2, use the correct prefix, and are separated by ordinary spaces. Restart after changing them. Next, verify that the command actually exists in CS2 and that you are observing the setting it is meant to control.
For +fps_max 0, check the current fps_max setting and whether the original cap was being reached. For -vulkan, inspect sys_info. For -w and -h, inspect the display mode. The game starting without an error is not sufficient evidence that every argument works.
Common launch-option problems and the first thing to try
Problem | Likely area to check | First action |
|---|---|---|
Black screen at startup | Unsupported resolution, display mode or renderer | Clear startup arguments, then restore a supported video mode. |
Resolution changes back | Conflicting Steam arguments and saved CS2 video settings | Use one method for selecting the resolution. |
No FPS improvement | Wrong expectation about what the argument actually does | Verify the real function, not an advertised generic boost. |
Stuttering immediately after Vulkan switch | Shader preparation or API performance | Warm up the renderer, compare again or remove |
Wrong window mode | Conflicting fullscreen and windowed arguments | Remove contradictory launch flags. |
Performance worsens after a copied config | Unneeded | Start with an empty field and add back only justified settings. |
Fastest reliable diagnosis. If trouble began immediately after pasting a long “FPS config,” clear the entire Steam field before inspecting every argument individually. If CS2 works again, reintroduce only the commands needed for a specific purpose. This establishes a known-good baseline and dramatically reduces the number of variables.
Frequently asked questions about CS2 launch options
What are the best CS2 launch options?
For most players, the best starting point is an empty Launch Options field. If you need to enforce fullscreen, use -fullscreen. If you want to test the effect of removing the FPS cap, use +fps_max 0. If you are comparing renderers, test -vulkan separately. A good setup contains only commands that solve a problem you actually have.
What are the best CS2 launch options for a low-end PC?
There is no special startup string that turns a weak processor or GPU into a faster one. Avoid automatic bundles of -nojoy, -threads and -high. If reducing graphics load is the goal, change the in-game resolution or other supported video settings; they can affect workload directly. Test Vulkan against DirectX 11 only when you can compare both under the same conditions.
Which CS2 launch options really help FPS?
+fps_max 0 can reveal a higher frame rate when an existing cap was holding the game back. -vulkan changes the rendering API and can perform differently on different GPUs. Neither is a guaranteed FPS multiplier. Arguments such as -console and -language english have other purposes and should not be described as frame-rate boosters.
Where are CS2 launch options if the game will not open?
You do not need to launch CS2 to edit its startup arguments. In Steam, open Library → right-click Counter-Strike 2 → Properties → General → Launch Options. Delete the problematic line and try starting the game again. This is often the fastest recovery step after a copied config causes startup trouble.
How do I use several CS2 launch commands together?
Enter them in one field, separated by spaces, and preserve their prefixes. For example:
-fullscreen -w 1280 -h 960Do not add commas between the commands or wrap the entire line in quotation marks. Avoid contradictory display modes and avoid stacking multiple versions of a setting that you intend to control only once.
How do I launch CS2 at 1920 × 1080?
-fullscreen -w 1920 -h 1080This requests a 1920 × 1080 fullscreen display mode. The resolution must be supported by your monitor and driver. If CS2 is already running at the correct resolution, there is no need to duplicate the setting in Steam. Using the game's Video menu is generally easier for an ongoing resolution preference.
How do I use 1280 × 960 stretched in CS2?
Use -w 1280 -h 960 if you need to request that 4:3 resolution at launch, or select 1280 × 960 from the CS2 Video menu. To fill a 16:9 screen without side bars, the GPU or monitor must also scale the 4:3 image appropriately. Launch options determine the requested resolution, not the entire scaling behavior.
Does -threads work in Counter-Strike 2?
It can affect the engine's worker-thread pool; that is not the same as unlocking more CPU cores or guaranteeing higher FPS. Tests have not established one optimal numeric value for all systems. Unless you are investigating a specific, measurable performance issue, leave the parameter unset and allow the engine to manage its default allocation.
Should I add -high for maximum FPS?
No universal benefit has been established. The parameter relates to process scheduling priority rather than raw CPU performance. A default setup should not include it just because an old guide lists it. If you are genuinely diagnosing CPU contention, compare measured results carefully rather than expecting an automatic boost.
What does -vulkan do in CS2?
On Windows, it selects the Vulkan graphics API instead of the usual DirectX 11 path. You can check the active renderer through sys_info. Published tests on different GPU setups have reached different conclusions about FPS, so evaluate the two APIs with matched game settings and repeated measurements.
Can I force 128-tick CS2 servers with launch options?
No. Adding -tickrate 128 to the Steam field does not convert official CS2 matches to the classic CS:GO 128-tick model. The game's subtick-based network design and the official server configuration are not controlled by that client launch argument.
Does -novid remove the CS2 startup screen?
-novid was designed to skip a particular intro video in older Valve games. It does not fix CS2's actual startup work such as resource loading or graphics initialization. Removing it from your command line will not reduce performance. If launching is unusually slow, investigate the real startup bottleneck.
Can I force English as the CS2 language?
You can use -language english, but it is often simpler to select the language through the relevant Steam game properties. Avoid conflicting language selections in multiple locations. A language argument is a localization preference, not a performance optimization.
Will CS2 launch options lower ping or remove input lag?
Changing the resolution, uncapping FPS and selecting Vulkan do not shorten the network route to the game server. They may change how quickly an image is rendered or how responsive the game feels, but they cannot directly fix a high-ping connection. Network troubleshooting and frame-time or input-latency testing address different problems. Old CS:GO network commands should not be treated as universal input-lag fixes.
Why did my FPS drop after copying launch options?
A copied line may have changed the renderer, worker-thread allocation, frame cap or display mode in an unhelpful way. Clear the launch options, confirm that performance returns to your baseline, and reintroduce only the settings you need. This is more informative than adding yet another purported FPS command.
Can one launch command reset every CS2 setting?
Deleting Steam launch arguments resets those startup overrides only. It does not automatically remove your crosshair, key binds or sensitivity settings. Separate procedures exist for resetting in-game configuration, but they should not be performed casually if you want to keep your preferences. Avoid random “full reset” commands from old guides.
Should I copy the launch options of donk, m0NESY or another pro?
Only copy a specific setting if you understand why you want it. A professional player's resolution and monitor setup may be very different from yours. Their line of startup arguments is not a tested optimization profile for every other computer, and some of the listed commands may simply reflect old habits.
Which CS2 launch options should you keep?
Keep the commands that produce a useful, observable result and remove the rest. An empty field is the right default when CS2 starts, looks and plays as expected. Use -fullscreen when you need fullscreen at launch, -w and -h for a specific supported resolution, +fps_max 0 to test performance without that frame-rate cap, and -vulkan to compare rendering APIs.
Start with the default configuration, test the three short presets separately and measure what actually changes. There is no reason to keep outdated DirectX 9 commands, -tickrate 128 or an arbitrary -threads value in a permanent startup string. A short, intentional setup is easier to understand, easier to troubleshoot and less likely to cause problems when CS2 receives updates.