Old CS2 Crosshair Code Not Working? Fix It

You paste the crosshair code you have used for four years into CS2, press apply, and nothing happens. The game tells you the code is invalid or old, and that is the entire explanation you get.

Your code is not corrupted and you did not type it wrong. Valve changed the format in September 2026, and every code in the old container stopped working on the same day.

Here is what changed, why there is no way to recover the exact crosshair without knowing your resolution, and how to get yours back in about thirty seconds.

What Valve actually changed

Crosshair codes come in two different containers now, and CS2 only reads one of them.

The old container is the one everybody recognises. CSGO- followed by five groups of five characters. It was introduced in CS:GO and it survived the first three years of CS2 untouched.

The new container starts with CS, has no dashes at all, and runs 44 characters after the prefix. If the code you are holding has dashes in it, the game will refuse it.

The change rolled out across a few updates in late September 2026, and the sources that tracked it do not fully agree on which update broke what. What they all agree on, and what you can verify yourself in ten seconds, is the end state: a code with dashes is rejected, and a dashless code starting with CS is accepted.

Valve shipped no converter of its own, which is the reason this is still catching people out weeks later.

Why the conversion depends on your resolution

This is the part that almost every explanation online skips, and it is the reason a lot of converters give you the wrong crosshair.

In the old format, crosshair length and thickness were not stored in pixels. They were stored as fractions of your screen height, in 480ths. A length of 2 did not mean two pixels, it meant two 480ths of however tall your screen was.

In the new format, those values are plain pixels.

So converting between them is not a lookup, it is a multiplication, and the multiplier is your resolution. The same old code produces different numbers depending on the screen it is destined for.

Take one real code, ZywOo's, and convert it three times. At 1280x960 the length comes out at 4 pixels. At 1920x1080 it is 5. At 2560x1440 it is 6, and the thickness doubles from 1 to 2.

All three are correct. They are the same crosshair, described for three different screens. A converter that does not ask for your resolution is quietly assuming one, and if it guesses wrong your crosshair comes out too big or too small and you spend a week thinking your aim broke.

This also explains something people find strange. If you change resolution in CS2 now, your crosshair stays the same physical size in pixels rather than scaling with the screen. That is the direct consequence of storing pixels instead of fractions, and it is a deliberate change, not a bug.

What the pro codes convert to

Here are five codes that were circulating everywhere before the update, run through the conversion at 1920x1080.

Two things worth noticing in that table.

The numbers get smaller, not bigger. ZywOo's old length of 2 becomes 5 pixels, which sounds like an increase but is not. The old 2 was already about 4.5 pixels on a 1080p screen. The number changed, the crosshair did not.

Negative gaps become small positive ones. A gap of -3.0 in the old format converts to 1. If you have been reading guides that tell you pros run negative gaps and you cannot find a negative number anywhere in your new settings, that is why. The scale moved, not the crosshair.

And a detail that trips up converters: the old format stored colour twice. There was a preset number for the five standard colours, and a separate set of red, green and blue values that only applied if the preset was set to custom. s1mple's old code carries white in the custom fields but uses preset 4, which is cyan. A converter reading the wrong one of those two gives you the right shape in the wrong colour.

How to get your crosshair back

Thirty seconds, four steps.

1. Find your old code. It is in an old config, a Discord message to a friend, or a Steam profile comment. Anything starting with CSGO- still contains every setting you had. The code is not dead, only the container is.

2. Paste it into the converter. Open the CS2 Crosshair Generator and drop the old code into the import field. Set the resolution selector at the top right to the one you actually play on, because the conversion depends on it.

3. Look at the preview before you copy anything. The crosshair appears over a real map screenshot at the size it will be in game. If it does not look like the crosshair you remember, you have the wrong resolution selected, not a broken code.

4. Copy the new code and import it. In CS2 open Settings, then Game, then Crosshair, then Import. Paste and apply.

If the code still will not import, check that you copied the whole thing. The new codes are long and have no dashes to break them up, so it is easy to miss the last few characters when you select by hand.

Or stop converting and just rebuild it

There is an argument for not converting at all, and it is a decent one.

Most players are carrying a crosshair they copied from a pro three years ago and never questioned. It was built for someone else's resolution, someone else's monitor and someone else's eyes, and the only reason it survived is that nobody wanted to retype a share code.

The reset is a free opportunity to fix that. The same generator has every crosshair cvar CS2 reads on one screen, with the preview updating as you drag, so you can build one from scratch in two minutes and actually see what each setting does instead of guessing.

Two things to get right while you are in there, because they matter more than the shape. Make sure the colour contrasts against the maps you play rather than looking nice on a menu, and keep it small enough that it does not cover the head you are aiming at. If you want the reasoning behind both, the crosshair settings guide covers what each cvar actually does.

And the crosshair is only half the job. Where you hold it decides the duel, and there is an exact correct height that comes out of the game's own dimensions rather than anyone's preference. That is in crosshair placement.

Where to go next

While you are resetting one piece of your setup, check the other one that quietly decides every duel. If your sensitivity is higher than your mousepad can physically support, no crosshair will save you. The eDPI Calculator tells you your centimetres per 360 in about ten seconds, and the Sensitivity Converter moves a setting across from another game without changing how far your hand travels.

If you want to see what the players at the very top are doing with their setups, the CS2 Pro Positions tool shows where every player on an HLTV top 50 team actually stands, map by map and round by round.

And for the number that tells you whether any of this is working, what counts as a good ADR explains why headshot percentage moves between ranks while ADR barely does. A crosshair change shows up there first.