How to Import & Export Crosshair Codes Between Any Game

Why Crosshair Codes Aren't Universal Between Engines

A crosshair code is just a compact, encoded list of every visual parameter — color, size, thickness, gap, outline, opacity, and a few game-specific extras — packed into a single string so it can be shared and reproduced exactly. The problem is that every game defines its own list of parameters, in its own order, using its own format, because each one was built independently by a different studio for a different engine. Valorant's crosshair code is a semicolon-delimited string unique to Riot's UI (for example, a real pro code looks like 0;s;1;P;c;1;h;0;0l;4;0o;1;0a;1;0f;0;1b;0). CS2 instead generates its own share code through Valve's "Share or Copy Crosshair Code" button in the Crosshair settings tab, or the same result can be built manually from individual cl_crosshairstyle, cl_crosshaircolor, cl_crosshairsize, and related console commands. Marvel Rivals, since Season 9.5, has its own separate reticle-code system entirely, imported through a completely different menu path.

Pasting a Valorant code into CS2's import field (or vice versa) will simply fail or produce garbage output, because the two games aren't reading the same schema — there's no shared standard the way there is for, say, image or video file formats. This is also why a "convert this code to another game" request doesn't have a real answer: the visual result (a small cyan dot with a slight gap, for example) can be manually recreated in any game, but the code string itself only ever works in the one game it was generated for.

Step-by-Step: Generate, Copy, Import

The process is the same shape in every game, even though the exact menu differs:

1. Generate the code. Build your crosshair with a live preview using the DCPROSENS crosshair generator (Valorant and CS2), or find a verified code in the pro crosshair database for Valorant, or your target game's own settings menu for games without an external generator.
2. Copy the code exactly. Use the provided copy button rather than manually highlighting and copying the text — manual selection is the most common source of a dropped leading character or an accidentally included space, both of which will make the import fail silently or produce a slightly wrong result.
3. Open the correct menu in the target game. In Valorant, go to Settings → Crosshair → and use the Profile Code import field near the bottom of the panel. In CS2, go to Settings → Game → Crosshair → Share or Import, paste the code, and click Import — or paste individual cl_crosshair* console commands directly into the developer console if you're working from commands rather than a share code. In Marvel Rivals, go to Settings → Keyboard tab → select the Combat option → scroll to the HUD section → find the Reticle Save Option → click Import Reticle → paste your code and confirm. Marvel Rivals also lets you set crosshairs per-hero: click the All Heroes button in the top-left of the combat settings screen, select a specific hero, and the crosshair you import from that point only applies to them.
4. Confirm the result. Most games update the live preview or the in-game crosshair immediately once a valid code is applied — if nothing changes, the import failed rather than silently applied.

One CS2-specific shortcut worth knowing: during a live match, typing cl_crosshair_copy [player_index] in the console instantly copies that specific player's crosshair settings onto your own — useful for grabbing a teammate's or opponent's exact setup mid-game without leaving the match to paste a code manually.

Troubleshooting a Code That Won't Import

Most failed imports trace back to one of a handful of specific causes:

• Wrong game's code pasted into the wrong menu — the single most common mistake. Double-check the code's source matches the game you're importing into; a Valorant code will never work in CS2's import field and vice versa.
• Truncated or extra characters from manual copying — re-copy using a copy button rather than a manual text selection, and paste into a plain text field first if you want to visually verify nothing got cut off or duplicated.
• An outdated code format after a game update — crosshair code schemas have changed before after major patches in both Valorant and CS2, which can make an old, previously-working code fail to import correctly on current versions. If a code that used to work suddenly stops, regenerating it fresh in the current version of the game's own menu (or the generator) usually resolves it.
• Console command syntax errors — if you're pasting individual CS2 console commands rather than a share code, make sure each command is on its own line or properly semicolon-separated, and that any command expecting a color value is using the correct numeric format the game expects.

If a code still won't import after checking all of the above, the fastest fix is usually to rebuild it from scratch in the generator or the game's own menu rather than continuing to debug a specific broken string — a fresh export is guaranteed to match the current schema.

Once your crosshair is correctly imported, pair it with an accurate sensitivity for the same game using the sensitivity converter — a great crosshair set on the wrong sensitivity still won't land shots consistently, since the two settings solve different problems entirely. For the full index of which games support code-based import in the first place, see our companion guide Crosshair Generator & Database — All Games Hub.

Recreating a Look Manually When No Code Exists

For games without a code system at all — Apex Legends, Overwatch 2, Fortnite, and others that expose crosshair customization purely through settings sliders — "importing" really means manually matching each individual parameter one at a time: color, thickness, center dot on/off, and opacity, in whatever order that specific game's menu presents them. There's no shortcut here beyond writing down the exact values you're trying to match (from a screenshot, a settings list, or a streamer's shared numbers) and setting each slider individually, since there's no single string to paste. It's slower than a true code import, but it reliably reproduces the same visual result once every individual value matches.

This is also the reason a written settings list — rather than a code — is still the standard way pro crosshair setups get shared for slider-only games: it's the only format that actually works universally across every game, code-based or not, even if it takes a few extra minutes to apply by hand.

Frequently Asked Questions