CS2 FPS Command: How to Show FPS in CS2 (2026)

Every CS2 FPS Counter Method at a Glance

Use the smallest tool that answers your question. Steam is ideal for a clean number, cl_showfps gives an immediate readout, and CS2 Telemetry helps separate a slow PC from a poor connection.

Run only one counter at first. Two overlays can overlap, report averages over different time windows, or add unnecessary capture hooks. Once you know which method you prefer, disable the others and keep that readout in the same corner for every benchmark.

Show FPS in CS2 via Steam Overlay

Steam’s counter is the quickest option when you only need the frame rate. It works without the CS2 console and stays enabled across launches. Because the setting belongs to Steam, it can appear in other games too.

1. Open Steam, select Steam in the top-left corner, then choose Settings.
2. Select In Game and find the In-game FPS counter option.
3. Choose a screen corner for the counter.
4. Enable high-contrast color if the number disappears against the map.
5. Launch or restart CS2 and check the selected corner.

You can also open the Steam Overlay with Shift+Tab during a match, use its Settings control, and reach the same In Game options. If nothing appears, confirm that Enable the Steam Overlay while in-game is turned on for both Steam and CS2.

The high-contrast option changes the number to a brighter color, which helps on light areas of maps. The Steam counter does not explain why FPS fell, and it does not replace ping or packet-loss diagnostics. Think of it as a clean dashboard number, not a troubleshooting panel.

Show FPS via CS2 In-Game Telemetry

CS2’s official Telemetry HUD is the best all-round method. It puts frame rate and network conditions in one place. Each item can stay hidden, remain visible, or appear only when conditions cross a warning threshold.

1. Open CS2 Settings.
2. Select Game, then scroll to Telemetry.
3. Set Show frame time and FPS to Always.
4. Set Show ping to Always if you want FPS and ping together.
5. Enable network-problem information when troubleshooting loss or jitter.

Do not treat every hitch as low FPS. If frame time remains clean while ping or the network indicator turns red, changing graphics settings will not fix the problem. Telemetry makes that distinction much clearer than a basic FPS number.

The frame-time value is especially useful because one slow frame can feel like a hitch even while the average FPS looks healthy. Set the warning threshold slightly above the slowest frame time you normally see. That way, an unusual spike becomes visible without keeping every graph on screen.

Valve’s network-quality readout measures conditions that actually interfere with game ticks, not simply every reordered packet. Detailed mode can expose raw loss and jitter, while the basic view stays compact. Use Always during a test, then switch noisy indicators to Poor when you only want warnings.

Show FPS via Developer Console With cl_showfps

The direct CS2 FPS command is cl_showfps 1. Enable the console under Settings > Game > Enable Developer Console, then press the tilde key. The CS2 developer console setup also accounts for keyboard-layout issues and the launch-option fallback.

The counter appears in the upper-left area. Enter cl_showfps 0 to hide it. Unlike an external overlay, this output comes from the engine and is useful when you are already testing console changes.

If the number does not appear, type the command again without quotes and confirm that the console accepted it. A config file, practice preset, or server script can change the variable later. Test from the main menu and again after joining a match before assuming the command failed.

cl_showfps Modes 1 to 4

The extra values expose different engine readouts. Mode 1 is the dependable player-facing counter, while modes 2 to 4 are more useful during testing. If an update changes a label, the console description remains the final check.

Mode 2 smooths the FPS reading, which makes broad trends easier to follow than an instant number. Mode 3 reports server milliseconds, and mode 4 adds FPS-oriented logging. For everyday use, choose mode 1 for a simple counter and Telemetry for diagnosis.

Bind cl_showfps to a Key

A toggle bind makes the counter easy to show during a benchmark and hide during a match. The alias switches between the enabled and disabled values each time the key is pressed.

Replace F10 with a free key. Avoid keys already used for screenshots, purchases, voice chat, or utility. To remove the bind, open the keyboard settings or enter unbind F10.

Use a toggle only when you genuinely switch the counter during play. If it should always remain visible, an autoexec line is simpler and less likely to conflict with another bind. Keep a short comment beside custom commands so you remember why they exist months later.

