How to Show FPS and Ping in CS2: Telemetry HUD and Commands (2026)

Lag, stutter and "my shots didn't register" all start with the same question: was it your frame rate, your ping or the network? CS2 can show you all three on screen — but not with the commands most guides still list. net_graph never made it from CS:GO, and Valve deleted CS2's own cq_netgraph in early 2024. This guide shows the built-in Telemetry HUD that replaced them, every setting and console variable behind it, the cl_showfps counter, how to read missed ticks and network quality, and how to cap your FPS now that it can't be changed mid-match. Checked 2026-10-25.

Turn on the Telemetry HUD

1. Open Settings → Game.

   Scroll to the Telemetry section.

2. Pick a mode for each line.

   Always keeps it on screen; Only in poor conditions shows it when something goes wrong; Never hides it.

3. Set the thresholds.

   The "poor" sliders decide when a line appears in the middle mode — ping counts as poor from 100 ms by default.

4. Play a match and check the readout.

   In the middle mode a line only appears once it crosses its threshold — so if nothing shows, nothing is wrong.

Values: 0 = Never, 1 = Only in poor conditions, 2 = Always. Defaults from Valve's variable list (SteamDB GameTracking-CS2, read 2026-10-25).

The cl_showfps counter

If you only want a frame counter, enable the console (Settings → Game → Enable Developer Console (~) → Yes) and type cl_showfps with a value. Valve's variable list describes it as "Draw fps meter at top of screen":

It needs no cheats and works in matchmaking. Some sites list different meanings for 2–4; the table follows Valve's own description.

What happened to net_graph?

CS:GO's net_graph 1 didn't come to CS2. CS2 launched with its own cq_netgraph, and on 15 February 2024 Valve's notes said: "Deleted cq_netgraph and cq_netgraph_problem_show_auto" and pointed players to cl_hud_telemetry_serverrecvmargin_graph_show instead — a console-only server graph. For everyday play the Telemetry lines above, added the same day, cover it.

Reading ping, missed ticks and network quality

• Ping is your round trip to the server in milliseconds. Steady matters more than low: 40 ms that never moves plays better than 15 ms that jumps to 90.
• Missed network ticks count updates lost to packet loss or jitter. Since 12 November 2024 Valve measures network quality by how often a tick is missed — a few in a busy round is normal, a steady stream is a connection problem.
• The packet-loss buffer in Game settings sets cl_net_buffer_ticks (0–2). Valve's own description: "This value controls the value of cl_interp_ratio, which you should not modify directly." Raise it only if missed ticks are frequent — it trades a little delay for smoother movement.

Cap your FPS — before you join

The in-game cap (fps_max) defaults to 400, the menu cap (fps_max_ui) to 200; fps_max 0 removes the limit. Since 14 August 2025 Valve's notes say fps_max "can no longer be changed while connected to a server", so set it in Settings → Video → Advanced, or with +fps_max in your launch options. A cap you can actually hold in a full fight feels smoother than a high average that collapses in smokes.

• 400default in-game FPS cap
• 200default menu FPS cap
• 100 msping counted as poor by default
• 0–2the packet-loss buffer range

If your numbers are bad

1. Low FPS:

   Lower Ambient Occlusion, Shader and Particle Detail first, update your graphics driver, and close overlays and browsers.

2. FPS drops only in fights:

   Lower the cap to what your PC holds in a busy deathmatch, so frame times stay even.

3. High ping:

   Use a cable instead of Wi-Fi and pause downloads and streams on your network.

4. Missed ticks:

   Check other devices on the network, then try the packet-loss buffer at 1.

Help with performance and play

• A settings and gameplay check: 1-on-1 coaching — from $18.00 an hour.
• Find the rounds you really lost: demo analysis — and the demo review guide.
• Read next: sensitivity and binds.