SteamSteamworksSteam DirectValvePartner AccountSteam Direct Fee
Steamworks Account Setup for Indie Devs
Step-by-step Steamworks partner signup for indies: paperwork, tax, bank match, $100 Steam Direct fee, and timers before you ship.

Steamworks / Steam Direct (Valve). Hover for a Voidge draft sketch inspired by a fragment of the still. This is Part 1 of the Ship It on Steam tutorial series.
Legit: if you want your first indie build on Steam, you do not start in SteamPipe. You start by becoming a Steamworks partner. That means a Steam account, digital paperwork, bank and tax that actually match your legal name, identity checks, and the Steam Direct Fee. This guide is the clean install for that first gate.
This is a tutorial, not a vibes post. I am walking the official Steam Direct and Onboarding path in systems order so you do not brick your partner account on day one.
Series map
- You are here: partner account + onboarding
- App credit + create Application (next)
- Store page assets
- SteamPipe depots
- Review, Coming Soon, wishlists, release
Ship it one patch at a time.
What you need on the desk before you click Sign in
Have this ready. Valve is not guessing who they are paying.
- A personal Steam account you control (this becomes your Steamworks login).
- Your legal first and last name (no alias, no Discord tag cosplay).
- Company Legal Name that matches bank and tax docs. Solo? Use Sole Proprietorship and your legal name as the company name. No DBA / friendly studio nickname here.
- A bank account under that same legal name (routing, account number, bank address). Name mismatch = stalled payouts.
- Tax facts for the interview (US folks think W-9 shape; many non-US folks think W-8BEN shape). Exact forms depend on where you live.
- A payment method Steam supports in your region for the $100 USD (or equivalent) Steam Direct Fee. Steam Wallet funds are not allowed for this fee.
Official source of truth: Onboarding docs and the Steam Direct Fee page.
Walkthrough video
Signup mindset, then the Steamworks checklist once you are inside. Prefer Valve docs if anything conflicts.
Open on YouTube if the embed does not load.
Step 1: Open Steam Direct and sign in
- Go to partner.steamgames.com/steamdirect.
- Sign in with the Steam account that will own Admin / Actual Authority for your partner.
- Choose the developer / publisher path and start the digital paperwork.
That Steam login is the keys to the kingdom. Guard it like a based config file.
Step 2: Sign the NDA and Steam Distribution Agreement
You electronically sign Valve's NDA and the Steam Distribution Agreement. Read them. Same page lists content rules: hate speech, unlabeled adult content, malware, crypto/NFT exchange apps, and ad-driven junk are hard nos. Games are the main yes. Gray-area tools should check the accepted list before you burn a fee.
Step 3: Company ID that matches reality
Valve wants the legal entity that owns publish rights and signs the Distribution Agreement.
- Legal first + last name only (no alias)
- Company Legal Name matching bank + tax docs
- Company Form (sole proprietorship, corporation, etc.)
- Solo: Sole Proprietorship + your legal name as Company Name
Bank account holder must match that legal name or payouts stall. That patch slapped harder than any FAQ reply.
Step 4: Bank + tax interview
Bank: routing, account number, bank address, holder matching your legal entity.
Tax: a short questionnaire steers you into the right forms. Third-party verification takes about 2 to 7 business days, sometimes with extra doc emails. You cannot casually edit tax info until that finishes. US data often looks W-9 shaped; many non-US cases look W-8BEN shaped. Details: FAQ.
Step 5: Pay the Steam Direct Fee ($100)
Per product you want on Steam, you pay the Steam Direct Fee: $100 USD or regional equivalent.
- Pay with a Steam-supported method in your country.
- Not with Steam Wallet funds.
- Fee is not refundable, but it is recoupable after the product hits at least $1,000 Adjusted Gross Revenue from Steam Store and in-app purchases (Valve's wording).
- Chargebacks / fraud flags can freeze revenue and fee repayment.
During first-time signup you are sent through the Steam store to pay, then bounced back to finish paperwork. Later, partner Admins can buy more app credits from the Steamworks home button. Only the payer activates that credit. Docs: Steam Direct Fee.

Step 6: Identity verification
Valve confirms who they are paying. Keep docs consistent and answer email requests fast. Not optional DLC.
Timers you should schedule now (even before the build is fun)
Official onboarding calls out timing that bites first-timers:
- Review: before store page or build go live, Valve runs a short check (about 1 to 5 days).
- 30-day wait: between paying the app fee and releasing your first titles, there is a 30-day waiting period while they confirm who you are.
- Coming Soon: you need a publicly visible Coming Soon page up for at least two weeks before release so wishlists and presentation practice can happen.
That means the clock starts when you pay and publish Coming Soon, not when you feel emotionally ready. Plan the build calendar around those gates.
Second video: Steam Direct reality check
Indie-angled look at Steam Direct after signup. Cross-check fees and timers against Valve docs.
Open on YouTube if the embed does not load.
Checklist: are you actually onboarded?
- Steam Direct signup started on the partner Steam account
- NDA + Distribution Agreement signed
- Legal company name + form match bank and tax
- Bank details submitted under the matching name
- Tax interview submitted and verification emails watched
- Steam Direct Fee paid (not via Wallet)
- You can see Steamworks home / manage users tools
- Calendar notes for 30-day wait + 2-week Coming Soon
When those boxes are patched, Part 2 turns the app credit into an Application without wasting the $100 on a blank checklist.
Keep these tabs open: Steam Direct, Getting Started, Onboarding, Steam Direct Fee.
Fps locked. See you in Part 2.
Image credits & rights
Images on this page are hotlinks from the official Valve / Steamworks websites, used with respect for their copyright.
