Sub-tick is the networking system Valve built Counter-Strike 2 around. Instead of handling your inputs only at fixed moments, the server records exactly when you started moving, fired or threw a grenade. Valve presented it as making tick rate irrelevant; three years later players still debate how the game feels, and Valve has shipped a long list of fixes.
What Valve said it does
Valve's Counter-Strike 2 page calls sub-tick updates "the heart of Counter-Strike 2". A game server updates the world in steps called ticks, and Valve explains that the old server "only evaluated the world" at those fixed intervals. With sub-tick, "servers know the exact instant that motion starts, a shot is fired, or a 'nade is thrown".
From that, Valve made three promises: tick rate "no longer matters for moving, shooting, or throwing", your movement and shooting will be "equally responsive" whatever the tick rate, and grenades "will always land the same way".
What sub-tick doesn't change
As Valve describes it, sub-tick is about timing your inputs precisely. The server still steps through the world tick by tick, and how often it does so still matters to players. Dust2.us reported that Valve appeared to hard-code CS2 servers to 64 ticks per second before the global release, so third-party platforms could no longer run the 128-tick servers they had offered for CS:GO.
That is the root of the debate: your click may be timed exactly, but what you see of an enemy still depends on server updates and your connection.
The debates
How it feels. In November 2023 HLTV described feedback from sub-tick input as "a sticking point in the discussion of why CS2 feels worse than CS:GO". The problem it pointed to: your shot was registered at the moment you clicked, but its sound and muzzle flash didn't show until a frame later, so hits felt late. Valve's fix that month made that feedback "always render on the next frame" and synchronised bullet spread between client and server.
128 tick. Some professionals and commentators still want 128-tick servers. In March 2025 the caster and former player Chad "SPUNJ" Burchill used HLTV Confirmed to ask Valve to allow them at least at the top level. He said that someone who plays for a living "can literally tell the difference between spraying your gun on 64 tick versus 128 tick".
Peeker's advantage. The player who moves around a corner sees the defender slightly before the defender sees them, because of latency. On February 6, 2024 Valve said it had reduced peeker's advantage "in many cases", by 16 ms in the steady state, and cut down cases of very large advantage caused by queued commands.
Demos that don't match. Until late 2025, demo playback showed the server's view, without network latency. Valve admitted this "could be confusing because shots would hit that didn't look like they should have, and vice versa".
What Valve changed
| Date | Change |
|---|---|
| June 6, 2023 | Limited Test: sub-tick movement made more precise and less "floaty" |
| September 14, 2023 | Lag compensation rebalanced to favour lower-latency players |
| November 8, 2023 | Sub-tick feedback renders on the next frame; spread synced with the server |
| February 6, 2024 | Sub-tick shooting adjusted; peeker's advantage reduced; optional buffering against packet loss |
| November 13, 2024 | Damage prediction setting added |
| September 2025 | Sub-tick shooting consistency and movement acceleration improved |
| November 4, 2025 | TrueView demo playback |
| January 21, 2026 | Landing time calculated with sub-tick precision |
| April 2026 | Animgraph 2 goes live, with lower networking costs for animation |
Two of these are settings you can use. Damage prediction plays the hit effects the moment you shoot instead of waiting for the server. Valve warned that it can occasionally be wrong, for example after aim punch or a death your client doesn't know about yet, and that it is switched off at high ping. The buffering option from February 2024 smooths over packet loss at the cost of some latency; a day later Valve stopped players changing the interpolation setting directly, saying scripts that set it high caused "very bad rubber-banding".
TrueView, from November 2025, re-runs the observed player's client-side prediction during demo playback, so a demo shows something much closer to what that player saw. Valve noted that some differences remain, especially in slow motion.
Animgraph 2 is an animation rewrite rather than a netcode change, but HLTV noted it reduced the CPU and networking cost of animations when it left beta in April 2026. Movement also changed in January 2026, when jumps started to use sub-tick landing times, as our Season Four article covers.
Where it stands in October 2026
Sub-tick is still the system, and Valve's release notes up to October 8, 2026 announce no change to the server tick rate. Valve has kept treating the complaints as a list of specific problems: feedback timing, peeker's advantage, packet loss, demo accuracy and movement. Whether that answers the 128-tick argument depends on whom you ask.
Related rules sit alongside the netcode. In August 2024 Valve stopped allowing hardware that automates counter-strafing on its servers and disabled binds that combine several actions, as our Snap Tap article explains. For how sub-tick arrived with everything else at launch, see our CS2 launch article.
Sources
- Counter-Strike 2 — counter-strike.net
- Release Notes for 2/6/2024 — Counter-Strike 2 news
- Counter-Strike 2 Update (November 13, 2024) — Counter-Strike 2 news
- Introducing TrueView — Counter-Strike 2 news
- Counter-Strike 2 Update (January 21, 2026) — Counter-Strike 2 news
- CS2 update addresses sub-tick feedback, syncs bullet spread — HLTV.org
- SPUNJ begs Valve to allow 128 tick subtick servers in CS2 — Dust2.us
- AnimGraph2 goes live in latest CS2 update — HLTV.org
