Vibe Coded Games on Steam: Costs, Rules, AI Disclosure
You can publish a vibe coded game on Steam, as long as you pay the $100 fee per game, pass Steam's review and answer its AI questions honestly. A first game has to wait at least 30 days after you pay, so start the paperwork well before the game is done.
This page reports what Steam's own documents say on 2 November 2026. It is general information and not legal advice, and Steam can change these rules.
What does it take?
| Step | What Steam says |
|---|---|
| Fee | $100 per product, not refundable, paid back after the product earns $1,000 in adjusted gross revenue |
| Paperwork | Bank, tax and identity details, about 15 to 30 days |
| Waiting | For your first few titles, 30 days after paying the fee |
| Store page review | Typically 3 to 5 business days. Submit at least 7 days before you want it live |
| Coming soon | The page must be public as coming soon for at least two weeks |
| Build review | Your near-final game is checked, then you press the release button yourself |
What do I have to say about AI?
Steam's content survey asks about AI content that ships with your game and that players consume, such as art, sound, story and translations. It splits this into two kinds:
- Pre-Generated: made with AI tools during development. It is reviewed like any other content.
- Live-Generated: made while the game runs. You must also say what guardrails you put on the AI.
On tools, the survey page says that efficiency gains through AI-powered development tools are "not the focus" of that section. It does not name coding assistants, so read the page and decide how it applies to your game. When in doubt, say more, not less.
What does an honest list look like?
Here is one for an invented game about running a post office on a volcano.
| What | Where it came from | Which kind |
|---|---|---|
| Game code | Written by AI, directed by me | Read the tools note above |
| Letter icons | Drawn by me | None |
| Villager portraits | AI image tool, retouched by me | Pre-Generated |
| Ending song | Bought, licence saved | None |
| Villagers chatting back | AI, while you play | Live-Generated, needs guardrails |
The last row is a real decision. Live AI chat means you must explain how you stop it from saying the wrong thing, and you must keep it working. For a first game, consider writing those lines ahead of time.
Is my game ready?
Ask yourself honestly:
- Is it a download? A browser game needs to be packaged. An engine like Godot says it can release to desktop.
- Does it hold up for an hour? A game can shine for ten minutes and then fall apart. Paying players go further than friends.
- Did strangers finish it? Friends are kind. Try it for free on the web first.
- Do you own everything in it? See Can you copy game mechanics?
Paste this to your AI
I want to release my game on Steam and answer its AI questions honestly. List everything that ships with the game: art, sound, music, text, translations and anything created while the game runs.
Go through the project and say where each item came from, and show me what that rests on: a file, a note or something I told you. If you cannot tell, write "origin unknown". Do not assume I made it.
Then draw a Mermaid chart of the road from my game today to a release on Steam: what each step needs from me and what has to wait for what. Walk along it and mark everything I am missing. Change nothing in the project yet.
Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP
How to check it worked
- Spot-check three items. Is the origin right? Do you remember making them that way?
- Read each "origin unknown". Find out, or replace that item.
- Read Steam's survey page next to your list. Does each row fit what it asks?
- Follow the chart to the end. Do you know how you will do each step?
- Install the game on another computer. Play it for an hour from start to finish.