Old CS2 Crosshair Code Not Working? What Changed in September 2026
Valve changed CS2 crosshairs on 22, 23 and 30 September 2026: pixel units, new console variables and a new share code format. What that means for an old code.
A crosshair code that loaded fine last summer can now fail, or load as a crosshair that looks wrong. The cause is not one change but three, spread over nine days in September 2026, and the third one changed the share code itself.
This guide sticks to what Valve has written down and what the game client itself declares. Where the only source is a third-party site, it says so.
Holding a code? The CS2 Crosshair Code Decoder reads the new
CScodes and the oldCSGO-layout and prints the console variables of the current game, in pixels. The last section says what it converts for an old code and what it leaves out.
Three updates in nine days
| Date | What Valve changed | What it means for a saved crosshair |
|---|---|---|
| 22 Sep | Crosshairs were "updated to be resolution independent". A new Crosshair/Scopes tab, new styles, and a new default, "Dynamic Quad".1 | The settings you tuned now sit in a different tab, with different controls. |
| 23 Sep | Thickness and length "are in pixels". Before, values used "an arbitrary scale" that the game converted to pixels by display resolution. Pixel counts now rescale when the resolution changes.2 | A number saved before this date is not a pixel count, so it cannot be copied across as it is. |
| 30 Sep | "Changed the format of the crosshair share code to accommodate newly included crosshair settings." Outline colour, a "Static Quadrant" style and scope dot scale and colour joined the code.3 | A code exported before this date was written in a different format from one exported after it. |
What Valve has not said
Valve's notes do not say what the game does when you import an old code. None of the three entries covers it, and no later entry up to 11 November mentions share codes again.
What circulates instead comes from third-party sites. One crosshair generator says current codes are 46 characters long, start with CS and have no dashes, and that the game stopped importing the old CSGO-xxxxx format with the 30 September update.4 That fits Valve's note, but it is a report, not documentation, and this article has not tested it in the game.
Valve has published no layout for the new code, and the csgo-sharecode library, the usual reference for the old one, documents only its older formats. Two open-source decoders describe one: cs2-crosshair by setpos.gg, which says it is ported from the game client of 8 October 2026,7 and csxhair, whose tests hold 30 share codes together with the console variables the game wrote for them.8 The layout is 32 bytes: a checksum, a version, the screen height the sizes were set at, the style and flags, the colour and outline colour as RGBA, thickness, gap and length in pixels, and the dynamic-style settings. The decoder on this site reproduces all 30 exports exactly. All 30 were set at 1080p and use the static or classic styles with a thickness of 1 or 2, so treat the layout as reconstructed, not documented. Decoders written for the old format cannot read a code that starts with CS and has no dashes.
Why an old crosshair cannot be copied across number for number
Before 23 September the size, thickness and gap in a code were numbers on an arbitrary scale, turned into pixels by the game using your resolution.2 Now they are pixels, and the client keeps a hidden variable, cl_crosshair_screen_height, described as "the res at which the user authored their size settings at". Its default is 1080.5
So turning an old size into a pixel count needs a screen height to be assumed. Any conversion is an estimate for one screen, and the same old numbers land differently at 1080p and at 1440p. Valve's own example shows the new units: thickness 1, length 8 and gap 4 give "a 1-pixel wide crosshair with a bar length of 8 pixels and a gap of 4 pixels".2
The console commands changed too
Decoders and older guides print lines such as cl_crosshairgap "-1". Here is how those names stand in the CS2 client's own variable list, as of the dump from 11 November 2026.5
| Old line | In the client now |
|---|---|
cl_crosshairsize | Hidden. Bar length is cl_crosshair_length, 0 to 255. |
cl_crosshairthickness | Hidden. Thickness is cl_crosshair_thickness, 0 to 32, minimum 1 pixel. |
cl_crosshairgap | Not defined. The gap is cl_crosshair_gap, from -3840 to 3840. |
cl_crosshairalpha, cl_crosshairusealpha | The first is hidden, the second is not defined. Opacity is the fourth colour channel, cl_crosshaircolor_a, 0 to 255. |
cl_crosshaircolor (preset index) | Not defined. Colour is cl_crosshaircolor_r, _g and _b. |
cl_crosshair_outlinethickness | Not defined. cl_crosshair_drawoutline is 0 for none, 1 for full or 2 for half, and the outline colour is cl_crosshairoutline_r, _g, _b and _a. |
cl_crosshairgap_useweaponvalue, cl_fixedcrosshairgap | Not defined. |
The style number needs the same care. The client now describes cl_crosshairstyle as 0 to 9: 0 Dynamic Cross, 1 Dynamic Circle, 2 Dynamic Cross (Legacy), 3 Static Circle, 4 Static Cross, 5 Static Cross (Shot Feedback), 6 Dot Only, 7 Dynamic Quad, 8 Static Square, 9 Static Quad.5 A style number copied from an old code or an old guide is worth checking in the menu before you trust it.
The dump shows what the client defines, not how it treats the hidden legacy variables. Whether they still feed the crosshair on screen is a question it does not answer. What it does show is that an old block of cl_crosshair* lines no longer lines up with the current names, which is the practical reason pasting one stopped reproducing a crosshair.
Getting a working crosshair back
- Open the Crosshair/Scopes tab in Settings, which Valve added on 22 September.1
- Set length, thickness and gap in pixels for the resolution you play at. Valve's example, thickness 1, length 8, gap 4, is a reasonable first guess for a thin crosshair.2
- If you still have the old code, decode it and read the proportions between bar length, thickness and gap. Enter them in pixels and compare the result with the crosshair you remember.
- Save a fresh share code from the new settings, so the one you keep is in the current format.3
To copy someone else's, Valve's 2020 announcement describes clicking a player to copy their crosshair.6 It does not say whether that works while watching a demo, and this article has not tested it. A code you are handed that starts with CSGO- and fails is worth replacing: ask for one exported after 30 September.
What the decoder does now
The decoder reads both formats. A CS code is decoded into the variables the current client defines: cl_crosshair_gap, cl_crosshair_length and cl_crosshair_thickness in pixels at the screen height stored in the code, the new style number and the outline colour. The block can be pasted into the console.
An old CSGO- code is decoded and converted only where a rule exists. Valve published no formula for old values to pixels. The one measured rule, taken by a third party at 1080p and 960p, covers the Classic Static style, so that is the only style for which the tool prints length, thickness and gap, for a 1080p screen. For every other old style it prints what carries over unchanged and says which lines it left out. Before this change the tool printed 21 lines for an old code, of which 6 named variables that the client no longer defines and 3 more named hidden legacy ones, which is the table above applied to its output. None of those are printed now.
Sources
Every number in this article traces to a source below. Where a claim could not be sourced, it was cut rather than softened.
- Primary sourceValve Corporation
That crosshairs became resolution independent, that a Crosshair/Scopes tab was added to Settings, that new crosshair styles were added, and that the default crosshair became "Dynamic Quad".
- Primary sourceValve Corporation
That crosshair thickness and length are now in pixels where the old values were "an arbitrary scale" converted by display resolution, the worked example of thickness 1, length 8 and gap 4, and that pixel counts rescale when the display resolution changes.
- Primary sourceValve Corporation
That the format of the crosshair share code changed, that scope dot scale and colour joined the code, and that an outline colour option and a "Static Quadrant" style were added.
- ReportingMetabot
That a third-party generator reports current codes as 46 characters starting with CS with no dashes, and reports that CS2 stopped importing the old CSGO-xxxxx format with the 30 September 2026 update. Valve's release notes do not state either.
- Primary sourceSteamTracking (mirror of Valve game files)
Which crosshair console variables the CS2 client defines, which are flagged hidden, the ranges and descriptions of cl_crosshair_length, cl_crosshair_gap, cl_crosshair_thickness and cl_crosshair_screen_height, the 0 to 9 cl_crosshairstyle list, and that cl_crosshairgap is not defined.
- Primary sourceValve Corporation
That crosshair sharing shipped in CS:GO in April 2020 as a spectator copy feature, described only as clicking a player to copy their crosshair.
- Reportingsetpos.gg (open source, MIT)
That the current share code is "CS" followed by 44 characters decoding to 32 bytes, and the byte layout of those bytes. The project says it is ported from the game client of 8 October 2026. Valve has not published this layout.
- ReportingSyberiaK (open source, MIT)
30 current-format share codes with the console variables the game wrote for each, used to check the decoder on this site.
Topics
- CS2
- Crosshair
- Share Codes
- Console Commands
Tools mentioned in this article
- CS2 Crosshair Code Decoder - Decode a CS2 crosshair share code into the cl_crosshair console commands of the current game. Reads the new CS... format and old CSGO- codes.
- CS2 Match Share Code Decoder - Decode a CSGO-xxxxx match share code into its match ID, outcome ID and token, and copy the command that downloads the demo.
- CS2 Sensitivity Converter - Convert mouse sensitivity between CS2, Valorant, Apex and more, with eDPI and cm/360.
- CS2 Voice Comms Calculator - Hear specific players in a CS2 or FACEIT demo - upload it to auto-fill players and get the tv_listen_voice_indices commands.