Configuration and diagnostics
The console accepts commands and configuration variables used to adjust supported client options, inspect state or manage an authorized server. Some settings are also available through menus, while others are primarily used by players, server operators or developers. Command names and behavior can change between updates, so CS2-specific documentation should be dated.
Opening the console is controlled through the game’s settings and an assigned input. The exact menu path and binding can vary with interface changes or the player’s setup. Use Key Bindings to understand the associated input and consult the current CS2 settings rather than relying on instructions from an earlier release.
Client, server and multiplayer context
Commands may affect the local client, a hosted server or a connected multiplayer session. A command that works in a local practice environment may be unavailable or restricted on an online server. Server-side settings generally require appropriate control of the server; having the console open does not grant permission to change the match.
Practice commands and bots are separate CS2 topics. Some commands require a practice context or server permission, and certain commands are restricted in multiplayer. The console should not be confused with third-party cheats or with a way to bypass anti-cheat or server rules. Refer to Practice Commands, Bots and Workshop Tools for their scoped CS2 uses.
CS2 applicability
This page covers the console as a CS2 interface. It avoids importing earlier games’ activation paths, command behavior or unrestricted examples. Consult current CS2 documentation for syntax and permissions before using a particular command.
sv_predictable_damage_tag_ticks (August 14, 2024)
The August 14, 2024 update identified sv_predictable_damage_tag_ticks as the server convar for adjusting the delay applied to damage-tagging effects and listed a default of 2. The patch does not convert that default into a real-time duration or say every community server must use it. This is a server-side mechanics setting, distinct from the client display settings described elsewhere. See Damage Tagging for what the delay changes when a player takes damage.
Client, server and practice command scope
The Developer Console is a text interface for entering commands and reading diagnostic output. Commands may affect the local client, a hosted server, or a particular game system, so a command appearing in a Wiki list does not mean it works for every player in every matchmaking session. Server commands generally require control of the server or permission from its administrator; cheat-protected commands require an environment where the server allows them. A command that changes local display or input is different from one that changes bots, teams or match rules.
For CS2 practice, keep experiments in a local session or a server you control. This makes it clear which settings are local and which affect everyone. Do not enter a command from an older Counter-Strike page without checking that it applies to CS2; command names, parameters and permissions can change. The Community Servers and Bots entries explain common practice contexts, while Settings covers the in-game controls available without console syntax.
Reading output and troubleshooting
A command may return an error because its spelling is wrong, its parameter is invalid, the command is unavailable in the current mode, or the user lacks server permission. Read the console response before repeating the command or changing unrelated settings. If a command changes a practice server, note the prior value so the test can be reversed or the session restarted cleanly. A console command is not an external cheat by itself; third-party software that manipulates game state is a different category.
Use the console as a targeted troubleshooting tool rather than a replacement for the Settings menu. A graphical option is easier to verify and less likely to be mistyped, while the console can expose diagnostics and server controls not shown as ordinary menu options. Bindings and audio choices should be checked in the current CS2 interface because exact menu names and defaults are version-sensitive.
September 27, 2023 Counter-Strike 2 launch update
The September 27, 2023 launch update restored the clutch_mode_toggle function. The patch records its return but does not give syntax, permissions or a full command description. It is a console-facing function, not a change to matchmaking or the rules for winning a clutch. Check current CS2 command help before relying on a specific invocation.
Long-frame diagnostic output (April 30, 2024)
The April 30, 2024 update added console output intended to help advanced users diagnose performance problems. When a very long frame occurs, the game prints a brief profile for that frame; at the end of a match it also prints a summary. The release note does not define a numerical threshold for a very long frame or list the fields included in either report, so the output should be treated as diagnostic context rather than a complete benchmark or a named performance counter.
The information is useful when investigating a stutter that occurs during play: the frame profile provides a short record associated with a long frame, while the match-end summary offers a broader report after the session. The update adds reporting only; it does not promise to fix the performance problem automatically, identify its cause, or improve frame rate by itself. No special console command is specified in the patch note.
sv_cheats exploit fix (April 7, 2024 record)
The Counter-Strike 2 patch index lists an April 7, 2024 update associated with an sv_cheats exploit fix. SteamDB records build 13982036 on April 8 UTC and lists “Fixed sv_cheats exploit” as an extra note; it says the build has no official patch notes. The one-line record confirms a correction but does not describe its technical cause, the exact protected settings involved, or every affected mode.
Because the record names sv_cheats, it belongs with the console permission context, but it does not show that normal console access grants authority over an online server. A fix to an exploit corrects an unintended boundary failure; it does not authorize use of restricted controls. No commands, reproduction steps, affected modes or implementation details are documented here. See Practice Commands for the separate authorized practice context.
fps_max restriction while connected to a server (August 14, 2025)
On August 14, 2025, CS2 stopped allowing fps_max to be changed while connected to a server. The patch records a restriction on changing this console variable during an active server connection; it does not state that the setting was removed, nor does it specify a required value. This is a version-dated console behavior, distinct from the same update’s fullscreen windowed display controls.
cl_allow_multi_input_binds (August 19, 2024)
The August 19, 2024 update introduced a default restriction on input binds containing more than one command from a specified movement and action list. Its notes identify the cheat-protected console variable `cl_allow_multi_input_binds 1` as the way to re-enable support in contexts where that protected setting is available. The rule is about combining commands in a bind; it does not remove individual movement, attack, jump or use commands from ordinary controls. It is also separate from the update’s official-server kick policy for certain kinds of hardware-assisted input automation.