Actions, devices and contexts
Controls are easiest to understand by their purpose. Movement inputs change position and stance; combat inputs fire, aim or reload; equipment inputs select weapons and grenades; interaction inputs use objects or open supported menus; communication inputs send voice or text messages; and interface inputs operate screens such as the scoreboard or Buy Menu. Some actions work only in a particular context. A buy command, for example, is useful during an allowed purchase period and location, while inspecting an item belongs to an inventory or menu context.
A binding connects an action to an input. Players may use a keyboard and mouse layout, change individual controls, or configure other supported devices. The visible label, available action and default key can depend on the current CS2 build, input device, language layout and personal configuration. That means two players can perform the same action with different keys, and a screenshot of one player’s settings is not proof of the universal default.
A practical setup should let a player reach essential actions without losing control of movement or aim. The player decides which movement keys, weapon slots, grenade actions, communication controls and menu shortcuts feel reliable. A binding cannot make an action legal when the mode or server disallows it, and it does not grant a gameplay ability the player does not otherwise have.
Movement and combat controls
Movement and firing inputs interact because the player’s state can affect weapon precision. A player who wants a controlled shot generally needs to stop before firing; a binding only sends the movement or fire input and does not perform that timing decision automatically. See Movement Inaccuracy, Counter-Strafing and Recoil for the mechanics affected by player input.
Primary fire, alternate fire, reload, weapon selection and weapon drop are separate actions where supported. Alternate fire can have a weapon-specific effect such as aiming through a scope, toggling a silencer or selecting a burst mode. The same input therefore does not imply the same result across every weapon. Weapon pages describe their own firing modes; Weapons is the category for browsing them.
Grenade selection and throw inputs also have distinct roles. Selecting a grenade equips it; holding or releasing an attack input may control the throw, depending on the action and current implementation. Players can practice the sequence in a suitable local session. A binding does not determine the grenade’s trajectory, fuse or effect; those belong to Grenade Throws and the individual grenade pages.
Changing and checking the active setup
The game’s settings interface is the first place to confirm an action and its current key. Check the relevant control before relying on a shortcut, particularly after changing devices, importing a configuration or installing a game update. A player can select an action and assign an input through the supported controls interface; the exact layout and labels may be revised over time.
The Developer Console can expose additional configuration commands in permitted contexts. Commands and multi-action binds have syntax and server rules of their own, so they should be documented separately from the standard controls interface. A command that changes a local practice session may be unavailable or restricted on a public server. Developer Console and Practice Commands cover those boundaries.
When troubleshooting, confirm that the intended action is still bound, check for conflicting inputs and test it in a low-risk local context. If a key performs an unexpected action, the cause may be a changed binding, a context-sensitive menu, a held input or a configuration override. Changing the binding should not be confused with changing the underlying movement, weapon or objective rule.
CS2 version scope
This page covers configurable actions in Counter-Strike 2 and uses dated patch examples only where they establish a specific control feature. It does not reproduce default-key tables from earlier Counter-Strike releases or assume that every historical binding remains available. For an exact current key, use the active CS2 Controls screen and record the game version if publishing a dated setup guide.
Bindings are personal configuration, so this encyclopedia focuses on what actions do and how they relate to match systems. It does not prescribe a single competitive layout. Changes to individual controls belong in Patch Archive and Gameplay Updates when they accompany broader CS2 changes.
Multi-binds, mouse wheel and jump-throw binds (June 6, 2023)
The June 6, 2023 Counter-Strike 2 update fixed a bug that could permanently break input when multiple commands were bound to a single key, restoring multi-binds with an explicit exception for jump-throw binds. Valve described jump-throw execution as a player skill. Commands bound to the mouse wheel were also made to execute reliably. These are input-system and bind-policy notes for the Limited Test; the patch does not give a list of command combinations or define a sanctioned jump-throw technique.
+voicerecord input handling (March 24, 2023)
The March 24, 2023 update corrected handling of input keys such as `+voicerecord` while the Panorama interface had focus. This is a dated input/UI-focus fix; it does not change the voice-chat key assignment or activation policy.
Multi-command bind defaults (August 19, 2024)
On August 19, 2024, Counter-Strike 2 began ignoring input binds by default when a single bind included more than one command from a named input list. The affected group includes movement directions and axes, jump, duck, sprint, attack, alternate attack, reload, use, zoom, turning, looking, and strafe-related commands. The update does not remove those actions from the game; it changes how combined command binds are handled by default.
The patch notes state that support can be re-enabled with the cheat-protected console variable `cl_allow_multi_input_binds 1`. Because this variable is cheat-protected, it is not a general way to restore automation on Valve official servers. The update separately says hardware-assisted movement or shooting automation can trigger a kick on official servers. These are related input-policy changes but distinct behaviors: a local bind restriction and server-side enforcement.