How to Show FPS in CS2: Every Method That Works

Method 1: The cl_showfps command

If your console doesn't open when you press ~, enable it first: Settings → Game → Enable Developer Console → Yes.

The command takes several values, each showing progressively more detail:

cl_showfps 1 is what you want for a quick check. cl_showfps 2is more useful when you're diagnosing stutter, because a game can average 200 FPS and still feel terrible if frame times spike — the min/max readout exposes that where a plain counter won't.

If you'd rather toggle it with a key than type it, bind it: bind f9 "toggle cl_showfps 0 1" puts it on F9. More detail on values and related commands lives on our cl_showfps command page.

Method 2: The telemetry HUD (the built-in option)

CS2 shipped with a proper performance overlay that doesn't need the console at all — and unlike the console counter, it's designed to be left on permanently without cluttering your screen.

1. Open Settings → Game and scroll to the Telemetry section.
2. Set "Show frame time and FPS" to Always.

A compact readout appears at the top-right of your HUD showing average FPS and frame time. The same section has toggles for ping, packet loss, and server tick health, each of which can be set to show always or only when there's a problem — genuinely useful, since a red packet-loss warning appearing mid-match tells you instantly whether that awful duel was your aim or your ISP.

For a permanent setup, this is the method to use. It survives restarts, doesn't depend on the console, and it's what the game itself expects you to use.

Method 3: Steam's FPS counter

Steam has its own overlay counter that works in any game:

1. In the Steam client, open Steam → Settings → In Game.
2. Find In-game FPS counter and pick a corner position.
3. Optionally tick the high-contrast option so it's readable against bright maps.

It's small, costs effectively nothing in performance, and works without touching CS2's settings. The downside is it only shows raw FPS — no frame times, no network info — so it's a monitoring tool, not a diagnostic one.

NVIDIA and AMD overlays do the same job, but stacking third-party overlays on a competitive shooter is asking for input overhead. If you only want a number in the corner, Steam's counter or the telemetry HUD does it cheaper.

Method 4: Launch option (on from boot)

You can have the counter active from the moment the game loads by adding it to launch options — right-click CS2 in your Steam library, Properties → Launch Options — but note the syntax:

+cl_showfps 1

The + prefix matters. It tells the engine to execute the console command at startup; without it the line does nothing, which is why half the people who try this method think it's broken. If you're setting launch options anyway, our launch options guide covers which ones actually still do something in CS2 and which are CS:GO leftovers.

What about net_graph?

net_graph 1was removed in CS2 — it doesn't exist, and no config line will bring the old text readout back. You have two replacements:

• The telemetry HUD (Method 2) covers everything net_graph told you — FPS, ping, loss — in a cleaner format.
• cq_netgraph 1 in the console gives you an actual graph again: a compact waveform in the top-right during matches, colour-coded so blue/green means a healthy connection and red/yellow flags packet loss or jitter.

Between those two, there's no real reason to miss the original.

What should your FPS actually be?

A number in the corner is only useful if you know what you're looking for. Rough guide for CS2:

• Below your monitor's refresh rate (e.g. under 144 on a 144 Hz panel): worth fixing. You're not seeing what your monitor can show.
• 1.5–2x your refresh rate: the comfortable competitive zone. Frame delivery stays smooth even in smoke-heavy retakes where FPS dips hardest.
• Wildly fluctuating: worse than a lower stable number. Watch the frame-time readout in cl_showfps 2 or the telemetry HUD — consistent frame pacing beats a higher average.

CS2 is noticeably more demanding than CS:GO was, and the usual FPS killers are smokes, mollies, and player models stacking in execute scenarios — exactly the moments you can least afford a dip. If your counter is telling you bad news, our FPS optimization guide walks through the settings, launch options, and system-level fixes that actually move the number in CS2.