In this article, we will explain the “unbindall” command in Counter-Strike 2, why you might want to use it, and how to fix the most common issues it can cause.
Why would you like to use “unbindall” command?
You may want to use the unbindall command in Counter-Strike 2 for several practical reasons. For example, if you are sharing a PC and using a single autoexec file for multiple players, loading your own custom config may cause conflicts with existing key binds. Running the CS2 “unbindall” command first allows you to remove all binds from the shared autoexec, ensuring that unwanted or leftover binds are not triggered by accident. The same logic applies when playing on LAN events, where removing key binds left behind by previous players is always a smart first step.
Additionally, the “unbindall” command in CS2 is extremely useful for troubleshooting broken or incorrectly configured binds, helping you quickly reset and start building your setup from scratch.
Overall, this makes the CS2 unbindall command a fast, reliable, and effective solution when you need full control over your key bindings.
Alternative Command to “unbindall” and First Fix
If you accidentally ran the “unbindall” command in Counter-Strike 2, or you don’t mind resetting your key binds to their original state, you should consider using the “binddefaults” command. As the name suggests, this command restores all key binds to CS2 default values.
The CS2 “binddefaults” command is often a better option than resetting settings through the in-game menu, because it resets only key bindings without affecting other important settings such “Mouse Sensitivity” or “Zoom Button Hold” behavior.
In the case, if your custom binds built upon default binds, you might wanna run this command right after “unbindall”. However, we do not recommend rebind defaults, instead create custom binds that you use and not all others and execute them from your binds config.
Main problem with “unbindall” Command
If you haven’t used the “unbindall” command in Counter-Strike 2 yet, you may soon discover its biggest drawback. The moment you run command, the game also unbinds on-server mouse movement, including horizontal (yaw) and vertical (pitch) input. As a result, your mouse stops controlling the crosshair entirely, basically mouse becomes unresponsive.
This issue cannot be fixed through the in-game options menu, as mouse movement bindings are not available there. Without access to the console, your only solution would be to reset all settings to default, which is far from ideal.
Fortunately, if you can use the console, the fix is simple. The input axes for mouse movement are “MOUSE_X” (horizontal) and “MOUSE_Y” (vertical). To restore normal crosshair movement, you need to bind them back to “yaw” and “pitch”, respectively. Doing so immediately reinstates standard mouse behavior.
How We Use “unbindall” in Our Autoexec
Here’s an example of how we use the unbindall command in our Counter-Strike 2 autoexec setup. When the game launches, it automatically executes a file named “autoexec.cfg” from cfg folder, even without being added to the launch options. In our setup, binds and settings are split into separate files, such as “autoexec_binds.cfg” and “autoexec_settings.cfg”, for better organization and easier management.
Once our “autoexec.cfg” runs, it executes the additional config files like “autoexec_binds.cfg”. However, before binding any keys or aliases from “autoexec_binds.cfg”, the autoexec runs the “unbindall” command. This means that every time the game starts, all existing key binds are cleared, and only the binds defined in our config files are applied. Of course, one of the first binds in our “autoexec_binds.cfg” are – “bind ‘MOUSE_X’ ‘yaw'” and “bind ‘MOUSE_Y’ ‘pitch'” – so we don’t lose control over crosshairs movement in-game.
Summary
In this article, we explained the “unbindall” command in Counter-Strike 2, including why it’s useful, its potential drawbacks, and how to fix common issues.
The command is ideal for clearing all key binds, whether you’re sharing a PC, using a single autoexec for multiple players, or troubleshooting broken or conflicting binds.
We also covered the “binddefaults” command as an alternative for restoring default key binds without affecting other settings. Additionally, we highlighted the main problem with “unbindall” command – it unbinds mouse movement (yaw and pitch) – and provided guide how to restore it using console commands.
Finally, we shared our personal autoexec setup, showing how “unbindall” is integrated to ensure clean, consistent, and fully customized key bindings every time the game starts.
