Valve started displaying average framerate data directly on Steam store pages for thousands of Steam Deck games. You can now see how a title performs before you buy it, pulled straight from anonymized player sessions rather than internal benchmarks. The feature launched on November 10, 2026, and the community is already tearing it apart over what that single number actually represents.
Where to find the new framerate data

The information lives under the Steam Deck Compatibility section on any supported game page. Click “Learn more” and you get an average FPS figure plus an expandable histogram. Valve confirmed the rollout covers thousands of titles at launch, with more added as players generate fresh data. Kotaku reports Final Fantasy VII Rebirth averages 37 frames per second on the Steam Deck OLED, while Hades II hits 88 FPS on the same hardware.
This data comes entirely from Steam Deck owners who opted into sharing anonymous performance statistics. Valve is not running its own benchmark suite for this feature. The existing Verified program still labels games based on controller support, text legibility, and baseline performance, but it never published a numeric framerate.
The histogram matters more than the average
A flat number tells you almost nothing about playability. An average of 40 FPS sounds fine until you realize half those frames were rendered during pause menus. Reddit users immediately spotted this flaw in the r/SteamDeck discussion. Several commenters pointed out that the Y-axis label reads “% Session” rather than “% Players”, meaning time spent sitting in a main menu or loading screen inflates the final average. One user noted seeing Crimson Desert Enhanced showing suspiciously high numbers, likely because someone launched the game, sat in the settings menu at 90 FPS, and closed it before actual gameplay began.
The histogram breaks down how frequently a game runs at specific frame rates. If the tallest bar sits at 25 FPS with tiny spikes reaching 90, your actual experience will feel like 25 FPS most of the time. Read the graph, ignore the headline number.
Why Steam Deck HQ says this does more harm than good
Not everyone sees this as a win. Steam Deck HQ argues the new framerate data does more harm than good for buyers. Their concern centers on context. A single average FPS figure ignores the massive impact of TDP limits, FSR upscaling, and custom graphics presets. Someone running a game at 15W with aggressive FSR will produce wildly different numbers than a player capping the device at 10W for battery life. When the store page presents one number without explaining the power profile behind it, buyers treat it as a guaranteed experience.
That mismatch between expectation and reality creates frustration. You see 45 FPS on the store, buy the game, run it at your preferred settings, and get 30. The fault lies with how the metric is presented, not necessarily the hardware.
ProtonDB remains your actual pre-purchase checklist
The new store page data gives you a rough pulse check, but it replaces nothing. ProtonDB stays the database where Steam Deck and Linux users report per-game performance with actual context: which Proton version they used, what launch arguments fixed stuttering, and whether a specific patch broke compatibility. User reviews there include tweak notes that tell you exactly how to hit a stable framerate instead of just showing you what strangers averaged blindly.
Cross-reference both. Use the store page histogram to spot if a game has wild variance or consistent stutters, then jump to ProtonDB to find the settings that smooth it out.
What we make of this update
Transparency is welcome, but execution matters. Valve giving you raw session data without filtering out menu time or documenting the power profiles behind it creates a misleading storefront metric. Treat the average FPS as a rumor, not a promise. The histogram holds actual value if you read it critically, especially the distribution shape. Until Valve normalizes the data collection or lets you filter by TDP and FSR usage, ProtonDB and community testing threads remain the only reliable way to know if a game will actually run well on your specific setup.