Steam's verification queue, not your development schedule, is what decides your release date. In November 2026, r/gamedev carried reports of Steamworks identity verification stretching to 45 business days — up from around 30 earlier in the year — alongside a developer who says Valve took the $100 fee, let 60 days pass, and then rejected the verification over an address mismatch. The official clocks are shorter, and most applicants clear them; the failures that turn weeks into months are almost always document mismatches that were preventable before the fee was paid.
A note on who's telling you this: Egmatic is a pre-alpha AI-native game-building tool, and this blog covers the publishing layer indie developers actually face — including the parts nobody controls. We have no stake in Steam's process and no inside line into it. What follows is assembled from Valve's own partner documentation, read live on November 20, 2026, plus community reports that are labeled as community reports, because those two classes of evidence behave very differently.
This article zooms into one stage: the identity, tax, and fee verification that stands between signing up and releasing. If you want the full signup-to-launch sequence — store page setup, builds, pricing — that's the Steam Direct 2026 walkthrough. For where Steam sits among all your distribution options, start with how to publish games on all platforms.
Quick answer
Five clocks govern the funnel, and only two of them are usually talked about. Here is each one as Valve documents it, as of November 20, 2026:
| Clock | Official timeline | When it starts |
|---|---|---|
| Identity verification (documents, ID, selfie) | No published timeline; community reports range from days to 45 business days | When you submit the digital paperwork |
| Tax information check | 2–7 business days; up to ~30 days for newly issued tax IDs | After the 5–10 minute tax interview |
| App fee to release waiting period | 21 days, fixed | When the $100 fee is paid |
| Coming Soon page visibility | At least 14 days publicly visible | Once the page is up (runs inside the 21 days) |
| Store page and build review | 1–5 days | When you submit for review |
If your documents are consistent, verification itself resolves in days to two weeks, and your binding constraint is the fixed 21-day window after the fee — plan around a month from payment to earliest release. If a document mismatches, verification becomes the longest clock in the funnel, and the 45-business-day reports are what that looks like from inside.
The five clocks, one at a time
Identity verification. During onboarding, Valve verifies who it's doing business with: your legal entity, a government ID, and — per Valve's own identification-document guidance — in many steps a photo of yourself holding that ID. That selfie has rules people skip and then pay for: send it as a JPEG, keep all four corners of the document visible, make the text legible, take off the hat and glasses unless they're in the ID photo. Valve publishes no service-level timeline for this stage, which is precisely why the community numbers exist. Reports in the November 2026 r/gamedev sweep put identity verification at up to 45 business days, against roughly 30 earlier in the year — treat those as the observed range of a queue with no published SLA, not as Valve promises.
Tax verification. After a 5–10 minute tax interview (W-9 for US persons, W-8BEN for treaty countries), your information goes to a third-party verification service. Valve's FAQ states this typically takes 2–7 business days, with a known slow case: recently issued US tax IDs can take up to 30 days because the IRS database itself hasn't absorbed them yet. You cannot edit your tax information while the check runs, so a typo discovered on day six costs you a support cycle, not a quick edit.
The $100 fee. Payable with any Steam-supported payment method except Steam wallet funds, only by users with admin permissions, and subject to VAT or similar taxes depending on your country. It is not refundable — but it is recoupable, returned as a line item in a payment once the product crosses $1,000 in adjusted gross revenue.
The fixed waiting periods. There is a 21-day waiting period between paying the fee and being allowed to release, and your Coming Soon store page must be publicly visible for at least 14 days before launch. These are scheduling constraints, not checks — they don't fail, they just run, and they quietly set your minimum runway at about a month no matter how fast everything else goes.
Store page and build review. Before anything goes live, Valve runs your game, looks at the store page, and checks the configuration — documented at 1–5 days. This is the clock people plan around, and it's the shortest and most reliable of the five. If your build itself fails here, that's a different failure class entirely: game build errors and their quick fixes covers that territory.
Why verifications actually fail
Verification is document matching, not judgment. Nearly every failure reported publicly traces to one of six mismatches:
| Failure mode | What triggers it | The prevention |
|---|---|---|
| Name mismatch | Onboarding under a studio, DBA, or "friendly" name; bank account held under a different name | Enter the legal name exactly as it appears on bank and tax documents; sole proprietors enter their full legal name |
| Address mismatch | The typed address differs from the identity document or supporting documents | Copy the address character for character from the ID — this is the exact failure in the 60-day rejection report |
| Unusable ID images | Glare, cropped corners, hat or glasses in the selfie-with-ID, wrong file format | JPEG, all four corners visible, face and document text fully legible |
| New tax ID delay | The IRS hasn't yet ingested a recently issued EIN or ITIN | Apply early: an EIN takes ~4 business days by fax, ~4 weeks by mail; an ITIN can take months |
| Mid-process name change | Founding or renaming a company during onboarding | Finish under your current legal name — a change later forces a full re-onboard and a new partner account |
| Relocation | Moving countries mid-process | Complete onboarding first; a country change forces the tax interview to be retaken |
Two quieter rules from Valve's FAQ deserve their own mention: don't use characters unique to a non-English language in the paperwork, and don't retake the tax interview casually — a retake deletes your previous interview even if that information was already verified and valid.
Every storefront runs its own version of a paperwork gate. Google Play's is the closed-testing requirement — 12 testers for 14 continuous days on new personal accounts — and its upload errors are a known taxonomy with fixes, covered in the top Android publishing errors and their fixes. Apple's is review rejection. Steam's is this: an identity check with no published timeline, where the risk isn't judgment but paperwork drift.
What to do, before and during
Before you pay the $100:
- Assemble the triple. Identity document, bank account details, and tax ID — then confirm the legal name and address agree across all three. This one hour of checking is the highest-leverage hour in the whole funnel.
- Decide your entity now. Individual or company, but decide before starting: the name you onboard under must be the name on the bank account and tax forms, and changing it later means starting over.
- Pre-write your details. Legal name, legal address as printed on the ID, company form ("a Washington State corporation," "a sole proprietorship"), tax ID. Type from documents, not from memory.
While verification runs:
- Watch your email like it's launch day. Valve explicitly warns that verification requests additional documentation by email and that the process waits on your response. A request sitting unread for a week is a week added to your timeline.
- Don't touch the tax interview. Editing is locked during verification anyway, and a casual retake deletes verified information. Only retake on a genuine change of circumstances.
- Prepare everything that doesn't need Steamworks access. Store page copy, capsule images, trailer, the coming-soon announcement. Store configuration unlocks when onboarding completes, but assets don't render faster for being started late — and the 14-day visibility clock will need that page ready.
- Keep shipping momentum elsewhere. If verification drags, a web build of the same game is a venue you control while Valve's queue runs. Portals gate hard too — why web game portals reject indie games covers that funnel — but a playable URL somewhere is progress a queue can't take away.
What the calendar actually looks like
| Scenario | Realistic calendar |
|---|---|
| Clean documents, first pass | Verification 1–2 weeks, overlapping the fixed 21-day window; earliest release ≈ one month after the fee |
| One document mismatch caught by email | Add one request-response round: typically 2–7 business days, longer if the fix is incomplete |
| Name or entity change discovered mid-process | Re-onboarding under a new partner account — effectively starting the paperwork over |
| Worst reported case | 45 business days of verification, or 60+ calendar days ending in rejection — the failure the prevention table above exists to keep you out of |
The pattern across these rows: the funnel's floor is fixed and its ceiling is self-inflicted. Valve's clocks are what they are; the document mismatches are the part you control completely.
Five mistakes worth avoiding
Onboarding under the studio name. The name that felt right on the itch.io page is a mismatch against a passport and a bank statement. Use the legal name; brand names belong on the store page, not the paperwork.
Typing the address from memory. The 60-day rejection was over an address. Memory rounds, abbreviates, and updates stale apartment numbers; the ID document doesn't.
Treating the ID selfie as a formality. Valve wrote a best-practices page about this photo because people fail on it: cropped corners, glare, hats, wrong format. It's the cheapest failure in the funnel to prevent and one of the slowest to recover from.
Planning launch off the review clock. The 1–5 day review is the number people quote and the least of your problems. The real runway is verification plus the fixed 21 days plus 14 days of Coming Soon visibility — plan against that sum, not the review.
Going dark during the wait. The months that verification can consume are months your game can still improve or your audience can still grow. A stalled Steam funnel with a live web build and a growing wishlist line is a delay; a stalled funnel with nothing else running is a stop.
Where Egmatic fits
The uncomfortable truth about verification is that it's dead calendar time for the business but potentially valuable time for the game. The layer we're building at Egmatic is aimed exactly at that gap: a pipeline where you direct the work — design decisions, what changes, what ships — and an AI teammate executes the builds, with every exported file staying yours. You direct, it executes, you own it.
We're pre-alpha and say so plainly: early access today means build news a handful of times a year, not promises of magic. But if the vision appeals — using the queue's dead time to make the build that clears the 1–5 day review on its first pass — then this is the pipeline worth watching:
Fact-check notes
Checked November 20, 2026, against Valve's live partner documentation and current community reporting:
- Onboarding sequence, the 21-day fee-to-release waiting period, the 14-day Coming Soon visibility requirement, the 1–5 day store/build review, the bank-name match rule, and the $100 fee terms: partner.steamgames.com Onboarding page, fetched live November 20, 2026.
- Tax verification at 2–7 business days, the ~30-day IRS database delay for newly issued TINs, the 5–10 minute tax interview, W-9/W-8BEN routing, the name-change re-onboarding rule, and the non-English-characters rule: partner.steamgames.com Onboarding FAQ, fetched live November 20, 2026.
- Selfie-with-ID requirements (JPEG, four corners, no unlisted hats or glasses): partner.steamgames.com Identification Documents Best Practices page, fetched live November 20, 2026.
- Fee non-refundability, recoupment at $1,000 adjusted gross revenue, wallet-funds exclusion, and VAT treatment: partner.steamgames.com Steam Direct Fee page, fetched live November 20, 2026.
- The 45-business-day identity-verification figure, the 60-day wait ending in an address rejection, and the "build approval stuck 1 day before launch" report: r/gamedev threads captured in the Egmatic feedback digest, sweep of November 11, 2026 — community reports, not Valve-published timelines, and labeled as such in the text.
- Google Play closed-testing gate (12 testers, 14 continuous days): our own October 2026 verification, documented in the Android publishing errors article linked above.
- EIN and ITIN issuance timelines (fax ~4 business days, mail ~4 weeks, ITIN "a few months or longer"): quoted from Valve's Onboarding FAQ citing IRS processing, November 20, 2026.