The Steam client overlay got a recent patch [Tomshardware] that introduced frame-level granularity like distinguishing between native frames and those generated by DLSS/FSR, alongside real-time readings of CPU load, RAM usage, clock speeds, and frame timing graphs. Those features have already transformed Steam’s HUD into one of the most comprehensive in-game instruments—effectively matching tools like MangoHud and MSI’s RivaTuner.

A beta was released, but quickly rolled back, that claimed to be better than Task Manager. The claim was that Task Manager can be inaccurate because it measures GPU usage on a per-process basis and relies on the GPU driver to report statistics according to the WDDM specification. Games that split work across multiple processes can therefore have portions of their GPU activity missed, and certain workloads can appear less intensive than they actually are. By aggregating usage across all related processes, Steam’s overlay purported to give a fuller and more precise picture of a game’s GPU demands.