How to Import a CS2 Crosshair Code

Open Settings → Crosshair / Scopes → Share or Import, paste the complete current CS share code, and confirm. This format starts with CS followed by 44 characters.

The website can read supported CSGO- pixel codes (v3) and produces a current CS code when copying or editing. Historical v1 codes use the resolution-based conversion workflow below; original records stay unchanged. A recent recording date or a valid prefix alone does not establish compatibility.

A share code replaces several crosshair settings at once. It does not change sensitivity or viewmodel, but it does overwrite the current crosshair, so save the old code before importing anything new.

Back up before importing

1. Open Share or Import in the crosshair settings.
2. Copy your current share code.
3. Save it in a note or your own collection.
4. Import the candidate code only after the backup is safe.

Restore the backup exported by your current client if needed. Do not rely on an untested historical code as your only restore point.

Import step by step

1. Click Copy beside the crosshair on xhair.pro. Historical codes open a dialog; follow the steps below to select your resolution and copy a compatible code. Current codes copy directly.
2. Open Settings → Crosshair / Scopes.
3. Select Share or Import beside the preview.
4. Paste and confirm.
5. Check that the settings preview changed.
6. Test in a practice map or deathmatch.

Convert a legacy crosshair

1. Click Copy on a player page or in a crosshair list. If you only have the code, paste it into the crosshair generator, load it, and click Copy crosshair code.
2. For supported legacy Classic Dynamic (2), Static Cross (4), or Shot Feedback (5), select your CS2 resolution under Game resolution, such as 1920 × 1080. For a custom resolution, enter the game viewport height.
3. Check the compatible preview as it updates with your resolution, read any Compatibility notes, then select Copy compatible code. The preview is stationary; test dynamic behavior in game.
4. Import that new code through Crosshair / Scopes and test it in game. If you change your game resolution, click Copy again and select the new resolution.

The original code and historical record stay unchanged. The new code approximates the stationary appearance at the selected height; conversion is not always lossless. Outline width, overlapping arms, opacity, weapon-dependent gaps, and pixel alignment can differ. Classic dynamic and shot-feedback styles can be converted approximately; retired legacy styles are not supported. A converted pro code does not establish that the player uses those settings in the current game.

Do not mix codes and commands

• A current CS… share code belongs in the in-game share-code window.
• Load a CSGO-… original on the website first, then copy its current CS derivative for in-game import.
• A command such as cl_crosshair_length 8 belongs in the developer console or a cfg file.
• A block of console commands is not a share code even when every line controls the crosshair.

If import fails

Check the compatibility status first: an intact historical code may still be rejected. For supported legacy styles 2, 4, and 5, use the separate conversion workflow above. Then check for missing characters, spaces, line breaks, copied button text, or truncation. Compare with a CS code exported by the current game; keep unsupported originals without guessing a replacement.

After a successful import, test distant heads, bright walls, dark corners, and close transfers before making it a permanent setup.