itch.io AI Game Policies in 2026: A Practical Compliance Walkthrough for Indie Devs

Why itch.io's AI rules matter more in 2026 than they did in 2023

itch.io has never banned AI-generated content outright, and that is precisely why the platform's policy has become the most scrutinized in indie games. Unlike Steam, which since January 2024 has required developers to disclose AI use in a dedicated pre-launch form and now reviews those disclosures case by case, itch.io relies on a lighter-touch model: creators must accurately describe what they made and how, and the platform reserves the right to remove listings that misrepresent authorship. In a market where a 2025 GDC survey found roughly 30% of game developers reporting some generative AI use in their workflow, that lighter-touch model is both an opportunity and a trap.

The opportunity is that itch.io remains the fastest path from a build folder to a public page. The trap is that "accurate description" is doing a lot of work in that sentence. In 2026, buyers are more AI-literate than they were two years ago, and a growing number of them scan store pages specifically for disclosure language. A vague tag or a buried note in the credits is now more likely to produce refund requests and review-bombing than it is to protect a launch.

This walkthrough is not legal advice, and itch.io's terms can change. But it is a practical map of where the policy friction actually sits, drawn from how the platform's listing tools, tagging system, and moderation have evolved, and from what comparable storefronts now demand.

The policy in practice: what itch.io actually asks of you

Disclosure lives in the page, not in a form

The single biggest structural difference between itch.io and Steam is where disclosure happens. Steam's AI disclosure is a checkbox-and-description step in the backend that reviewers see before a store page goes live. itch.io has no equivalent mandatory AI form. Instead, the expectation is embedded in the project page itself: the description, the tags, the credits, and the asset files you upload.

That means the burden falls on you to decide what counts as material AI use and to state it plainly. In practice, moderation tends to respond to (a) reports from users who feel misled, and (b) obvious mismatches between a page's claims ("hand-painted," "solo-developed over three years") and the content. The policy is therefore less a checklist and more a truthfulness standard — which is harder to game and easier to fail accidentally.

The asset-level question: what you upload is part of the claim

itch.io hosts downloadable builds and asset packs, and many creators sell art, music, and sound packs alongside games. If a pack contains AI-generated sprites, music, or voice, the listing needs to say so. This is where a lot of quiet violations happen: a developer generates background music with a tool like Soundraw or Suno, ships it in a game, and never mentions it because the game itself is "mostly hand-made." That may pass a casual read, but it fails the truthfulness standard if the page implies all assets are original human work.

The safer pattern is asset-level labeling: a short "AI use" section in the description that names the categories (art, audio, code, text) and the tools, without turning the page into an essay. Buyers who care will find it; buyers who don't will skip it. Everyone gets an accurate record.

How the disclosure standard compares across storefronts

The itch.io approach only makes sense in contrast to its neighbors, because most indie developers ship to more than one store.

Steam formalized AI disclosure in January 2024 with a pre-launch review process, and by 2025 it had refined the distinction between pre-generated (live-generated) content and content generated during runtime. Valve's reviewers can and do reject pages where the disclosure is incomplete. Epic Games Store has been slower to publish a dedicated AI policy, leaning on its general content guidelines, while Google Play and Apple's App Store have moved toward requiring developers to flag generative AI features that produce user-facing content. The net effect is a patchwork: the same game may need a formal disclosure form on Steam, a runtime-AI note on mobile, and a plain-language paragraph on itch.io.

That patchwork is the real compliance cost in 2026 — not any single platform's rules, but keeping the story consistent across all of them. A page that says "no AI" on itch.io while a Steam form lists AI-generated audio is the kind of inconsistency that attracts reports.

Real cases and concrete numbers worth knowing

• Steam's January 2024 disclosure rollout remains the reference point. Valve's initial policy required developers to describe AI use at submission, and the company later clarified that live-generated content (e.g., an LLM-driven NPC) needs additional guardrails described in the build. Any itch.io page that also ships on Steam should align its language with that form.
• The 2025 GDC State of the Game Industry survey reported about 30% of developers using generative AI in some capacity, with sentiment split sharply by discipline — artists and writers were the most skeptical. That split is why disclosure matters commercially, not just legally: your buyers are not a monolith.
• The 2023–2024 Steam AI-art wave — hundreds of low-effort AI-generated games submitted in a short window — is the origin story for most platform skepticism. itch.io's lighter rules exist partly because its community is smaller and more curated, but the same wave reached it, and moderation tightened in response.
• Tool-level licensing shifts matter too. Adobe's Firefly model, integrated into Photoshop, was trained on licensed and public-domain content and marketed as commercially safe; Midjourney's terms have changed repeatedly. If your page names a tool, make sure the license you relied on at generation time still covers commercial release.

Practical advice: a pre-upload routine that holds up

1. Inventory AI use by asset category before you write the page. List art, audio, voice, code, text, and runtime features separately. "We used AI" is too vague to be useful and too vague to be credible.
2. Write a short, plain-language AI section in the description. Two to five sentences naming categories and tools beats a legalistic disclaimer. Put it above the fold if AI is central to the game.
3. Label asset packs at the item level. If you sell a pack, state which files are AI-generated and which are not. This is the most common source of buyer disputes.
4. Keep your cross-platform story identical. Match your itch.io wording to your Steam disclosure form and any mobile flags. Inconsistency is the fastest route to a report.
5. Document tool versions and dates. Record which model or tool version generated each asset. Licenses and terms shift; a dated log protects you if a tool's commercial-use terms change after launch.
6. Check licenses for every tool in the chain. Tripo3D for 3D props and Play.ht for voice both have terms that govern commercial use and redistribution — read them before you ship, not after.
7. Use runtime AI guardrails if you ship an LLM feature. If your game generates dialogue or content live, describe the moderation layer on the page. Steam expects this; itch.io buyers increasingly ask for it.
8. Respond to reports quickly and factually. A corrected page is almost always cheaper than a removed one.

Outlook: disclosure becomes a trust signal, not a tax

The direction of travel is clear. Storefronts are converging on the principle that AI use must be disclosed, even as the mechanics differ. itch.io is unlikely to adopt Steam's formal review form, because its identity depends on low-friction publishing — but it will keep enforcing truthfulness through reports and moderation, and its community's tolerance for vague pages is falling, not rising.

The practical implication for indie developers is that disclosure is shifting from a compliance cost to a marketing asset. In a 2026 market where AI-assisted games are common, a page that clearly states what was made by hand and what was assisted reads as competent rather than apologetic. The developers who will struggle are not the ones who use AI — they are the ones whose pages tell a story that does not match the build. Get the story right before you hit publish, and itch.io's light-touch policy works in your favor.