What subtick is in CS2 and how it works

A simple explanation of the subtick system in CS2: how it differs from 64 and 128 tick and what it means for your game.

20 October 2026 1 min read 12
#cs2 #subtick #tickrate #netcode #guides

In CS:GO the server processed the game in "ticks" — 64 or 128 times per second. Anything between ticks was only counted on the next tick. In CS2 Valve introduced the subtick system.

📌 How it works

  • The CS2 server still runs at 64 ticks per second.

  • But every action you take — a shot, a jump, starting to move — gets an exact timestamp.

  • The server knows exactly when between ticks you pressed the button.

That is why the "64 vs 128 tick" debate no longer applies in CS2: shot accuracy does not depend on whether your click landed exactly on a tick.

🎯 What it means for you

  • A shot counts at the moment you clicked, not on the nearest tick.

  • Movement and stopping (counter-strafing) are processed more precisely.

  • Grenades fly the same at any FPS.

🔧 What helps subtick work better

  • Stable FPS — above your refresh rate without drops.

  • A stable connection without packet loss.

  • Ping — the lower it is, the smaller the difference between what you see and what the server sees.

⚠️ Myths

  • There are no launch options that "enable 128 tick" on official servers.

  • CS:GO commands like cl_interp and rate do not need tweaking in CS2 — the game handles them itself.

Was this article helpful?