This page uses separate editorial thresholds for each generation. Historical v1: length at or below 2.5. Current CS2: arm length at or below 10 pixels at a 720p reference height, or Dot Only thickness at or below 4 pixels. Circles, Static Square, and Static Quadrant are excluded because arm length does not measure their footprint. Gap and color are unrestricted; small does not automatically mean thin or pure dot. These thresholds are browsing rules, not a conversion formula.
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.
Modern settings (CS2)
Current codes only. Dimensions are pixels normalized to a 720px screen height.
- Sample count
- 245
- Median size
- 1.5
- Median gap
- 0.8
- Median thickness
- 1.5
- Static share
- 98%
- Most common color
- Green
Historical settings (v1)
Historical codes only. Dimensions retain their original units and are calculated separately.
- Sample count
- 693
- Median size
- 1
- Median gap
- -4
- Median thickness
- 0.9
- Static share
- 96%
- Most common color
- Custom green
Recorded pro crosshairs
Size and visibility
- Smaller arms preserve more distant target detail.
- Muzzle flash, utility, and fast turns can make the center harder to recover.
- Color, thickness, and outline can restore visibility, but too much weight cancels the low-coverage advantage.
Choose one supported current code near the current-generation medians and another with similar size but different color or thickness. That comparison reveals whether the issue is size or contrast.
Signs it is too small
- You actively search for the crosshair after entering a dark or busy scene.
- Your eyes track the next target but lose the center during a transfer.
- You keep adding thickness and outline until it covers as much as a regular crosshair.
If you keep losing the center, try a slightly larger shape that stays visible.