Steam release QA checklist: what to verify before you press Publish

Releasing a game on Steam is a lot of small steps, and most of the painful mistakes are small too. After testing and helping with game releases I keep a checklist of things to verify in the build and on the store page before pressing Publish. This is a general guide: always follow the current Steamworks documentation, because rules and tools change.

1. The build players will actually download

• Install the build exactly as a player would: from the Steam client, on a clean Windows user profile or a clean virtual machine, not from your development folder.
• Check that the correct build is set on the default branch.
• Launch from Steam, from the library and, if relevant, from the desktop shortcut.
• Confirm that all required redistributables install and nothing depends on files only your computer has.
• Check the install size and that updates download as expected.

2. Core gameplay on the release build

Run your smoke test and your save tests on the exact build that will go live. For a manual checklist you can reuse, see my manual game QA checklist. Pay attention to the first 30 minutes: that is when most players decide whether to keep the game or refund it.

3. Steam features you configured

• Achievements: each one unlocks once, at the right time, and shows the correct text and icon.
• Cloud saves: save on one machine, load on another, and test a conflict.
• Controller support: if you declare it, test with a real gamepad, including the Steam overlay and Big Picture.
• Overlay and screenshots: work and do not break rendering.
• Leaderboards and Workshop: if used, test as a regular user, not only as the developer.

4. Store page and metadata

• Title, short description, long description and screenshots match the actual game.
• Trailers and screenshots show real gameplay and are not outdated.
• Supported languages and the interface, audio and subtitle flags are accurate. If you list a language, test it from start to finish.
• System requirements are realistic: test on a low-spec machine.
• Age ratings, content descriptors and tags are filled in correctly.
• Pricing, regional prices and release date are what you intend.
• Links to your website, support email and privacy policy work.

5. Localization

A language listed on the store page is a promise. Check the menus, the first-run flow and the credits in every language, using the approach from my article on localization testing for games.

6. Compatibility

• Different resolutions and aspect ratios, including ultrawide.
• Windowed, borderless and fullscreen modes, and alt-tabbing.
• Low and high frame-rate limits.
• Steam Deck behaviour if you want to be verified or just not crash on it.
• Antivirus or security software false positives on the build.

7. Legal and support readiness

• Credits, licences and third-party notices are correct.
• A support route is clearly visible: email, Discord or the community hub.
• You know how you will collect and triage bug reports after release. A simple template based on my bug report guide saves a lot of time.

8. Launch day plan

• Keep a branch ready for a hotfix and test the update process before launch.
• Prepare a short "known issues" note for the community page.
• Monitor reviews, discussions and crash reports in the first days.
• Fix blockers first: crashes, progress-stoppers, broken saves.

Final pass

Do one last install from Steam on a clean machine, play the first level, change a setting, save, quit and load. If that works, you have covered the failures that hurt most.

I tested and released two games on Steam myself and wrote down my process in the Steam release record. If you need an independent tester before your own release, you can contact me.

More articles

← All articles