How to Fix Net Jitter in CS2

Net jitter measures the variation in latency between your PC and the game server. While ping tells you the average round-trip time (e.g., 30ms), jitter tells you how much that time fluctuates from packet to packet. A ping of 30ms with 1ms of jitter means your connection is very stable. A ping of 30ms with 15ms of jitter means some packets arrive in 15ms while others take 45ms.

You can see your jitter value in CS2 by enabling the net graph. Open the console and type cq_netgraph 1 to display network statistics. The jitter value appears alongside your ping and packet loss readings.

In a game like Counter-Strike where timing matters at the millisecond level, inconsistent packet delivery causes the server to receive your inputs at irregular intervals. This leads to desync between what you see on screen and what the server calculates, resulting in shots that look clean on your end but miss on the server side.

Jitter usually originates from your local network or your ISP's infrastructure. Here are the most frequent culprits:

• Wi-Fi interference: Wireless connections are inherently less stable than wired ones. Other devices, walls, microwaves, and neighbouring Wi-Fi networks all introduce variability
• Network congestion: Other devices on your network streaming video, downloading files, or running cloud backups consume bandwidth and introduce packet queuing delays
• Outdated router firmware: Older firmware can have bugs that affect packet processing consistency
• ISP routing issues: Your packets travel through multiple hops between your home and the game server. Congestion or poor routing at any hop increases jitter
• Background applications: Programs that periodically send or receive data (cloud sync, auto-updates, antivirus scans) can cause momentary latency spikes
• VPN or proxy usage: Additional routing layers add latency variability

Work through these fixes in order, testing your jitter after each change:

• 1. Use a wired connection: Switch from Wi-Fi to an Ethernet cable. This single change eliminates the most common source of jitter for most players
• 2. Close bandwidth-heavy applications: Shut down streaming services, cloud sync (Dropbox, Google Drive, OneDrive), torrent clients, and anything else that uses your network while you play
• 3. Restart your router and modem: Power cycle both devices by unplugging them for 30 seconds. This clears cached routing tables and can resolve transient issues
• 4. Update router firmware: Log into your router's admin panel and check for firmware updates. Manufacturers regularly release fixes for packet handling issues
• 5. Disable QoS if misconfigured: Quality of Service settings on your router can help or hurt. If you are unsure how your QoS is configured, try disabling it and testing. Properly configured QoS can prioritise game traffic
• 6. Change DNS servers: Switch to Google DNS (8.8.8.8 / 8.8.4.4) or Cloudflare DNS (1.1.1.1). While DNS does not directly affect jitter, faster DNS resolution can reduce initial connection variability
• 7. Disable VPN: If you use a VPN, disable it while playing CS2. VPNs add routing hops that increase jitter

Within CS2 and your operating system, a few settings can help reduce jitter impact:

• Max acceptable matchmaking ping: In CS2 settings, lower your maximum acceptable ping. This forces the game to connect you to closer servers with less routing variability
• Disable Nagle's algorithm: On Windows, you can disable Nagle's algorithm for your network adapter, which reduces the batching of small packets. This requires a registry edit -- search for "TcpNoDelay" and "TcpAckFrequency" for your network interface
• Network adapter power management: In Windows Device Manager, open your network adapter properties and disable "Allow the computer to turn off this device to save power"
• Disable Wi-Fi power saving: If you must use Wi-Fi, set the wireless adapter power mode to "Maximum Performance" in Windows power settings

For more command-line optimisations, refer to the Steam support documentation on network troubleshooting.

If you have exhausted all the steps above and jitter remains high, the problem likely lies outside your home network. Here is how to identify and communicate ISP-side issues:

• Run a traceroute: Use tracert on Windows or traceroute on macOS/Linux to trace the path to a CS2 server. High latency variation at a specific hop indicates a problem at that network node
• Test at different times: If jitter is consistently worse during peak hours (evenings, weekends), this points to ISP congestion rather than a hardware issue
• Document the issue: Capture screenshots of your traceroute results and CS2 net graph showing the jitter values. Concrete data helps your ISP's support team diagnose the problem faster
• Ask about routing: Request that your ISP check the routing path to Valve's server infrastructure. Sometimes a simple routing change on their end resolves persistent jitter

If your ISP cannot resolve the issue and jitter continues to impact your gameplay, consider whether an alternative ISP is available in your area. Fibre optic connections generally provide the most stable latency compared to cable or DSL.