Valve says the review process for games submitted to Steam is taking longer than normal, with some build reviews now reaching 12 business days. The company usually aims to complete them within three to five days, but it is dealing with a sharp increase in store-page and build submissions. The delay has practical consequences for developers working toward a launch date.
Valve explained the backlog in its November 3 Steamworks Development announcement, titled Updates to the Pre-Release Review Process. The post also details new submission checklist items intended to reduce avoidable re-reviews.
Why are Steam game reviews taking longer?
Steam reviews both public store pages and game builds before a launch. Valve says the volume of submissions has risen significantly in recent months. Some builds also require another review after the company finds basic launch or functionality problems. Repeating those checks uses capacity that could otherwise go toward first-time submissions.
That means the quoted 12 business days is not a new universal minimum waiting period. It is the upper end Valve currently says some build reviews can take. Individual submission times may vary, and a store-page review is not identical to a build review.
Valve wants developers to launch their game through Steam before submission
One of the most concrete changes is a requirement to run a submitted game using the Steam client for at least five minutes. Valve notes that a game can start successfully when launched directly from an executable but still fail when installed and launched through Steam due to missing depots or incorrect launch settings.
The recorded playtime must come from the preceding seven days or from the current build if it was uploaded more than seven days earlier. Valve also notes a short delay before playtime is recorded in the release checklist.
What else can hold a build up?
Valve is asking developers to make sure store descriptions and assets clearly represent what customers will receive. Testers compare the build with the store page, including advertised language options and major game features. Content disclosures matter as well: the content survey must cover potentially sensitive material and AI usage when relevant.
The company is also improving checklist guidance around achievements and required shared components such as DirectX or Visual C++ runtimes. For teams planning a release, the broader message is to test the complete distribution path rather than only the game executable.
What this means for players and indie studios
For players, a Steam release date can occasionally slip because a developer is waiting for platform approval, not because the game itself changed overnight. For indie studios, the safest response is to build extra time into release schedules and avoid assuming that a last-minute submission will pass immediately.
Valve says further review-process improvements are planned. Until they arrive, developers should consult the current Steamworks release checklist, run real Steam client tests, and leave enough room for possible corrections before advertising a fixed launch day.