Recommended Free Tools
Prepare a Steam launch by completing Steamworks onboarding, building the store page and a near-final game build in parallel, submitting the store page before the build, and testing the delivered game through Steam. Both the store presence and the product build need approval, and neither approval releases the game automatically. Plan around Steam’s waiting periods and review estimates, then release manually when you are ready.
How do I prepare my indie game for Steam?
Steamworks organizes launch preparation around two separate checklists: Store Presence and Game Build. The store page must be submitted before the build, and both must be approved before release. Follow the checklists in your Steamworks account as the operational source of truth; labels and requirements can change.
1. Finish Steamworks onboarding
Complete the digital agreements, app deposit, bank and tax information, and identity verification listed in Steamworks onboarding. For a first release, Valve’s documentation specifies a 30-day wait after paying the app fee, as well as a public Coming Soon page visible for at least two weeks. Factor both into the schedule before announcing a launch date.
2. Prepare the store page and game in parallel
Work on the Store Presence checklist while the game build is being prepared. The page should describe the version you can actually submit for review—not a future plan. Steam checks that the game starts on every operating system listed on the page and that features marked as supported are implemented in the submitted build. Remove or revise claims for features that are not yet available.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
3. Submit the store presence first
Complete the Store Presence checklist and submit the page for review. Steam says this review typically takes 3–5 business days and recommends submitting at least seven business days before the intended live date. These are published estimates, not a guaranteed turnaround; leave time to respond to feedback and resubmit changes. See Steam’s review guidance.
4. Upload and configure a near-final build
Use the Steamworks SDK and developer tools to configure the game’s depots and upload its build. Complete the Game Build checklist, then submit the build after the Store Presence has been submitted. Steam recommends a mostly final default-branch build containing the features described on the store page. Approval does not prevent later updates, but the build Valve reviews should be playable and representative. The Steamworks SDK documentation describes the relevant build and upload tasks; the release process covers the submission sequence.
5. Test the Steam delivery experience
Test installation and launch through Steam, not just by running a development build outside the platform. Choose access based on who needs to test, how controlled access must be, and whether signups should appear on the public game page. Options are outlined in Steam’s playtesting documentation and Steamworks application documentation.
6. Release manually when ready
Once the store presence and build are approved, release the game using Steamworks’ release controls. Valve states that approved titles do not release themselves; you must use those controls when you want the product to go live. The public Coming Soon page must have been live for at least two weeks before release. Check the release process for the current steps.
How long does Steam review take?
Steam’s published typical review estimates and recommended lead times are:
| Review | Typical review time | Recommended submission lead time |
|---|---|---|
| Store Presence | 3–5 business days | At least 7 business days before the desired live date |
| Product build | 3–5 business days | At least 7 business days |
These figures come from Valve’s Steamworks review documentation, accessed October 7, 2026. They are estimates, not promises that a submission will be approved or finished by a particular day. Feedback, fixes, and another review can add time, so do not schedule launch around the shortest estimate.
Rank #4
How should the store page match the build?
Steam’s build review checks that the product starts on every operating system listed on its store page and that supported features work in the submitted build. A feature described as planned but not yet released should not be presented as currently supported. Submit a near-final default-branch build that represents the page’s claims; Steam allows updates after approval, but that flexibility is not a substitute for accurate launch information.
How do I test my game on Steam before release?
Steam offers several access routes. They are not interchangeable: choose according to audience, confidentiality, access management, and whether you want testers to find a signup on the main game’s page.
| Option | Useful for | How it works |
|---|---|---|
| Steamworks users or internal access | Team and employee testing | Add users to the Steamworks account or provide suitable access keys. |
| Steam Playtest | External playtesting managed through Steam | A separate app associated with the main game; its signup appears on the main game’s page. Steam describes it as free and low-risk. |
| Release-override keys | Closed betas, including confidential tests | Give testers access using keys; track and manage the keys carefully. Steam identifies this as an alternative when the test should run off the main game’s App ID or an NDA is needed. |
| Build branches | Testing updates separately from the live version | Assign a build to an alternate branch. Branches can optionally be password-protected. |
Steam describes Playtest as its preferred method for enabling closed betas. A separate branch can also help keep a test build apart from the live version; it controls which build testers access, while the access route determines who can reach it. Consult the Playtest documentation and application documentation for setup details.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Should I make a demo?
A Steam demo is a separate App ID associated with the full game, with its own depots, build, and release checklist. It is an additional product to prepare and review, so make one when it serves the game and its audience rather than treating it as a required launch step. If the demo goes live before the full game, Steam advises having the base game’s Coming Soon page ready so visitors can wishlist it. See Steam’s demo documentation.
How much lead time should I leave before launch?
Work backward from the release date. For both the store page and build, Steam’s typical review estimate is 3–5 business days, and it recommends allowing at least seven business days. A first release also has the 30-day waiting period after app-fee payment, while the Coming Soon page must be publicly visible for at least two weeks before release. Because review feedback may require changes, treat these as minimum planning constraints rather than a launch guarantee.
Quick Recap
- Complete onboarding and pay the app fee early enough to clear the first-release waiting period.
- Publish the Coming Soon page at least two weeks before the planned release.
- Submit the Store Presence with at least seven business days for review and possible changes.
- After submitting the Store Presence, submit a representative, near-final build with at least seven business days for review.
- Confirm both approvals, then use Steamworks release controls when you are ready to launch.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
