Valve updates Steam review checklist: developers must launch and play for 5 minutes before submitting for review
Valve has added a mandatory requirement to the Steamworks product build review checklist: developers must use a developer account to launch and run the game under review through the Steam client for at least 5 minutes before they can submit the build for review. Build versions that do not meet this check cannot enter the review process.
The play record must meet one of the following conditions: completed within the past 7 days, or after the current game version was uploaded to the default branch. This change was first discovered on October 26, 2026 by a developer posting on Reddit r/gamedev (including a screenshot discussion of the checklist item “Played Through Steam for 5 Minutes”). Valve has not publicly explained when it went live or why it was introduced. Foreign media such as Automaton and 4Gamers cross-checked the backend rules.
The community and reports generally speculate that this move is aimed at the large number of crude AI-generated games that have recently appeared during Steam Next Fest — many creators submitted directly without performing even basic run tests, significantly increasing the review burden. A similar mechanism appears in Super Mario Maker, which requires creators to clear their custom levels before sharing them, but Steam’s threshold only verifies that the game can run normally for 5 minutes and does not judge overall quality or content.
ABAB AI Insight
After generative tools pushed the marginal cost of game production close to zero, the scarce resource in platform review shifted from content judgment to basic runnability verification. Valve did not ban AI tools themselves (it had previously made clear that it would not set technical barriers), but instead moved the minimum behavioral constraint to the submission stage, turning whether the developer has actually launched that version into an automatically verifiable hard metric. This reduces wasted review capacity while partially shifting verification costs back to the submitter. Historically, UGC platforms have often introduced similar minimum behavioral thresholds during periods of content explosion (such as Mario Maker’s completion requirement); in essence, when supply expands without limit, observable behavior is used to filter out the path of “uploading without any testing.” The current rule does not assess quality, only confirms that the game can launch, making it a low-intensity signal filter; its long-term effect depends on whether subsequent recommendation and review algorithms further adjust their weighting.
ABAB News · Cognitive Law
When generation costs approach zero, platforms first set a minimum observable behavioral threshold.
Review burden spills over: from content adjudication to run verification.
Once low-threshold tools become widespread, verification costs become the new scarcity.