Valve is changing the checks developers must complete before putting a game through Steam’s release-review process, responding to a queue that has stretched far beyond its usual target. The company says new-title reviews are intended to take roughly three to five days, but some are currently taking as long as 12 business days.

That is not a minor scheduling inconvenience for a small studio. A Steam launch often sits at the center of a tightly timed campaign involving a trailer, wishlists, community posts, creator outreach and a promised release date. When approval arrives late, the work does not simply move to a new day on the calendar: player expectations have already been set, and the attention generated before launch can be difficult to recapture.

Valve’s immediate answer is less glamorous than a sweeping new content policy. It is asking developers to perform a handful of practical, platform-specific checks before submitting builds. The goal appears to be reducing avoidable follow-up reviews, so reviewers can spend less time discovering basic setup issues that a developer could have caught.

The measures arrive amid a sharp rise in game submissions and wider concern about games built or assembled rapidly with generative AI tools. That broader context matters, but the new requirements themselves are about whether a submitted game works correctly within Steam’s ecosystem—not a declaration that every game using AI is defective or that AI use alone is responsible for the queue.

The new five-minute rule is about the player’s actual route into a game

The clearest new requirement is also the most fundamental: developers must run their game through Steam for at least five minutes before review. On its face, that sounds like a checkbox so obvious it could be printed on a sticky note. In practice, it targets a meaningful distinction between launching a program directly on a development machine and launching it the way a customer will after downloading it from Steam.

A game can appear to work perfectly when its executable file is opened directly, yet still fail when Steam is responsible for installation, startup, services and user-facing integration. Valve says it is reviewing some builds that have not been played through Steam at all. That creates a predictable problem: reviewers may find a basic issue only after the submission enters the queue, then the build needs changes and another look.

Requiring a short Steam-based play session should help developers verify the pathway their audience will use. It does not prove that a game is polished, balanced or free of every bug. Five minutes is not a substitute for quality assurance. But it can expose whether the release candidate clears the minimum hurdle of being installed and launched through the store platform without an obvious setup failure.

For a review backlog, that distinction is important. A failed submission can consume more than one block of reviewer time: there is the initial check, the communication of a problem, the developer’s fix, and the subsequent re-review. Avoiding even a portion of those repeat loops could make the queue more predictable for everyone waiting in it.

Related coverage includes Valve Tightens Steam Release Checks as Game Review Delays Stretch to 12 Days.

What developers now need to verify before review

Valve is also requiring developers to confirm several other common areas of Steam readiness:

  • Redistributables: Developers must check that required components such as DirectX and Visual C++ are properly handled.
  • Achievements: Developers need to confirm that achievement implementation is ready.
  • Steam Cloud: Save-file paths must be configured correctly for Steam Cloud.
  • Screenshot labels: Store screenshots must be categorized as gameplay, menus, concept art or cinematics.

Redistributables are supporting software components that some PC games need in order to run. A developer’s own PC may already have those components installed from other software, concealing a missing dependency. A customer with a different setup may not be so lucky. Confirming the required components before submission is an attempt to prevent the classic “works on my machine” trap from reaching a review build.

Steam Cloud refers to Steam’s system for synchronizing designated save data. The relevant practical issue is the save path: Steam needs to know which files belong to the game’s saved progress. If that path is wrong, a player could find that progress does not follow them as expected between installations or machines. The rule does not promise flawless cloud saving in every circumstance, but correct configuration is the essential first step.

Achievement readiness and screenshot classification are different kinds of checks, yet both speak to the same operational problem. Achievements are a visible platform feature that needs to be correctly connected before players arrive. Screenshot categories are store-page metadata, helping distinguish what a shopper is actually seeing. Gameplay footage, menus, concept art and cinematics serve different purposes; labelling them gives the store clearer information about the assets presented.

None of these items is especially controversial on its own. The significance lies in Valve turning them into explicit pre-review responsibilities at a moment when reviewer capacity is under pressure.

Why a delay can hit indie launches particularly hard

The queue is already having concrete consequences for developers with dates on the calendar. Some indie teams have reportedly missed launches by weeks while waiting for review progress. Cubic Earth developer structmira described a campaign in which the game’s trailer had surpassed 60,000 YouTube views and the title had gained more than 6,000 wishlists, only for the Steam Community page to begin filling with complaints as the planned release slipped.

A wishlist is a player’s indication of interest in a Steam game before purchase. It is not a sale, but it is a useful sign that marketing has reached potential customers. That makes a delayed release especially awkward: an audience can be aware of a date, ready to act, and then be met with a store page that is not yet able to deliver the game. The result is not automatically permanent damage, but it can disrupt the momentum a small team spent time and money building.

Valve acknowledged the stress created by longer waits and said further improvements to the build-review process are planned. The present changes are therefore best understood as an initial queue-management measure, aimed at preventing avoidable resubmissions rather than as a complete solution to submission volume.

AI disclosures point to a bigger volume problem, but not a simple explanation

Discussion around the backlog has focused heavily on a recent influx of AI-related releases, including quickly produced games sometimes described as “vibe-coded.” One developer, 2 Left Thumbs, said the review-time increase appeared to spike around September and October and connected it, in part, to the amount of low-effort material reaching Steam.

There is evidence that disclosed AI use has become common in recent Steam activity. An analysis by Reddit user u/ploz found that 49.9 percent of games released on Steam in October disclosed AI-generated content. Separately, nearly 20 percent of game demos in June’s Next Fest disclosed AI use.

Those figures are useful indicators of a changing submission environment, but they need careful interpretation. A disclosure identifies that a game used AI-generated material; it does not establish the amount used, the quality of the game, whether the title caused a re-review, or whether the game was made with little human oversight. Likewise, a correlation between greater AI disclosure and a slower queue does not by itself show exactly how much of the delay comes from AI-created projects versus the overall growth in submissions or other review demands.

Still, the operational concern is straightforward. If the store receives more builds that have not been tested through Steam or lack basic configuration, every avoidable rejection creates work that could otherwise go toward the next developer in line. Valve’s checklist addresses that bottleneck directly, irrespective of how a game was made.

What the changes mean for developers and players

For developers, the practical message is to treat a Steam submission as its own release candidate, not merely a copy of the game that ran successfully outside the platform. Launch it through Steam, play it, validate dependencies, verify achievements and cloud paths, and make sure store imagery is accurately categorized before entering the review queue. Doing that will not guarantee approval by a specific date, particularly while turnaround remains elevated, but it should reduce the risk of losing additional time to correctable platform issues.

For players, the changes are unlikely to be noticed as a flashy storefront redesign or a new consumer feature. Their value is more basic: fewer releases with setup mistakes, better-labelled store assets and a smoother route from a developer’s planned launch to a game actually being available. That is not a full answer to questions about store discoverability or AI-generated content, but it is a practical attempt to keep the review pipeline from being clogged by preventable errors.

Valve’s move also places responsibility where it can act fastest. Rather than attempting to infer quality from a game’s production method, the new process asks whether the submitted build meets clear platform requirements. With review waits currently stretching to 12 business days, that kind of pre-flight discipline may be the most immediate way to reduce repeat work while larger process improvements are developed.

For more on the policy shift and the concerns surrounding rapidly produced submissions, see our coverage of Valve’s updated Steam pre-release checks.