CS2 Console Commands: The Ones That Still Work in 2026
The CS2 console commands that still work in 2026: how to open the console, FPS and ping, viewmodel, radar, a copy-paste practice config and dead CS:GO commands.
On this page
Key takeaways
- Turn the console on in Settings → Game → Enable Developer Console, then press the ~ key.
- net_graph is gone. Use cl_showfps 1 or the Telemetry menu (Settings → Game → Telemetry) for FPS, ping and packet loss.
- Viewmodel, radar and HUD commands work in normal matches. Practice commands need sv_cheats 1 on your own server.
- Rate, interpolation and many CS:GO graphics commands no longer exist. Old configs full of them do nothing.
- Crosshair commands changed in the September 22, 2026 update — use our crosshair guide instead of old lists.
Most “CS2 console commands” lists online were copied from CS:GO guides. Half of those commands do nothing in Counter-Strike 2 — and after the September 22, 2026 update even the crosshair commands changed. This page keeps only the commands that work right now, grouped by what you actually want to do.
How to open the console
- Open Settings (gear icon) → Game.
- Set Enable Developer Console (~) to Yes.
- Press ~ (the key below Esc) in the menu or in a match. Press it again to close.
- Type a command and press Enter. Start typing a name and the console suggests the rest.
FPS, ping and the end of net_graph
net_graph 1 was the first thing every CS:GO player typed. It does not exist in CS2, and no command brings it back. You have two replacements.
Telemetry menu (best for most players). Settings → Game → Telemetry. You can show frame time and FPS, ping and network problems. Each one can be set to Never, only in poor conditions or Always.
Console counter (fastest). Type cl_showfps 1 for a small FPS number in the corner. Values 2–4 show more detail. cl_showfps 0 hides it again.
| Command | What it does |
|---|---|
cl_showfps 1 |
Simple FPS counter (0 = off) |
cl_hud_telemetry_frametime_show 2 |
Same as the Telemetry FPS setting (0 never, 1 poor conditions, 2 always) |
cl_hud_telemetry_ping_show 2 |
Shows your ping (same 0/1/2 values) |
cl_hud_telemetry_net_misdelivery_show 2 |
Shows packet loss and network problems (0/1/2) |
cq_netgraph 1 |
Small network graph in the top-right corner |
fps_max 0 |
Removes the FPS cap. Use a number such as fps_max 400 to set one |
To keep the FPS counter on every launch, add +cl_showfps 1 to the Steam launch options. The plus sign is required — without it the game ignores the command.
Viewmodel: where your gun sits on screen
These commands only move the weapon model. They do not widen your real field of view — that is fixed in CS2 for everyone.
| Command | Range | What it does |
|---|---|---|
viewmodel_fov |
54 – 68 | Higher = the gun looks smaller and further away |
viewmodel_offset_x |
−2.5 – 2.5 | Moves the gun left or right |
viewmodel_offset_y |
−2 – 2 | Moves the gun closer or further away |
viewmodel_offset_z |
−2 – 2 | Moves the gun down or up |
viewmodel_presetpos |
1, 2, 3 | Presets: Desktop, Couch, Classic |
The setup most pros use — paste the lines one by one, or put them in your autoexec (see below):
viewmodel_fov 68
viewmodel_offset_x 2.5
viewmodel_offset_y 0
viewmodel_offset_z -1.5
Radar and HUD
A zoomed-out radar shows more of the map, so you see where teammates are without checking the big map.
| Command | Range | What it does |
|---|---|---|
cl_radar_scale |
0.25 – 1.0 | Radar zoom. Lower = more of the map visible |
cl_hud_radar_scale |
about 0.8 – 1.3 | Size of the radar box on screen |
cl_radar_always_centered |
0 / 1 | 0 lets the radar show more space around you near walls |
cl_radar_rotate |
0 / 1 | 1 = radar turns with you, 0 = north is always up |
hud_scaling |
0.5 – 0.95 | Size of the whole HUD |
cl_hud_color |
0 – 10 | HUD accent colour |
A good starting point: cl_radar_scale 0.4; cl_hud_radar_scale 1.15; cl_radar_always_centered 0.
Practice commands (your own server)
These need sv_cheats 1 first, so they only work offline or on a server you control. Start an offline map from Play → Practice, open the console and paste the whole block below.
// ClutchHub practice config
sv_cheats 1
bot_kick
mp_limitteams 0
mp_autoteambalance 0
mp_warmup_end
mp_freezetime 0
mp_roundtime 60
mp_roundtime_defuse 60
mp_respawn_on_death_t 1
mp_respawn_on_death_ct 1
mp_buy_anywhere 1
mp_buytime 9999
mp_maxmoney 60000
mp_startmoney 60000
sv_infinite_ammo 1
ammo_grenade_limit_total 5
sv_grenade_trajectory_prac_pipreview 1
sv_grenade_trajectory_prac_trailtime 8
cl_grenadepreview 1
sv_showimpacts 1
sv_showimpacts_time 10
mp_restartgame 1
What the less obvious lines do:
| Command | What it does |
|---|---|
sv_grenade_trajectory_prac_pipreview 1 |
A small camera window follows your grenade to where it lands |
sv_grenade_trajectory_prac_trailtime 8 |
Keeps the flight path on screen for 8 seconds (the maximum) |
cl_grenadepreview 1 |
Shows the arc while you hold the grenade |
ammo_grenade_limit_total 5 |
Carry every grenade type at once (default is 3) |
sv_showimpacts 1 |
Marks where your bullets hit — great for spray practice |
sv_rethrow_last_grenade |
Throws your last grenade again from the same spot |
Old CS:GO commands that no longer work
If you copy a config from an old guide, these lines are dead weight. CS2 either handles them automatically or removed them.
Crosshair commands are a special case: Valve rebuilt the crosshair on September 22, 2026, moved it to its own Crosshair/Scopes tab and changed how sizes work. Old cl_crosshair… lines from earlier guides may give a different result. Our crosshair guide explains the new system and the new share codes.
Save your commands with autoexec
Typing everything again after each launch gets old fast. An autoexec file loads your commands automatically.
- In Steam, right-click Counter-Strike 2 → Manage → Browse local files.
- Open the folder game → csgo → cfg. (Not the
csgo\cfgfolder at the top level — that is the most common mistake.) - Create a text file called autoexec.cfg and put one command per line in it.
- In Steam: right-click CS2 → Properties → Launch options, add
+exec autoexec. - Changed the file while playing? Type
exec autoexecin the console to reload it.
Next step: once your FPS and viewmodel are set, check where you stand in CS2 ranks and Premier rating.
Sources
- Counter-Strike 2 update notes, September 22 – October 2, 2026 (official Steam news)
- How to show FPS in CS2 — setup.gg (updated September 2026)
- FOV and viewmodel commands — setup.gg (checked September 2026)
- CS2 practice commands — GameServerKings
- CS2 console command reference — CSDB
FAQ
How do I open the console in CS2?
Go to Settings → Game and set Enable Developer Console to Yes. Then press the ~ key (below Esc) in the menu or in a match. If it does not open, check which key is assigned to the console in the keyboard settings.
What replaced net_graph in CS2?
The Telemetry section in Settings → Game. It can show frame time and FPS, ping and network problems. From the console you can use cl_showfps 1 for a simple FPS counter or cq_netgraph 1 for a small network graph.
Can console commands get me banned in CS2?
No. Normal client commands (FPS counter, viewmodel, radar, binds) are allowed everywhere. Commands that need sv_cheats 1 only work on your own server or offline, so you cannot use them in matchmaking at all.
Where do I put my autoexec.cfg?
In Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg. Then add +exec autoexec to the launch options in Steam. Note the folder: it is game\csgo\cfg, not just csgo\cfg.
How do I see where my grenade will land?
On your own server type sv_cheats 1, then sv_grenade_trajectory_prac_pipreview 1. A small camera follows the grenade to where it lands. sv_grenade_trajectory_prac_trailtime 8 keeps the flight path visible for eight seconds.