GDnD Wiki

GDnD Wiki

This site is for Ulster University students and staff. Enter the class access password to continue.

Source: Steamworks Store and Release Documentation

3 min read

Source metadata

Key takeaways

  • A Steam release is a staged process, not a single button press. Valve separates store-page review, build review, release-date management, pricing, and final release actions. A Coming Soon page must be reviewed before it can go public, and a product build should be submitted with buffer time before launch.
  • Coming Soon pages are an early marketing tool, not a final checklist item. Steam recommends publishing the Coming Soon page as soon as you are ready to talk publicly about the game, so it can collect feedback and wishlists while development continues.
  • Wishlists matter, but Steam does not treat them as a magic conversion formula. The docs frame wishlists as evidence of audience-building work already done elsewhere, not as a guaranteed sales predictor.
  • Store messaging should be concise and current-state focused. The short description is for quickly communicating the game’s theme, style, and appeal. Steam explicitly discourages formatting tricks and time-based copy that will go stale.
  • Visual marketing assets have platform-specific constraints. Capsule art and store graphics are not free-form adverts. Steam disallows discount copy, award names, and cross-promotion in key graphical assets.
  • Gameplay-first communication is strongly preferred. Steam’s trailer guidance puts gameplay trailers first because customers need to understand how the game actually plays, not just its mood or lore.
  • Early Access is for playable products with transparent uncertainty. Steam presents Early Access as a way to gather feedback while finishing a game, not as a pre-purchase or a promise that all planned features will definitely arrive.
  • Post-launch communication is part of discoverability. Steam links major updates to visibility systems, especially for players who own or wishlist the game, so updates should be treated as communication and release beats, not just patch notes.

Notable claims

  • Steam recommends submitting a Coming Soon page for review at least seven business days before you want it live.
  • Steam says build review typically takes three to five business days, but asks partners to plan for at least seven business days.
  • Steam’s store-description guidance says the short description should avoid formatting gimmicks and time-based text.
  • Steam’s asset rules explicitly disallow discount marketing copy in graphical assets.
  • Steam’s Early Access rules say customers should buy based on the game’s current state, not on promises about its future.

Relevance

This source primarily informs:

It also directly supports:

Open questions raised

  • Steam’s guidance is clear about process, but much less explicit about how much wishlist volume is enough for different kinds of launch. That remains a strategic judgement call, not a platform guarantee.
  • Visibility systems and storefront presentation evolve over time. Which parts of today’s advice are stable principles, and which are merely current platform conditions?

Graph View

Backlinks