Settings & Config
Best CS2 Crosshair Settings in 2026 (Stop Copying Pro Codes)
Two major sites published different codes for the same pro in the same month. Here is what to do instead.
Beginner
·
8
MIN READ
·
·
Brian Sirbu
Beginner
·
8
MIN READ
·
·
Brian Sirbu
WHAT YOU’LL LEARN
Pro crosshair code lists contradict each other. Two major sites published different codes for the same four players in the same month, and one of them was not even a valid code.
Static or dynamic is the only choice that really matters. Set cl_crosshairstyle 4 and the decision is made.
Four values do all the work: size 2 to 3, thickness 0.5 to 1, gap between minus 3 and minus 1, and outline on.
Pick a colour nothing in the game shares. Cyan and green survive every map. White, red and yellow disappear on at least one.
Set it once, then play three full matches before you judge it. Swapping crosshairs after a bad round is how none of them ever feel right.
Pro crosshair code lists contradict each other. Two major sites published different codes for the same four players in the same month, and one of them was not even a valid code.
Static or dynamic is the only choice that really matters. Set cl_crosshairstyle 4 and the decision is made.
Four values do all the work: size 2 to 3, thickness 0.5 to 1, gap between minus 3 and minus 1, and outline on.
Pick a colour nothing in the game shares. Cyan and green survive every map. White, red and yellow disappear on at least one.
Set it once, then play three full matches before you judge it. Swapping crosshairs after a bad round is how none of them ever feel right.

WHAT YOU’LL LEARN
Why every pro crosshair code list on the internet contradicts the others.
The one setting that matters more than size, gap and colour combined.
The four values worth changing, and the range the professional field actually sits in.
How to test a crosshair properly instead of swapping it every third match.
Search “best CS2 crosshair” and you get the same page forty times: a wall of pro codes, copy one, done.
There is a problem with that page, and it is not a small one.
Two sites, same month, same pros, different codes
I pulled the pro crosshair codes from two of the biggest CS2 sites that publish them. Both updated recently. Both claim to list what the players are using right now.
Not one code matches.

Four players, eight codes, zero agreement. One of those codes is not even a valid share code: it has seven characters in the last block instead of five. Another site lists the exact same code for two different players.
This is not sloppiness from one site. It is what happens when pros change their crosshair between events and nobody goes back to update a list from eight months ago. The code you paste is not what that player is using. It is what someone thought they were using, at some point, maybe.
So the honest answer to “which pro crosshair should I copy” is: none of them, and it would not help you anyway. Their crosshair is tuned to their resolution, their monitor, and a game they have played for ten thousand hours. Yours should be tuned to you.
Here is what actually matters instead.
Static or dynamic is the whole decision
Every other setting is a detail. This one is not.
A dynamic crosshair opens up when you move and when you fire. It looks like it is giving you information. It is not giving you anything you do not already know, because you are the one who pressed W and you are the one holding mouse one.
What it does do is move the lines away from the single point you need to see.

The orange dot is where the bullet goes. In the top row the lines wander off and leave that point unmarked exactly when you need it most. In the bottom row the crosshair is identical in all three states, because the point that matters never moved.
The professional field is close to unanimous on this. Set cl_crosshairstyle 4 and stop thinking about it.
If you want the information that a dynamic crosshair pretends to give you, it comes from a different place: knowing that you are inaccurate while moving, and stopping properly before you shoot. That is a habit, not a crosshair setting.
The four settings that change anything
There are around twenty crosshair commands in CS2. You will touch four of them.

