A keybind is not a setting, it is muscle memory with a config file attached. Which is why the right process is boring: bind the things you press under pressure to keys your left hand can reach without leaving WASD, copy the handful of layouts that hundreds of professionals actually agree on, and then change one binding at a time. The data below comes from an analysis of 776 CS2 pro configs, the r/GlobalOffensive configuration wiki, and the r/buildapc hardware wiki — plus an honest note about where public data for VALORANT and Fortnite runs out.
What the pro data actually says
In March 2026 a member of r/GlobalOffensive published an analysis of 776 pro profiles and 784 config files, snapshotted on 3 January 2026. On binds, the findings were narrower than most settings videos suggest:
| Action | What the data shows |
|---|---|
| Drop | The one real standard: 397 drop binds across 29 keys, 335 of them on G |
Inspect weapon (+lookatweapon) |
F is the most common home |
| Ping | Mouse3 is a common home |
| Jump | Mouse wheel is very common; space is also still very common — no winner |
| Push-to-talk | Scattered, no consensus |
| Jump-throw | Scattered, no consensus |
r_cleardecals combo binds |
Present but niche, on keys like F, Shift, Mouse1, W, Tab |
The author's own summary of the bind section is worth keeping: "some actions really do have a standard home" and the rest is preference, habit or practice-server noise. The practical instruction that falls out of it: copy G for drop and F for inspect because that is what everyone you play with expects, and stop treating the rest as a solved problem someone is hiding from you.
Four rules that make a bind stick
Reachable without moving your hand. Your left hand lives on WASD. Everything you press mid-fight has to be reachable from there: Q, E, R, F, G, C, V, B, Shift, Ctrl, Space, and 1-5. A bind on Y is a bind you will not press when it matters.
One key, one job, no overloading under stress. Sharing a key between a movement action and a utility action works fine in the menu and fails the first time you are being pushed. If you need a second layer, put it on a key you never touch while shooting.
Bind the action, not the theory. The reason G-for-drop survived hundreds of configs is that dropping a weapon happens in a two-second window while someone is asking for it. The same logic ranks your own binds: what do you actually do under pressure, in what order?
Change one at a time. A binding is only as good as the reflex attached to it, and reflexes are built by repetition, not by decision. The cost of a rebind is a week of playing slightly worse. Pay it once per change, not five times at once.
CS2: where binds live
The r/GlobalOffensive Advanced Configuration wiki is still the reference for the mechanics. The parts that matter:
- Console first. Enable the developer console in Game Settings, or with
-consolein launch options, then open it with the tilde key. - Put binds in a file, not in the console. Console binds vanish. An
autoexec.cfgin the game'scfgfolder loads automatically in CS2, and everything in it survives updates and re-installs. - Follow the wiki's etiquette. All lowercase; quotation marks around both arguments; necessary commands first, then plain aliases, then
+aliases, then-aliases; and no abbreviations — the wiki's own example is to write+scoregraphrather than+sbng, because in six months you will not remember whatsbngwas.
The wiki also notes the input settings worth checking before you blame a bind: raw input on if your Windows sensitivity is anything other than the middle notch, and mouse acceleration off unless you have deliberately chosen it. If a bind "feels late", check those and your mouse polling rate before rewriting the config.
VALORANT and Fortnite: what is different, and what we cannot verify
Neither Riot nor Epic publishes a machine-readable keybind reference we could retrieve, so this section is deliberately about structure rather than specific default keys — read those off your own settings screen, which is the only source that is guaranteed current for your build.
VALORANT. There is no console and no autoexec: everything is done in the in-game controls menu, and bindings are stored with your account rather than in a file you can copy. Two consequences. First, you cannot script, so every "bind" is literally one key to one action — which makes the reachability rule above the whole game. Second, because abilities occupy Q, E, C and X on top of the movement and weapon keys, the left-hand budget is fuller than in CS2; anything you add has to displace something, so decide what you are giving up before you rebind.
Fortnite. The distinguishing feature is that building and editing have their own binding groups alongside combat, so the same physical key can mean different things depending on what you are doing. That is the thing to plan around: the useful question is not "which key for wall" but "which four keys can my left hand hit in sequence without the hand moving", and then assign the build pieces to those in the order you use them. Everything else is the four rules above.
For both games, the honest summary is that the public, verifiable bind data that exists for CS2 does not exist here. Treat any article giving you "the pro VALORANT keybinds" as one person's preferences unless it names its source.
Your keyboard is part of the binding
This is the failure mode people misdiagnose as a config problem. The r/buildapc peripherals wiki explains key rollover: it is how many keys a board can register at once, 2-key rollover is the minimum most keyboards ship with, and N-key rollover means any number simultaneously. The wiki notes that gamers press multiple keys at once as a matter of course — and that is exactly the situation a bind creates. Hold W and A, add Shift to walk, then press your utility bind: that is four keys, and on a 2KRO board the fourth one is simply not delivered.
The wiki also mentions why PS/2 has not died out despite being much older than USB: it does not have the same rollover problem.
So before you rebuild your config, test the hardware. Our keyboard tester lights up every key as it is pressed and, more usefully, keeps the highlights so you can hold your actual movement combination and see which keys never register. If a combination fails there, no binding will fix it — pick different keys, or a different keyboard.
While you are at it, the reaction time test is a reasonable before-and-after control: if a rebind is genuinely making you faster, it should not make your baseline reaction worse.
Five mistakes
Binding in console and never saving. It works until you restart. Write it into autoexec.cfg the same day.
Copying a streamer's whole config. The 776-config analysis is blunt about this: outside a handful of actions, pros do not agree with each other. Copying one person's binds copies their habits, not a standard.
Rebinding before a match. Never on match day. The week after a rebind is the week you play worse.
Ignoring the hand, optimising the key. The best binding is the one your hand already reaches, not the one that is theoretically two milliseconds faster.
Treating a bind as a fix for aim. If the problem is that you are missing, a keybind will not help. Measure it separately with a mouse test or a reaction test, change one variable, and keep the config out of it.
FAQ
What is the most standard keybind in CS2?
G for drop. In an analysis of 776 pro configs published in March 2026, the author found 397 drop binds spread over 29 different keys, and 335 of them were on G. Nothing else in the dataset is close to that level of agreement.
Should I bind jump to the mouse wheel or to space?
Both are common among pros and the same analysis found no consensus. Wheel jump makes bunny-hopping and jump-throws more forgiving; space is more precise for a single timed jump. Many players keep both bound, which costs nothing.
Where do I put my CS2 binds so they survive?
In autoexec.cfg in the game's cfg folder — CS2 loads it automatically. The r/GlobalOffensive wiki's etiquette for writing them still applies: all lowercase, quotation marks around both arguments, and no abbreviations you will not recognise in a year.
Why do some key combinations stop working while I move?
Key rollover. The r/buildapc wiki explains that 2-key rollover is the minimum most keyboards ship with, meaning the board stops registering keystrokes past a couple of simultaneous presses. Gaming means holding two movement keys plus crouch plus a bind, so this is a real limit rather than a theoretical one.
How many binds should I change at once?
One. A keybind is muscle memory, and muscle memory is what you are actually training when you play. Change one thing, play it for a week, then decide — changing five at once means you cannot tell which one helped.