How to Change Crosshair in CS2: Settings, Codes & Pro Tips

TL;DR (fast answer)

Settings → Game → Crosshair
Tweak style, size, thickness, gap, color, outline
Click “Share or Import” to paste a crosshair code (they look like CSGO-…)
(Optional) Use the console for precise commands
(Optional) Save everything in an autoexec.cfg so it loads every time

Why your CS2 crosshair matters

Your crosshair is your aiming reference. A good one is visible in all map lighting, small enough for precision, and stable under pressure. You don’t need what a pro uses; you need what you can track instantly on every map and angle.

Tip: Avoid colors that blend with map palettes. On sandy maps (e.g., Dust II, Mirage, Anubis) a yellow crosshair can vanish against walls. Consider green, cyan, white, or custom RGB.

Method 1 — Change crosshair using CS2 Settings (the easy way)

Path:
Settings (gear icon) → Game (tab at top) → Crosshair

What to change (and why):

Style
- Classic Static (4): Doesn’t move; most consistent for aim training and headshots.
- Classic Dynamic (2): Expands when you move/shoot (teaches inaccuracy).
- Classic Hybrid (5): Expands only when shooting (not when moving).
Center Dot: Add/remove a dot (great for tapping at long range).
Size / Thickness: Keep small to medium so targets aren’t obscured.
Gap: Controls the space in the middle; small gaps are common for precision.
Outline & Outline Thickness: A thin black outline keeps the crosshair readable on bright surfaces.
Color: Use preset or custom RGB. Pick something with high contrast across maps.
T-Style: Removes the top arm; improves head visibility on larger crosshairs.
Follow Recoil: On = crosshair follows spray path (good for practice); Off = traditional static look.

Import / Export a crosshair code:

Go to Settings → Game → Crosshair
In the preview, click “Share or Import”
Paste a crosshair code (they typically start with CSGO-) → Import
Use “Share” to copy your code for backup or to share with friends

Method 2 — Change crosshair with console commands (precise & fast)

Enable the console: Settings → Game → Enable Developer Console = Yes → press ~ in-game.

Common commands (paste one per line or chain them with ;):

Style
- cl_crosshairstyle 4 // Classic Static
- cl_crosshairstyle 2 // Classic Dynamic
- cl_crosshairstyle 5 // Classic Hybrid
Shape & visibility
- cl_crosshairsize 2.5 // line length
- cl_crosshairthickness 1 // line/dot thickness
- cl_crosshairgap -2 // inner gap (smaller = tighter)
- cl_crosshair_drawoutline 1 // 0/1 outline
- cl_crosshair_outlinethickness 1 // 0.1–3
- cl_crosshairdot 0 // 0/1 center dot
- cl_crosshair_t 0 // 0/1 remove top arm
- cl_crosshairalpha 255 // transparency (low = faint)
- cl_crosshaircolor 5 // preset colors (0–4) or set custom RGB:
  - cl_crosshaircolor_r 0
  - cl_crosshaircolor_g 255
  - cl_crosshaircolor_b 170
Dynamic behavior (if using style 2 or 5):
cl_crosshair_dynamic_splitdist 7
cl_crosshair_dynamic_splitalpha_innermod 1
cl_crosshair_dynamic_splitalpha_outermod 0.5
Sniper scope line thickness:
cl_crosshair_sniper_width 1
Friendly warning indicator:
cl_crosshair_friendly_warning 1
Follow Recoil (toggle example):
bind alt toggle cl_crosshair_recoil true false

Quick dot crosshair example

cl_crosshairstyle 4; cl_crosshairsize 0; cl_crosshairdot 1; cl_crosshairthickness 1; cl_crosshair_drawoutline 0; cl_crosshaircolor 5

(Change thickness to taste, e.g., 0.8–1.5)

Method 3 — Save your crosshair in an autoexec (so it loads every launch)

Create a text file named autoexec.cfg
Paste your favorite crosshair commands (one per line)
Put it in one of the standard CS2 cfg locations (Windows examples):
- User-specific: …\Steam\userdata\<yourSteamID>\730\local\cfg\
- Game folder: …\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\
In Steam → Library → Counter-Strike 2 → Properties → Launch Options, add:
+exec autoexec.cfg
In-game, you can reload any time with:
exec autoexec

Pro tip: Keep two presets in separate files (e.g., xhair_tap.cfg and xhair_spray.cfg) and bind a toggle:

bind “mouse5” “exec xhair_tap.cfg”

bind “mouse4” “exec xhair_spray.cfg”

Choose a crosshair that fits your aim style

