Skip to content
CS2 crosshair guide

CS2 Crosshair Generator and Code Preview

Import a pro or personal baseline, preview one-variable edits, and export a CS2 share code or console commands.

Last reviewed 2026-07-25
Maintained by the xhair.pro data team · See our data method

A generator works best for controlled edits. Import a real pro or personal code, change one setting, compare the preview, then export a format CS2 can use.

Browser previews speed up selection but cannot reproduce your resolution, scaling, map lighting, muzzle flash, and movement.

Recommended workflow

  1. Import your current main code and save the original.
  2. Choose one goal, such as reducing distant coverage.
  3. Change one setting at a time.
  4. Export a candidate and test it in CS2.
  5. Restore the original if it fails; name and save the new code if it passes.

Adjustment order

  1. Size for silhouette and target coverage.
  2. Gap for empty center space.
  3. Thickness for visibility after the shape is right.
  4. Dot, outline, and color for specific background problems.
  5. Style only when you deliberately want static or dynamic behavior.

Share code or console commands

  • Use a share code for importing, backup, sharing, and moving between computers.
  • Use console commands for cfg files, binds, or direct inspection.

Stop when the center is easy to recover at near, mid, and long range without covering important target information. Stability matters more than tiny visual improvements in the browser.

Open crosshair builder

Build and preview a CS2 crosshair before committing it to your config.

Continue reading

FAQ

Can a generator create a valid CS2 share code?

Use it to preview and export supported settings, then verify the result in game.

Should I start from scratch?

Starting from a real pro or personal code usually gives a better baseline than a blank setup.