game-launch

Follow a phased checklist: validate the release build with clean builds and zero P0/P1 bugs, prepare all capsule images and screenshots, publish a Coming Soon page at least two weeks early for wishlists, and complete a go/no-go review with a rollback plan before launch day.

Steam requires header, small, main, and vertical capsule images, a hero graphic, library artwork, at least five screenshots, a gameplay trailer, store description, tags, and system requirements. Missing or non-compliant assets delay submission or cause rejection.

Yes, most storefronts require an age rating such as ESRB for North America, PEGI for Europe via IARC, or CERO for Japan. Missing ratings can get a game pulled post-launch, so submit questionnaires well before the release date.

First-party certification typically takes two to four weeks per platform, and first submissions rarely pass on the first attempt. Budget four to eight weeks total including at least one rejection-and-resubmission cycle.

Skip the full pipeline when the game is still in active development with incomplete features, when releasing an internal playtest build, or when submitting a non-commercial game jam entry where only build validation matters.

A day-one patch should contain bug fixes found during certification, final balance tuning, localization corrections, and performance optimizations. It should never add new features, and it must pass the same validation process as the gold build.