If your saved crosshair code returns an error, or your autoexec crosshair quietly did nothing after the update, the crosshair system changed under you. Valve replaced the old scale-based crosshair with a pixel-based one in the September 2026 updates, and the share code format changed with it. This post covers what broke, the command names to use now, and how to rebuild the crosshair you had.
What changed
The September 23 update replaced the arbitrary scale with pixels. Valve's note is explicit about the old behaviour: values used to be defined on an arbitrary scale and converted to pixels based on display resolution, so the same value produced different pixel counts at different resolutions. The new settings are pixels. Valve's own example: for a 1 pixel wide crosshair with a bar length of 8 pixels and a gap of 4 pixels, set thickness to 1, length to 8, and gap to 4.
The new system also rescales on its own when the display resolution changes. Valve's example: a crosshair configured at 1280x720 with a thickness of 2 pixels, moved to 2560x1440, rescales the thickness to 4 pixels so it stays proportionally the same.
Why your code stopped working
The September 30 update changed the format of the crosshair share code to accommodate newly included crosshair settings. The same update added a crosshair outline color option and a new crosshair style, and Valve noted that scope dot scale and color preferences are now part of the new share code. Codes saved before that change no longer import, and the game returns "Invalid or old crosshair code". Valve has not published an official converter, so the fan-made ones are the only route back if you want your exact old crosshair rather than a rebuild by eye.
The new command names
- cl_crosshairsize is now cl_crosshair_length, range 0 to 255 pixels.
- cl_crosshairthickness is now cl_crosshair_thickness, range 0 to 31 pixels.
- cl_crosshairgap is now cl_crosshair_gap, range 0 to 128 pixels.
- cl_crosshairalpha is now cl_crosshaircolor_a, range 0 to 255.
- cl_crosshair_style runs 0 to 8, and cl_crosshair_dynamic_spread_limit runs 0 to 255.
The September 30 update allowed negative gaps again for the classic dynamic crosshair style, which is worth knowing if you pulled your lines inward with a negative gap. The September 23 update added a static square style.
Rebuilding your old crosshair
1. Open Settings and go to the Crosshair tab, then set thickness to 1.
2. Set length to 2 to 6 and gap to 0 to 3. Those ranges cover most professional settings.
3. If your old crosshair used a negative gap, Valve's September 30 note allowed negative gaps again for the classic dynamic crosshair style, so that part should carry over.
4. If your old crosshair used a fractional outline thickness, the result will not be identical. The LIS-SKINS guide reports that the 0.5 outline is gone, and you now choose between no outline, a half outline that draws only the top and left portions, or a full one.
5. Paste your old code into a converter such as the cs2-crosshair-migrator to get a starting point, then tune from there.
The console command apply_crosshair_code is still present in the current build dump and applies a code to the current crosshair settings.
Sources