CS2 Tips: Quick Fixes and Console Commands

Short, fast, useful. These tips solve one problem each, usually in under a minute. Most use the developer console, so turn it on first: Settings, Game, Enable Developer Console, then press the tilde key.

Must-know console commands

How to open the console

1. Settings, Game, Enable Developer Console: Yes.
2. Press the tilde key (top left of keyboard).
3. Type a command and press Enter.

Tips by category

Practice

• Practice config
• Infinite money
• Stop bots shooting
• Headshot-only mode

Settings and HUD

• HUD color
• Hide the HUD
• Show FPS

Binds and utility

• Remove a bind
• Jump-throw

Ranks

• Check your rank

Why small tweaks matter

None of these tips will make you a pro overnight. But each one removes a small annoyance or makes practice faster. Over time, faster, smoother practice adds up to real improvement.

For bigger improvements, check our guides and lessons.

Why tips matter more than you think

Small things add up. Shaving a few seconds off every practice session, seeing your FPS so you can fix a stutter, having your binds set up so you never fumble a grenade: none of these alone will make you a pro. But together, they remove friction from your game so you can spend your time on what actually improves you. Think of this page as your CS2 toolbox.

Setting up the developer console properly

Almost every tip here uses the console, so let's make sure it's set up right.

1. Open Settings, then Game.
2. Set "Enable Developer Console" to Yes.
3. Close settings and press the tilde key (the key above Tab, left of 1).
4. The console opens. Type a command and press Enter.

If tilde doesn't open it on your keyboard layout, go to Settings, Keyboard/Mouse, find "Toggle Console" and bind it to another key.

Console tips

• Press the up arrow to repeat recent commands.
• Type part of a command and use the suggestions that appear.
• Separate multiple commands with semicolons to run them all at once.
• Commands that need sv_cheats 1 only work in private matches you host.

Essential commands by category

Practice commands

Bot commands

Display and performance commands

Radar commands

Viewmodel commands

Setting up an autoexec file

An autoexec is a config file that runs every time CS2 starts. It's the best way to make sure your settings, binds and preferences never get lost.

1. Go to your CS2 cfg folder (inside Steam, steamapps, common, Counter-Strike Global Offensive, game, csgo, cfg).
2. Create a new text file called autoexec.cfg.
3. Add your commands, one per line. For example, your crosshair, radar settings, binds and fps_max.
4. At the end, add host_writeconfig to save.
5. In Steam, right-click CS2, Properties, Launch Options, and add +exec autoexec.

Now every launch loads your setup, even after updates or a reinstall.

A starter autoexec

Tips for faster practice sessions

1. Save configs for each type of practice. exec aim, exec nades, exec spray.
2. Use rethrow for lineups. Watch your smoke land from the target area.
3. Place bots for prefire. Recreate real angles on your map.
4. Keep sessions short and focused. 15 minutes on one skill beats an hour of random play.
5. Warm up right before you queue. The effect fades if you practice hours earlier.

Quality-of-life tips

• Clear decals: bind r_cleardecals to your walk key to remove blood and bullet marks that can hide enemies.
• Quick switch: turn on quick weapon switching in settings for faster swaps.
• Show loadout: keep your weapons visible on the HUD.
• Mute toxic players: use the scoreboard to mute players who tilt you.
• Bind drop for teammates: helps you share weapons quickly on buy rounds.

Troubleshooting common problems

Safety reminder

Only use commands and configs from sources you trust. Never download random executable files claiming to be "configs," and never run anything that asks for your Steam login. Real CS2 configs are plain text files.

More tips coming

We add new tips regularly. Have a question we haven't answered? Let us know through our contact page.

What each tip covers

Change HUD color

How to pick a HUD color in settings or with cl_hud_color, what each value looks like, and the recommended competitive HUD setup including scale and radar. Plus radar commands that let you see more of the map and common HUD mistakes.

Headshot-only mode

How to enable mp_damage_headshot_only in a private match, extra practice commands, headshot-only drills from beginner to expert, and how to combine it with crosshair placement training on your main map.

Remove a bind

How to unbind keys from the console or settings, reset all binds, back up your config, the binds most players should have, and how to fix common bind problems.

Stop bots shooting

The bot_dont_shoot command plus full bot practice setups for aim training, prefire routes, moving targets and mimic mode. Includes bot difficulty settings and a 10-minute bot warm-up.

