The Finals Sensitivity: Best Settings, Yaw and 1:1 Games

The Finals (Embark Studios, Unreal Engine 5) shipped late 2023, hit Season 10 in March 2026, and quietly settled into one of the cleanest yaw setups in modern FPS — a flat 0.0066 degrees per mouse count. The same constant Blizzard chose for Overwatch and the COD engine uses for Warzone. Three different studios, three different engines, one shared rotation rate. If you bounce between any two of these games, your sensitivity number does not change.

What yaw value does The Finals use?

Yaw is the engine constant that maps raw mouse counts to in-game rotation degrees. The Finals uses 0.0066 — the same constant as Overwatch 2 (Blizzard engine) and Call of Duty Warzone (IW/Treyarch engine). That convergence is the reason your in-game sens number transfers 1:1 between any two of them at the same DPI.

For everything else, the conversion is a simple ratio. Take your source-game yaw, divide by 0.0066, and multiply your in-game sens by the result. A CS2 sens of 1.5 (yaw 0.022) becomes 5.0 in The Finals (0.022 / 0.0066 = 3.33; 1.5 × 3.33 = 5.0).

How do I convert sens from another game to The Finals?

Multipliers below assume hip-fire base sensitivity. ADS-per-weapon and scoped multipliers are independent in every game — tune those separately. DPI stays the same on the mouse; only the in-game slider changes. Each row links through to a dedicated pair page with worked examples, reference tables, and pro stats.

Why do three games share the same yaw?

Coincidence, mostly. Embark, Blizzard, and Infinity Ward each picked the same default rotation rate for their engines independently. The result is one of the rare quality-of-life accidents in FPS: a single in-game sensitivity number that travels cleanly across three live competitive games. If you grind ranked Warzone weekdays and Finals tournaments weekends, you do not need to remember two numbers.

How do I pick a sensitivity for The Finals if starting fresh?

1. Identify the game you aim well in already — CS2, OW2, Valorant, anything.
2. Use the table above to convert that sens into The Finals (or use the dedicated pair page if you want a worked example with cm/360°).
3. Stick with the converted number for 10+ hours of gameplay before tweaking. Your brain needs reps, not constant re-tuning.
4. If flicks consistently overshoot, drop by 10%. Undershoot, raise by 10%. Anything bigger is panic-tuning.
5. Match horizontal and vertical sens unless you specifically know you want split — default 1.0 vertical ratio is the right call for 95% of players.

Settings that matter beyond sens

• Polling rate — 1000Hz is the standard. Higher (4000/8000Hz) is overkill for The Finals' tick rate and adds CPU load.
• ADS sens multiplier — separate setting, tune independently. Default 1.0 is fine to start.
• FOV — 71–90° hipfire range; pick what feels comfortable, then leave alone.
• Motion Sync (mouse software) — most pros leave it off for the most direct "one-to-one" feel.

Why is there no verified pro settings list for The Finals?

Because nobody publishes one — not us, and not anyone else. The competitive scene is real and documented: there are dozens of rostered teams, and Embark ran an official world championship at DreamHack Stockholm in 2025. What does not exist anywhere is the settings data. Even the community wiki that tracks every match has a page reserved for player mouse settings and it is still empty.

That matters, because the gap gets filled with invention. Search for The Finals pro settings and you will find pages presenting a confident table of names and numbers. Check who is on it.

• If the list names Shroud, TenZ, aceu, Wardell, Hiko, EliGE or Stewie2K, it is not a The Finals list. Those are Counter-Strike, Valorant and Apex players, and the sensitivities beside them are their settings from those games.
• Those players do not compete in The Finals. That single check settles it without needing to know anything about the numbers.
• No source link and no date is the tell that decides the rest. A real settings entry can be checked against where it came from and shows when it was last confirmed.

The same three checks work on any settings page for any game, including this one. Our own rule is that a player is only added with a source URL and a verification date attached, which is why the list here is empty rather than plausible. An empty table is worth more than a wrong one: a wrong sensitivity costs you weeks of muscle memory built on a number nobody actually plays.