What Is the Tick Rate for CS2?
64 — and sub-tick changed what that number governs rather than making it irrelevant
CS2's official servers run at 64 ticks per second. Sub-tick updates mean your inputs are timestamped to the exact instant they happened instead of being rounded to the next tick, which removed a real defect — but the server still evaluates and sends you the world 64 times a second. Sub-tick does not make 64 tick equivalent to 128 tick, and Valve has never said it does.
This is a question with a straight answer and a complicated footnote, and most pages give you one or the other. The straight answer is 64. The footnote is that Valve deliberately stopped treating the tick rate as a headline number when CS2 shipped, and that shift is what the entire 64-versus-128 argument has been talking past ever since.
So this page does both: the number, then a careful account of which problem sub-tick solved and which problems it left exactly where they were.
The number, and where it comes from
Valve's official matchmaking servers — Competitive, Premier, Casual, Deathmatch, all of it — run at 64 ticks per second, the same rate CS:GO's official servers used.
Worth being upfront about the sourcing, because this is a topic where confident numbers get invented. Valve does not publish a tick-rate figure for CS2 anywhere. It is not on the Steam store page, it is not in the release notes, and it is not on counter-strike.net. Reading back through every Valve release note since the CS2 announcement, the only tick-rate number Valve has printed at all is a reference to CS:GO running at 128 tick, used in June 2023 as the comparison point for how bunny hopping should feel.
That silence is the point rather than an oversight. Valve's CS2 feature list sells tick-rate-independent gameplay, and its own description of sub-tick states that tick rate "no longer matters for moving, shooting, or throwing". If the design goal is that the number stops mattering, printing the number undercuts it.
What sub-tick actually changed
In the old model the server evaluated the world only in discrete intervals. An action did not exist until the next tick came round, so two players who genuinely pressed fire at different moments could be treated as having fired simultaneously. Valve's account of the fix is that CS2's sub-tick architecture lets servers know the exact instant that motion starts, a shot is fired or a grenade is thrown — and that as a result, whatever the tick rate, moving and shooting are equally responsive and grenades land the same way.
That is a real fix to a real defect, and it is the thing sub-tick is for. It is also narrower than the marketing shorthand suggests. Precisely:
| Fixed by sub-tick? | |
|---|---|
| Your input being rounded to the next tick boundary | Yes. This is exactly what it addresses. |
| The timing of your shot, jump or grenade release | Yes. Timestamped, not quantised. |
| How often the server evaluates and sends the world | No. Still 64 times a second. |
| How often you receive other players' positions | No. Same snapshot cadence. |
| Round-trip latency to the server | No. Nothing in an engine removes this. |
| Interpolation and lag compensation | No. Both still present and still doing their old jobs. |
The bottom four rows are why peeker's advantagesurvived the transition intact — that page works through the mechanism properly and there is no point repeating it here. The short version: sub-tick sat on top of peeker's advantage, not underneath it.
The claim to be suspicious of
You will see it phrased several ways: that sub-tick makes 64 tick "effectively 128", or "better than 128", or that tick rate no longer exists in CS2. All three are wrong, and the third one is the tell that whoever wrote it did not read Valve's wording carefully.
Ticks did not go away. CS2 still counts in them, visibly:
- The buffering setting in the game menu is denominated in ticks — None, 1 tick, 2 ticks — which only means something if a tick is still a real unit of time you can choose to pay.
- Valve changed the network-quality measurement in November 2024 to count how often a tick is missed due to loss or jitter. You cannot miss something that does not exist.
- Server-side gameplay values are still expressed in ticks, and Valve still ships bug fixes about individual ticks being added or subtracted incorrectly.
What changed is that the tick stopped being the resolution at which your input is recorded. It remains the resolution at which the world is simulated and transmitted. Conflating those two is the entire confusion.
Why there is no 128-tick option any more
In CS:GO this was a setting. Valve added a -tickrate parameter for server operators in a May 2012 beta update, official matchmaking stayed at 64, and third-party leagues ran 128 — which is where the whole cultural argument came from.
CS2 has no equivalent. There is no tick-rate console variable in the engine's variable list at all, and the CS:GO client-side rate model that went with it was dismantled: cl_updaterate and cl_cmdrate do not exist in CS2, and neither do the server-side sv_minupdaterate and sv_maxcmdrate limits. Interpolation is no longer a value you set. Our CS2 interp settings page goes through the survivors command by command, and it is the page to read before you paste anything from a CS:GO-era config.
So sub-tick was not shipped as an option alongside choosing a rate. It was shipped as the replacement for choosing one.
What to measure instead
Since there is no tick-rate dial and no tick-rate readout, the productive question is where your latency is actually coming from. In rough order:
- Turn on the telemetry HUD under Settings → Game → Telemetry. Ping, frame time, ticks missed due to loss or jitter, and a jitter graph. Measure before you change anything.
- Run
cl_ticktiming. Valve added it in February 2024 specifically to print a report breaking down the sources of latency, which is closer to what people are actually asking when they ask about tick rate. - Play on the nearest server region. Still the single biggest lever available to you, and it costs nothing.
- If you are seeing missed ticks, fix the loss rather than buffering around it — the buffering setting buys stability with effective ping. Start with our packet loss fix.
- Rule out frame pacing before blaming the netcode. A stuttering client feels identical to a bad connection; the FPS optimization guide separates the two.
The honest summary
CS2 runs at 64 tick on Valve's servers. Sub-tick removed the input quantisation that made a low tick rate feel arbitrary, and it did so well enough that Valve now declines to publish the rate at all. That is a genuine engineering change, not a rebrand.
It is also not a doubling. The server still simulates and transmits 64 times a second, latency is still latency, and the duel around a corner still resolves the way it always did. Anyone selling you sub-tick as an equivalence to 128 tick has skipped the second half of Valve's own sentence. For the engine context behind all of this, see what engine is CS2 built on?
Frequently Asked Questions
- What is the tick rate for CS2?
- Valve's official servers run at 64 ticks per second — the same rate CS:GO's official matchmaking used. Valve does not publish that number anywhere in CS2's store page, release notes or documentation, because its stated position is that the rate should no longer determine how responsive the game feels.
- Does sub-tick make 64 tick the same as 128 tick?
- No, and Valve has never claimed it does. Sub-tick removes tick quantisation — the server is told the exact instant an action began instead of rounding it to the next tick. The server still evaluates and transmits the world 64 times a second. Those are two different things, and only the first one was fixed.
- Can you play CS2 on 128-tick servers?
- CS2 exposes no tick-rate setting. There is no tick-rate console variable anywhere in the CS2 engine variable list, unlike CS:GO where server operators were given a -tickrate parameter in a 2012 update. Sub-tick was shipped as the replacement for choosing a rate, not as an option alongside it.
- Does tick rate still matter in CS2 at all?
- Yes, just not for the thing it used to matter for. Your inputs are timestamped, so shooting and movement no longer snap to tick boundaries. But the tick is still the unit the server sends snapshots on, and it is still the unit CS2 measures things in — the buffering setting is denominated in ticks, and the telemetry HUD counts ticks missed to loss or jitter.
- Did CS2 remove the old rate commands?
- Most of them. cl_updaterate and cl_cmdrate are not present in CS2 at all, and neither are sv_minupdaterate or sv_maxcmdrate. Interpolation is no longer something you set directly. Our CS2 interp settings page goes through the survivors one at a time.
- How do I check the tick rate in a CS2 match?
- There is no tick-rate readout in the game. What CS2 gives you instead is the telemetry HUD under Settings, Game, Telemetry — ping, frame time, ticks missed due to loss or jitter, and a jitter graph — plus the cl_ticktiming console command Valve added in February 2024, which prints a breakdown of where your latency is coming from.