CS2 Pro Crosshair Settings: Data From 1,000+ Pro Profiles
What crosshair CS2 pros actually run - style, color, size, gap, thickness, and dot - aggregated live from cs2pedia's dataset of 1,000+ pro profiles, with denominators disclosed.
Most crosshair guides hand you a list of named pro crosshairs and a share code to paste. This page does the opposite: it aggregates every crosshair parameter across cs2pedia’s dataset of 1,000+ pro profiles and shows you the distribution, so you can benchmark your own crosshair against the field instead of copying one player.
The headline result is convergence - the overwhelming majority of pros who recorded a crosshair run the same style, the same dot setting, and a narrow band of sizes and gaps. There is a “pro default” crosshair, and the data makes it visible.
This is a data reference, not a how-to; if you want the mechanics of changing your crosshair, see the scope note at the end.
One thing up front, because it shapes everything below: cs2pedia stores the individual crosshair parameters per player, not an importable share code. We do not publish “pro crosshair codes,” and you will not find a paste-ready string here. What you get instead is the real distribution of each underlying value.
Crosshair Style Distribution
cl_crosshairstyle controls how the crosshair behaves. The two values that matter in competitive play are Classic Static (style 4 - a fixed crosshair that never moves or expands while you shoot) and Legacy (style 2 - the old CS:GO-era crosshair that expands dynamically with movement and fire).
Static won the argument years ago: a crosshair that stays put gives you a constant reference point for placement, and the dynamic expansion of Legacy just adds visual noise that tells you nothing your spray pattern doesn’t already.
Among the pros who recorded a crosshair style, the result is near-unanimous: a clear, overwhelming majority run Classic Static, and only a small remnant still run Legacy.
Style 4 = Classic Static (fixed). Legacy = dynamic, expands with movement/fire.
If your crosshair still expands when you move or shoot, you are in the small minority and almost certainly should switch. There is no competitive case for dynamic expansion in 2026 - the static crosshair is the field standard for a concrete reason, not fashion.
Crosshair Color
cl_crosshaircolor sets the preset color, with Green (1), Yellow (2), Cyan (4), and a fully custom RGB mode (5) being the common choices. Color is the one genuinely personal crosshair setting - it is purely about contrast against the maps and skyboxes you play, and there is no “correct” answer the way there is for style. The pro field reflects that: it is split, not unanimous.
That said, the data does show a clear preference order. Among pros who recorded a color, Green is the plurality by a wide margin, with Custom RGB and Cyan as the main alternatives.
Green/Yellow/Cyan are presets; Custom is per-channel RGB.
Green wins because it sits in a hue that human eyes resolve sharply and that rarely blends into CS2’s environments - there is very little bright green in the maps. Cyan is the visibility-optimized alternative for players who find green disappears against specific backgrounds (foliage, certain lighting), and Custom RGB exists for anyone who wants to dial an exact value, often a near-cyan or a pink that pops against everything.
Pick the one that stays visible on the maps you actually play; the field’s preference for green is a reasonable default, not a rule.
Size, Gap, and Thickness
These three numbers define the crosshair’s geometry, and this is where “benchmark yourself against the field” is most useful - there is a tight pro band, and being far outside it usually means your crosshair is too big.
cl_crosshairsize- the length of each line in pixels. Smaller is more precise (the center is easier to read against a head-sized target) but harder to find in peripheral vision. The pro field clusters tightly at the low end.cl_crosshairgap- the empty space between the center and where each line starts. Negative values pull the lines inward, tightening the crosshair around the exact aim point. Almost the entire field runs a negative gap.cl_crosshairthickness- how many pixels wide each line is. Thin lines occlude less of the target; the field splits between a 1-pixel line and a near-hairline.
The distributions below are sorted by frequency and capped to the top values; the long tail of one-off custom numbers is omitted. Each is shown against the pros who recorded that specific field.
Line length in pixels. Top values only; the long custom tail is omitted.
Negative values pull the lines inward toward the center. Top values only.
Line width in pixels. Top values only.
The takeaway is the clustering, not any single value. The most common size is a small one, the most common gap is a modest negative pull, and thickness splits between a thin 1-pixel line and an even thinner sub-pixel line.
If your crosshair is large, has a wide positive gap, or runs a fat line, you are well outside the pro band - and the simplest upgrade most players can make is to shrink it until it stops covering the target’s head at common engagement distances.
Crosshair Dot
cl_crosshairdot adds a single pixel-dot at the exact center of the crosshair. The argument for a dot is a precise aim reference for tap-firing and pixel-peeking; the argument against is that it occludes the very target you are trying to see, especially at distance. The field has a strong opinion here.
Among pros who recorded the setting, the large majority run no center dot, with only a small minority enabling it.
No = no center dot. The field overwhelmingly disables it.
The dot earns its keep mainly for two niches: AWP-focused players who want an unambiguous center reference for the scoped-to-unscoped transition, and anyone running a larger crosshair with a wide gap, where the dot replaces the missing center information. For a standard small rifler crosshair, the field’s verdict is to leave it off.
T-Shape and Outline
Two finishing parameters round out the picture, and the dataset is decisive on both.
cl_crosshair_t removes the top line, turning the cross into an inverted “T.” The theory is that the missing top line uncovers a sliver more of the target’s head. In practice the field has rejected it almost entirely - among pros who recorded this setting, essentially all of them keep the full four-line cross and run no T-shape.
No = standard four-line cross (top line kept).
cl_crosshair_drawoutline adds a thin dark border around the crosshair lines so they stay legible against bright surfaces (sky, white walls, smokes). It is a visibility aid, not a precision setting, so it comes down to whether you struggle to see your crosshair on light backgrounds. The field leans heavily toward leaving it off, but a meaningful minority enables it.
Adds a dark border for legibility on bright surfaces.
Outline is the one parameter here where the minority choice is genuinely defensible: if your crosshair vanishes against the skybox on an AWP angle, turning the outline on is a sound fix, and a real slice of the pro field does exactly that. T-shape, by contrast, is a setting almost no one in the data runs - treat it as a curiosity, not an edge.
The Dominant Pro Template
Assemble the most-common value of each parameter and you get the composite “pro default” crosshair. This is the mode of each field stitched together - no single player necessarily runs this exact combination, but every value in it is the field’s plurality choice:
cl_crosshairstyle 4 // Classic Static - fixed, no expansion
cl_crosshaircolor 1 // Green
cl_crosshairsize 1 // small line length
cl_crosshairgap -3 // lines pulled inward
cl_crosshairthickness 1 // thin line
cl_crosshairdot 0 // no center dot
cl_crosshair_t 0 // full four-line cross
cl_crosshair_drawoutline 0 // no outlineTwo honest caveats.
First, this is a per-field aggregate, not a copied crosshair - the modal size and the modal gap come from different overlapping groups of players, so the combination is a statistical center, not any one pro’s setup.
Second, every value here is plurality-among-recorded, and several of these fields (style, color, dot, outline) have a non-trivial slice of profiles that never recorded the setting at all - the distributions above disclose exactly how many.
The template is a strong, defensible starting point precisely because it sits at the center of where the field converges; it is not a claim that any other value is wrong.
How to Import or Customize
cs2pedia stores these as individual parameters, not as a paste-ready share code - the copy_code field is empty across the entire dataset, so there are no importable “pro crosshair codes” on this site, and any guide claiming a one-click pro crosshair import from a dataset like this is overselling.
To see a specific player’s exact parameter values, browse the player profiles, where each pro’s recorded crosshair settings are listed individually. For the aggregate view of these and every other setting, see the stats page.
When you want to actually change your crosshair - whether by hand with the cl_ commands above or via CS2’s built-in share-code system - that is a how-to question, and it lives in our how to change your crosshair in CS2 guide. Scope note: this page is the data (what pros run); that page is the mechanics (how to set yours). They are deliberately separate.
A Note on the Data
These distributions are computed at build time from cs2pedia’s dataset of 1,000+ active pro profiles, the same database that powers the rest of the site - not a hand-typed list that goes stale the moment a player retunes.
Each table states its own denominator: how many profiles recorded that specific field, and what share did not. Crosshair parameters are among the better-recorded fields in the dataset, but they are not complete, and we show you exactly where the gaps are rather than passing a plurality of the recorded subset off as full-field consensus.
The usual freshness caveat applies: pros adjust crosshairs between events, and the dataset is a snapshot rather than a live per-match feed - so read the exact shares as current-but-not-instant. The shape of the result is stable, though: a small, static, dotless, green-ish crosshair is the pro field’s center of gravity, and that has not meaningfully moved across the CS2 era.