CS2 key binds and config commands: bind, unbind, toggle, exec, and how CS2 saves your settings
Posted: Tue Oct 20, 2026 2:32 pm
Quick summary
CS2 keeps your key bindings and console settings outside the in-game menus. If a bind stops working after an update, or you want the same setup on a second machine, the commands below are the ones that do the work. Valve publishes them in a single alphabetical table on the Developer Community wiki.
Commands that manage keys
Loading and saving settings
What to expect after an update
Valve's notes on the same page warn that some commands may be removed or hidden by default when the game receives new updates. A bind that works today can therefore disappear after a patch. Re-running the command, or pointing it at a config that still exists, is usually the fix.
Sources
CS2 keeps your key bindings and console settings outside the in-game menus. If a bind stops working after an update, or you want the same setup on a second machine, the commands below are the ones that do the work. Valve publishes them in a single alphabetical table on the Developer Community wiki.
Commands that manage keys
- bind: Bind a key.
- unbind: Unbind a key.
- unbindall: Unbind all keys.
- binddefaults: Bind all keys to their default values.
- bindss: Bind a key for a particular splitscreen player.
- toggle: Toggles specified convar value on and off.
- alias: Alias a command.
Loading and saving settings
- exec: Execute a cfg file.
- execifexists: Execute a cfg file if file exists.
- host_writeconfig: Saves out the user config values.
- writekeybindings: Saves current key bindings to disk.
- cvarlist: Show the list of convars/concommands.
What to expect after an update
Valve's notes on the same page warn that some commands may be removed or hidden by default when the game receives new updates. A bind that works today can therefore disappear after a patch. Re-running the command, or pointing it at a config that still exists, is usually the fix.
Sources