Steam Frame Verification Is No Longer a 90 FPS Club
Steam Frame verification is Valve’s VR game certification label that tells players whether a title runs natively and comfortably on the upcoming Steam Frame headset without major issues or manual tweaking, and the company has now relaxed the performance bar while tightening image clarity expectations for that badge.
Valve originally told developers at Game Developers Conference that native VR games needed to hit a minimum of 90 fps to earn the Steam Frame Verified badge, alongside a separate 30 fps at 1,280 × 720 target for flatscreen titles. That 90 fps requirement was a clear statement of ambition—and a clear warning that ports would need real optimization. But a few months later, without a news post or public fanfare, Valve quietly changed the rules: native VR games can now target 72 fps instead, as long as they render at 1,728 × 1,728 per eye during normal play. On paper, that moves Steam Frame verification from “elite performance tier” toward “good-enough standard,” and that shift is deliberate.
From 90 FPS to 72 FPS: Why Valve Blinked
Valve’s first spec effectively demanded that developers exceed the headset’s own minimum 72Hz refresh rate by around 25%, setting 90 fps as the target for the Steam Frame Verified badge. The intent was obvious: make native VR games feel smoother than competing standalone hardware. The problem is that such a high bar, applied across a fragmented VR market, would slow content down to a trickle. According to Valve’s documentation, developers can now qualify at 72 fps if they hit 1,728 × 1,728 per eye and provide motion-vector and depth data so users can run higher refresh rates via improved reprojection techniques. In other words, Valve traded raw frame rate for a more modern “resolution + reprojection” strategy that leans on the headset’s capabilities instead of forcing every game to brute-force 90 fps.
This is less a retreat and more a recalibration: Valve keeps a high baseline for clarity while accepting that consistent 72 fps plus good reprojection is a fairer ask than strict native 90 fps. The introduction of an ‘Unsupported’ badge for VR games that cannot reach 1,440 × 1,440 per eye shows Valve still wants to warn players when visual quality falls below a threshold, but it deliberately leaves those titles playable on Steam Frame. That signals a platform philosophy: guide, don’t gatekeep.
Developer Reality: Easier Ports, Wider Access
For developers, especially small teams and modders, the change takes Steam Frame verification from intimidating to achievable. The earlier 90 fps requirement was a major hurdle for porting existing native VR games built around a 72Hz baseline. Under the new rules, many titles targeting 72 fps elsewhere can reach Steam Frame Verified with smart optimization and resolution management instead of full-scale rewrites. Valve also explicitly encourages developers to submit motion-vector and depth data, which lets the headset’s reprojection system carry more of the performance load. That is a subtle but important shift: the certification process is no longer just about brute-force rendering, but about whether a game cooperates with the platform’s tech stack.
The Half-Life 2: VR Mod is a good example of how demanding Steam Frame verification still is in practice. The team reports that their mod initially would not start on the headset, then ran with poor performance and many bugs, and only became playable after extensive fixes, frame-timing optimization, and the addition of eye-tracked foveated rendering to cross the threshold. Their latest update, which brought the mod to Steam Frame Verified status, also includes performance boosts on lower-end CPUs, Linux startup fixes, and new features that benefit players on any headset. Lowering the frame-rate target does not mean Valve is handing out badges; it means more teams can realistically aim for them.
Player Experience: More Native VR Games, Messier Labels
For players, the quieter rule change is likely to matter more than any hardware spec sheet. By easing the Steam Frame verification requirements for native VR games, Valve is almost guaranteeing a larger catalog at launch. One source explicitly notes that the new resolution-plus-frame-rate system may give developers an easier path to porting existing Quest content to Steam Frame while discouraging them from gutting resolution just to chase 90 fps. More ports and more native VR games mean fewer early adopters staring at an empty library. At the same time, the introduction of the ‘Unsupported’ tag makes expectations clearer: if a game cannot reach 1,440 × 1,440 per eye, you will see the warning upfront, but you can still buy and run it on Steam Frame anyway.
This open-door policy cuts both ways. On the plus side, Steam Frame users will likely enjoy plenty of experiments, smaller projects, and legacy titles right from the start, instead of waiting for months of ports. On the downside, the badge hierarchy adds complexity. A Steam Frame Verified label signals a polished experience, an Unsupported label signals risk, and everything in between will rely on community reviews to explain performance quirks. The Half-Life 2: VR Mod’s recent optimization update, which fixed shaky headsets on uneven ground, smoothed controller poses, and improved performance on lower-end CPUs, shows how much polish can still arrive after a game hits a headset. Steam Frame’s ecosystem will live or die on how well players learn to read those signals.
Valve’s Long Game: Certification as Platform Strategy
All of this is happening against the clock. Valve has confirmed that Steam Frame is shipping “this summer”, and import logs show pallets of the headset already heading into company warehouses. At the same time, the company has positioned Steam Frame as a device that can stream and natively run your existing Steam library, with SteamOS at its core and the possibility of that operating system appearing on third-party VR headsets later. In that context, Steam Frame verification is more than a badge: it is a template for how Valve wants VR game certification to look if other manufacturers adopt SteamOS as their platform. Relaxing the rules now is about filling the store, but it is also about creating a scalable, realistic standard other vendors could live with.
Lowering the native frame-rate bar while enforcing resolution floors, reprojection data, and clear Unsupported tags is a pragmatic compromise between purity and growth. It accepts that in VR, experience quality is not a single number. It depends on clarity, stability, and smart use of the headset’s tools. If Valve holds this line—and keeps communicating what Steam Frame verification means—players should get a rich, if uneven, launch catalog, and developers will have a reachable target instead of a brick wall. That is the trade Valve has chosen, and, on balance, it is the right one.
