Steam’s in-game performance monitor helps investigate local rendering problems. It can show frame-rate and hardware information, but it does not measure your connection to a game server. Use it to answer “did the game stop producing frames smoothly?” while collecting network evidence separately.
That separation is useful when movement feels uneven despite a reassuring ping number. A pause in local rendering, a delayed online update and a Remote Play stream interruption can feel similar. They need different observations before you choose a fix.
Turn on the monitor for the game you are testing
Valve documents the monitor in Understanding the In-Game Overlay Performance Monitor. Look in Steam’s In Game settings for its performance-monitor controls and choose a readable detail level. Available metrics vary by operating system and supported hardware, so an absent field is not a zero reading.
If no overlay appears, check the global and per-game overlay choices before troubleshooting the network. Valve’s overlay guide describes those controls. Some games, launch paths or software interactions need their own supported troubleshooting; do not assume an invisible monitor proves a connection problem.
Collect two observations, not one diagnosis
For a local observation, note the monitor’s frame behavior at the moment the symptom occurs. For an online observation, use the game’s own network display if it provides one. Keep their names and units in your notes. FPS and milliseconds to a server are different quantities.
For example, record “camera motion froze briefly; the local minimum FPS fell; in-game ping stayed near its previous reading.” That does not prove the CPU caused the pause. It does establish that a router-only explanation would ignore part of the evidence. Likewise, a network warning with steady rendering deserves investigation even if the local hardware monitor looks calm.
Run a comparison you can interpret
- Choose a repeatable scene. Use a training area, replay or other suitable noncompetitive section. Avoid comparing a quiet menu with a busy multiplayer match.
- Record the context. Note the game, display settings, frame-generation state where applicable, background applications and whether the game is being played locally or streamed.
- Observe the symptom. Keep a brief note of when it happens and which visible metrics change. A screenshot taken after the event may miss the change.
- Change one local factor. Close a safe background task or compare a lower game graphics setting. Keep the connection and scene as similar as possible.
- Repeat before concluding. A single smooth pass is encouraging, but can reflect a different workload. Look for the same change across comparable attempts.
- Test the network separately if needed. Pause the game or its downloads before a baseline connection check, then return to the original workload.
This procedure is a diagnostic plan, not a benchmark we performed on your game. It deliberately avoids promising that a particular utilisation percentage identifies one failed component.
Why an average FPS number can miss a pause
Valve’s monitor distinguishes average frame behavior from a minimum indicator intended to highlight unusually long frames. Frame generation can also produce a displayed frame rate different from the underlying game’s rate. Read the labels together instead of comparing two screenshots with different rendering settings.
Do not interpret the minimum indicator as an internet packet-loss counter. Nor does high CPU or GPU activity, on its own, establish a defect. The useful question is whether the workload and symptom change together under a controlled comparison.
Asset loading, transitions and menus can behave differently from steady play. Note where the pause occurs. A repeated issue in the same section gives game support a more useful starting point than an unexplained claim that “the internet causes low FPS.”
When connection checks become relevant
If local motion remains smooth but other players jump or a game reports network trouble, investigate the application connection. Our guide to Roblox’s performance statistics illustrates why a game’s own network and rendering metrics should be read separately; other games use different labels and calculations.
A browser internet speed test can describe transfers to its measurement endpoint. It cannot certify a match route, count that game’s UDP losses or explain a local rendering pause. Check how the browser measurements work before comparing them with game telemetry.
If the problem follows household uploads or downloads, use the loaded-latency comparison as a separate experiment. It helps observe additional HTTP delay under load, while the in-game record shows whether your actual symptoms occur under the same conditions.
Escalate with the right evidence
Send game or platform support a concise description of the scene, hardware, software versions and repeat steps. Include the graphics setting you changed, what the local monitor showed and any separate network warning. State whether the issue also occurs outside an online match, where that comparison is available.
If the game is being streamed from another computer, collect the streaming application’s statistics too. Local game FPS, video delivery and remote match connectivity are separate layers. Keeping those layers visible makes it easier to choose the next test and avoids spending money on a faster connection to solve the wrong problem.