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

Why itch.io's AI Rules Matter More Than Ever

itch.io has never been the loudest platform on AI. Valve made headlines when it started requiring generative AI disclosure on Steam in January 2024, then refined the policy that April to split pre-generated and live-generated content. itch.io moved more quietly, but by 2024–2025 its content rules had been rewritten to require disclosure of AI-generated assets, and the platform began removing or flagging pages that didn't comply. For a storefront that hosts hundreds of thousands of indie projects and game jams, that quiet shift has outsized consequences.

The reason is structural. itch.io is where prototypes, jam entries, and small commercial releases live. A large share of those projects now touch generative tools somewhere in the pipeline — a Suno track, a Midjourney background, an ElevenLabs voice line. When a platform this permissive starts enforcing disclosure, the people most affected are solo devs and tiny teams who never had a legal or community manager to draft a policy statement.

There's also a reputational layer. itch.io's audience skews toward players who care about provenance. Getting caught hiding AI use is worse there than on a storefront where nobody reads the description. The practical question is no longer "can I use AI?" — it's "how do I label it so I stay listed, stay trusted, and stay shippable?"

What itch.io Actually Requires

Disclosure, not prohibition

itch.io does not ban AI-generated content. Its rules require that you disclose it. The platform's quality and content guidelines ask creators to be transparent about assets that were generated by AI, and moderation has acted against pages that misrepresent how assets were made. That's the core of the policy: the problem isn't the tool, it's the concealment.

In practice, disclosure means stating on the project page which parts of the game use AI — art, music, voice, code, or text — and, ideally, which tools were used. A short, honest "AI disclosure" section in the description is the norm. Some devs go further and list tools per asset category. There is no official standardized template on itch.io the way Steam's disclosure form is structured, which cuts both ways: you have latitude, but you also have no checkbox to hide behind if a moderator disagrees with your framing.

The jam and asset-pack gray zones

Two areas cause the most confusion. First, game jams. Many itch.io jams publish their own AI rules, and they often diverge from the platform baseline — some ban AI art entirely, some allow it with disclosure, some say nothing. The jam's rules govern the jam. Read them before you build, not after.

Second, asset packs and tools sold on itch.io. If you're selling a pack of AI-generated sprites, the same disclosure expectation applies, and buyers increasingly ask. A pack that doesn't say how it was made invites refund requests and bad reviews.

How itch.io Compares to Steam

Steam's system is more formal. After the January 2024 policy and the April 2024 revision, developers must declare whether their game uses pre-generated or live-generated AI, and live-generated content must include guardrails against illegal output. Valve reviews those disclosures and has rejected games for inadequate ones. The disclosure lives in a dedicated field, and it's visible on the store page.

itch.io's approach is lighter-touch and more prose-based. There's no dedicated AI field; you write it into your page. That means enforcement is more subjective and more dependent on user reports. The upside for devs is flexibility — you can explain nuance, like "AI-assisted cleanup on hand-painted art" versus "fully generated." The downside is that the line between compliant and non-compliant is blurrier, so the safe move is to over-disclose rather than under-disclose.

A useful mental model: Steam asks you to fill in a form; itch.io asks you to tell the truth in your own words. Both punish lying. Only one gives you a structured place to do it.

Concrete Cases and Data Points

• January 2024: Valve introduces mandatory AI disclosure on Steam, triggering a wave of delistings and re-submissions. This is the event that pushed the whole indie ecosystem, itch.io included, to clarify its own stance.
• April 2024: Valve revises the policy into the pre-generated / live-generated split. Many itch.io devs who also ship on Steam now maintain two disclosure statements for the same game.
• 2024–2025: itch.io updates its content guidelines to require AI disclosure and removes pages that violate them. The exact enforcement volume isn't published, but community threads on the itch.io forums document takedowns and appeals.
• Tool provenance matters: If you generate music with Suno or Udio, voice with ElevenLabs-class tools, or 3D assets with Tripo3D, those are the things you name in your disclosure. Players and moderators increasingly recognize specific tool signatures.

Practical Advice for Shipping on itch.io

1. Write a disclosure section before you publish, not after a complaint. A three-line block in your project description is enough: what's AI, what isn't, which tools.
2. Be specific per asset type. "AI-generated background music (Suno), hand-drawn characters, AI-assisted code refactoring" beats "some AI used."
3. Check jam rules separately. If you're entering a jam, its AI policy overrides your assumptions. Screenshot it in case of disputes.
4. Keep a provenance log. Track which tool produced which file and when. If a moderator asks, you can answer in minutes instead of guessing.
5. Don't rely on "everyone does it." itch.io's audience is provenance-sensitive. Disclosure protects you commercially, not just legally.
6. Mirror your Steam disclosure if you ship on both. Consistency across storefronts reduces the risk of a contradiction being flagged.
7. If you sell AI-generated asset packs, say so in the pack description and the license. Buyers ask, and a clear answer converts better than a vague one.

Outlook

Expect itch.io's rules to tighten rather than loosen. The platform has been moving from informal norms toward explicit guidelines, and as generative tools get better at producing content that's hard to distinguish from human work, the pressure to require disclosure will only grow. The likely direction is a more standardized disclosure format — possibly a dedicated field — and clearer enforcement criteria for asset packs.

For developers, the strategic takeaway is simple: treat disclosure as a permanent part of your release checklist, not a temporary compliance chore. The devs who document their AI use clearly will have a smaller moderation risk, a better relationship with itch.io's audience, and an easier time porting the same project to Steam or consoles later. The ones who hide it are one report away from a delisted page — and on a platform built on community trust, that's the expensive outcome.