Steam Launch QA Checklist: What to Test Before You Go Live

Launch day on Steam is not the time to discover that cloud saves are broken, your crash reporter is pointed at a staging server, or the game soft-locks on Intel integrated graphics. A systematic pre-launch QA pass catches the embarrassing, the damaging, and the review-killing bugs before players encounter them. This checklist covers every category that trips up indie developers on launch day — drawn from post-mortems, player reviews, and the crash dashboards of studios that shipped before they were ready.

1. Steam Deck Compatibility

Steam Deck is no longer optional to consider. Valve’s handheld has a large installed base, and the compatibility badge on your store page influences purchase decisions. Testing is split into two parts: automated (Valve’s compatibility checker) and manual.

• Run the game in Steam’s Desktop Mode with a gamepad only — no keyboard, no mouse
• Verify all menus and UI elements are navigable with the controller
• Check that text is readable at 1280×800 (the Deck’s native resolution)
• Test the in-game overlay and Steam button functionality
• Check that the game does not require a system keyboard for any required input
• Verify performance at the Deck’s default TDP settings — aim for a stable 30 or 60 fps
• Submit for official Valve Deck review at least two weeks before launch

If you do not own a Steam Deck, use the Deck emulation mode in the Steam desktop client to catch the most obvious issues before committing to a hardware test.

2. Steam Platform Features

Steam provides a suite of platform features that players expect to work. Each one needs individual verification in your final release build — not your development build, which may have different Steamworks configuration.

• Achievements: Trigger every achievement in the game at least once and verify it appears in the Steam overlay. Check that achievements are not triggering prematurely or failing to trigger at all.
• Cloud saves: Save the game on one machine, log into Steam on a second machine (or log out and back in), and confirm the save loads correctly. Delete local save files and verify cloud sync restores them.
• Steam Overlay: Open the overlay mid-game. Verify the game does not crash, freeze, or lose audio. Check that overlay-based features like the web browser, screenshots, and friend list work without breaking game state.
• Screenshots: Take a Steam screenshot (F12 by default) in several scenes, including the main menu and during gameplay. Verify the screenshots appear in your Steam library and are not black or corrupted.
• Steam Input: If you have a Steam Input configuration set, test it end-to-end on a physical Steam controller or with the Steam Input emulation layer enabled.

3. Minimum Spec Hardware Testing

Your game runs beautifully on your development machine. Your developer machine almost certainly exceeds your stated minimum requirements by a significant margin. This gap is where launch-day one-star reviews come from.

• Identify the GPU, CPU, and RAM combination that represents your stated minimum spec
• Test on a machine that matches or is close to that spec — borrowed, rented via a cloud gaming service, or a secondary machine
• Verify the game launches, runs above 30 fps at minimum settings, and does not crash on startup
• Pay special attention to Intel integrated graphics and AMD APUs, which account for a large share of budget gaming hardware
• Check that the graphics settings menu correctly detects and adapts to low-end hardware
• Confirm that your minimum spec claims are honest — if the game needs more than you’ve stated, update the store page before launch

4. Resolutions and Window Modes

Players use a wide range of display configurations. Test the full matrix before launch.

• Fullscreen exclusive mode at 1080p, 1440p, and 4K if supported
• Borderless windowed mode at the same resolutions
• Windowed mode, including resizing the window and returning to fullscreen
• Ultra-wide resolutions (21:9) if supported — or verify that UI does not break at those aspect ratios
• Alt+Tab behavior in fullscreen exclusive mode on both Windows 10 and 11
• Multi-monitor setups: confirm the game launches on the primary monitor and does not span across screens unexpectedly
• Check that the game remembers window mode and resolution settings between sessions

5. Controller Support

Incomplete controller support is one of the most common reasons for negative Steam reviews in certain genres. Completeness means more than “the buttons work.”

• Test with an Xbox controller, a PlayStation DualSense, and a Switch Pro controller if possible — button prompts should match the connected controller type
• Verify every menu, dialog, and UI screen is fully navigable with a controller (no mouse-only interactions)
• Check that plugging in or unplugging a controller mid-game does not crash the game
• Verify rumble and haptic feedback work correctly and can be disabled in settings
• Test the game with no controller connected, then with one connected mid-session
• If your game does not support controllers at all, confirm that accidental controller input does not interfere with keyboard/mouse controls

6. The New Player Funnel (First 10 Minutes)

The first ten minutes of your game deserve their own dedicated test pass. This is where first-time crashes, tutorial logic bugs, and default settings problems concentrate — and it is the exact experience that every Steam reviewer and refund-requesting player goes through.

