Valve Steam review delays: submissions now take up to 12 days

What happened

Valve has acknowledged a surge in game submissions to Steam and says its review queue has slowed as a result. In a new post, the company said it has seen "a significant increase in submissions for store and page review in recent months" and that it is "running a little behind", with reviews now taking "up to 12 business days" rather than the usual 3 to 5.

The delay has frustrated independent developers, who have recently voiced concerns about lengthy approval times for their titles. The Verge, which reported the update, indicates that Valve is making changes to deal with the increase. The summary available for this briefing does not set out what those changes involve.

Why it matters

For a storefront, review time is part of the product. A developer waiting up to twelve business days to see a store page go live experiences the platform through its slowest step. When that wait runs beyond a stated norm, the uncertainty is costly in its own right: launch dates slip, marketing plans are reset, and teams must decide whether to hold or push ahead without knowing when approval will arrive.

The episode also shows how volume spikes expose the operating model behind a digital service. Review pipelines that perform well at normal volumes can degrade quickly under a surge, and the consequences appear first as broken expectations rather than as visible outages. For any platform running a gated approval process, capacity planning and clear communication are part of the same service design problem.

By the numbers

• Up to 12 business days: the current review window Valve cites for store and page submissions.
• 3 to 5 days: the typical review timeframe Valve describes as its norm.

The Renascence take

Most readers will focus on the wait. The more useful signal is how Valve chose to communicate it.

Being open about a backlog is a service-design decision, not a concession. Stating a longer expectation gives developers the mental model they need to plan around it, and that matters more than the queue's speed on any given day. The principle underneath is expectation management: people tolerate delay far better when it is explained, bounded and predictable. Any platform operator facing a submission surge should publish realistic timeframes early, measure the wait developers actually experience, and treat a stated service level as a promise to keep.