cs2 · settings · fps

Fix CS2 Lag and Packet Loss: Ping, Loss, and Choke

Learn how to tell ping, loss, and choke apart in CS2 and optimize your network and settings.

14 Oct 2026 · 3 min read

A screenshot of CS2 gameplay with the console open, showing network commands and FPS display.

CS2 lag and packet loss can feel the same in game, but they have different causes and fixes. You need to know whether you're dealing with high ping, packet loss, or choke to make the right changes. Start with a rate of 786432 and test from there. This guide will help you tell the difference and improve your online experience.

Symptom, Check, and Change
SymptomWhat to CheckWhat to Change
High ping (150+ ms)Your ping in the scoreboard or console (net_graph 1)Try a wired connection or contact your ISP
Spiky ping, sudden disconnectsPacket loss with net_graph or third-party toolsSwitch to a wired connection or contact your ISP
Lag that only happens when moving or shootingChoke via net_graph or in-game performanceLower your rate or adjust video settings for stable FPS
FPS drops when many players are on screenVideo settings and frame timesLower particle and model detail, turn VSync off
Unresponsive controls, delayed shotsReflex Low Latency settingTurn Reflex On or On + Boost if available

net_graph is not available in CS2; use cl_showfps 1 for FPS and your ISP's tools for ping and loss.

How to Optimize Your CS2 Settings

  1. 01

    Open the console

    Press ~ or ` to open the console. If it doesn’t open, go to Steam > Settings > Controller > Advanced and enable the in-game developer console.

  2. 02

    Set a baseline rate

    Type rate 786432 and press Enter. This is the default starting point for most players with a decent connection.

  3. 03

    Check your FPS

    Type cl_showfps 1 to see your FPS in the corner of the screen. Avoid spiky frame times and aim for consistent performance.

  4. 04

    Adjust video settings

    Go to Options > Video and try this preset: VSync off, MSAA off or 2x, shadows low, model/texture low or medium, filtering bilinear or trilinear, shaders low, particles low, ambient occlusion off, FSR off unless GPU-limited, Reflex On.

  5. 05

    Test wired vs. Wi-Fi

    Switch to a wired Ethernet connection and test performance. If your lag improves, your Wi-Fi is likely the issue.

Understanding Network Issues in CS2

CS2 is sensitive to network conditions. If your ISP is throttling your upload speed or your router is dropping packets, you won't get a smooth experience even with perfect settings. Use tools like your ISP's speed test or third-party apps like PingPlotter or Wireshark to get a better idea of your network health.

Should I set cl_updaterate or cl_cmdrate for better hit registration?+

No. Matchmaking in CS2 often ignores cl_updaterate and cl_cmdrate. These commands won’t fix hit registration issues or packet loss.

Do launch options like -novid or -high help with lag?+

Not reliably. Most CS:GO launch options don’t work in CS2 due to Source 2’s architecture. -console is fine, and +fps_max N can cap frames if needed.

Can packet loss be fixed with a better GPU or higher rate?+

No. Packet loss is a network issue, not a GPU or CPU problem. It’s usually fixed by switching to a wired connection or contacting your ISP.

What if I can't switch to a wired connection?+

Try to reduce background traffic on your Wi-Fi (close other apps, restart your router). If your ping is still spiking, the problem might be outside your control.

Once your settings are optimized and your network is stable, try playing CS2 retakes on retakes.gg. The site runs retake servers in Europe with six ranked lobbies, live player counts, and a shared leaderboard. Join from the site or use TeamSpeak at ts.retakes.gg to connect with the community.

Play CS2 retakes

Sources

← All posts