How to Fix Packet Loss in CS2

Every action you take in CS2 -- moving, shooting, throwing a grenade -- is sent to the game server as a network packet. Simultaneously, the server sends packets back to your client with information about what other players are doing. Packet loss occurs when some of these packets fail to reach their destination.

Even small amounts of packet loss create problems in CS2. A lost packet containing your shot input means the server never processes that shot. A lost packet from the server means an enemy's movement skips frames on your screen. At high levels of competitive play, even 1% packet loss creates a noticeable disadvantage.

Packet loss differs from high ping. High ping means all packets are delayed but still arrive. Packet loss means some packets never arrive at all. The distinction matters because the fixes are different -- latency issues are about distance and routing, while packet loss is about connection stability and reliability.

CS2 provides built-in tools to monitor packet loss in real time:

• Net graph: Open the console and type cq_netgraph 1. This overlays network statistics on your screen, including packet loss percentage for both incoming and outgoing packets
• Scoreboard indicators: CS2 displays warning icons when network issues are detected. A broken chain-link icon indicates packet loss
• Windows command line: Open Command Prompt and run ping -n 100 google.com to test your general connection. Lost packets here indicate a problem outside of CS2

If the net graph shows packet loss only during certain moments (like when many grenades explode or lots of players are in view), the issue may be related to your PC's processing power rather than your network. If loss is constant, it is a network problem.

Work through these fixes systematically. After each change, play a match or two and check your net graph to see if packet loss has improved:

• Switch to Ethernet: Wi-Fi is the number one cause of packet loss for gamers. An Ethernet cable provides a direct, interference-free connection to your router. If running a cable is impractical, consider powerline adapters as an alternative
• Restart network hardware: Power cycle your modem and router by unplugging them for 30 seconds. This clears overloaded buffers and refreshes connections to your ISP
• Close competing applications: Streaming, large downloads, cloud sync, and video calls all consume bandwidth. Pause or close them while playing
• Check cables: Damaged or loose Ethernet cables cause intermittent packet loss. Try a different cable if yours is old or shows visible wear
• Update network drivers: Outdated network adapter drivers can cause packet handling issues. Check your motherboard or adapter manufacturer's website for the latest drivers
• Disable background network services: Windows Update, OneDrive sync, and antivirus cloud features can spike network usage unpredictably. Temporarily disable them while gaming
• Test on a different device: If another PC or console on the same network also shows packet loss (via a speed test), the problem is with your router, modem, or ISP

CS2 offers several console commands and launch options that can help manage packet loss effects. Note that these do not eliminate the root cause but can mitigate the impact:

• rate 786432: Sets the maximum data rate between your client and the server. The default and maximum value of 786432 ensures you are not artificially limiting your bandwidth
• cl_interp_ratio 1: Reduces interpolation, making the game use fewer buffered frames. This feels more responsive but is less forgiving of packet loss. Use cl_interp_ratio 2 if you experience frequent loss
• Max acceptable ping setting: Lowering this in game settings forces matchmaking to select closer servers, which generally have fewer routing hops and less chance of packet loss

For a comprehensive list of launch options and console commands, see our launch options guide. These tweaks complement the network fixes above but should not be relied on as the sole solution.

If local fixes have not resolved your packet loss, the issue likely lies with your router hardware or ISP infrastructure:

• Update router firmware: Log into your router's admin panel (usually at 192.168.1.1 or 192.168.0.1) and check for firmware updates. Manufacturers fix packet handling bugs in firmware updates
• Check router age: Routers older than 5-6 years may struggle with modern network demands. Consider upgrading to a newer model with better packet processing capabilities
• Enable/configure QoS: Quality of Service settings can prioritise game traffic over other network traffic. Configure CS2 or Steam as high priority in your router's QoS settings
• Run a traceroute: Use tracert (Windows) or traceroute (macOS/Linux) to a CS2 server IP. Look for hops with high latency or timeouts -- these indicate where packets are being lost
• Contact your ISP: Share your traceroute results with your ISP's technical support team. Request they check for congestion or faulty equipment along the route. Ask specifically about packet loss at the identified hops

If your ISP is unable to resolve persistent packet loss, consider whether alternative providers are available. Fibre optic connections generally provide the most reliable packet delivery. For more network troubleshooting, see our guide on fixing net jitter and check if CS2 servers are down to rule out server-side issues. You can also refer to Steam Support for additional networking guidance.