cl_crosshairsize is the length of the lines. Long lines cover the head you are trying to hit, especially at range. Almost every professional sits at 2 or 3.
cl_crosshairthickness is how wide the lines are. Decimals work, and 0.5 is a common choice. A thick crosshair feels solid and hides the exact pixel underneath it.
cl_crosshairgap is the hole in the middle. Negative numbers close it. A tight gap frames a head at twenty metres instead of swallowing it.
cl_crosshair_drawoutline 1 puts a thin black edge around the lines. It costs nothing and it stops your crosshair disappearing into a wall of the same colour. There is no reason to have this off.
Everything else on the command list is either cosmetic or only applies to dynamic styles you are not using.
A starting point that works
If you have no idea where to begin, start here and adjust from there:
cl_crosshairstyle 4cl_crosshairsize 2cl_crosshairthickness 0.5cl_crosshairgap -2cl_crosshair_drawoutline 1cl_crosshairdot 0cl_crosshaircolor 5cl_crosshaircolor_r 0cl_crosshaircolor_g 255cl_crosshaircolor_b 255
That is a small, thin, static cyan crosshair with an outline. It is deliberately boring. It is also close to where most of the professional field lands, which is the point.
Rather than typing those in one at a time, you can build and preview the whole thing in the CS2 crosshair generator and copy the finished code out.
The colour question, briefly
cl_crosshaircolor 5 unlocks custom RGB, and then _r, _g and _b take values from 0 to 255.
Cyan and green win for a simple reason: almost nothing in Counter-Strike’s maps is those colours. White disappears on light walls and on smoke. Red disappears on Inferno and on blood. Yellow disappears on Dust 2 in half the places you look.
Pick a colour that nothing in the game shares, then leave it.
How to import a code, step by step
Open settings with the cog icon.
Go to the Game tab, then Crosshair.
On the crosshair preview, click Share or Import.
Before you paste anything, copy your current code and save it somewhere.
Paste the new code and click Import.
Step four is the one people skip and then regret.
How to actually test one
Swapping crosshairs between matches is how you end up with none of them feeling right. A crosshair is like sensitivity: the value matters less than leaving it alone long enough for your hand to learn it.
Test it like this. Load aim_botz and stand at distance, not up close. Put the crosshair on a head and leave it there. You are checking one thing: can you see the exact point you are aiming at, or is the crosshair covering it?
Then play three matches without touching it. Not three rounds. Three matches.
If after that you are still overshooting heads or feeling imprecise, the problem is more likely your sensitivity than your crosshair. Run your numbers through the eDPI calculator before you change the crosshair again.
The five mistakes
Copying a pro code from a list. You already know why.
Changing it every time you lose. The crosshair did not lose the round.
Making it big because it feels comfortable. Comfortable up close, costly everywhere else.
Leaving the outline off. Free visibility, thrown away.
Using a dynamic style because it looks more advanced. It is the opposite.
Where the crosshair fits
Honestly: low. Your crosshair is worth a small, permanent improvement in how clearly you see what you are aiming at. That is real, and it is also the end of it.
It will not fix walking into angles, dying with utility in your bag, or shooting while moving. If you want the layers in order, the settings guide covers which settings matter at all, and which ones players tinker with instead of practising.
Set the crosshair once. Then go and practise the thing that is actually costing you rounds.
WHAT YOU’LL LEARN
Why every pro crosshair code list on the internet contradicts the others.
The one setting that matters more than size, gap and colour combined.
The four values worth changing, and the range the professional field actually sits in.
How to test a crosshair properly instead of swapping it every third match.
Search “best CS2 crosshair” and you get the same page forty times: a wall of pro codes, copy one, done.
There is a problem with that page, and it is not a small one.
Two sites, same month, same pros, different codes
I pulled the pro crosshair codes from two of the biggest CS2 sites that publish them. Both updated recently. Both claim to list what the players are using right now.
Not one code matches.

Four players, eight codes, zero agreement. One of those codes is not even a valid share code: it has seven characters in the last block instead of five. Another site lists the exact same code for two different players.
This is not sloppiness from one site. It is what happens when pros change their crosshair between events and nobody goes back to update a list from eight months ago. The code you paste is not what that player is using. It is what someone thought they were using, at some point, maybe.
So the honest answer to “which pro crosshair should I copy” is: none of them, and it would not help you anyway. Their crosshair is tuned to their resolution, their monitor, and a game they have played for ten thousand hours. Yours should be tuned to you.
Here is what actually matters instead.
Static or dynamic is the whole decision
Every other setting is a detail. This one is not.
A dynamic crosshair opens up when you move and when you fire. It looks like it is giving you information. It is not giving you anything you do not already know, because you are the one who pressed W and you are the one holding mouse one.
What it does do is move the lines away from the single point you need to see.

