CS2 Crosshair Command Guide and Troubleshooting
A practical workflow for using CS2 crosshair commands, with common syntax, visibility checks, and fixes for commands that do not seem to apply.
Enable the CS2 Developer Console
Valve's Steam Support instructions for Counter-Strike 2 are:
- Open CS2.
- Click the gear icon in the main menu.
- Open the Game tab.
- Find Enable Developer Console (~).
- Set it to Yes.
- Press the
~key to open the console.
If your keyboard layout uses a different key for the console, check the current key binding in the game settings. The label can vary with language and keyboard layout.
Paste a Complete Crosshair Command
Start with one complete preset instead of changing several unrelated values:
cl_crosshairstyle 4; cl_crosshairsize 2; cl_crosshairthickness 1; cl_crosshairgap -2; cl_crosshaircolor 1; cl_crosshairdot 0; cl_crosshair_drawoutline 1; cl_crosshair_outlinethickness 1; cl_crosshairusealpha 1; cl_crosshairalpha 255
The semicolons separate commands. After pasting, press Enter and check the crosshair in the current preview or a practice environment.
Tune One Command at a Time
Use a single command when you want to isolate a change:
cl_crosshairsize 1.5
cl_crosshairgap -3
cl_crosshairthickness 0.5
cl_crosshairdot 1
Make one change, test it, and record the value before changing the next setting. This makes it easier to undo a bad adjustment and understand which command changed the shape.
Common CS2 Crosshair Command Problems
The Console Does Not Open
- Confirm Enable Developer Console (~) is set to Yes.
- Try the key assigned to the developer console for your keyboard layout.
- Check the current key binding instead of assuming the US keyboard key applies.
The Whole Line Does Nothing
- Confirm you pressed Enter after pasting.
- Check that commands are separated with semicolons.
- Paste a short test such as
cl_crosshairsize 2. - Paste the command without smart quotes or extra formatting.
One Setting Has No Visible Effect
Check whether the active style uses that property. A style change, dot, dynamic behavior, or outline can make a value appear different from what you expect. Compare the current Crosshair/Scopes preview and test on a real map background.
The Crosshair Looks Different From a Screenshot
Check:
- Style.
- Resolution and aspect ratio.
- Color and alpha.
- Outline and thickness.
- Dot and gap.
- Whether the screenshot was taken before the September 22, 2026 crosshair update.
The update changed the settings system and added new styles. An imported code can be valid even when an old screenshot is no longer a perfect visual match.
When to Use the Settings Menu Instead
Use the Crosshair/Scopes menu when you want a visual preview, a share-code import, or a clear backup of the final setup. Use the console when you want to compare one command at a time or rebuild a preset manually.
The practical workflow is:
- Start with a complete command preset.
- Tune one value in the console.
- Verify the result in the current game menu.
- Test it at your actual resolution.
- Save both the share code and command values.
Command Reference
For the full parameter list, see CS2 Crosshair Commands. For the menu-based workflow, see How to Change Your CS2 Crosshair.