This sheet gives you role‑specific CS2 crosshair codes, explains every important crosshair parameter, and shows how to convert your CS:GO or Valorant sensitivity into a CS2‑ready value that you can keep long‑term.
Use it as a quick reference while configuring a new PC, bootcamp setup, or LAN client. Every code is structured for current CS2 config format and annotated so you understand what you are using, not just pasting commands blindly.
- Crosshair presets for riflers, AWPers, IGLs, and support players.
- Copy‑paste console strings and explanation of each setting.
- Sensitivity conversion examples from CS:GO and Valorant to CS2.
- Quick diagnostic table for common aim and spray problems.
CS2 Crosshair and Sensitivity Basics
Accessing Crosshair Settings
You can configure crosshairs either through the in‑game settings menu or via console commands. For maximum control, this sheet uses console syntax so that presets can be copy‑pasted quickly.
- Open console (enable it in Settings → Game → Enable Developer Console).
- Paste the provided code, then press Enter to apply.
- Save your config or bind a key if you want to swap crosshairs for different roles.
Key Crosshair Parameters
| Command | What It Controls | Typical Range | Notes |
|---|---|---|---|
cl_crosshairsize |
Length of each crosshair line. | 1.5 – 3.5 | Smaller size = more precise but harder to see. |
cl_crosshairgap |
Gap in the center of the crosshair. | -3 – 2 | Negative values pull lines inward; helps for tap‑aim. |
cl_crosshairthickness |
Line thickness. | 0.5 – 2 | Too thick blocks targets; too thin is hard to see. |
cl_crosshairdot |
Adds a central dot (0 = off, 1 = on). | 0 or 1 | Useful for some players who tap‑aim more than they spray. |
cl_crosshair_drawoutline |
Black outline around the crosshair. | 0 or 1 | Outline improves visibility across bright textures. |
cl_crosshaircolor_r/g/b |
RGB color channels. | 0 – 255 | Custom colors (e.g., cyan, lime) stand out well on maps. |
cl_crosshair_t |
Enables T‑shaped crosshair (top bar removed). | 0 or 1 | Helps some players with head‑level focus. |
Role‑Based Crosshair Presets
Values are tuned for clarity and control in CS2 as of the current version. Treat them as strong starting points and adjust in small steps (±0.5 size, ±1 gap) if needed.
Rifler / Entry Fragger
Compact static crosshair with tight gap for precise tapping and reliable spray tracking. Works well for players who take first contact and high‑pace duels.
Console code:
cl_crosshairsize "2"; cl_crosshairgap "-2"; cl_crosshairthickness "0.8";
cl_crosshairdot "0"; cl_crosshair_drawoutline "1"; cl_crosshair_outlinethickness "1";
cl_crosshair_t "0"; cl_crosshaircolor_r "0"; cl_crosshaircolor_g "255"; cl_crosshaircolor_b "170";
AWPer / Primary Sniper
Slightly larger, clearer crosshair with dot for centered pre‑aim when unscoped, while the scope itself still dominates when zoomed.
Console code:
cl_crosshairsize "2"; cl_crosshairgap "-1"; cl_crosshairthickness "1";
cl_crosshairdot "1"; cl_crosshair_drawoutline "1"; cl_crosshair_outlinethickness "1";
cl_crosshair_t "0"; cl_crosshaircolor_r "255"; cl_crosshaircolor_g "255"; cl_crosshaircolor_b "255";
IGL / Support
Slightly larger gap and size for better peripheral view of utility and environment, suitable for players focusing on information and mid‑fight calls.
Console code:
cl_crosshairsize "2.5"; cl_crosshairgap "-1"; cl_crosshairthickness "1";
cl_crosshairdot "0"; cl_crosshair_drawoutline "1"; cl_crosshair_outlinethickness "1";
cl_crosshair_t "0"; cl_crosshaircolor_r "0"; cl_crosshaircolor_g "220"; cl_crosshaircolor_b "255";
Anchor / Site Holder
Very stable, slightly thicker crosshair for holding angles and counter‑strafing rather than wide swinging. Good for players anchoring bombsites.
Console code:
cl_crosshairsize "2"; cl_crosshairgap "-1"; cl_crosshairthickness "1.2";
cl_crosshairdot "0"; cl_crosshair_drawoutline "1"; cl_crosshair_outlinethickness "1";
cl_crosshair_t "0"; cl_crosshaircolor_r "255"; cl_crosshaircolor_g "255"; cl_crosshaircolor_b "0";
Sensitivity Conversion to CS2
From CS:GO to CS2
CS2 inherits most of CS:GO’s sensitivity logic, so in many cases your old value will feel close. However, engine and FOV differences plus new mouse settings mean you should verify rather than blindly copy.
- Start by using the same DPI and sensitivity you used in CS:GO.
- Load a CS2 aim map or offline server and run simple 180° turn tests.
- If 180° flicks overshoot consistently, lower CS2 sens by 0.1–0.2; if short, raise it.
- Once flicks and spray transfer feel natural, lock that value as your new baseline.
From Valorant to CS2
Sensitivities between Valorant and CS2 are not one‑to‑one because of different FOV and internal scaling. A practical way is to preserve your cm/360 by using approximate factors.
Quick starting point (community‑tested):
- CS2 sens ≈ Valorant sens × 3.2 if you keep the same DPI.
- Example: Valorant sens 0.4 → CS2 sens about 1.28.
- Example: Valorant sens 0.5 → CS2 sens about 1.6.
Suggested Sensitivity Ranges by Role
| Role | Suggested Sens Range (400 DPI) | Notes |
|---|---|---|
| Rifler / Entry | 1.5 – 2.2 | Favors faster flicks and wide swings. |
| AWPer | 1.8 – 2.6 | Many AWPers play slightly higher sens for quick repositioning. |
| IGL / Support | 1.4 – 2.0 | Balanced between precision and quick adjustment. |
| Anchor | 1.2 – 1.8 | Lower sens helps with holding tight angles and counter‑strafe sprays. |
Common Crosshair & Sens Problems
| Problem | Symptoms | Likely Cause | Fix |
|---|---|---|---|
| Crosshair feels too big | Blocks heads at longer ranges. | Size and gap values too high. | Lower cl_crosshairsize by 0.5 and gap by 1, then re‑test. |
| Crosshair hard to see | Gets lost against bright textures and flashes. | No outline or low contrast color. | Enable outline and pick a bright cyan, green, or yellow color. |
| Aim feels jittery | Micro corrections wobble around target. | Sensitivity slightly too high. | Reduce sens by 0.1 and repeat headshot only drills. |
| Spray control inconsistent | First 5–7 bullets fine, rest go wild. | Sens too high or no recoil training. | Drop sens slightly and practice full‑mag sprays on a wall pattern. |
| Good in aim maps, bad in matches | Clean tracking offline, messy in full games. | Positioning and crosshair placement, not pure aim. | Review demos focusing on angle choice and pre‑aim spots. |
| Feels different after update | Same number but different feeling. | Mouse settings reset or raw input toggled. | Re‑check DPI software, Windows pointer options, and in‑game raw input. |
Pre‑Match Setup Checklist
- Crosshair preset chosen and saved to config.
- Same DPI and CS2 sensitivity used on all PCs you play on.
- Windows mouse acceleration disabled and raw input enabled in CS2.
- Simple warm‑up: at least 10–15 minutes of headshot‑only bots or aim map plays.
- You have not changed sensitivity in the last few games; you are committing to test it properly.
About GamingStunt
GamingStunt builds high‑signal guides for competitive players: from sensitivity blueprints to map callouts and crosshair presets. Every resource is designed so you can print it or keep it on a second screen and immediately apply it in ranked play.
Official Links
- Tools: https://gamingstunt.com/tools
- Books / Free Resources: https://gamingstunt.com/books
- YouTube: @gamingstunt
- Instagram: @gamingstuntofficial
Version and Disclaimer
All settings and example ranges reflect CS2 as played and documented by the community going into 2026. Individual patches can change subtle behavior, so treat these values as strong defaults and adjust after checking current patch notes and in‑game behavior.
This resource is not affiliated with or endorsed by Valve Corporation. Counter‑Strike and CS2 are trademarks of Valve Corporation. All trademarks belong to their respective owners.
Print or save as PDF with full layout and branding.