If you have ever wondered why your crosshair feels like it is lagging behind your aim, or why you keep dying behind cover, the answer is probably in your network settings. CS2 uses a set of console commands that control how your client communicates with the server. Understanding them helps you make informed decisions instead of blindly copying configs from 2018.
The Four Commands That Matter
cl_interp sets the interpolation time in milliseconds. Interpolation is the engine's way of smoothing out the gaps between server updates. Without it, player models would teleport and stutter. The value you set here is the baseline delay your client uses to buffer incoming data.
cl_interp_ratio is a multiplier for cl_interp. It determines how many updates the client holds in its buffer. A ratio of 1 means the buffer holds roughly one update. A ratio of 2 means it holds two. Higher ratios give you smoother visuals on unstable connections but add more delay.
cl_updaterate controls how many times per second your client requests updates from the server. On 128-tick servers, this should be 128. On 64-tick servers, 64 is fine.
cl_cmdrate controls how many times per second your client sends your actions (shooting, moving) to the server. This should match your updaterate.
Recommended Settings
For a stable, low-ping connection on wired Ethernet:
Code: Select all
cl_updaterate 128
cl_cmdrate 128
cl_interp_ratio 1
cl_interp 0.015625
Code: Select all
cl_updaterate 128
cl_cmdrate 128
cl_interp_ratio 2
cl_interp 0.03125
What Not to Do
Never set cl_interp to 0 in online play. Interp 0 removes the buffer entirely, which means your client renders every update the instant it arrives. On a LAN with zero ping, this is fine. Online, it makes your hit registration worse because the client has no tolerance for jitter.
Do not copy old CS:GO configs without checking them. Some commands from 2018 are deprecated or behave differently in CS2. The sub-tick system changed how the server processes actions, and some old advice no longer applies.
Do not change your network settings between matches. If you tweak every time you miss a spray, you will never develop consistent muscle memory. Pick a setting based on your connection quality and stick with it.
When Settings Are Not the Problem
No console command can fix severe packet loss, poor routing by your ISP, or a faulty router. If you are rubberbanding violently, run a bufferbloat test and check your packet loss before touching cl_interp. If your ping spikes to 200ms during peak hours, that is an ISP issue, not a config issue.
Putting It Together
Open your autoexec.cfg file (create one in csgo/cfg/ if you do not have it) and add the four commands. Save the file, restart CS2, and test in Deathmatch. If your crosshair feels responsive and you are not dying behind cover, you are good to go.
Sources
[1] Best CS2 Interp Settings (Full Optimization Guide) - SKIN.LAND
[2] Best CS2 Launch Options 2026 Guide - Eloboss