CS2 Console Commands

CS2 console commands are useful because they let you tune parts of the game quickly and precisely. The problem is that most command lists online are bloated, outdated, or packed with things players do not actually need.

A smaller list is usually better.

First: Enable the Console

Before using console commands, enable the developer console in the game settings.

After that, you can open it and type commands directly.

Useful CS2 Console Commands

Here are some of the most practical ones for everyday setup work:

fps_max 0
sensitivity 1.00
viewmodel_fov 68
viewmodel_offset_x 2.5
viewmodel_offset_y 2
viewmodel_offset_z -2
cl_hud_radar_scale 1.0
cl_radar_always_centered 0
cl_radar_rotate 1
cl_radar_scale 0.4
volume 0.5

What they help with:

• fps_max 0 removes the default cap
• sensitivity changes your in-game mouse sensitivity
• viewmodel commands clean up weapon position
• radar commands improve map awareness
• volume lets you tune game sound quickly

Binds Are One of the Best Uses of the Console

Console becomes especially useful when you want custom binds.

Example structure:

bind "mouse4" "slot7"
bind "mouse5" "slot8"
bind "n" "noclip"

The exact bind matters less than the principle: put important actions where they are easy to reach without breaking movement.

If you use jump, utility, or inspect binds often, the console is the fastest way to keep them clean.

Radar Commands Worth Knowing

If your minimap feels cramped or unhelpful, the radar commands are some of the highest-value setup changes in CS2.

Core ones:

• cl_hud_radar_scale
• cl_radar_always_centered
• cl_radar_rotate
• cl_radar_scale

For the full explanation, see CS2 Radar Settings.

Viewmodel Commands Worth Knowing

If the weapon model feels too bulky or distracting, the viewmodel commands are another easy win:

• viewmodel_fov
• viewmodel_offset_x
• viewmodel_offset_y
• viewmodel_offset_z

Related: CS2 Viewmodel Settings.

Do Not Treat Commands Like Magic

Console commands are useful, but they do not replace:

• good video settings
• solid crosshair placement
• better movement and accuracy

Many players bury themselves in config tweaks to avoid working on real habits.

Be Careful With Old Lists

A lot of old CS:GO config guides still circulate under CS2 titles. Some commands are harmless but unnecessary. Others are outdated. Others solve problems you do not actually have.

That is why it is smarter to keep a short personal list of commands you understand instead of copying 200 lines from someone else's autoexec.

Takeaway

The best CS2 console commands are the ones you actually use: sensitivity, viewmodel, radar, FPS cap, volume, and a few smart binds. Keep your list tight, understand what each line does, and avoid turning the console into a superstition dump.