Steam review takes 3 to 5 business days per round, and there are two rounds: the store page first, then the build. Valve asks you to plan for at least 7 business days each. The page must also sit in Coming Soon for 2 weeks before release. With one rejection round per review, a first release needs the store page submitted about 6 weeks before launch day.
How long does Steam review take for the store page and the build?
Valve publishes the same typical time for both, but the two reviews do different jobs and cannot run in parallel. Valve’s release page says the store page must be submitted before you can submit the build. The table comes from the Steamworks review process page, the release process page and the Coming Soon page (all accessed 29 October 2026).
| Review | Typical time (Valve) | Valve’s planning advice | What has to happen before it |
|---|---|---|---|
| Store page and pricing | 3-5 business days | Submit at least 7 business days before you want the page live | Store presence checklist complete |
| Build | 3-5 business days | Plan for at least 7 business days, in case an issue comes up | Store page already submitted; near-final build on the default branch |
| Trading cards (optional) | 3-5 business days | none given | Card assets uploaded |
| Adult Content page and build | longer than 3-5 business days | Both must be submitted before the page is reviewed | Mature Content Survey marked Adult Only |
A business day here means a weekday, so a build submitted on a Friday afternoon has used none of its 5 days by Monday morning. Valve’s Steam Direct page describes the same check more loosely, as a review that “takes between 1-5 days”. Plan on the review page’s figures, because they are the stricter ones.
The review clock only covers Valve’s side. The build you send should already be tested, because a fix found during review means a new upload and possibly a new round. To size that testing, the QA hours calculator estimates hours from your genre, build size and milestone.
What does Valve check in review, and what does it skip?
Valve lists four store page checks and three build checks. The page may show only features and content available at launch. Capsules need a readable title or logo, and screenshots must show gameplay. The description has to be detailed and coherent, with no links to other websites. An Early Access page must also answer every question in the Early Access section.
The build review asks for less. The game must start on every operating system listed on the store page. Every listed feature must be in the build, and in-game transactions must use Steam Wallet. The review page says nothing about testing for bugs. Valve’s Next Fest documentation is blunter: build review “will not catch or even look for most bugs” (accessed 29 October 2026).
So “Ready for release” means the build launches and matches its page. It says nothing about saves, frame times on a min-spec laptop or a controller prompt bug. If no one outside the team has played the exact build you will submit, a one-day Smoke Test puts one tester on it for 8 hours. The prioritized bug list comes back in 2 business days, inside the week before build submission in the calendar below.
Which other waiting periods sit in front of a first release?
Review time is the shortest wait on the list. A first-time developer runs into four more, and two of them are fixed in calendar days, not business days.
| Waiting period | Length | Source (accessed 29 Oct 2026) |
|---|---|---|
| Onboarding paperwork (bank, tax, identity) | 15-30 days | Steam Direct |
| Tax information check by a third party | up to 30 days | Onboarding |
| App fee paid to release allowed | 30 days on the Steam Direct page, 21 days on the onboarding page | Steam Direct, Onboarding |
| Coming Soon page live before release | at least 2 weeks | Release process, Coming Soon |
| Release date can no longer be changed | inside the last 2 weeks before the date | Release dates |
The two Valve pages disagree on the app fee wait, and the Steam Direct fee is $100 per app either way. Plan on 30 days, the longer figure. The release date lock matters most once review starts. Valve’s release dates FAQ allows date changes up to two weeks before the date. After that the game shows up more in upcoming lists, and the date stays put. A build stuck in review on day 13 before launch can no longer buy time by moving the date in Steamworks.
What is the fastest a first Steam release can go?
On paper, about 17 to 21 days from the first store page submission, if nothing comes back. Submit the store page on a Monday. At 3 business days it is approved on Thursday; at 5, the following Monday. You post it as Coming Soon the same day and wait the required 14 days. The build review has to finish inside those two weeks. Add the 30 days after the app fee, which has to be paid before you can build anything in Steamworks.
That path assumes zero feedback on either review and no business days lost to holidays. Developers report otherwise. In a 2025 Steam Community thread, one studio’s first build and store page review came back after 5 days with requested changes. Another developer was on day 13 and counting, and a third reported 20 business days (Steam Community, “Build review has taken weeks, can’t push back release”, accessed 29 October 2026). Those are individual reports, not Valve statistics. The original poster quotes a Valve support reply: “plan around the possibility of failing the build review at least once”. The same reply suggests submitting the build “about two or three weeks before release”.
How far before release should you submit for Steam review? A 6-week calendar
The calendar counts back from an example launch on Thursday, 15 April 2027. It is a weekday on purpose: Valve’s date picker hides weekends, when the Steam team is unavailable to help. Each review gets Valve’s 7 business days, plus one full feedback round. Days are counted as T minus calendar days to launch. Swap in your own date and keep the gaps.
| T | Date | What happens | Rule behind it |
|---|---|---|---|
| T-77 | Thu 28 Jan 2027 | Pay the $100 app fee, start onboarding paperwork | Paperwork 15-30 days; fee at least 30 days before release |
| T-42 | Thu 4 Mar | Submit the store page (round 1) | 3-5 business days, submit 7 business days ahead |
| T-35 | Thu 11 Mar | Round 1 result at 5 business days. If approved, post as Coming Soon | Coming Soon can go up once the page is approved |
| T-30 | Tue 16 Mar | If Valve sent feedback, fix and resubmit the page (round 2) | Second round, same 7 business days |
| T-28 | Thu 18 Mar | Submit the near-final build, after an outside test of that exact build ID | Build only after the page; plan 7 business days |
| T-21 | Thu 25 Mar | Store page round 2 result. Post as Coming Soon by today | Leaves 7 days over the 2-week minimum |
| T-17 | Mon 29 Mar | Build round 1 result at 7 business days | Plan for failing once |
| T-15 | Wed 31 Mar | Resubmit the build if feedback came back. Last safe day to move the release date | Date change allowed until 2 weeks before |
| T-14 | Thu 1 Apr | Coming Soon must be live from today at the latest; date locked | 2 weeks of Coming Soon |
| T-6 | Fri 9 Apr | Build round 2 result at 7 business days | Second round, same 7 business days |
| T-0 | Thu 15 Apr | Press Release App in Steamworks | Approved games do not release themselves |
The buffers are an editorial estimate, not a Valve rule. They answer one question per row: what happens if this review comes back with feedback? If both reviews pass the first time, the page goes up at T-35 and the build is approved around T-17. The spare weeks then go into testing and marketing. If you start later than T-42, cut the slack in the store page rounds first. Keep the build submission at least two weeks out, as Valve support suggested.
After approval the build can still change. Valve says you can keep updating after approval without a second review. Use the T-6 to T-0 window for a final regression pass on a beta branch, and leave new features for after launch.
What happens if Valve sends feedback or review runs long?
The Steamworks pages do not describe a formal rejection. They say Valve will “send you any feedback if necessary”, and if none is needed it marks the page or product “Ready for release”. Feedback means a fix and a new submission. The docs give no faster clock for the second round, so plan the full 7 business days again.
Most store page items in Valve’s checklist can be fixed before you submit. Look for features on the page that are not in the build, screenshots with concept art or awards, a capsule without a readable title and links in the description. For the build, the checklist names two failures: a game that does not start on a listed operating system, and a listed feature missing from the build. Remove planned features from the Basic Info tab until they ship, as the review page asks.
If a review runs past its planned date, the docs offer no fast lane. Contact Valve support with your release date, and keep the build frozen so the version under review is the one you tested.
Does Early Access, a demo or Next Fest change the timeline?
Early Access uses the same two reviews, plus the Early Access questionnaire on the store page. Valve’s Early Access page adds one trap. Switching an existing Coming Soon page to Early Access means the store page “will need to be reviewed again prior to release” (accessed 29 October 2026). The rest of the Early Access rules are in our Early Access launch checklist.
A demo is a separate app with its own store page and build checklists. You mark both as ready for review, as with the base game (Steamworks demos page, accessed 29 October 2026). The page gives no review time for demos. Next Fest has fixed submission dates of its own, which the February 2027 demo QA plan maps week by week.
Count back from launch day, give each review two rounds, keep the store page live for more than 14 days, and test the build before Valve sees it. The Steam review process glossary entry has the one-paragraph definition to share with the rest of the team.