Keep the FPS Counter On Across Sessions

The Steam and Telemetry methods already persist. A persistent console counter belongs in autoexec.cfg, using the correct CS2 config and autoexec structure.

A shorter alternative is the Steam launch option below. Use it only when you want the counter on every launch, since the command will keep returning until the launch option is removed.

If an autoexec does not load, check that Windows did not save it as autoexec.cfg.txt and remove duplicate lines that reset cl_showfps. Only functional CS2 launch options should remain in the startup configuration.

Show FPS and Ping Together in CS2

Use Settings > Game > Telemetry and set both frame time/FPS and ping to Always. This keeps both values visible and can add network-quality information when packet loss or jitter affects play.

The official replacement is the Telemetry HUD. Its receive-margin graph focuses on a narrower network timing question, not a recreation of the old CS:GO panel. The menu provides frame time, FPS, ping, missed-tick information, and optional packet-loss and jitter details without relying on an undocumented cq_netgraph_summary command.

Watch the values during the exact moment a hitch occurs. A red frame-time warning with normal ping points toward rendering, CPU scheduling, drivers, or a background task. A clean frame with rising ping points toward routing. Network-quality warnings with stable ping can still expose jitter or missed ticks.

If you need the receive-margin graph for a focused test, use the Telemetry control instead of presenting it as the old net graph. The graph answers a narrower networking question and can clutter a normal match, so leave it off once the investigation is complete.

• Frame-time spike: investigate the PC or game workload.
• Ping spike: investigate the route or server distance.
• Network warning: investigate loss, jitter, or Wi-Fi.
• All values stable: the hitch may need deeper capture.

Show FPS via NVIDIA or AMD Software

Driver overlays can combine FPS with GPU utilization, clock speed, temperature, and latency. They are more useful for hardware testing than a match counter, but overlays can introduce their own conflicts. Enable only the metrics you need.

If an overlay does not detect CS2, update the driver app, confirm that its in-game overlay is enabled, and restart the game. NVIDIA users who are also tuning the driver can follow our NVIDIA settings for CS2 without mixing every change into the same benchmark.

When comparing overlay results, use the same sampling period. A driver overlay may average FPS differently from cl_showfps or Steam, so small disagreements are normal. Large differences usually mean one counter is reading a menu, background window, or different time window than the others.

Disable detailed GPU metrics after testing if the overlay causes visual clutter or input problems. Keep only the values you still use.

How to Cap Your FPS With fps_max

The command fps_max controls the game’s frame-rate cap. For example, fps_max 300 targets a 300 FPS ceiling, while fps_max 0 removes the cap. A sustainable cap can reduce heat and frame-time swings, but the best value depends on the PC and monitor.

Frame-rate ceilings belong to CS2 FPS cap testing, where refresh rate, latency, menu caps, and benchmark comparisons can be evaluated together.

Check the cap with the same counter used for the uncapped run. If FPS sits against the limit with fewer spikes, the cap may be doing its job. If it frequently falls well below the target, the system cannot sustain that ceiling and needs a lower cap or performance work.

Related: How to Boost FPS in CS2

An FPS counter measures performance but does not improve it. If the result is low, start with fullscreen, V-Sync off, reduced anti-aliasing, sensible shadow settings, clean background processes, and stable temperatures. Change one category at a time so the counter shows what actually helped.

• Compare average FPS and frame-time spikes, not one peak number.
• Use the same map, player count, and practice route.
• Check CPU and GPU temperatures during a full session.
• Keep Boost Player Contrast and useful dynamic shadows.
• Restart CS2 after renderer or driver changes.

A low counter reading leads into the CS2 FPS optimization workflow, while a broader CS2 settings baseline covers the related video categories.

Save the original result before tuning. Test one group, such as advanced video, background software, or a driver option, then repeat the same route. If the average rises but frame-time spikes become worse, revert the change. Competitive smoothness depends on the slow frames as much as the headline FPS.

Conclusion

Use Steam for a clean FPS number, cl_showfps 1 for a quick console check, and Telemetry when diagnosing frame-time or network problems. Measure a repeatable workload before changing settings.

Frequently Asked Questions