Choose a color you can see against map textures, utility effects, and fast camera movement. Color does not change weapon accuracy or fix unsuitable size and gap settings.
The most common color above describes the available pro records, not the best choice for every display. Current CS2 always stores red, green, blue, and opacity in cl_crosshaircolor_r, _g, _b, and _a; the old preset selector and cl_crosshairalpha belong to historical v1.
Use the current CS format for in-game import. Supported legacy styles 2, 4, and 5 can produce a compatible code for your resolution; dynamic behavior is approximate and original records stay unchanged. See the compatibility and import guide.
| Color | Primary strength | Check first |
|---|---|---|
| Green | Balanced brightness and visual weight | Ancient foliage and green materials |
| Cyan | Strong contrast on many warm and dark areas | Sky, blue materials, and highlights |
| White | Neutral and clear on dark backgrounds | Bright walls, sky, and flash recovery |
| Yellow | Visible on dark backgrounds | Warm Dust2, Mirage, and Anubis areas |
| Custom RGB | Fine control for a specific display | Whether the full RGB values are preserved |
Choose by elimination
- Keep size, gap, and thickness fixed.
- Test your two most-played maps first.
- Check bright walls, dark corners, foliage, smoke edges, and fire.
- Eliminate colors that disappear in a frequent scene.
- Use a full deathmatch to choose between the final two.
Outline can add a boundary for white or very thin crosshairs, but it also adds coverage. Pick the main color first, then compare outline off and on. Current CS2 supports off, full, and half outlines with custom color and opacity, but no separate outline-thickness control; change crosshair thickness separately if necessary.