CS2 Net Settings: Rate & Interp
What rate, cl_interp and cl_interp_ratio actually do in Counter-Strike 2 — and why CS2's sub-tick networking makes most of the old CS:GO interp tweaking pointless.
rate
rate caps how many bytes per second CS2 will pull from the server. Too low and you’ll see choke under fire; there’s no downside to setting it high on a normal broadband connection. The current maximum is rate 786432, and that’s what most players run.
rate "786432"— the cap; fine for almost everyone.rate "512000"— a middle option for a weaker connection.
cl_interp and cl_interp_ratio
Interpolation smooths the small gap between server updates so other players move cleanly instead of teleporting. cl_interp_ratio sets how many update intervals of buffer to keep, and cl_interp sets a minimum time. The common, safe default is:
cl_interp "0"— let CS2 compute the minimum interp for you.cl_interp_ratio "1"— one interval of buffer; lowest latency.
On an unstable connection, cl_interp_ratio 2 adds a second interval of buffer, which can feel steadier at the cost of a little delay. There’s no single “pro” value that fits everyone here.
Why CS2 is different
CS2 uses sub-tick updates: the server records the exact moment of your shot rather than snapping it to a tick boundary, so the heavy interp micro-tuning people did in CS:GO matters far less now. Setting a high rate and leaving interp at the defaults above is enough for the large majority of players. Treat any claim of a magic interp number with caution — most measurable differences come from your actual connection, not the cvar.
Check your connection in-game
Turn on net_graph 1 (or cl_showfps 2) to watch ping, loss, choke and your real var/fps while you play. If you see loss or choke, that’s a network or rate issue — no interp value will fix a bad route.
Add these to your config
These belong in your autoexec.cfg so they load every session. The autoexec builder already includes a rate selector; drop the interp lines in alongside it.