CS2 Console Commands That Actually Do Something

Ask in any CS2 lobby whether console commands are cheating and you will get three different answers, all of them wrong.

Here is the actual split. There are 144 console commands worth knowing in CS2. 130 of them do not need sv_cheats at all, and the fourteen that do are almost entirely practice and bot commands you would only ever use on your own server.

Your crosshair, your viewmodel, your radar, your audio, your binds and your demo controls are all plain settings. They are the same thing as moving a slider in the menu, except faster and with values the menu will not give you.

Where the 144 actually live

Sorted by category, the list is not shaped the way most guides imply.

Match and rounds is the biggest group at 25 commands. Those are the mp_ settings, round time, freeze time, buy time, start money, warmup. They are what you use to build a practice server, not what you type mid match.

After that it is Practice at 16, HUD and radar at 16, Audio and voice at 15, and Crosshair at 14. Those four are where almost all of the useful day to day stuff is, and none of them require anything special.

Now look at the bottom of the chart. Performance is the smallest category in the entire list, at six commands.

That is worth sitting with, because the internet suggests otherwise. There is an entire industry of FPS boost videos listing twenty or thirty console commands, and the honest count of performance commands that exist and do something is six. Everything else in those lists is either a dead CS:GO command or a setting that has a slider in the menu.

The sv_cheats question, answered properly

Fourteen commands out of 144 are gated behind sv_cheats, which means they only work on a server you control.

Eight of them are practice commands: noclip, god, sv_infinite_ammo, sv_rethrow_last_grenade, give, host_timescale, cl_showpos and sv_regeneration_force_on. Five are bot commands: bot_place, bot_freeze, bot_dont_shoot, bot_crouch and bot_mimic. The fourteenth is cl_drawhud, which hides the interface.

Eight of the eleven categories contain no sv_cheats commands whatsoever.

So the answer to the lobby argument is this. Typing commands into your own console is not cheating and never has been. The commands that could give an advantage are the ones the game refuses to run unless you own the server, which is the whole point of sv_cheats existing.

One thing that trips people up, and it is not about cheats. The mp_ match settings need a server you control too, not because they are dangerous but because they are server settings. Typing mp_roundtime on an official matchmaking server does nothing, because it is not your server to configure.

Three packs instead of typing

Most of the time you do not want one command, you want a working setup. The tool ships three, each one copied in a single click.

The practice server pack gives you infinite ammo, the grenade trajectory preview, bullet impacts, no round end and max money. Paste it once on your own server and you have somewhere to learn lineups.

The FPS and network pack uncaps your frame rate and puts the counter on screen. Two things, both of which work in any match.

The clean HUD and radar pack gives you a bigger, centred, zoomed out radar that does not rotate, with your loadout permanently visible. This is the one most players feel immediately, because the default radar is small and rotating and genuinely harder to read.

Why commands silently fail

If you paste something and nothing happens, it is almost always one of four things.

The command is from CS:GO and no longer exists. CS2 does not reject unknown commands loudly when they come from a config file, so a dead config and a working one look identical. This is the single most common reason a practice setup appears broken, and the specific dead commands are listed in the practice config guide.

You do not own the server. Anything mp_ or sv_ needs your own server, official matchmaking will ignore it.

sv_cheats is off. Those fourteen do nothing until you turn it on, and it resets.

The console is not enabled. Settings, Game, Enable Developer Console, then the tilde key.

Commands typed into the console also last only until you close the game. To keep them, they go in an autoexec file, which is a separate thing worth getting right once.

Where to go next

The full searchable list is in the CS2 Console Commands tool, grouped into the eleven categories above with a plain English explanation of what each one does and a copy button on every line. The commands that need sv_cheats are marked so you know before you paste.

If what you actually want is for your setup to survive a restart, the CS2 Binds Generator builds the whole autoexec for you. You click a key on a visual keyboard, pick what it does, and it writes one file with your binds, sensitivity, crosshair and viewmodel in it. For which binds are still legal after Valve's rule change, the binds guide has the test you can apply to any bind you find anywhere.

For the two settings most worth typing a command for, the CS2 Crosshair Generator and the Viewmodel Generator both give you a preview before you commit, which the console cannot.

And if you are about to go through the whole settings menu anyway, the settings that actually matter is a short list, and most of it is not in the console at all.