CS2 Tickrate and the Subtick System Explained
CS2 ditched the classic tickrate model in favor of subtick. Here's what that actually means for your server and your players.
The Short Version
CS2 does not work the same way CS:GO did. The classic 64-tick vs 128-tick debate doesn't apply here. Valve introduced a subtick architecture that changes how movement and shooting are processed at a fundamental level.
How Subtick Actually Works
In CS:GO, everything was processed once per tick. At 64-tick, that's 64 snapshots per second. At 128-tick, 128. Your shot was only as precise as the tick it landed on.
CS2 runs its server loop at 64 Hz, but it records the exact timestamp of events like shots, jumps, and direction changes — not just which tick they occurred in. When the server processes a tick, it knows you fired at 14.37ms into the tick, not just "somewhere in tick 14." That's subtick precision.
The result: peeking, clicking heads, and movement inputs are processed more accurately than classic 64-tick, even though the server is still running at 64 Hz.
What This Means in Practice
- The 128-tick "feel" advantage from CS:GO is reduced but not completely gone — client-side prediction and interpolation still matter
- Ping and routing quality have a bigger impact on your experience in CS2 than raw tickrate ever did
- A low-latency server close to your players will feel better than a distant server, regardless of anything else — see CS2 Server Location Options
The Launch Parameter That Does Nothing
If you're coming from CS:GO server administration, you may be used to this:
-tickrate 128
This does not work in CS2. The parameter is ignored. Community servers run at 64 Hz and there is no supported way to change this.
Why Players Still Notice Differences
Even with subtick, players will notice differences between servers. The main factors:
Client-side interpolation (cl_interp, cl_interp_ratio) — these settings smooth out network jitter but introduce slight input lag. Competitive players often tune these aggressively.
Ping — this matters more in CS2 than it did in CS:GO because subtick timestamps are relative to when packets arrive. A 10ms player and a 80ms player are not experiencing the same game even if the tickrate is identical.
Routing — packet loss and jitter cause far more noticeable issues than tickrate ever did. A clean 60ms connection beats an unstable 20ms connection.
Server CPU load — a server that can't keep up with its 64 Hz loop will have inconsistent tick timing, which players feel as choppiness or hitreg issues.
What to Actually Optimize For
When picking or configuring your server, focus on:
- Location — pick the region closest to your player base
- Network quality — DustBowl routes traffic on low-latency paths, not just raw bandwidth
- CPU speed — single-core performance matters; CS2's game logic is largely single-threaded
- Plugin load — too many CounterStrikeSharp plugins can eat into tick processing time