Driftholm
Steam approval is slow right now: what's going on
Valve says pre-release reviews are taking up to 12 business days. Here's why, how the path to a Steam release works, and where Driftholm is.
Justice Daniels · · 8 min read
If you make games and you've submitted anything to Steam lately, you may have noticed the wait. If you play games and you've wondered why a small studio's "coming soon" seems to take forever to actually come, this is part of the answer.
Valve has said publicly that its pre-release reviews are running behind. We're in the middle of this process ourselves with Driftholm, so we read Valve's post and its documentation closely. Here's what's happening, how the whole path to a Steam release works, and what we're doing while we wait.
What Valve said
On November 3, 2026, Valve posted an update on its Steamworks Development group called Updates to the Pre-Release Review Process. The key line is in its FAQ. Valve says it aims to test every build "typically within 3-5 business days", but that it's "running a little behind right now and taking up to 12 business days."
Valve also explained the cause, and we appreciated how direct it was. The post opens by saying the team has seen "a significant increase in submissions for store page and build review in recent months." And on the delay itself: "Much of that delay is due to having to re-review games."
In other words, it's not only that more games are being submitted. A lot of builds fail review for basic reasons, get fixed, and come back for a second look, which takes reviewer time that could have gone to someone else's first look. Valve says the changes in the post are meant to help more games pass the first time. Inven Global's coverage the next day sums it up the same way.
It's worth saying: this is Valve being open about a problem and shipping fixes for it. A slow queue is frustrating, but a queue whose owner tells you why it's slow and what they're doing about it is a lot easier to plan around.
What's new in the release checklist
To cut down on re-reviews, Valve added several items to the checklist developers complete before submitting. From the post:
- Run your game through Steam for at least 5 minutes. You click the green "Play" button in Steam and run the game for five minutes or more. Valve's reasoning is refreshingly plain: "sometimes we review builds that have not ever been played through Steam." Any user's playtime counts, as long as it's within the past seven days, or since your last build if that was uploaded longer ago.
- Confirm common redistributables. Tell Steam which things like DirectX or Visual C++ it should install, or say that your game doesn't need any.
- Achievements get checked. Steam now flags incomplete setups, such as missing names or icons.
- Steam Cloud has to actually work. If your store page says the game supports Steam Cloud, someone in your partner group needs to have written a save to it.
- Five gameplay screenshots. Screenshots now have categories, and store pages need at least five marked as gameplay.
- Reminders at submission. Steam now asks about common things people forget, like including every language your store page promises.
Valve also shares what reviewers are looking for, and it's a short list: is the store page clear and complete, does the build match what the page promises, and is sensitive content (including mature content and AI usage) disclosed in the content survey.
The full path, step by step
Here's how getting a new game onto Steam works, based on Valve's own Steamworks documentation. Times are Valve's typical figures, not guarantees.
1. Join Steamworks and pay the app fee. Each new game needs a Steam Direct fee of $100 USD (or equivalent). It isn't refundable, but you get it back in a later payment once the game has made at least $1,000 in Adjusted Gross Revenue. Valve's Steam Direct page says signing up also means completing bank, tax and identity paperwork, which it says takes 15 to 30 days.
2. The waiting period. You've probably heard "30 days" for this. Valve's current docs actually say something different: there's a 21-day waiting period between paying the app fee and being able to release that game. The Steam Direct page says this applies to your first few titles, and gives Valve time to confirm who it's doing business with.
3. Store page review. You build your store page (description, capsule art, screenshots, ideally a trailer) and submit it. Valve's review process docs say this typically takes 3 to 5 business days, and recommend submitting at least 7 business days before you want the page live.
4. Coming Soon. Once the page is approved, you publish it yourself as Coming Soon. Valve requires a new game's Coming Soon page to be up for at least two weeks before release. This is when people can start wishlisting.
5. Build review. You upload a mostly final build and submit it. You can only do this once the store page has been submitted. Normally this also takes 3 to 5 business days, and Valve asks you to plan for at least 7. Right now, as we covered above, it's taking up to 12.
6. Release. Once both reviews are approved and the two weeks have passed, you press the button. Literally: Valve's release docs say approved titles "will not release themselves". You choose the moment.
Some of these steps overlap. The waiting period runs in the background, and the store page can be in review while you're still finishing the game. But it adds up, and a backlog in step 5 can push a planned date.
What developers can do meanwhile
If you're on this path too, here's what we're taking from Valve's advice:
- Submit early. Valve's own documentation already recommends leaving room. With reviews running long, leave more.
- Treat the checklist like a test you can pass the first time. Play your build through Steam, not just from your editor. Check achievements, cloud saves, languages and redistributables before you hit submit. A failed review costs you a second trip through the queue.
- Make the store page say exactly what the game does. Reviewers compare the page to the build. Don't promise a feature, language or mode that isn't in the build you send.
- Disclose honestly. If your game uses AI in ways the content survey asks about, say so. We think that's the right thing to do anyway.
- Keep building in the meantime. A review wait is a good week for bug fixes, a devlog, or a playtest.
If you want a walkthrough of the Steamworks side, Code Monkey (Hugo Cardoso) just published How to Publish your Game on Steam! (FREE Course). Its description covers the store page checklist and "why you shouldn't wait for your final build to submit it for review", which is good advice at any time and especially now.
Where Driftholm is
Here's where we stand, plainly.
Driftholm's Steam page isn't live yet. We're working through the steps above, and we'll announce it here the day it goes up, so you can wishlist it. We're not going to give a release date until we're confident in one.
In the meantime, you don't have to wait to play. There's a free web demo of Driftholm right here on our site. Open it in your browser and lay a few tiles, with nothing to install. It's the same game we're bringing to Steam: islands that lean, edges to match, weather that always warns you first.
If you'd like to help shape the Steam version, our playtest program is the best way in, and the Driftholm page has everything else, including a sign-up to hear from us when there's news.
Waiting is part of making games. We'd rather spend it making Driftholm better than refreshing a dashboard. If you're in the queue right now too: good luck, and we hope your build passes the first time.
Sources
- Valve, Steamworks Development: "Updates to the Pre-Release Review Process" (Nov 3, 2026): the delay, the cause, the new checklist items and reviewer guidance.
- Inven Global: "Valve says Steam pre-release reviews now take up to 12 business days" (Nov 4, 2026).
- Steamworks docs: Steam Direct Fee: $100 fee, not refundable, recouped after $1,000 Adjusted Gross Revenue.
- Steamworks docs: Onboarding: 21-day waiting period after paying the app fee.
- Steamworks: Steam Direct: paperwork timing (15 to 30 days) and the waiting period for your first few titles.
- Steamworks docs: Review Process: typical 3 to 5 business day reviews; plan for at least 7.
- Steamworks docs: Coming Soon: at least two weeks as Coming Soon before release.
- Steamworks docs: Release Process: order of reviews and releasing manually.
- Code Monkey: "How to Publish your Game on Steam! (FREE Course)" (Nov 2026).