CS2 Crosshair Migrator: Convert Old Codes and Commands
Preserve the original setup, rebuild or import it in the current menu, and test the result before exporting a fresh code.
Start With a Manual, Reproducible Migration
This guide uses only the current CS2 menu, a saved share code, and a player-run verification scene. It does not depend on an external converter or claim that a third-party result has been tested in the current client. A screenshot is a comparison reference, not a complete record of settings.
What a Crosshair Migration Means
There is no separate Valve migration button. In practice, migrating a crosshair means preserving the old version, importing or rebuilding it in the current Crosshair/Scopes tab, and checking the visible result at the resolution you actually play.
Valve's September 2026 updates changed the crosshair settings system, added styles, made crosshairs resolution independent, and changed the default to Dynamic Quad. On September 30, Valve also changed the share-code format to carry additional crosshair settings. An old code can still import while looking different from an old screenshot, or while leaving newer fields to be checked in the current client.
Check the Share-Code Format Change
If you imported an older code before the September 30 update, treat it as a source snapshot, not as a complete record of every current crosshair field. Valve says the new format includes scope-dot scale and color preferences and was changed to accommodate the added settings. Import the old code, inspect the current preview and controls, then export a fresh code from your client after testing.
This is a compatibility check, not a claim that every older code is invalid. Keep both strings and label them with the client date so you can tell which one contains your current exported settings.
Preserve the Old Version First
Before changing anything, keep at least one of these records:
- The complete
CSGO-share code. - A screenshot of the old preview and visible settings.
- The old command preset, if the setup was built with console commands.
- The resolution, aspect ratio, style, color, outline, dot, length, gap, and thickness.
Label the record with a date and display context. A code without its source date is difficult to compare when a player or database publishes a newer snapshot.
Migrate Through the Current Menu
- Open Settings -> Crosshair/Scopes.
- If you have a share code, choose Share or Import and paste the full
CSGO-string. - If you only have a screenshot or old commands, rebuild the closest visible shape in the current preview.
- Check the selected style before changing size or gap.
- Compare the imported or rebuilt version at your normal resolution and aspect ratio.
- Export the result as a new personal code after testing. Re-export even when the old code imports successfully, because the current share-code format carries fields added by later updates.
Do not paste a console command bundle into the share-code field. Do not assume an old cl_crosshairsize number will produce the same visible length after the update.
Diagnose the Difference
| What changed | First check | Why |
|---|---|---|
| The whole shape looks different | Selected style | Styles can change the shape more than a small size adjustment |
| The shape looks larger or smaller | Resolution and aspect ratio | The updated system uses resolution-aware pixel behavior |
| The center looks closed | Gap, thickness, dot, and outline | Several controls can hide the visible opening |
| The reticle disappears | Color and outline on the actual map | Menu preview contrast is not the same as a live scene |
| The code does not load | Full prefix, spaces, and import location | Share codes and console commands use different inputs |
Change one control at a time and keep the original version available for rollback. Use the code-not-working checklist when the import itself fails, or the five-minute testing routine when the import works but the result feels wrong.
Keep the Migrated Version
Keep the original code and the tested code as separate records. Save the new code with the date, resolution, and the reason you kept it. That gives you a reproducible personal setup instead of treating a public player snapshot as a permanent setting.
For a dated starting point, use the CS2 crosshair code directory. For a player-specific comparison, see donk's crosshair snapshots.
Migration Checklist: Do This Before You Paste Anything
Migration is safer when you can return to the exact starting point. Before opening a converter, the console, or the import field, make a small record outside the game. Copy the whole share code if you have one. If you do not, take a screenshot of the menu and write down the display resolution and aspect ratio used for the old setup. Include the style, color, outline, dot, length, gap, and thickness that are visible. A command line without the screen conditions that produced it is not a complete backup.
Keep the original record unchanged. Give the test version a different name, date, and resolution. That distinction matters when an import looks acceptable in the menu but feels different in a match. It also makes it possible to undo one failed experiment without guessing which of several changes caused the problem.
Use this order:
- Export or copy the current
CSGO-code before you change it. - Save one screenshot of the current Crosshair/Scopes controls and preview.
- Write down your normal resolution and aspect ratio; do not rely on a remembered screenshot from another PC.
- Pick one route: import a complete share code, rebuild in the menu, or inspect one old console setting. Do not mix the routes on the first pass.
- Test the candidate in a practice scene before exporting a fresh code.
- Keep the old and new records side by side until the new one has survived the test.
The objective is not to prove that a legacy setup is “compatible.” The objective is to preserve a reproducible old reference, then decide whether the visible result in the current client is the one you want to keep.
Pick the Correct Migration Route
| What you still have | Start here | Do not assume | Finish condition |
|---|---|---|---|
A complete CSGO- code | Crosshair/Scopes → Share or Import | An import proves every field looks identical | Inspect the preview, test it, then export a new code |
| A screenshot | Crosshair/Scopes menu | The picture records resolution, style, or every hidden field | Rebuild the visible shape one control at a time |
| Old console commands | Read them as a historical checklist | A command bundle belongs in the share-code import box | Change or inspect one setting at a time, then check the menu |
| A player page | Treat it as a dated reference | It is a current, in-game-verified recommendation | Compare it against your own saved setup |
If you only have an image, do not try to reverse-engineer a perfect configuration from pixels. Start with the current style, then make the shape readable at your normal resolution. A screenshot can be useful for comparison but cannot show every setting, whether a dynamic style was active, or whether the image was stretched after capture.
Import a Share Code Without Losing Your Baseline
Open the current settings panel and navigate to Crosshair/Scopes. Use Share or Import only for a complete code beginning with CSGO-. Paste the whole string without adding quotation marks, command names, or extra explanation. After import, stop before changing five controls to chase the old picture. First identify the selected style and inspect the preview. Then look at the center, bar length, gap, thickness, color, outline, and dot.
If the import completes but the appearance differs from an older screenshot, that is a comparison result, not automatically an error. Valve's September updates changed the system and later changed the share-code format to accommodate more settings. Check the current client rather than declaring the old value broken. If the import fails, re-copy the complete code and make sure it is not a command line, a truncated chat message, or a value with spaces inserted by formatting. The code-not-working checklist covers the import failure path.
When the imported version is visible, change only the field that corresponds to the symptom. For example, inspect the selected style before trying to repair a whole shape with a gap value. Check resolution and aspect ratio before treating a size difference as a bad code. Test outline and color on actual map surfaces rather than deciding from a single menu background.
When You Only Have Commands
Console commands and share codes are different inputs. Do not paste a command bundle into Share or Import, and do not paste a CSGO- string into the console. Older command examples can be useful for understanding which visual property a player tried to change, but they are not proof of a current visual result after the update.
If you choose to inspect commands, first preserve the old text in a note. Enable the developer console through the current game settings if it is not available. Enter one command, submit it with Enter, and check the Crosshair/Scopes preview. Then look at the same crosshair in a practice scene. If you cannot see a reliable change, undo it with the saved code instead of stacking another command on top. The after-update commands guide gives the full menu-first verification sequence.
Do not use this page to copy an untested “best” bundle. There is no claim here that legacy numeric settings map one-to-one to the current client. The safe use of a command is narrow: change one known property, observe the result, and keep it only after your own test.
A Five-Minute Acceptance Test
Use the same scene, display, and weapon for both the old reference and the candidate. Start with a bright surface, then a dark corner, then a distant target at head height. Strafe, stop, and fire one controlled shot; repeat with a short burst. You are not measuring aim skill. You are checking whether the center remains readable and whether any feedback helps or distracts you.
Ask four questions at the end:
- Can I find the center immediately on a bright and a dark background?
- Does the selected style make sense for what I am trying to see: a stable reference or movement/spread feedback?
- Does the shape remain readable at my normal resolution and aspect ratio?
- Can I reproduce this result from the backup and the final exported code?
If the answer to any question is no, keep the original backup and return to one setting. If the answer is yes, export the current client result as a new personal share code and label it with the date and display context. This is a player-run acceptance test, not an assertion that the site independently verified the result.
Watch a Visual Walkthrough, Then Verify in Your Client
The video below is a third-party visual walkthrough of changing a CS2 crosshair. It is included to help locate the general menu workflow, not as evidence for update facts, command compatibility, or a recommended preset. Use Valve's notes and the current game client for those decisions.
Migrator FAQ
Is there an official Valve crosshair migrator?
No separate Valve migration button is documented in the cited update notes. The practical route is to preserve the old setup, use the current Crosshair/Scopes controls or a clearly labeled community tool, and verify the result in the client.
Can I paste Migrator output into Share or Import?
Only paste a complete CSGO- share code into Share or Import. A console command line or configuration text is not a share code; preserve it as a historical reference and verify one property at a time through the console route.
Why does an old code import but look different?
First check the selected style, resolution, aspect ratio, dot, outline, length, gap, and thickness. The September updates introduced a new settings system and resolution-aware behavior; September 30 also changed the share-code format. An accepted import is not a guarantee that an old screenshot will match exactly.
Should I copy a pro's old code after the update?
Treat any third-party player code as a dated snapshot, not a current verified setting. Keep your own backup, import only if you want a starting point, and confirm the current result in your client.
Sources
Related Guides
CS2 Crosshair After Update: 2026 Changes and Fixes
What to check if your CS2 crosshair changed after the September 2026 update: new styles, Crosshair/Scopes, resolution behavior, and code fixes.
CS2 Crosshair Code After the 2026 Update
Troubleshoot a CS2 crosshair code that looks different after the September 2026 update, with an import, style, resolution, and backup checklist.
CS2 Crosshair Code Not Working: Import and Preview Checklist
Fix a CS2 crosshair code that will not import, appears unchanged, or looks different from the source screenshot.
CS2 Crosshair Resolution Settings: Test the Shape on Your Display
Test a CS2 crosshair at the resolution and aspect ratio you actually use, especially after the 2026 update.