CS2 net graph commands: show FPS, ping, choke, loss and fix spikes

Show your CS2 FPS, ping, choke and loss on screen with exact net graph commands to diagnose and fix lag spikes.

How to show net graph, ping and FPS on screen in CS2

Start CS2 and open the developer console by pressing the key bound to it, usually ~ or \.

Type net_graph 1 and press Enter to enable the net graph overlay. This shows FPS, ping, choke, and packet loss in real-time.

You can change the net graph position using net_graphpos 1, 2, or 3 for left bottom, bottom center, or right bottom positions.

Adjust font size and style with net_graphproportionalfont 0 or 1 depending on your preference for readability. Before you commit to anything, it is worth looking at high packet loss low ping.

If net graph information clutters the screen, reduce its size with net_graphproportionalfont 0 to switch to a smaller font. The default font can be hard to read on smaller monitors or in fast action, so toggle to see which works best.

You can disable the net graph anytime by typing net_graph 0 in the console. This removes the overlay but keeps your previous settings intact for quick toggling during matches.

1. Open CS2 and enable developer console in settings if disabled.
2. Press the console key (~ or \).
3. Type net_graph 1 and press Enter to show net graph.
4. Adjust position with net_graphpos [1-3].
5. Toggle font style with net_graphproportionalfont [0 or 1].

What the net graph readings mean for lag and performance

Ping is the time in milliseconds it takes for your PC to communicate with the game server. Typical values range from 20 to 100 ms depending on server distance and connection quality. If that sounds like your situation, read up on triple buffering on or off for gaming next.

Choke represents how many packets your client is trying to send but the server is unable to process due to rate limits or congestion. Values above 1-2% can cause rubber-banding and perceived lag.

Loss counts packets lost in transmission. Even 0.1-0.5% can lead to stuttering or missed actions.

FPS is frames per second your PC renders. CS2 feels smooth above 60 FPS, anything lower can cause choppiness. Before you commit to anything, it is worth looking at reducing packet loss in cs2.

High ping with low choke and loss suggests network latency. High choke or loss suggests issues sending or receiving data packets reliably.

Ping can vary widely based on your physical distance to the server and your ISP's routing quality. For example, a player in Europe connecting to a US server may see pings above 100 ms regularly, causing noticeable lag.

Choke can spike momentarily when your network bandwidth is saturated, such as during downloads or streaming on the same connection. This causes the net graph choke percentage to jump and gameplay to feel jerky. People in this spot often ask about how to adjust the manual choke as well.

FPS drops often coincide with CPU or GPU bottlenecks. Running CS2 on older hardware may show FPS dipping below 60 during intense scenes, causing stutter even if network stats look fine.

• Ping: 20-100 ms normal; spikes above 150 ms cause lag.
• Choke: Ideally 0%; above 3% causes rubber-banding.
• Loss: Should be 0%; even 0.5% harms gameplay.
• FPS: Above 60 FPS feels smooth; below 30 feels laggy.

Why CS2 lag can happen even with good ping

CS2 can suffer lag due to choke and loss spikes even if the ping is steady and low.

Choke spikes occur when your client sends more packets than the server can handle or your network buffers overflow. The other half of this decision is lower ping in cs2.

Packet loss happens when data is dropped en route, causing the server and client to resync and resulting in momentary freezes.

Sub tick feeling occurs when game updates are delayed or uneven even with 60 FPS, caused by network jitter or client processing delays.

Packet loss can be caused by faulty hardware like old routers or bad Ethernet cables. Even with good ping, these hardware issues cause packets to drop and lag spikes to appear. Before you commit to anything, it is worth looking at cs2 cl_interp_ratio input delay.

Network jitter, which is the variability in packet arrival times, can cause inconsistent game updates. This makes movement and shooting feel unreliable, even if average ping is good.

Sometimes software conflicts, such as over-aggressive antivirus or firewall settings, can delay or block packets causing lag spikes. Temporarily disabling these can test if they're the cause.

• Good ping but rising choke causes rubber-banding.
• Loss spikes freeze player actions briefly.
• Network jitter disrupts smooth game updates.
• Too low FPS combined with network issues worsens lag.

How to fix CS2 ping spikes and choke loss counters

Identify the source of ping spikes by monitoring net graph and running ping tests to the CS2 server.

Reduce network congestion by closing background apps and using a wired Ethernet connection over Wi-Fi.

Limit choke by lowering your client’s outgoing packet rate with the cl_updaterate command or manually adjusting choke to limit packet burst.

Use QoS settings on your router to prioritize CS2 traffic if your router supports it.

If spikes persist due to ISP routing or server distance, consider a game booster like GearUP to reroute traffic.

Monitor your net graph during gameplay to spot exactly when spikes occur. If spikes appear only during certain times, they may relate to other devices on your network or scheduled tasks on your PC.

Adjust cl_cmdrate and cl_updaterate to lower values such as 30 or 40 if your connection is unstable. This reduces how many packets your client sends and receives, easing choke but also reducing update frequency.

If router QoS is not an option, prioritize CS2 traffic by temporarily disconnecting other devices or scheduling heavy downloads outside gaming sessions to lower network strain.

1. Check net graph for ping spikes and choke/loss values.
2. Close background internet-heavy apps.
3. Switch to wired Ethernet if possible.
4. Lower cl_updaterate to reduce choke (start at 64).
5. Set manual choke if needed (see next section).
6. Try router QoS for CS2 traffic.
7. Test with GearUP booster for routing issues.

How to adjust a manual choke in CS2

CS2 allows you to set a manual choke percentage to limit how many packets your client sends per second.

Use the console command cl_manualchoke [value] where value ranges from 0 (auto) to 100 (maximum choke).

Start with small values like 10 or 20 to ease packet bursts and observe if choke and loss counters stabilize.

Manual choke reduces packet flood but can increase input delay, so balance it carefully.

Reset to automatic by setting cl_manualchoke 0 if issues worsen.

Manual choke can be useful when automatic settings fail to control packet bursts during intense actions like multiple kills or explosions.

Start with cl_manualchoke 10 and monitor the net graph. If choke and loss improve but input delay increases noticeably, reduce the value to 5 or disable it to find a better balance.

Keep in mind manual choke adds input delay because it holds packets back. If you notice your shots register late or movement feels sluggish, dial back the choke value or turn it off.

1. Open console in CS2.
2. Type cl_manualchoke 10 and press Enter.
3. Play and watch net graph choke and loss.
4. Adjust value up or down to find balance.
5. Set back to 0 to disable manual choke.

Why CS2 feels sub tick even with 60 FPS

Sub tick feeling means game responsiveness feels below the server’s tick rate even if FPS is high.

CS2 runs at a server tick rate around 64 ticks per second, but client updates need to match this closely for smooth gameplay.

Network jitter, packet delay, or uneven frame pacing can cause the game to feel less smooth than FPS suggests.

Fixing sub tick feeling requires ensuring stable ping, minimal choke/loss, and consistent frame timing.

Tools like net graph help diagnose if network or frame timing is the root cause.

Even with 60 FPS, frame times can be uneven causing micro stutters. Using a frame time graph or tools like MSI Afterburner helps check if frames render consistently.

CS2's server tick rate fixes the game state updates at 64 times per second. If your FPS is just above 60 but not stable, some frames miss syncing with server ticks causing a sub tick feel.

Improving CPU performance and closing background apps can help stabilize frame pacing. Also, running the game in fullscreen mode often reduces input lag and improves timing consistency.

Questions people still ask

I have tested CS2 net graph commands extensively to diagnose lag and confirm choke adjustment helps smooth gameplay.