Useful CS2 Binds
Binds save seconds every round and cut out the busywork: one key instead of three actions. This guide collects working binds for Counter-Strike 2 - from jumpthrow and instant buys to clearing decals and practice commands. Every command is current for the latest CS2 build on the Source 2 engine and tested in-game.
What a bind is and why you need one
A bind is the assignment of a game command, or a sequence of commands, to a key. Pressing a single button performs an action that would otherwise require opening the console, the buy menu, or several mouse clicks.
In CS2, binds are used for fixed-trajectory grenades (jumpthrow), instant weapon buys, clearing bullet marks and blood, controlling voice and radio, and for training on practice maps. A well-built set of binds makes play faster and more consistent without breaking any rules - all commands are legal and built into the game itself.
The bind command syntax
The basic syntax looks like this: bind "key" "command". The key is given by its internal name (for example f, mouse4, kp_end), and the command is wrapped in quotes.
To run several commands from one key, separate them with a semicolon inside the quotes. Commands with a + prefix (for example +jump) run while the key is held, and the - prefix cancels them on release - this is exactly what complex binds like jumpthrow are built on.
You can check or remove a binding with bind "key" (shows the current value) and unbind "key".
// basic syntax
bind "f" "+lookatweapon"
// several commands via semicolon
bind "h" "+jump; -attack"The jumpthrow bind
Jumpthrow is a bind that jumps and releases the grenade at the same time, giving a perfectly repeatable trajectory for timed smokes and molotovs. In CS2 this bind works through an alias - a named sequence of commands.
Hold LMB to wind up the grenade, then press the assigned key - your character jumps and throws the projectile at the exact same point of the jump. That keeps lineups consistent round after round.
The jumpthrow bind is legal and will not trigger a VAC ban: it only uses standard in-game commands. What is banned are third-party scripts that produce a result impossible by hand (for example auto bunny-hop).
alias "+jumpthrow" "+jump; -attack; -attack2"
alias "-jumpthrow" "-jump"
bind "alt" "+jumpthrow"Weapon buy binds
Buy binds let you grab your loadout for the round with a single press, without opening the buy menu. CS2 uses the buy command with the item's internal name for this.
It is handy to put buys on extra keys or the numeric keypad (kp_*) so they don't interfere with core actions. Several buys can be chained with a semicolon - so one press can grab a rifle, armor and grenades.
buy ak47 and buy m4a1 can sit on the same key: the game buys whichever rifle your side has access to.
| Key | bind command | What it buys |
|---|---|---|
| kp_end | bind "kp_end" "buy vesthelm; buy vest" | Armor and helmet |
| kp_downarrow | bind "kp_downarrow" "buy ak47; buy m4a1" | Main rifle (side-aware) |
| kp_pgdn | bind "kp_pgdn" "buy hegrenade; buy flashbang; buy smokegrenade" | Grenade set |
| kp_home | bind "kp_home" "buy deagle" | Deagle |
| kp_uparrow | bind "kp_uparrow" "buy defuser" | Defuse kit |
Clearing decals (r_cleardecals)
Bullet marks, blood and soot (decals) build up on walls and can make it harder to spot an enemy. The r_cleardecals command wipes them instantly.
It is most often bound to the movement keys so decals clear automatically as you play. That way you always keep a clean image without a separate press.
// clear on a dedicated key
bind "x" "r_cleardecals"
// auto-clear on movement
bind "w" "+forward; r_cleardecals"
bind "a" "+left; r_cleardecals"
bind "s" "+back; r_cleardecals"
bind "d" "+right; r_cleardecals"Dropping the bomb, voice and radio
A fast bomb drop saves clutches: the drop command throws your active item, so it helps to select the C4 first and then drop it to a teammate. It is cleaner to make a dedicated bind that switches to the bomb, drops it, and returns to your weapon.
Voice chat works on a held key through +voicerecord by default. Radio commands and quick messages are bound to separate keys so you can talk to your team without a menu.
// drop the bomb to a teammate
bind "l" "use weapon_c4; drop"
// voice on a held key
bind "v" "+voicerecord"
// radio and quick commands
bind "z" "radio1"
bind "c" "radio2"
bind "t" "player_ping"Showing team equipment and quick switch
The +cl_show_team_equipment command shows each teammate's weapon and whether they have grenades/armor while the key is held. This helps you quickly read the team's strength before a push.
Quick switch to the knife and back speeds up weapon changes and is used for fast swaps. In CS2 this is done through lastinv or by selecting slots directly.
// show teammates' equipment (held key)
bind "b" "+cl_show_team_equipment"
// quick switch to knife and back
bind "q" "lastinv"
// quick switch via slots
bind "mouse5" "slot3; slot1"Practice binds for training
On a private server with sv_cheats 1 it is handy to bind training tools: infinite ammo, instant grenade respawn, teleport to a spot, and trajectory display.
These commands only work on a server with cheats enabled (practice maps, local server) and have no effect on matchmaking. They cannot be used on official servers.
// requires sv_cheats 1 (practice server)
bind "o" "sv_rethrow_last_grenade"
bind "p" "noclip"
bind "k" "god"
bind "j" "give weapon_hegrenade; give weapon_flashbang; give weapon_smokegrenade"
bind "u" "sv_showimpacts 1"Where to store binds - autoexec
So binds don't reset and apply on every launch, they are stored in an autoexec.cfg file. Create a text file with that name in the CS2 config folder and write all your bind commands into it.
The path is usually: ...\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\autoexec.cfg. In modern CS2 builds autoexec.cfg is most often picked up automatically; if not, add the line host_writeconfig at the end of the file and set the game to run it via the +exec autoexec.cfg launch option in the Steam game properties.
This way your whole set of binds and settings moves between PCs as a single file and isn't lost after updates.
Keep a backup of autoexec.cfg - major CS2 updates sometimes reset user configs.
// example autoexec.cfg
bind "alt" "+jumpthrow"
bind "x" "r_cleardecals"
bind "b" "+cl_show_team_equipment"
host_writeconfig