
How to fill in Steam's AI disclosure, with examples
Describe the AI-made content that ships in your game and that players see or hear, such as art, sound, text or localisation, and say how you made it. Valve says efficiency gains from AI dev tools are "not the focus". If AI generates content while the game runs, also describe your guardrails against illegal content.
- List what ships
- 2Pre-Generated wording
- 3Live-Generated guardrails
- 4Submit for review
- 5Update via Support
The example wording on this page is ours, not text Valve supplies or approves. Describe what your game actually does. This isn't legal advice.
In or out of scope? A quick list
| Situation | Disclose? | Why (Valve's wording, or what it doesn't say) |
|---|---|---|
| AI concept art you painted over and shipped in the game | Yes, as Pre-Generated | Pre-Generated covers content "that ships with your game and is consumed by players that is created with the help of AI tools during development". |
| AI music or sound effects in the build | Yes, as Pre-Generated | The section names "artwork, sound, narrative, localization, etc." |
| AI voice lines in the build | Yes, as Pre-Generated | Voice lines are sound that ships with the game and players hear. |
| AI-translated store or in-game text | Yes, as Pre-Generated | "Localization" is one of Valve's named examples. |
| Code written with Copilot, Cursor, Claude Code or ChatGPT | Not stated by vendor | Valve says efficiency gains from AI-powered dev tools are "not the focus of this section". Whether shipped AI-written code itself must be listed: Not stated by vendor. |
| AI images used only as reference, nothing AI-made ships | Not stated by vendor | The section is about content that "ships with your game". Valve doesn't list reference-only use, so this row is our reading, not Valve's. |
| AI placeholder art removed before release | Not stated by vendor | Valve compares your answers "relative to the content in your build". The rule that you disclose content even if it's not accessible is written for mature content, not AI. |
| An LLM writes NPC dialogue while the game runs | Yes, as Live-Generated | Live-Generated is content "created with the help of AI tools while the game is running", and you must describe your guardrails. |
Source: Steamworks Content Survey · Checked
Everyone: steps 1–2
Know what the AI section asks
- Open the Content Survey in Steamworks before you submit your store page and build for review. It has three parts: General Content, Mature Content and Generative AI Content.
- Read the AI part as being about content that ships with your game and that players consume, such as artwork, sound, narrative and localisation.
- Keep the full rules page open: our Steam & store AI disclosure page summarises Pre-Generated and Live-Generated AI and other stores' rules.
You should see: A list of the content types in your build that AI helped make, and whether any AI runs while the game is playing.
Watch out: Valve's review compares your answers "relative to the content in your build and on your store page", so describe the build you're actually submitting.
From the official docs: Steamworks: Content Survey ↗
List every AI-made thing that ships
- Go through your build by content type: art, UI, music, sound effects, voice, story and dialogue text, translations.
- For each one, note the tool you used and what a person did after (repainted, edited, re-recorded, proofread).
- Mark anything AI generates at runtime separately: that's Live-Generated.
You should see: A short table of content type, tool and human step that you can turn into one or two sentences each.
Watch out: Disclosure doesn't fix a licence problem. Check each tool's commercial-use terms on its listing or the cheat sheet before you ship its output.
From the official docs: Steamworks: Content Survey ↗
Then pick your path
Pre-Generated examples
Art and UI
- Example (ours): "Background environment concepts were generated with [tool] and repainted by our artist. Final in-game backgrounds are hand-finished."
- Name the content (backgrounds, item icons, portraits), the tool, and the human step.
You should see: One or two plain sentences a reviewer can check against the build.
Watch out: Don't describe AI use you didn't ship. Valve's section is about content that ships and players consume.
From the official docs: Steamworks: Content Survey ↗
Music and sound effects
- Example (ours): "Some ambient music loops and UI sound effects were generated with [tool], then edited and mixed by us."
- If only some tracks are AI-made, say which kind (ambient loops, menu music, foley).
You should see: A sentence that tells players which sounds came from AI.
Watch out: Several AI music tools only allow commercial use on paid plans; check before release.
From the official docs: Steamworks: Content Survey ↗
Voice lines
- Example (ours): "Voices for minor NPCs were generated with [tool] text-to-speech from our own scripts. Main characters are voiced by human actors."
- Say which characters or lines use AI voices.
You should see: A clear split between AI voices and recorded voices.
Watch out: Voice cloning of a real person raises consent questions that disclosure doesn't answer.
From the official docs: Steamworks: Content Survey ↗
Story, dialogue and item text
- Example (ours): "First drafts of item descriptions and side-quest dialogue were written with [tool] and rewritten by our writer."
- Mention the share only if you know it (for example, item descriptions only).
You should see: A sentence naming which text started as AI drafts.
Watch out: Don't invent percentages. Describe what you did.
From the official docs: Steamworks: Content Survey ↗
Localisation
- Example (ours): "The French, German and Spanish translations were machine-translated with [tool] and reviewed by native-speaking testers."
- List the languages and whether a person reviewed them.
You should see: A sentence players of each language can rely on.
Watch out: If a language was not reviewed by a person, say so plainly rather than implying it was.
From the official docs: Steamworks: Content Survey ↗
Live-Generated and guardrails
Describe the runtime AI
- Example (ours): "Tavern NPCs answer the player's typed questions using [model] from [provider], accessed through our server."
- Say what the AI generates while the game runs (text, voice, images) and where it runs.
You should see: A reviewer can tell exactly which feature uses runtime AI.
Watch out: Live-Generated content follows the same rules as Pre-Generated content, plus the guardrails requirement.
From the official docs: Steamworks: Content Survey ↗
Describe your guardrails
- Example (ours): "Player input is filtered for banned topics before it reaches the model. Every reply passes an output moderation check, NPCs refuse sexual, hateful and illegal topics, players can report a reply from the dialogue menu, and reports are logged for review."
- Cover input filtering, output moderation, blocked topics, player reporting and logging.
You should see: An answer to Valve's request to "tell us what kind of guardrails you're putting on your AI to ensure it's not generating illegal content".
Watch out: Valve says it doesn't want to ship Live-Generated AI Adult Only Sexual Content "at this time".
From the official docs: Steamworks: Content Survey ↗
Plan for running costs
- Pick how players pay for ongoing AI costs. Valve's FAQ lists four ways: build it into the game's price, microtransactions for each interaction, a subscription for ongoing access, or a one-off DLC that unlocks unlimited interactions.
- Collect any payment with a Steam-supported payment method.
You should see: A monetisation plan that matches what your store page says.
Watch out: You manage access to the external AI service for your players, so plan for the service changing its prices or models.
From the official docs: Steamworks: Content Survey ↗
After release
Change your answers when the content changes
- If an update adds or removes AI content, check whether the survey still matches.
- Some answers can't be edited after approval without contacting Steam Support. Send a summary of what changed, which survey answer it affects and how a tester can reach the content.
You should see: Your survey answers match the current build.
Watch out: Keep your own notes of tools and dates as you go. They make the update email quick.
From the official docs: Steamworks: Content Survey ↗
Remember what disclosure doesn't do
- Treat the survey as a description, not a permission slip.
- Re-check the content rules for anything you disclose.
You should see: Valve's FAQ answer: "Products on Steam must adhere to the content rules, regardless of whether it is disclosed in these surveys."
Watch out: Disclosure also doesn't settle a tool's licence. A non-commercial free plan stays non-commercial after you disclose it.
From the official docs: Steamworks: Content Survey ↗
Questions
What do I write in Steam's AI disclosure?
Describe the AI-made content that ships in your game and that players consume, such as art, sound, text or localisation, and how you made it. The example wording on this page is ours, not Valve's. source
Do I have to disclose Copilot or ChatGPT for code?
Valve says efficiency gains from AI-powered dev tools are "not the focus" of the AI section. Whether shipped AI-written code itself must be listed is Not stated by vendor. source
What's Live-Generated AI?
Content created with the help of AI tools while the game is running. As well as following the Pre-Generated rules, you must tell Valve what guardrails stop it generating illegal content. source
Can I change my answers after release?
Some answers can't be edited after your build and store page are approved without first contacting Steam Support. Send a summary of what changed and which survey answer it affects. source
Does disclosing make any AI content OK?
No. Valve says products on Steam must follow its content rules whether or not the content is disclosed in the survey. source
Example wording is ours, not Valve's, and this is a summary of Valve's public Content Survey page on the check date, not legal advice. The exact field labels and character limits inside Steamworks are behind a login: Not stated by vendor. Written from the official documentation linked on each step and checked . No vendor reviews or pays for these guides.