CS2 to TF2 Sensitivity Converter

Convert your Counter-Strike 2 sensitivity to the exact Team Fortress 2 equivalent. The tool below is pre-set to this pair and verifies every result with a matching cm/360.

This direction is for CS2 players visiting TF2 — for casual nights, community servers, or the classic classes. Your sensitivity is identical on arrival, which makes TF2 the lowest-friction palate cleanse in gaming.

Converted sensitivity
0.4

Physical aim match: 129.9 cm/360 in the from-game = 129.9 cm/360 in the to-game, at 800 DPI. If the two numbers differ, the conversion is wrong — ours always match.

The conversion

CS2 and Team Fortress 2 share the same 0.022 Source-engine yaw — your sensitivity moves across 1:1 at the same DPI, no math required.

Worked example: 1.5 CS2 = 1.5 TF2 at 800 DPI — both are a 34.6 cm/360.

Common values (800 DPI)

CS2 sensTF2 senscm/360
0.380.38136.7 cm
0.60.686.6 cm
0.750.7569.3 cm
1.21.243.3 cm

Before you switch: TF2 specifics

Coming from CS2, the first thing to internalise: CS2 keeps the classic Source yaw (0.022) — a CS2 sens converts to Valorant by dividing by 3.18182 (Valorant numbers are smaller).

TF2 uses the original Source yaw (0.022) — identical to CS2 and Apex hipfire.

Typical TF2 sensitivity runs 1–3, and professionals play in the 800–2000 eDPI band. If your converted value lands far outside that band, double-check your DPI — the math is only as good as the number your mouse actually reports.

FAQ

What is 1.5 CS2 sens in TF2?

1.5 CS2 sensitivity equals 1.5 TF2 sensitivity at the same DPI — the games share the same 0.022 yaw, so the number does not change.

Why do CS2 and TF2 share a sensitivity?

TF2 is the older Source title and CS2 inherited its mouse-look constant. Same engine lineage, same 0.022 degrees per count.

Anything to check after switching?

Confirm raw input is enabled in TF2's mouse options and that your DPI is unchanged. With those two things true, the transfer is physically exact.

Related tools