Valve implements new Steam pre-release checklist to reduce build review backlog
Steam now requires developers to run games through the Steam client for at least five minutes to ensure build integrity before submission.
Summary
Valve has introduced several mandatory requirements to its Steam pre-release checklist to address a growing backlog in build reviews. The most significant change requires that a game be launched via the Steam client and run for a minimum of five minutes prior to submission. This measure aims to prevent the submission of builds with broken launch options or missing depots, which previously forced reviewers to restart the process.
In addition to the playtime requirement, Valve is enforcing stricter standards for store pages and technical configurations. Developers must now provide at least five gameplay screenshots, verify Steam Cloud functionality with a test save, and list all necessary redistributables. These changes are intended to stabilize the review timeline, which has recently expanded from three to five days to as many as 12 business days due to failed initial checks.
New Steam submission requirements
- Build Validation: Developers must log at least five minutes of playtime through the Steam client within the last seven days (or since the last build upload) to verify depot and launch option integrity.
- Cloud and Achievement Integration: Submissions must include a successful test save written to Steam Cloud and a fully configured achievement system.
- Metadata and Dependencies: Requirements now include a minimum of five screenshots tagged specifically as gameplay and a comprehensive list of required redistributables, such as DirectX or Visual C++.
- Review Process Optimization: The new checklist is a direct response to increased submission volumes and a rise in review times caused by builds failing basic functional checks.
Why it matters
These changes will likely improve the stability of games on the Steam platform, including better compatibility for Linux and Steam Deck users by ensuring launch parameters are functional. While it adds a mandatory step to the development workflow, it aims to provide more predictable review turnaround times for developers.
Original reference: www.techpowerup.com →