Crosshair Code Decoder
See what any share code looks like and every value it sets, before you import it.
When to use the decoder
- Someone shares a code in chat or on Reddit and you want to see it before importing.
- You found a code on a blog and want to check it is real. Fake codes fail the checksum.
- You want the console commands for a code so you can put them in your autoexec.
- You want to tweak a code: decode it, then open it in the generator.
How the code format works
The 25 characters after CSGO- are a base-57 number. Decoding it gives 18 bytes. Byte 0 is a checksum of the other 17, byte 1 is always 1, and bytes 2 to 14 carry the crosshair values in fixed positions: gap, outline thickness, red, green, blue, alpha, split distance plus the recoil flag, fixed gap, colour preset plus outline flag, split alphas, thickness, style plus the dot, weapon-gap, alpha and T flags, and finally size. Decimal values are stored as tenths, so a gap of -3.5 is stored as -35.
Because the preset colours 0 to 4 override the RGB bytes, a code can carry leftover RGB values that are never shown. The decoder resolves the preset first, exactly as the game does.
Decoder FAQ
What is inside a crosshair share code?
A share code is 18 bytes encoded in base-57. The first byte is a checksum. The rest hold all 21 crosshair values: style, size, gap, thickness, outline, RGB colour, alpha, the dot, T-style, weapon-gap, follow-recoil and the dynamic split settings.
Why does my code say checksum mismatch?
A single wrong character breaks the checksum. Check for a copied space, a missing dash, or a confusable letter. Codes never contain the letters I, l, g or the digits 0 and 1. If it still fails, the code was probably typed by hand or invented.
Does the decoder work with CS:GO codes?
Yes. CS2 kept the CS:GO format. The only difference is that CS2 added the follow-recoil flag in a previously unused bit, which decodes as off for older codes.
Does the decoder send my code anywhere?
No. Decoding runs entirely in your browser. Nothing is uploaded.