Show FPS

Three ways to show FPS, what average FPS, 1% lows and frame time mean, how to use the performance graph, how to cap FPS and how to tell whether your CPU or GPU is the bottleneck.

Jump-throw

Why CS2 made jump throws consistent without a bind, every throw type and when to use it, a jump-throw practice drill and common mistakes.

Infinite money

The commands for unlimited money in private matches, buy-anywhere settings, what to practice with unlimited cash and troubleshooting.

Hide the HUD

How to hide the HUD, weapon and crosshair for clean screenshots and clips, skin showcase tips, viewmodel tweaks and a toggle bind.

Check your rank

Where to find your Premier rating and Competitive map ranks, what each rating color means, why your rank might be hidden and how to track progress.

Practice config

A full copy-paste practice config, what each command does, how to save it as a file, extra commands like sv_rethrow_last_grenade and ready-made session templates.

The 10 tips every CS2 player should know

If you're short on time, these are the highest-value quick wins:

1. Set up a practice config. Saves time every session.
2. Use grenade trajectory preview. Learn lineups faster.
3. Zoom out your radar. See more of the map at a glance.
4. Show FPS while tuning settings. Know what helps.
5. Bind push-to-talk to a mouse button. Talk without stopping movement.
6. Bind drop. Help teammates on buy rounds.
7. Clear decals on your walk key. Fewer visual distractions.
8. Headshot-only warm-ups. Better crosshair placement.
9. Use an autoexec. Never lose your settings.
10. Mute toxic players. Protect your mindset.

Tips by player type

How we test these tips

Every command on this page is tested in a private match on the current version of CS2. Valve sometimes renames or removes commands in updates. If something doesn't work, let us know through our contact page and we'll update it.

Launch options that still matter in CS2

Launch options are set in Steam: right-click CS2, Properties, General, Launch Options. Many old CS:GO launch options do nothing in CS2, and some can cause problems. Keep it simple.

If you have a long list of old launch options from CS:GO, clear them out and start fresh with just -novid and +exec autoexec.

Useful binds for everyday play

These binds make common actions faster. Add them to your autoexec or type them in the console:

Grenade slot numbers can change between updates. If a bind pulls out the wrong grenade, check the current slot numbers in the console.

Practice routines you can build from these tips

15-minute warm-up

1. Run your practice config.
2. Add bots, freeze them and turn off shooting (guide).
3. Five minutes of headshot-only one-taps.
4. Five minutes of spray control with sv_showimpacts 1.
5. Five minutes of community deathmatch.

15-minute lineup session

1. Run your practice config with infinite money.
2. Learn two new smokes with jump throws where needed.
3. Use sv_rethrow_last_grenade to check each landing.
4. Practice one post-plant molotov per site.

Settings tune-up

1. Show FPS and play one deathmatch.
2. Adjust video settings based on your 1% lows.
3. Tweak your HUD color and radar.
4. Save everything in an autoexec.

Myths about console commands

Tips FAQ

Do console commands work in Premier or matchmaking?

Display and preference commands like cl_showfps, cl_hud_color, radar settings and binds work everywhere. Practice commands that need sv_cheats 1, like infinite ammo, noclip or grenade trajectory preview, only work in private matches or servers where you have admin rights.

Can using console commands get me VAC banned?

No. Console commands are part of the game. VAC bans are for cheating software. Practice commands in your own private match are completely safe.

Where are my CS2 config files?

In your Steam folder: steamapps, common, Counter-Strike Global Offensive, game, csgo, cfg for custom configs like autoexec. Your personal settings are also saved in your Steam userdata folder and Steam Cloud.

What's the most useful single tip on this page?

Set up an autoexec with your crosshair, binds and radar settings. It saves your setup permanently and makes moving to a new PC take seconds.

How do I reset everything if I break my settings?

Remove your custom launch options, rename your autoexec so it doesn't run, and use the "reset to defaults" options in each settings tab. Then rebuild your setup one step at a time.

Will these tips work after CS2 updates?

Most will. Valve occasionally changes or removes commands. We test and update this page after major patches.

Our favorite tip combo

If we had to pick one combination for any player, it's this: an autoexec with your crosshair, radar and binds, plus a practice config you run before every session. Ten minutes of setup, and every practice session after that starts instantly and every match starts with your exact setup. It's the closest thing to a free upgrade CS2 has.