The orange dot is where the bullet goes. In the top row the lines wander off and leave that point unmarked exactly when you need it most. In the bottom row the crosshair is identical in all three states, because the point that matters never moved.
The professional field is close to unanimous on this. Set cl_crosshairstyle 4 and stop thinking about it.
If you want the information that a dynamic crosshair pretends to give you, it comes from a different place: knowing that you are inaccurate while moving, and stopping properly before you shoot. That is a habit, not a crosshair setting.
The four settings that change anything
There are around twenty crosshair commands in CS2. You will touch four of them.

cl_crosshairsize is the length of the lines. Long lines cover the head you are trying to hit, especially at range. Almost every professional sits at 2 or 3.
cl_crosshairthickness is how wide the lines are. Decimals work, and 0.5 is a common choice. A thick crosshair feels solid and hides the exact pixel underneath it.
cl_crosshairgap is the hole in the middle. Negative numbers close it. A tight gap frames a head at twenty metres instead of swallowing it.
cl_crosshair_drawoutline 1 puts a thin black edge around the lines. It costs nothing and it stops your crosshair disappearing into a wall of the same colour. There is no reason to have this off.
Everything else on the command list is either cosmetic or only applies to dynamic styles you are not using.
A starting point that works
If you have no idea where to begin, start here and adjust from there:
cl_crosshairstyle 4cl_crosshairsize 2cl_crosshairthickness 0.5cl_crosshairgap -2cl_crosshair_drawoutline 1cl_crosshairdot 0cl_crosshaircolor 5cl_crosshaircolor_r 0cl_crosshaircolor_g 255cl_crosshaircolor_b 255
That is a small, thin, static cyan crosshair with an outline. It is deliberately boring. It is also close to where most of the professional field lands, which is the point.
Rather than typing those in one at a time, you can build and preview the whole thing in the CS2 crosshair generator and copy the finished code out.
The colour question, briefly
cl_crosshaircolor 5 unlocks custom RGB, and then _r, _g and _b take values from 0 to 255.
Cyan and green win for a simple reason: almost nothing in Counter-Strike’s maps is those colours. White disappears on light walls and on smoke. Red disappears on Inferno and on blood. Yellow disappears on Dust 2 in half the places you look.
Pick a colour that nothing in the game shares, then leave it.
How to import a code, step by step
Open settings with the cog icon.
Go to the Game tab, then Crosshair.
On the crosshair preview, click Share or Import.
Before you paste anything, copy your current code and save it somewhere.
Paste the new code and click Import.
Step four is the one people skip and then regret.
How to actually test one
Swapping crosshairs between matches is how you end up with none of them feeling right. A crosshair is like sensitivity: the value matters less than leaving it alone long enough for your hand to learn it.
Test it like this. Load aim_botz and stand at distance, not up close. Put the crosshair on a head and leave it there. You are checking one thing: can you see the exact point you are aiming at, or is the crosshair covering it?
Then play three matches without touching it. Not three rounds. Three matches.
If after that you are still overshooting heads or feeling imprecise, the problem is more likely your sensitivity than your crosshair. Run your numbers through the eDPI calculator before you change the crosshair again.
The five mistakes
Copying a pro code from a list. You already know why.
Changing it every time you lose. The crosshair did not lose the round.
Making it big because it feels comfortable. Comfortable up close, costly everywhere else.
Leaving the outline off. Free visibility, thrown away.
Using a dynamic style because it looks more advanced. It is the opposite.
Where the crosshair fits
Honestly: low. Your crosshair is worth a small, permanent improvement in how clearly you see what you are aiming at. That is real, and it is also the end of it.
It will not fix walking into angles, dying with utility in your bag, or shooting while moving. If you want the layers in order, the settings guide covers which settings matter at all, and which ones players tinker with instead of practising.
Set the crosshair once. Then go and practise the thing that is actually costing you rounds.
COMMUNITY
FIND TEAMMATES. ASK ANYTHING.
Queue with players at your level instead of going solo, and ask whatever you are stuck on in the questions channel.
Queue with players at your level instead of going solo, and ask whatever you are stuck on in the questions channel.
JOIN THE DISCORD
→

Brian Sirbu
CS2 COACH // GAMESENSELAB
MORE CS2 GUIDES
STOP IMPROVING ALONE
Turn scattered practice into a repeatable system with feedback, accountability, and a clear next round.
Turn scattered practice into a repeatable system with feedback, accountability, and a clear next round.
$5/MONTH · CANCEL ANYTIME · +200 ELO GUARANTEE


