Welcome to the most complete CS2 console commands reference available. I’ve compiled every essential command you need to customize Counter-Strike 2, from crosshair tweaks to performance optimization. These CS2 console commands unlock settings that simply aren’t available through the in-game menus, giving you total control over your experience.
Whether you’re a competitive player looking to optimize your setup or just want to experiment with practice modes, this guide covers everything. I’ve organized commands by category so you can quickly find what you need without scrolling through endless lists. Let’s dive in.
How to Enable the Developer Console in CS2?
Before you can use any CS2 console commands, you need to enable the developer console. Here’s exactly how to do it:
Step 1: Launch CS2 and go to Settings
Step 2: Click on the “Game” tab
Step 3: Find the “Enable Developer Console” option and set it to “Yes”
Step 4: Press the tilde key (~) to open the console (it’s usually next to the 1 key, below Escape)
If the console doesn’t open with the ~ key, check your keyboard language settings. Some keyboards require different keys – the backtick (`) or grave accent key often works as an alternative. You can also bind a different key through the in-game keyboard settings if needed.
CS2 Console Commands Complete List – Understanding Command Syntax (April 2026)
Before jumping into specific commands, it helps to understand what all those prefixes mean. I see this question constantly on Reddit – people typing commands without understanding what sv_, cl_, and mp_ actually do. Let me clear that up.
Command Prefixes Explained:
sv_ – Server variable. These commands affect server-side settings and typically require sv_cheats 1 or admin privileges on private servers. Examples: sv_cheats, sv_grenade_trajectory_prac_pipreview
cl_ – Client variable. These are client-side settings that affect your local game only. They’re safe to use anywhere and don’t require special permissions. Examples: cl_crosshairsize, cl_righthand, cl_hud_color
mp_ – Match/playback variable. These control match settings and work on private servers you host. Examples: mp_roundtime, mp_warmup_end, mp_restartgame
host_ – Host settings. These control the game host behavior when you’re running a server. Examples: host_sleep, host_timescale
Most commands use simple toggle values: 0 means off/disabled, 1 means on/enabled. Some commands accept number ranges (like cl_crosshairsize 1-5) or text values. The console will show you valid options if you type a command incorrectly.
What does sv_cheats 1 mean?
sv_cheats 1 enables cheat commands on private servers. This is required for practice commands like noclip, god mode, and infinite ammo. These commands only work on private servers you host – they will NOT work on official matchmaking servers or community servers with VAC enabled. Using sv_cheats commands in offline practice is completely safe and won’t result in any bans.
Crosshair Customization Commands
Your crosshair is arguably the most important visual element in CS2. These commands let you customize every aspect of its appearance:
| Command | Description | Default/Example Values |
|---|---|---|
| cl_crosshairsize | Controls crosshair thickness | 0-5 (default: 2) |
| cl_crosshairgap | Distance between crosshair lines | -10 to 10 (default: 1) |
| cl_crosshairthickness | Thickness of crosshair lines | 0-3 (default: 0) |
| cl_crosshairstyle | Crosshair display style | 0-5 (default: 1) |
| cl_crosshaircolor | Crosshair color preset | 0-5 (0=red, 1=green, 2=yellow, 3=blue, 4=cyan, 5=custom) |
| cl_crosshaircolor_r | Custom crosshair color (red value) | 0-255 |
| cl_crosshaircolor_g | Custom crosshair color (green value) | 0-255 |
| cl_crosshaircolor_b | Custom crosshair color (blue value) | 0-255 |
| cl_crosshairdot | Enable center dot | 0 (off) or 1 (on) |
| cl_crosshairusealpha | Enable transparency | 0 (off) or 1 (on) |
| cl_crosshairalpha | Transparency level | 0-255 (255 = fully opaque) |
| cl_crosshair_dynamic_splitdist | Dynamic crosshair splitting distance | 0-127 (0 = static crosshair) |
| cl_crosshair_sniper_width | Sniper crosshair width | 1-3 |
Pro tip: Most players prefer static crosshairs for consistent aim. Set cl_crosshair_dynamic_splitdist to 0 for a crosshair that doesn’t expand when moving or shooting.
HUD and Radar Customization Commands
A clean HUD and properly configured radar give you crucial information without clutter. These CS2 console commands let you optimize your interface:
| Command | Description | Default/Example Values |
|---|---|---|
| cl_hud_color | HUD color theme | 0-10 (0=default, 1=white, 2=blue, 3=red, etc.) |
| cl_hud_background_alpha | HUD background transparency | 0-255 (0 = fully transparent) |
| cl_hud_healthammo_style | Health/ammo display style | 0 (classic) or 1 (modern) |
| cl_hud_playercount_pos | Player counter position | 0 (hidden), 1 (top-center), 2 (top-right) |
| cl_hud_bomb_under_radar | Move bomb indicator under radar | 0 (off) or 1 (on) |
| cl_radar_scale | Radar zoom level | 0.25-1.0 (higher = more zoomed out) |
| cl_radar_icon_scale_min | Minimum player icon size on radar | 0.4-1.0 |
| cl_radar_rotate | Radar rotates with player | 0 (fixed north) or 1 (rotates) |
| cl_radar_square | Square radar instead of circular | 0 (circular) or 1 (square) |
| cl_radar_always_centered | Player always centered on radar | 0 (off) or 1 (on) |
Many pros prefer cl_radar_always_centered 0 – this keeps the radar fixed and shows more map area as you move. It takes getting used to but provides better tactical awareness.
Viewmodel and FOV Commands
Your viewmodel determines how your weapon appears on screen. Finding the right viewmodel settings can improve visibility and reduce visual clutter:
| Command | Description | Default/Example Values |
|---|---|---|
| viewmodel_fov | Field of view for viewmodel | 54-68 (default: 60) |
| viewmodel_offset_x | Horizontal position | -2.5 to 2.5 (default: 0) |
| viewmodel_offset_y | Forward/backward position | -2 to 2 (default: 0) |
| viewmodel_offset_z | Vertical position | -2 to 2 (default: 0) |
| viewmodel_presetpos | Quick viewmodel presets | 0-3 (0=desktop, 1=couch, 2=classic, 3=custom) |
| viewmodel_recoil | Viewmodel recoil animation | 0 (off) or 1 (on) |
Popular viewmodel settings: viewmodel_fov 68, viewmodel_offset_x 2.5, viewmodel_offset_y 0, viewmodel_offset_z -1.5. This gives you maximum visibility while keeping the weapon in a natural position.
Bot Management Commands
Bots are essential for practice. These CS2 console commands give you complete control over bot behavior in private servers:
| Command | Description | Default/Example Values |
|---|---|---|
| bot_add | Add a bot to the game | bot_add (adds random team), bot_add_t, bot_add_ct |
| bot_add_t | Add T-side bot | bot_add_t |
| bot_add_ct | Add CT-side bot | bot_add_ct |
| bot_kick | Remove all bots | bot_kick |
| bot_kick | Remove specific bot | bot_kick BotName |
| bot_difficulty | Set bot difficulty | 0 (easy), 1 (medium), 2 (hard), 3 (expert) |
| bot_stop | Bots stop moving | 0 (off) or 1 (on) |
| bot_place | Place bot at crosshair position | bot_place (must be enabled first) |
| bot_dont_shoot | Bots won’t shoot | 0 (off) or 1 (on) |
| bot_freeze | Freeze bots in place | 0 (off) or 1 (on) |
| bot_all_weapons | Bots get all weapons | Requires sv_cheats 1 |
| bot_crouch | Bots crouch only | 0 (off) or 1 (on) |
For aim practice, I recommend bot_difficulty 3 with bot_dont_shoot 1 – this gives you stationary expert bots to practice spray patterns without getting killed.
Gameplay and Practice Commands
These CS2 console commands are perfect for setting up practice scenarios and experimenting with game mechanics. Most require sv_cheats 1:
| Command | Description | Default/Example Values |
|---|---|---|
| sv_cheats 1 | Enable cheat commands (private servers only) | 0 (off) or 1 (on) |
| sv_infinite_ammo 1 | Unlimited ammunition | 0 (off) or 1 (on) |
| sv_grenade_trajectory_prac_pipreview 1 | Show grenade trajectory preview | 0 (off) or 1 (on) |
| mp_warmup_end | End warmup immediately | Server host only |
| mp_restartgame 1 | Restart the match | Server host only |
| mp_roundtime_defuse 60 | Set round time in minutes | 1-60 |
| mp_freezetime 0 | Remove freeze time | 0-60 (default: 15) |
| mp_buytime 9999 | Extend buy time | Seconds (default: 90) |
| mp_buy_anywhere 1 | Buy from anywhere on map | Requires sv_cheats 1 |
| mp_free_armor 1 | Free armor each round | 0 (off) or 1 (on) |
| mp_startmoney 16000 | Set starting money | 0-16000 |
| noclip | Fly through walls (sv_cheats required) | noclip (toggle) |
| god | Invincibility mode (sv_cheats required) | god (toggle) |
| impulse 101 | Give $16,000 (sv_cheats required) | impulse 101 |
| sv_rethrow_last_grenade | Re-throw last grenade for practice | sv_rethrow_last_grenade |
For smoke practice, use sv_cheats 1, sv_grenade_trajectory_prac_pipreview 1, and sv_infinite_ammo 1. This combination lets you throw unlimited grenades with trajectory previews.
Performance and Graphics Commands
If you’re struggling with FPS drops, these CS2 console commands can help optimize performance without sacrificing too much visual quality:
| Command | Description | Default/Example Values |
|---|---|---|
| fps_max 0 | Uncap FPS (0 = unlimited) | 0-300 (default: 300) |
| fps_max_menu | Max FPS in main menu | 0-300 |
| mat_queue_mode 2 | Multi-core rendering | -1 to 2 (2 = multi-core) |
| r_dynamic 0 | Disable dynamic lighting | 0 (off) or 1 (on) |
| r_drawtracers_firstperson 0 | Hide bullet tracers | 0 (off) or 1 (on) |
| r_drawparticles 0 | Reduce particle effects | 0 (off) or 1 (on) |
| r_eyegloss 0 | Disable eye reflections | 0 (off) or 1 (on) |
| r_eyemove 0 | Disable eye movement | 0 (off) or 1 (on) |
| r_shadows 0 | Disable shadows | 0 (off) or 1 (on) |
| r_visualizeproplightculling 1 | Optimize prop lighting | 0 (off) or 1 (on) |
| cl_showfps 1 | Show FPS counter | 0 (off) or 1 (on) |
| cl_showpos 1 | Show position and velocity | 0 (off) or 1 (on) |
Start with fps_max 0 and mat_queue_mode 2 – these are safe optimizations that work on almost all systems. Disable shadows and particles only if you’re desperate for FPS.
Network and Netcode Commands
Network commands can help reduce lag and improve hit registration. These are advanced CS2 console commands – only use them if you understand what they do:
| Command | Description | Default/Example Values |
|---|---|---|
| rate 786432 | Maximum bytes per second | 786432 (recommended) |
| cl_cmdrate 128 | Commands sent to server per second | 64 or 128 (tickrate dependent) |
| cl_updaterate 128 | Updates received from server per second | 64 or 128 (tickrate dependent) |
| cl_interp 0 | Interpolation time (set to 0 for auto) | 0 (recommended) |
| cl_interp_ratio 1 | Interpolation ratio | 1 or 2 (1 = lower latency) |
| cl_lagcompensation 1 | Enable lag compensation | 0 (off) or 1 (on – keep ON) |
| cl_predict 1 | Enable client-side prediction | 0 (off) or 1 (on – keep ON) |
| net_graph 1 | Show network performance graph | 0-1 (shows ping, loss, choke) |
| net_graphproportionalfont 0 | Smaller net_graph font | 0 (small) or 1 (large) |
Warning: Don’t change rate, cl_cmdrate, or cl_updaterate unless you know your server’s tickrate. Using mismatched settings can actually worsen hit registration.
Audio Commands
Sound is crucial in CS2 – these console commands let you fine-tune your audio setup for competitive advantage:
| Command | Description | Default/Example Values |
|---|---|---|
| volume 0.5 | Master volume | 0.0-1.0 |
| snd_musicvolume 0 | Menu music volume | 0.0-1.0 (0 = off) |
| snd_mute_losefocus 0 | Don’t mute when alt-tabbed | 0 (off) or 1 (on) |
| snd_headphone_pan_exponent 2 | Headphone positional audio | 1-4 (higher = more precise) |
| snd_front_headphone_position 45 | Front headphone position | Degrees (default: 45) |
| snd_rear_headphone_position 135 | Rear headphone position | Degrees (default: 135) |
| room_type 0 | Room effect type | 0 (off) for competitive |
| voice_enable 1 | Enable voice chat | 0 (off) or 1 (on) |
| voice_scale 0.5 | Voice chat volume | 0.0-1.0 |
For competitive play, I recommend snd_musicvolume 0 (no distractions) and room_type 0 (clear audio without reverb effects).
Weapon and Equipment Commands 2026
These CS2 console commands affect weapon display and behavior:
| Command | Description | Default/Example Values |
|---|---|---|
| cl_righthand 0 | Switch to left-handed weapon view | 0 (left) or 1 (right) |
| cl_use_opens_buy_menu 1 | E key opens buy menu | 0 (off) or 1 (on) |
| cl_autowepswitch 0 | Disable auto weapon pickup | 0 (off) or 1 (on) |
| cl_showloadout 1 | Show loadout in buy menu | 0 (off) or 1 (on) |
Left-handed players should use cl_righthand 0. Most competitive players also disable cl_autowepswitch to prevent accidentally picking up weapons in clutch situations.
How to Create an autoexec.cfg File in CS2?
Tired of typing commands every time you launch CS2? An autoexec.cfg file automatically loads your preferred settings when the game starts. Here’s how to create one:
Step 1: Open File Explorer and navigate to your CS2 config folder
Windows: Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\
Step 2: Create a new text file and name it autoexec.cfg
Step 3: Open autoexec.cfg with Notepad or your preferred text editor
Step 4: Add your desired commands (one per line)
Step 5: Save the file
Step 6: Launch CS2 and open the console
Step 7: Type exec autoexec.cfg to load your config manually
Step 8: Add -exec autoexec.cfg to your CS2 launch options to auto-load it every time
Here’s an example autoexec.cfg with essential CS2 console commands:
// Crosshair settings
cl_crosshairsize 2
cl_crosshairgap 1
cl_crosshairthickness 0
cl_crosshairstyle 4
cl_crosshaircolor 2
// Viewmodel
viewmodel_fov 68
viewmodel_offset_x 2.5
viewmodel_offset_y 0
viewmodel_offset_z -1.5
// HUD and Radar
cl_hud_color 5
cl_radar_scale 0.4
cl_radar_always_centered 0
// Audio
snd_musicvolume 0
room_type 0
// Performance
fps_max 0
mat_queue_mode 2
cl_showfps 1
// Misc
cl_righthand 0
cl_autowepswitch 0
cl_use_opens_buy_menu 1
If your commands don’t seem to load, check that autoexec.cfg is in the correct folder and that you’ve added -exec autoexec.cfg to your launch options. You can also verify it loaded by typing exec autoexec.cfg in the console – it should show confirmation messages.
FAQs
What does sv_cheats 1 mean?
Does sv_cheats work in CS2?
What is sv_bounce?
What are the most useful CS2 console commands?
Can you get banned for using console commands in CS2?
Are CS2 console commands the same as CS:GO commands?
How do I open the console in CS2?
What does cl_ mean in CS2 console commands?
Conclusion
This CS2 console commands complete list covers everything you need to customize your game, practice efficiently, and optimize performance. Remember that client commands (cl_) are safe to use anywhere, while server commands (sv_) require private servers. Start with the basics – customize your crosshair, optimize your viewmodel, and set up an autoexec.cfg to save your preferences.
Experiment with different settings to find what works best for your playstyle. The console is a powerful tool that gives you access to features most players never discover. Whether you’re practicing smokes with sv_grenade_trajectory_prac_pipreview or fine-tuning your audio for competitive advantage, these CS2 console commands will help you get the most out of the game.
Have questions about specific commands or want to share your favorite autoexec setup? Drop a comment and I’ll help you troubleshoot. Happy fragging.