How to Import a CS2 Crosshair Code

The fastest path is Settings → Crosshair / Scopes → Share or Import. Use the dedicated Crosshair / Scopes tab, paste the complete string beginning with CSGO-, and confirm. Supported current v3 codes are ready for this workflow. Historical v1 codes remain unchanged for reference and may be rejected by the current client; supported legacy static crosshairs can produce a separate compatible code using the steps below. A recent record or a CSGO- 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.

Use a historical static 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 legacy static style 4, select your resolution in CS2 under Game resolution, such as 1920 × 1080. For a custom resolution, enter the game viewport height.
3. Compare the previews, which update automatically, read any warnings, then select Copy compatible code. Both previews use the same game height and display scale.
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. Dynamic and retired legacy styles are not supported for conversion. A converted pro code does not establish that the player uses those settings in the current game.

Do not mix codes and commands

• A CSGO-xxxxx-... string belongs in the share-code window.
• 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 static style 4, use the separate conversion workflow above. Then check for missing characters, spaces, line breaks, copied button text, or truncation. Compare with a known current v3 code; 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.