Steam is screwing over game developers...

Summary

The presenter argues that Steam’s pre-release review process is delaying game launches and disrupting developers’ release plans. Steam says reviews usually take 3–5 business days, while acknowledging that delays can reach 12 business days. The presenter and developers in their community report waits of 15 or more days in some cases.

If a submission is rejected, it returns to the regular queue rather than receiving priority review, potentially adding another lengthy wait.

Steam’s review requirements and process changes

Steam’s updated guidance asks developers to verify more items before submitting, with the aim of reducing rejections and repeat reviews. Developers are asked to:

• Run the game for at least five minutes and confirm that it starts and works.
• Check that required redistributables and achievements are set up.
• If Steam Cloud is enabled, upload a save from a developer account.
• Mark at least one screenshot as showing gameplay.
• Confirm that the build has been tested on another PC and that reviewers can access its features.
• Ensure the build includes everything promised on the store page, including controller support, Steam Cloud, and listed languages.

The presenter says Steam still displays the typical 3–5 business day estimate despite acknowledging longer delays. They also describe a past rejection over a Spanish localization listing that did not distinguish between Latin American Spanish and Spain Spanish—a small mismatch that triggered another wait in the queue.

Studio examples and operational impact

Desktop Island had scheduled its next game for release on November 27. Its build had been in review since October 29. At the time of the video, the presenter estimated that about 16 business days remained before release, leaving little room for a rejection and resubmission.

The studio was also waiting for approval of the store page and demo for another project, submitted on October 27 and 28. The full game build could not be submitted until the store page went live.

The presenter describes the studio’s earlier project, Unicycle Pizza Time, as a “Hail Mary” that went from start to finish in about one month and helped the studio. They argue that long approval waits make similarly fast-turnaround projects much harder to execute.

Practical advice for developers

• Submit builds early. The presenter recommends submitting a review build as soon as it runs, ideally one to three months before launch, rather than waiting until the game is nearly finished.
• Use a minimal but functional review build. According to the presenter, the build does not need to be the final release version. It should boot, include some gameplay, and meet the technical requirements for the features enabled.
• Avoid promising unfinished features. If localization, achievements, Steam Cloud, or other features are not ready, the presenter recommends temporarily leaving those options unchecked and submitting a build that does not claim to include them. Developers can add the features in a later update after approval.
• Protect the release schedule. Missing a planned launch can disrupt a studio’s calendar and hurt a game’s performance. The presenter frames early review as a way to reduce deadline risk and the stress of a late rejection.

The presenter criticizes Steam’s communication as insufficient given the delays and suggests that the company should communicate more directly about the backlog. They also argue that the review process can slow down copycat projects by extending the time needed to get a store page, demo, and full game approved.

Presenter and source

• Presenter: BiteMe Games; name not stated
• Source: Steamworks announcement about updates to the pre-release review process