Best CS2 Binds: Useful Keybind Commands for 2026

Quick Reference

Start with the action that keeps getting in your way, rather than replacing every key at once. These are example assignments to adapt. Do not copy the jump-throw row; it shows the kind of script to avoid.

Typing bind "key" tells you what a key currently does. Check that before replacing it with one of these examples. To assign CS2 keys, either use the console or make the change through the keyboard settings menu.

Grenade and Utility Binds

A direct grenade key equips the grenade. That’s all: you still move, aim and release it yourself. Put smoke on a key you can reach without cycling past the flash or HE when you need it quickly.

bind "z" "slot6"
bind "x" "slot7"
bind "c" "slot8"

bind "v" "slot9"
bind "mouse4" "slot10"

bind "mouse5" "slot8"

Used your only smoke already? The smoke key has nothing left to equip. These slot numbers refer to fixed grenade types, not the order you happen to prefer carrying them in.

Movement Binds

Wheel jump gives you one jump input per notch. Scrolling through several notches gives you more chances to meet the landing timing, but there’s no landing detection in the bind.

bind "mwheeldown" "+jump"
bind "space" "+jump"

The distinction is what happens when your hand stops. Stop the wheel and you stop sending jump inputs. A bunny-hop macro keeps supplying its timed sequence after one press instead, which is among the advantage-producing external macros FACEIT prohibits.

For switching back to the item you just held, use lastinv:

bind "q" "lastinv"

No alias is needed for that. Some longer quickswitch scripts force a knife or do something else on key release. Neither addition is necessary if all you wanted was the item you held before this one.

Buy Binds

You can put armour on F3 and a kit on F4 to avoid reopening the buy menu. Still check what the team is buying before spending. FACEIT permits autobuy configuration; it isn’t treated like a script that performs movement for you.

That AK/M4 command tries both purchases. A T can’t buy the M4 and a CT can’t buy the AK, leaving the valid team purchase to succeed if money, buy time and loadout allow it. Grenade limits still apply too. The semicolon isn’t the forbidden part of a bind; combining protected player actions is.

Make sure the F-key isn’t doing something you still need. On a full-size keyboard, the numpad is another place to put purchases without crowding the keys used during a fight.

Audio and Communication Binds

Decide what you want muted. Turning down incoming voice lets you keep making calls; switching off the voice module is broader than that.

bind "j" "voice_modenable_toggle"

bind "k" "toggle snd_voipvolume 0 1"

bind "l" "voice_toggle_open_mic"

The current incoming-volume setting is snd_voipvolume. If an old guide gives you voice_scale, it’s referring to CS:GO. Don’t confuse either volume setting with voice_modenable_toggle, which changes the voice module.

Practice and Crosshair Binds

Crosshair display toggles are ordinary client settings you can use in public matches. The training tools below aren’t all in that category. Noclip, position readouts and grenade-practice controls need the appropriate permissions in a session you host or are allowed to practise in.

Start a local map before enabling practice permissions. A minimal setup can begin with:

sv_cheats 1
bind "p" "noclip"
sv_grenade_trajectory_prac_pipreview 1

In that setup, noclip is the reason for sv_cheats 1. The grenade preview belongs to the server controls but isn’t itself cheat-flagged. You don’t have authority to turn these training permissions on in Valve matchmaking or an ordinary FACEIT match. A community server’s administrator decides what to allow there.

A separate file for practice-only console commands makes the distinction easier to maintain. Executing it on a competitive server won’t give your account permissions the server hasn’t granted.

Binds That No Longer Work

There are two reasons an old script can fail. CS2 ignores binds containing more than one protected movement or attack action by default. Valve’s Side-stepping Skill policy also prohibits automating multiple player actions from a single input on official servers, where detection may result in a kick.

The protected list covers attack and secondary attack, forward, back, left, right, jump, duck, reload, use and zoom, as well as turning, strafing, looking and related movement axes. Spelling each command correctly won’t help if the problem is the combination.

Jump-Throw and Run-Throw Binds

A jump-throw script supplies both the jump and the grenade release from one key. Add forward movement and you have the running version. These are examples to remove from an official-match config, not copy into one:

bind "alt" "+jump; -attack"
bind "alt" "+forward; +jump; -attack"

To do it manually, prime the grenade, jump, then promptly release attack. Hitting the intended timing produces a grunt that nearby players can hear too. That’s the confirmation to listen for. Valve designed reliable jump throws without a script; the jump and release still come from you.

A running throw adds your own forward movement and a chosen jump point. If an old video used a script, its bind isn’t the part to bring into your config. Practise a manual timing cue for the throw instead.

Null Binds and Input Automation

A null bind can release one direction when you press the other. That release is being supplied by the bind, not your finger lifting off the original key. It automates part of counter-strafing; Valve specifically names null binds in the restriction.

alias "+leftnull" "+left; -right"
alias "-leftnull" "-left"
bind "a" "+leftnull"

Valve says detection may cause a kick. Don’t turn that into a claim that every incident automatically earns a VAC ban. The reverse isn’t true either: getting through a match without a kick doesn’t make the bind valid. Protected combinations remain ignored by default.

The setting cl_allow_multi_input_binds 1 is cheat-protected. It belongs in an appropriate local test, not a workaround for Premier, Competitive, Casual, Wingman, Deathmatch or FACEIT rules.

Keep the parts of your layout you still use. To remove an old script, find its bound key and follow the aliases it calls, then remove those entries specifically.

Save Binds in autoexec.cfg

Saving the layout in an autoexec gives you something to check later. If C stops selecting smoke, there’s a line in a file to inspect instead of a console command you vaguely remember typing.

1. Create a plain-text file named autoexec.cfg. Make sure Windows has not silently added a .txt extension.
2. Place it in ...\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\.
3. Add one bind per line, using quoted key and command strings.
4. Launch CS2 and enter exec autoexec in the developer console.
5. Run key_listboundkeys. Inspect the resulting assignments.

A clean starter file might look like this:

bind "z" "slot6"
bind "x" "slot7"
bind "c" "slot8"
bind "mouse4" "slot10"
bind "mwheeldown" "+jump"
bind "space" "+jump"
bind "q" "lastinv"
bind "j" "voice_modenable_toggle"

Run exec autoexec yourself if loading fails, and read what the console says. A filename error or a bad command may be right there. Steam’s launch options can also include +exec autoexec.cfg. Remember that loading successfully isn’t the end of it: a later command can overwrite the same key.

You don’t have to end the file with host_writeconfig. That command writes configuration state; the autoexec already holds your saved assignments. Keep the custom lines together, and look for conflicts in the menu, Steam Cloud or another CFG if one unexpectedly changes.

key_listboundkeys
bind "f3"
unbind "f3"

That example clears F3 and leaves the other keys alone. Substitute the key you actually want to change, then bind it again if needed. Don’t use unbindall to fix one key: it clears movement and your other controls as well.

Frequently Asked Questions