CS2 Telemetry (Net Graph): How to Enable, Read and Fix Performance Issues
The CS2 replacement for net_graph: menu settings, all cl_hud_telemetry commands with defaults, what every number means, ready presets, binds and how to fix what it shows
Counter-Strike 2 has no net_graph. If you're looking for it, the CS2 version is called Telemetry: a small overlay in the HUD that shows FPS, frame time, ping, packet loss and jitter in real time.
It's not just a nicer look. Telemetry tells you whether the "lag" you feel comes from your PC, your connection or the server. In this guide I show how to turn it on, what every number means, which settings to use, and what to do when the numbers go red.
CS2 Net Graph Is Now Telemetry: What Changed
In CS:GO net_graph 1 put a block of numbers at the bottom of the screen. CS2 rebuilt it as Telemetry: separate small indicators you turn on one by one, and each of them can stay hidden until something goes wrong. net_graph doesn't exist in CS2.
Average FPS and the worst recent frame time in ms. Problems on your PC.
Round trip latency to the server in ms.
Percentage of ticks missed because of loss or late delivery, up and down.
Raw packet loss, jitter and a live jitter graph.
How to Turn On Telemetry in CS2
- Open Settings (gear icon) → Game.
- Scroll down to the Telemetry section.
- For each item choose Never, If conditions are poor or Always.
| Menu item | What it shows |
|---|---|
| Show frame time and FPS | The worst recent frame time in ms and the current average FPS |
| Frame time warning threshold | Above this frame time conditions count as poor |
| Show ping | Round trip latency to the server in ms |
| Show network problems (ticks missed due to loss / jitter) | Percentage of ticks not available in time, upstream and downstream |
| Network tick miss rate warning threshold | Above this miss rate conditions count as poor |
| Use the detailed network quality display | A second line with raw packet loss and jitter |
| Show network jitter / misdelivery graph | Live jitter graph, loss and reordering highlighted |
That's all, the numbers appear in your HUD right away.
CS2 Telemetry Commands
The same settings from the console (turn it on in Settings → Game → Enable Developer Console → Yes, open with ~). All show commands use the same values: 0 never, 1 only if conditions are poor, 2 always.
| Command | Default | Values | What it does |
|---|---|---|---|
cl_hud_telemetry_frametime_show |
1 | 0 / 1 / 2 | Frame time and FPS in the HUD |
cl_hud_telemetry_frametime_poor |
100 | 1 to 100 ms | Frame time above this is "poor" |
cl_hud_telemetry_ping_show |
1 | 0 / 1 / 2 | Ping in the HUD |
cl_hud_telemetry_ping_poor |
100 | ms | Ping above this is "poor" |
cl_hud_telemetry_net_misdelivery_show |
1 | 0 / 1 / 2 | Percentage of user commands and server snapshots missed because of the network |
cl_hud_telemetry_net_misdelivery_poor |
2 | 0 to 100 % | Miss rate above this is "poor" |
cl_hud_telemetry_net_detailed |
0 | 0 / 1 / 2 | Breakdown of loss, late delivery and peak jitter |
cl_hud_telemetry_net_quality_graph_show |
0 | 0 / 1 / 2 | Graph of packet jitter and loss / reordering |
cl_hud_telemetry_serverrecvmargin_graph_show |
0 | 0 / 1 / 2 | Graph of how early or late your commands arrive at the server; 1 shows it only when there are command queue problems |
So by default CS2 already shows FPS, ping and network problems, but only when they're poor. The default "poor" values are generous: 100 ms frame time is 10 FPS, 100 ms ping, 2% misses. Lower them if you want earlier warnings, see best settings.
How to Read CS2 Telemetry
FPS vs Frame Time
FPS is an average. The frame time in telemetry is the worst recent frame in milliseconds. If FPS says 300 but the frame time jumps from 3 ms to 30 ms, you feel stutter. That's why frame time tells you more about smoothness than FPS. For reference: 4.2 ms is 240 FPS, 6.9 ms is 144 FPS, 16.7 ms is 60 FPS.
Ping and Jitter
Ping is the delay to the server and back. Jitter is how much it jumps. A steady 40 ms feels better than ping that jumps between 20 and 80, even if the average looks lower. The detailed line and the graph show jitter, the plain ping number doesn't.
Network Problems: Missed Ticks, Loss and Late Delivery
This is the most useful network number. The game describes it as the percentage of ticks that are not available at the time they're needed because of loss or late delivery, shown for both directions: up to the server and down from it. A lot of misdeliveries get corrected automatically, the number only counts the ones that weren't. Climbing values mean rubber-banding, ghost shots and teleporting players.
- Problem upstream (your commands to the server): usually your side, Wi-Fi, a busy upload.
- Problem downstream (snapshots from the server): your connection, your ISP or the route to the server.
Network Quality Graph
A live jitter graph with loss, reordering and big jitter spikes highlighted. You don't need it all the time, but it's great when you test a new router, cable or ISP: a flat line is good, colored spikes are what you feel as micro lag.
Server Recv Margin Graph
The graph of how early or late your commands reach the server before they're executed. Mostly for debugging. If it shows problems while your ping and misses look fine, the issue may be on the server side.
Best CS2 Telemetry Settings
You don't need a wall of numbers all the time. Three setups you can paste into the console or your autoexec:
Minimal Always On
FPS and ping always visible, network problems only when they happen. Clean HUD for every match.
cl_hud_telemetry_frametime_show 2 cl_hud_telemetry_ping_show 2 cl_hud_telemetry_net_misdelivery_show 1 cl_hud_telemetry_net_quality_graph_show 0
Show Only When Poor
Everything hidden until something goes wrong, with stricter thresholds so it warns you earlier.
cl_hud_telemetry_frametime_show 1 cl_hud_telemetry_frametime_poor 20 cl_hud_telemetry_ping_show 1 cl_hud_telemetry_ping_poor 80 cl_hud_telemetry_net_misdelivery_show 1 cl_hud_telemetry_net_misdelivery_poor 1 cl_hud_telemetry_net_detailed 1 cl_hud_telemetry_net_quality_graph_show 1
Full Debug
Everything on, for testing hardware, settings or a laggy connection. Not pretty, but you see everything.
cl_hud_telemetry_frametime_show 2 cl_hud_telemetry_ping_show 2 cl_hud_telemetry_net_misdelivery_show 2 cl_hud_telemetry_net_detailed 2 cl_hud_telemetry_net_quality_graph_show 2 cl_hud_telemetry_serverrecvmargin_graph_show 2
Suggested Thresholds
| Metric | Default | Suggested "poor" | Why |
|---|---|---|---|
| Frame time | 100 ms | 15-20 ms | Above this the game feels choppy even if FPS looks fine |
| Ping | 100 ms | 80-100 ms | Delay becomes noticeable in duels |
| Network misses | 2 % | 1 % | Even small loss causes rubber-banding and ghost shots |
These aren't strict rules, just safe values for competitive play. On a 240 Hz monitor you can go even lower with the frame time, for example 10 ms.
Telemetry Binds and Scripts
Toggle With One Key
bind "c" "toggle cl_hud_telemetry_frametime_show 2 0"
Press C to show or hide FPS. Good if you want a clean HUD most of the time but quick checks when you need them.
Show While Holding a Key
alias "+netstat" "cl_hud_telemetry_frametime_show 2; cl_hud_telemetry_ping_show 2; cl_hud_telemetry_net_detailed 2" alias "-netstat" "cl_hud_telemetry_frametime_show 1; cl_hud_telemetry_ping_show 1; cl_hud_telemetry_net_detailed 0" bind "c" "+netstat"
Hold C to see FPS, ping and the detailed network line, release to go back to "only if poor".
Alias Toggle for Longer Chains
alias "telemetry" "tm_on" alias "tm_on" "cl_hud_telemetry_frametime_show 2; cl_hud_telemetry_net_quality_graph_show 2; alias telemetry tm_off" alias "tm_off" "cl_hud_telemetry_frametime_show 1; cl_hud_telemetry_net_quality_graph_show 0; alias telemetry tm_on" bind "c" "telemetry"
More ready scripts: custom telemetry scripts and CS2 useful scripts.
Fix What Telemetry Shows
| What you see | Likely cause | What to do |
|---|---|---|
| Frame time spikes, ping and misses fine | Your PC | Fullscreen, right refresh rate, sync settings, shader cache, drivers |
| Ping high but steady | Distance to the server | Lower Max Acceptable Matchmaking Ping |
| Ping jumps, jitter high | Wi-Fi, busy network, router | Cable instead of Wi-Fi, pause downloads, restart the router |
| Misses upstream | Your upload: Wi-Fi, uploads, streams | Cable, stop uploads and cloud sync |
| Misses downstream | Your connection, ISP or route | Cable, router QoS for your PC, cl_net_buffer_ticks 1 |
| Everything fine, still feels laggy | Server or frame pacing | Try another server, check sync and refresh rate |
Spiky Frame Time
If the frame time jumps like a heartbeat, it's your PC. Full steps in how to fix FPS drops and stuttering in CS2: fullscreen, refresh rate, V-Sync, G-Sync and Reflex, shader cache, drivers. Also check temperatures, an overheating CPU or GPU drops clocks and frame time jumps.
High Ping, Jitter or Network Misses
Use a cable instead of Wi-Fi, stop downloads and streams, restart the router. If misses stay, the setting Buffering to smooth over packet loss / jitter (cl_net_buffer_ticks 1) trades a little delay for a smooth game. Everything about ping in how to lower ping in CS2.
cl_showfps and Other Ways to Test Performance
Telemetry is the main tool, but CS2 still has cl_showfps. The game describes it as an FPS meter at the top of the screen with four modes:
| Command | What it shows | Use it for |
|---|---|---|
cl_showfps 1 |
FPS | Quick check |
cl_showfps 2 |
Smoothed FPS with frame time stats | Steadier number, basic profiling |
cl_showfps 3 |
Server frame time in ms | Checking server performance |
cl_showfps 4 |
FPS and a log to file | Benchmarks and comparing settings |
cl_showfps 4 writes a .csv file with FPS and frame time into the game folder:
...\common\Counter-Strike Global Offensive\game\csgo\
Run the same map and route before and after a change and compare the logs, that's the honest way to see if a tweak helped. More about every FPS counter in how to show FPS in CS2.
Third-Party Overlays
MSI Afterburner with RivaTuner shows FPS, frame time, temperatures and GPU load. CS2 blocks programs that draw over the game by default, so it needs the launch option -allow_third_party_software, which turns off the protected mode. For everyday play the built-in telemetry is enough.
Conclusion
Telemetry replaced net_graph and it's more useful: frame time for your PC, ping and jitter for the connection, network misses for loss in both directions. Keep it on "only if poor" with stricter thresholds, and it warns you exactly when something breaks. When you feel lag, look at telemetry first and you'll know where to dig.
CS2 Telemetry FAQ
Is there net_graph in CS2?
No. The CS2 replacement is Telemetry: Settings → Game → Telemetry, or the cl_hud_telemetry_* commands.
How do I show FPS and ping all the time?
cl_hud_telemetry_frametime_show 2 and cl_hud_telemetry_ping_show 2, or set both to Always in the menu.
Does Telemetry lower FPS?
Not noticeably. It shows numbers the game tracks anyway and runs no extra process like third-party overlays. On a very weak PC the always-on graph may cost a frame or two.
What matters more, FPS or frame time?
Frame time. Even at high FPS, jumping frame times feel like stutter.
What does "network problems" in telemetry mean?
The share of ticks that didn't arrive in time because of loss or late delivery, for upload and download separately. Above 1-2% you feel it.
Why do I have packet loss but normal ping?
Ping only measures delay. Loss means data doesn't arrive at all, which causes rubber-banding and ghost shots even with low ping.
What causes jitter in CS2?
Usually Wi-Fi, a busy home network, the router or ISP routing.
Where are the cl_showfps 4 logs saved?
As a .csv file in ...\Counter-Strike Global Offensive\game\csgo\.


