Your crosshair is the one thing on screen you look at in every single round, yet most players copy a code from someone else and never ask whether it suits their monitor, their maps or their eyes. A good crosshair is not a magic aim boost. It is a tool that should be easy to see, small enough to leave the target visible, and consistent from one match to the next.
This guide explains each setting in plain language, gives starting ranges you can adjust by feel, and shows how to move a crosshair into Valorant (profile code) or CS2 (console commands). You can follow along with the free crosshair generator, which previews your design on light, dark and colorful backgrounds.
The building blocks of a crosshair
Almost every crosshair in a tactical shooter is made from the same few parts. Knowing what each one does makes tuning much faster than changing values at random.
- Inner lines: the four short bars closest to the center. They are the core of most designs.
- Outer lines: an optional second set farther out, available in Valorant. Many players leave them off for a cleaner view.
- Length and thickness: how long and how wide each bar is.
- Gap: the distance between the center and where the lines start. A larger gap opens up the middle of the screen.
- Center dot: marks the exact point where the shot lands.
- Outline: a thin dark border around the shape so it survives bright surfaces.
- Color: decides how much the crosshair stands out from the map.
Change one value at a time. If you move three sliders at once you will not know which one made the crosshair feel better or worse.
Size, thickness and gap: keep the target visible
The most common beginner idea is that a bigger crosshair is easier to see, so it must be better. The problem shows up at long range: a large cross or a wide gap can sit right on top of a distant enemy's head, which is exactly where you need to see clearly. Shorter lines and a small gap keep the center free.
Thickness works in the opposite direction from what people expect. Very thin lines can vanish against detailed backgrounds, while very thick ones cover pixels you want to see. Thickness of 1 to 2 is a sensible starting zone in most cases, and the outline can add readability without making the lines heavier.
The gap is personal. A gap of zero or close to it gives a tight, precise shape; a small positive gap keeps the exact center completely clear. Try both in the practice range and notice which one lets you see the enemy model better while you aim at it.
Center dot or no dot?
There is no correct answer here, only trade-offs. A dot gives a precise point to aim with and is the simplest crosshair possible when used alone. On the other hand, combining a dot with long lines can feel crowded, because several marks compete for attention in the same small area.
- Dot only: minimal view, nothing covers enemies. Works best with a bright, outlined color.
- Lines only: familiar and easy to read, but the exact center is empty.
- Both: maximum precision, at the cost of more clutter. Keep the lines short if you do this.
Test all three in the practice range and keep the one you hit most comfortably, not the one that looks best in a screenshot.
Color and outline: visibility on every map
Contrast matters more than any other single choice. A crosshair that disappears against one wall or one patch of sky will cost you shots at the worst possible moment. Colors such as cyan, green, yellow and magenta often stand out because few surfaces use them. Red is risky on maps with many red walls, and white can fade on bright skies.
The outline is your safety net. A thin dark border keeps the shape readable on light surfaces, and it is often the reason a pale color still works on a bright map. Turn it on first, then judge the color.
Always check your color against both the brightest and the darkest places you play. The generator lets you switch the preview between light, dark and colorful scenes, so you can catch problems before you queue.
Starting points you can adjust
These are own starting suggestions to fine-tune by feel, not official or measured values. Units differ between Valorant and CS2, so treat the numbers as a first draft, not a rule. Comfort matters more than any table.
| Situation | Suggested start | Reason |
|---|---|---|
| Precise head-level aim | Inner lines, length 2-4, gap 0-2, thickness 1-2 | Small shape leaves the target visible |
| Minimal view | Center dot only, thickness 2-3 | No lines, nothing covers enemies |
| Classic cross | Length 4-6, gap 1-3, outline on | Easy to read at a glance |
| CS2 static | Style 4, size 2-5, thickness around 1, gap -2 to 0 | Does not move while shooting |
| Bright maps and sky | Outline on, cyan or green | Contrast against light surfaces |
| Dark or colorful maps | Yellow, magenta or white, outline on | Stays visible in shadows |
Pick the row closest to your situation, apply it, and then nudge one value at a time.
A quick worked example of how size and gap add up (own example, in the units your settings screen shows): the overall width of a four-line cross is 2 × gap + 2 × length. With gap 2 and length 4 that is 2 × 2 + 2 × 4 = 12. Dropping the gap to 0 gives 2 × 0 + 2 × 4 = 8, so the shape is a third smaller (4 ÷ 12) and covers less of a distant target. To test it, shoot 20 bot flicks with each of three designs (60 shots in total), count the hits for each and keep the one with the most hits you can repeat on another day.
Valorant: importing a profile code
Valorant stores the entire crosshair in a single text string called a profile code. In the game, open Settings, go to the Crosshair tab and choose Import Profile Code. Paste the code and every field fills in at once, ready to save as one of your profiles.
The generated code follows the format documented by the community. Riot does not publish official documentation of it, so if a code is ever rejected, copy it again without extra spaces, and if it still fails, set the numbers by hand from the list shown under the preview. The generated code also switches off the firing error and movement error animations, so the crosshair never changes shape; you can turn them back on in the game whenever you like.
CS2: console commands and autoexec
CS2 has no import string. The crosshair is a set of console commands such as cl_crosshairstyle, cl_crosshairsize, cl_crosshairthickness, cl_crosshairgap, cl_crosshaircolor, cl_crosshairdot and cl_crosshair_drawoutline. Each line simply sets one value.
- Enable the developer console in the game settings if you have not already.
- Open the console, paste the whole block and press Enter.
- To keep it permanently, add the same lines to your
autoexec.cfg, so they reload every time the game starts.
Because every command is separate, you can edit a single line later and keep the rest. The classic static style (cl_crosshairstyle 4) does not move while you shoot, which makes it easier to read during sprays.
Common mistakes and how to test
- Copying a crosshair without testing it. Someone else's settings were tuned to their screen, resolution and eyes.
- Changing it every day. Give a new crosshair a few sessions before judging it. Constant changes stop you from building a stable feel.
- Ignoring resolution. If you switch monitor or resolution, check the size again, because the same pixels look different.
- Skipping the outline. It is the cheapest fix for a crosshair that vanishes on bright surfaces.
- Forgetting a backup. Save the previous code or commands before experimenting so you can return to one that felt good.
For testing, use the practice range or an offline match, not a ranked game. You can also warm up your tracking and flicking with the reaction and aim trainer, which lets you pick the crosshair style and color so the test looks like your game. Pair this with a sensitivity that suits you; the guides on building an aim routine and choosing a CS2 sensitivity cover that side, and Valorant sensitivity and DPI does the same for Valorant.
Frequently asked questions
How do I import a crosshair code in Valorant?
Step 1: copy the full code without spaces. Step 2: in Valorant open Settings, then the Crosshair tab, then Import Profile Code. Step 3: paste, press Import and save it as one of your profiles; every field fills in at once.
How do I use the CS2 crosshair console commands?
Step 1: enable the developer console in the game settings. Step 2: open it, paste the whole block (for example cl_crosshairstyle 4, cl_crosshairsize 3, cl_crosshairthickness 1, cl_crosshairgap -1 as own example values) and press Enter. Step 3: add the same lines to autoexec.cfg to keep them permanently.
Why does Valorant say my crosshair code is invalid?
The most common cause is a code copied incompletely or with a space at the start or end. Copy it again and paste it into the import box; Riot does not publish official documentation of the format, so a rare mismatch is possible. If it still fails, set the numbers by hand from the list under the preview, for example length 4, gap 2, thickness 2.
Should I use a center dot?
There is no universal answer, but the test is easy: take 20 bot flicks each with dot only, lines only and both, count the hits (for example 14, 12 and 11 of 20) and keep the one with the most hits you can repeat on another day. A dot is precise but can feel crowded next to long lines.
Will a new crosshair improve my aim?
Not by itself. A clear crosshair removes distractions, but a 10 percent change in sensitivity moves your cm/360 far more than any crosshair tweak (for example 0.35 to 0.315 in Valorant at 800 DPI changes 46.7 cm to about 51.9 cm). Accuracy still comes from practice and a sensitivity that suits you.
A good crosshair is clear, small enough to leave targets visible, and stable over time. Start from a preset, change one value at a time, check the color on bright and dark backgrounds, and test it offline before ranked. When you are ready, open the crosshair generator, copy your code or console block, and give the result a few sessions before you judge it.