How to Show FPS in CS2

Seeing your framerate on screen is the first step to diagnosing performance problems in CS2. If you do not know your FPS, you cannot tell whether a change helped. There are a few simple ways to display it, and each shows slightly different information.

If your FPS is low or unstable, pair this with how to increase FPS in CS2 and how to fix stuttering.

Method 1: cl_showfps

The simplest option. Open the developer console and type:

cl_showfps 1

This shows a small framerate counter, usually in the top-left. Set it back to 0 to hide it. If your console is not enabled, turn it on in Settings > Game, or see CS2 console commands.

Method 2: The Steam FPS Counter

If you would rather not touch the console, Steam has a built-in overlay counter:

1. Open Steam > Settings > In Game.
2. Set In-game FPS counter to a corner of your choice.
3. Optionally enable "high contrast color" so it is easy to read.

This works across all Steam games, not just CS2, which is handy for comparing performance.

Method 3: Performance Overlays

Third-party tools such as your GPU software (NVIDIA or AMD) can display more detailed overlays including frametimes, GPU load and temperatures. These are useful when you are troubleshooting stutters rather than just checking a number.

How to Read the Numbers

• Average FPS tells you overall performance, but it hides problems.
• Frametime consistency matters more than the headline number. Stutters come from uneven frametimes, not just a low average, which is why a steady 200 FPS feels better than a spiky 300.
• If your FPS is far below your monitor's refresh rate, you are leaving smoothness on the table.

Use the counter as a before-and-after tool: change one setting, then watch how the number and its stability respond.

Takeaway

The fastest way to show FPS in CS2 is cl_showfps 1 in the console; the Steam overlay is the no-console alternative, and GPU tools give deeper detail for troubleshooting. Watch frametime stability, not just the average, and use the counter to measure whether each performance change actually helped.