• Delete all save data and launch the game as a completely new player on a clean machine
• Verify the first-launch experience: language selection, graphics defaults, intro cutscenes, tutorial
• Check that default graphics settings produce acceptable performance on a mid-range machine
• Confirm the tutorial or onboarding flow cannot be soft-locked or skipped by accident
• Watch for assumption errors: the game assumes data that only exists after the first launch (common save-system bugs)
• Time the first ten minutes yourself — if it takes more than ten minutes to reach meaningful gameplay, consider whether that is the experience you want reviewers to have

“The first ten minutes of your game will be played by more people than any other ten minutes. Every player who ever touches your game starts there. It deserves more testing time than any other section.”

7. Verify the Crash Reporter Is Live

This step is skipped more often than you might expect. Developers integrate a crash reporter during development, test it in a staging environment, and never confirm that the production build is pointing at the right endpoint with live credentials.

• Trigger a test crash in the release build (most crash reporting SDKs include a test method)
• Verify the crash report appears in your Bugnet dashboard within a few minutes
• Confirm the report includes the correct build version, platform, and stack trace
• Check that crash reports are not being silently swallowed by a firewall or misconfigured API key
• If you use Bugnet, verify that the project ID and API key in your release build match your production project, not a dev or staging project

Without a working crash reporter on day one, you are flying blind during the most crash-dense period of your game’s life. The first hours after launch generate more unique crash signatures than any subsequent period — hardware configurations, edge cases, and usage patterns that never appeared during internal testing all surface at once.

8. Windows 10 and Windows 11

Despite Windows 11’s age, a substantial portion of the Steam player base is still on Windows 10, which reaches end-of-life in late 2025 but will remain widely used for years. Test on both.

• Launch and run the game on Windows 10 22H2 (or the latest Windows 10 build)
• Launch and run on Windows 11 24H2
• Verify there are no Windows version-specific crashes, especially around DirectX initialization, audio drivers, and antivirus conflicts
• Test with Windows Defender active on both versions — some games trigger false positive detections that block launch
• Check that your installer and uninstaller behave correctly on both OS versions

9. Steam Rich Presence

Steam Rich Presence is the text that appears next to a player’s name in friends lists and the Steam overlay, showing what they are doing in your game (“In the Main Menu,” “Level 3 - Forest,” “Boss Fight”). It is a small detail that contributes to social visibility and discovery.

• Open the Steam friends list while playing and verify the Rich Presence string updates correctly as you move through the game
• Check that the strings are not empty, truncated, or showing raw token names like %gamestatus%
• Verify strings are grammatically correct and appropriately descriptive
• Confirm localization: if your game is localized, ensure Rich Presence strings are also localized

10. Store Metadata: EULA and Content Warnings

Valve requires accurate content warnings, and incorrect age ratings or missing content descriptors can result in removal from the store after launch. Review every metadata field.

• Verify your ESRB/PEGI/USK ratings are correct and reflect the actual game content
• Check that all required content descriptors are present (violence, language, adult content as applicable)
• Read your EULA if you have one — it should be current, accurate, and not reference a different product name
• Confirm your short description, long description, and system requirements are accurate and not copied from a placeholder
• Verify your supported languages list is correct — listing a language that is only partially translated is a common review trigger

11. The Uninstall Process

Uninstalling is the last impression a player has of your game, and a broken uninstaller generates genuine frustration. It is also a signal about overall code quality.

• Uninstall the game through Steam and verify it completes without errors
• After uninstalling, check that the game’s installation directory has been removed
• Verify that the uninstaller does not leave stray files in %APPDATA%, %LOCALAPPDATA%, or the registry (or that it leaves only save data, as intended)
• Reinstall after uninstalling and confirm the game launches correctly on a fresh install
• If your game writes files outside the Steam install directory, document this behavior and ensure the uninstaller handles it gracefully

The Master Pre-Launch Checklist

Print this out, work through it on your release candidate build, and do not push the launch button until every item has a name and a date next to it.

1. Steam Deck: manual test pass completed, Valve review submitted
2. Achievements: all triggered and verified in overlay
3. Cloud saves: cross-machine sync confirmed
4. Steam Overlay: no crashes or audio issues
5. Minimum spec: game runs acceptably on stated minimum hardware
6. Resolutions: fullscreen, borderless, windowed all tested
7. Controller support: Xbox, PlayStation, Switch Pro controllers tested
8. New player funnel: full first-ten-minutes test on clean machine
9. Crash reporter: test crash verified in Bugnet dashboard
10. Windows 10 and 11: both OS versions tested with Defender active
11. Rich Presence: strings updating correctly in friends list
12. Store metadata: ratings, descriptors, EULA reviewed and accurate
13. Uninstall: complete uninstall and clean reinstall tested

Run through this list on the actual build you are submitting to Steam — not a development build, not a build from last week. Build IDs matter. A checklist passed on the wrong binary is worth nothing.

The worst time to find a broken crash reporter is after 10,000 players have downloaded your game. Check it before you ship.