Updated May 2026. Every menu path below is written from the live 2026 client of each game. Where a game lets you paste a profile code, the exact import location is given so you can stop guessing and start playing.
Ask a hundred ranked players why they miss and almost none will say "my crosshair." They will say sensitivity, monitor, or tilt. Yet the crosshair is the one variable you stare at on every single duel, and a badly chosen one quietly costs you the half-second it takes to find your own aim point against a busy texture. This guide is not a list of "best" reticles - there is no single best - it is the game-accurate menu reality for the five FPS titles that matter in 2026, plus the reasoning competitive players actually use when they tune. Read the game you play, copy the menu path exactly, lock it, and move on.
The crosshair does not improve your accuracy. Your hand does that. What the crosshair changes is acquisition speed: how fast your eye locks onto the aim point and how cleanly you can place it on a head without the reticle itself hiding the target. Those are two competing pressures. A tiny dot is the most precise possible aim point but is slow to find in a chaotic fight. A large four-line cross is instantly visible but its center is ambiguous, so headshot placement drifts by a few pixels - and a few pixels at 50 metres is a miss.
The competitive answer that has held for years is a small static reticle with a defined center, usually a short cross plus a center dot, in a color that never appears in the map texture you fight on. Static, not dynamic: a crosshair that expands when you move or fire teaches you nothing useful and hides exactly where your bullets are going. Disable dynamic spread in every tactical shooter. The only place dynamic feedback helps is when you are still learning a spray pattern, and even then you should graduate off it within a week.
Valorant is the easiest game in this list to get right because Riot built a full crosshair profile system with shareable codes. Path: Settings → Crosshair. At the very top of that screen is the Import Profile Code box. Paste any published code there, hit the arrow, and it loads instantly. ProSettings and similar trackers publish working codes for nearly every VCT pro, so you can run TenZ's or Aspas's exact reticle in ten seconds.
If you are building your own, the values competitive Valorant players converge on look like this:
| Setting | Typical pro value | Why |
|---|---|---|
| Crosshair Color | Cyan or Green | Never appears in Valorant map textures; fastest to track |
| Outlines | On, opacity ~0.5, thickness 1 | Keeps the reticle visible on bright walls without bloating it |
| Center Dot | On, thickness 2, opacity 1 (split opinion) | A defined aim point for one-taps; some pros prefer no dot |
| Inner Lines | Length 4-6, thickness 2, offset 2-3 | Compact cross; small enough not to mask a head at range |
| Outer Lines | Off | Outer lines add visual noise without helping placement |
| Movement / Firing Error | Off | Static reticle - dynamic error hides true bullet position |
One detail people get wrong: Valorant's in-game sensitivity scalar is 0.07. That number is not a crosshair setting, but it is why your Valorant sens feels nothing like your CS2 sens at the same DPI. To compare across games, multiply DPI by in-game sens by the game scalar to get eDPI, then match centimetres per 360. Use the FPSAim sensitivity converter tool rather than eyeballing it - the scalar differences between titles are large enough that a guess will be 20-40% off. Once your sens is matched, the crosshair is the only thing left to standardize, which is the whole point of this page.
After you import or build a crosshair, validate it the right way: load the Valorant aim trainer here, run one block of static placement, then play deathmatch with the same reticle. If you cannot find your dot fast in DM, the color is wrong for the maps you play, not the size.
Counter-Strike 2 moved most crosshair editing into a visual menu (Settings → Game → Crosshair), but it still maps to the classic console variables, and sharing a crosshair via its share code in that same menu is now the standard. The values that decide how a CS2 crosshair plays:
cl_crosshairstyle 4). Static is non-negotiable for competitive play - it never expands, so what you see is exactly where bullets go on the first shot.The September 2024 input update changed how raw mouse movement is handled in CS2 subtly, which is worth knowing because it affects how your sens feels even though it does not change crosshair variables. If your CS2 aim feels different from your old CS:GO muscle memory at the same eDPI, that input change - not your crosshair - is the usual cause. Keep the crosshair fixed while you re-calibrate sens, change one variable at a time, and confirm with the CS2 aim trainer before you blame the reticle.
Apex Legends is the odd one here because there is no single global crosshair. Hipfire uses a default reticle per weapon class, and aiming down sights swaps to whatever optic is attached. What you actually tune in Apex is the reticle color and FOV, both under Settings.
The reticle color options (Settings → Mouse/Keyboard or Controller, then the color picker) follow the same logic: pick a color that contrasts with the desert and foliage you fight in. The bigger Apex-specific lever is FOV. Apex defaults to a wider field of view than the tac-shooters, so the same numeric reticle covers more visual space and the world moves faster across your screen. A higher FOV (104-110) shows more but makes distant targets smaller; a lower FOV makes targets larger but reduces peripheral awareness. There is no correct number - it interacts with your sensitivity and your monitor distance - but it must be locked along with your crosshair.
Apex also has manual recoil that you control, not a spray pattern that resets like CS2. That means crosshair placement at the start of a fight matters more than the reticle's exact shape: you want it pre-aimed at head height as you push a corner. Practice that with a tracking-and-flick block in the Apex aim trainer, then carry the warmed-up placement straight into a match. A polling-rate detail worth knowing: Apex on Steam versus the standalone client can default to different polling behavior - standardize to 1000 Hz so your input is identical across sessions.
Fortnite splits cleanly into two input worlds, and the crosshair advice is genuinely different for each. On mouse and keyboard, the reticle is small and the editing options are limited - the real "aim setting" in Fortnite is your edit/build sensitivity multipliers (Settings → Mouse Sensitivity, then the build and edit multipliers), because most lost fights are lost on a slow edit, not a missed shot. Keep the targeting reticle small and high-contrast and spend your tuning time on build/edit speed.
On controller, aim assist and the look-input curve dominate. The two settings that decide everything are Look Sensitivity and the advanced look curve (Linear vs Exponential). Linear gives a 1:1 stick response that competitive controller players overwhelmingly prefer because it is predictable; Exponential ramps and is harder to be consistent with. Aim assist strength is fixed by Epic per input, so you cannot inflate it - what you can do is choose Linear, set a sensible sensitivity, and not change it.
For either input, the transferable skill is target acquisition under pressure with builds going up around you. Drill clean first-shot placement and rapid retargeting in the Fortnite aim trainer so the reticle work is automatic and your attention stays on the build fight.
Overwatch 2 has the most flexible crosshair system of any game here, and it should be used per hero, not globally. Path: Options → Controls → Reticle, then use the per-hero dropdown at the top of that screen so each hero can have its own reticle. This matters because Overwatch heroes have radically different aim demands:
The big Overwatch-specific number is the relative aim sensitivity while zoomed for Widowmaker and Ana - it scales scoped sens independently and is the single most important Widow setting. Set the per-hero reticle, set the relative scope sensitivity, and lock both. Validate the hitscan reticles with a click-timing and flick block in the Overwatch aim trainer; the tracking reticles want a strafing-target routine instead.
The reason multi-game players feel inconsistent is almost never the crosshair shape - it is that the same in-game sensitivity number means a different physical hand distance in each title because every game uses a different internal scalar. Valorant uses 0.07. CS2, Apex, Fortnite and Overwatch each have their own. If you do not normalize, your CS2 flicks will overshoot in Valorant and undershoot in Apex even with an identical reticle.
The fix is mechanical, not stylistic: standardize centimetres per 360 across every game using the FPSAim sensitivity converter, then standardize the crosshair color and a compact static shape across all of them. Once cm/360 and reticle are matched, switching games costs you almost nothing because the only thing that changes is the map art and recoil model, not the muscle memory.
Then validate the whole stack the way pros do, not by feel: a short structured block in the relevant per-game trainer, immediately followed by deathmatch in the same game. The full 30-day structure for turning that validation into a real rank jump is laid out in our how to improve aim fast guide, and the routine database has copy-ready warmups for each title at the aim training routine database. Settings get you to a clean starting point. Structured reps are what move the rank.