If you mostly tap/burst (AK headshots, pistol duels)

Small static crosshair (style 4), no dot or a tiny dot
Tight gap (–3 to –1), thin (0.5–1.0)
Consider T-Style ON if you run a larger crosshair but want a clear view of heads

If you mostly spray/entry

Static or Hybrid (4 or 5)
Slightly larger gap (–1 to +1) and thicker (1.0–1.5) for tracking
Try Follow Recoil ON for practice, then OFF in matches if it distracts you

If you AWP a lot (but rifle often)

Keep your rifle crosshair small/static
Set cl_crosshair_sniper_width to a comfortable value (1–2)

Make it visible on every map

Avoid colors that match your common backgrounds. Cyan/green/white tend to pop on most maps.
Keep an outline (cl_crosshair_drawoutline 1) to survive bright skyboxes and flash transitions.
Test your crosshair on maps you actually queue (quick sandbox in Deathmatch works great).

While you’re optimizing maps and callouts, grab these for targeted practice:
Mirage • Overpass • Inferno • Dust 2 • Anubis • Nuke • Vertigo
Broader guides: CS2 Maps • CS2 Ranks

Dot crosshair in CS2 (when and how)

Why use it: maximal precision for long-range tapping and AWP hip-precision (pre-scope micro-adjusts).
Downside: can be hard to see in motion and on certain surfaces if too small or low-contrast.

Safe starter dot:

cl_crosshairstyle 4

cl_crosshairsize 0

cl_crosshairdot 1

cl_crosshairthickness 1

cl_crosshair_drawoutline 1

cl_crosshair_outlinethickness 1

cl_crosshaircolor 5 // cyan (or use custom RGB)

If the dot feels too big, try cl_crosshairthickness 0.7–0.9.

Try a pro’s crosshair (then tweak it for you)

Importing a pro’s share code is a great starting point—but always adjust for your monitor, resolution, and comfort. After you experiment, check out our pro settings write-ups for quick imports and full configs:

s1mple CS2 settings • m0NESY • donk • NiKo • ZywOo
ropz • b1t • Stewie2K • FalleN • shroud • kennyS
YEKINDAR • Aleksib • snax • device • jL • d0cc
EliGE • rain • magixx • sh1ro • woxic

Troubleshooting (real fixes to common pain points)

“My crosshair won’t change or keeps resetting.”

Make sure you’re editing the current profile and not a view-only preview.
If using autoexec, confirm the file is in a valid cfg location and add +exec autoexec.cfg to Launch Options.
End your autoexec with host_writeconfig if your settings aren’t sticking after quit.

“My crosshair disappears sometimes.”

Check cl_crosshairalpha (keep it high, like 200–255).
Turn on cl_crosshair_drawoutline 1 (with cl_crosshair_outlinethickness 1).
If using a dot, increase cl_crosshairthickness slightly.

“It’s too big/too small on certain maps.”

Adjust gap and thickness; avoid extremes.
Use T-Style to open headspace if you run thicker lines.
Switch to a higher-contrast color for the maps you play most.

“Should I keep Follow Recoil on?”

Use it to learn recoil and spray control; many competitive players prefer OFF during matches to keep a predictable, static aim point.

Bonus: quick presets you can paste

Clean static (rifling/tapping)

cl_crosshairstyle 4; cl_crosshairsize 2; cl_crosshairthickness 0.9; cl_crosshairgap -2; cl_crosshair_drawoutline 1; cl_crosshair_outlinethickness 1; cl_crosshairdot 0; cl_crosshaircolor 5

Hybrid spray helper (practice)

cl_crosshairstyle 5; cl_crosshairsize 3; cl_crosshairthickness 1.2; cl_crosshairgap -1; cl_crosshair_drawoutline 1; cl_crosshair_outlinethickness 1.2; cl_crosshairdot 0; cl_crosshaircolor 2; cl_crosshair_recoil 1

High-visibility (for dark monitors)

cl_crosshairstyle 4; cl_crosshairsize 3; cl_crosshairthickness 1.3; cl_crosshairgap -1; cl_crosshair_drawoutline 1; cl_crosshair_outlinethickness 1.5; cl_crosshairdot 0; cl_crosshaircolor 1

Pro workflow to iterate faster

Use a crashz’ Crosshair Generator v4 map to try and preview new crosshairs instantly.
Keep two to three saved presets (tap/spray/AWP).
Test in Deathmatch and on the maps you actually queue.
Save your final pick into autoexec.cfg so it’s consistent on every PC.

What are You Looking For?