itch.io AI Game Policies in 2026: What Indie Devs Must Disclose

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

When Steam opened the floodgates to AI-generated games in January 2024, it did so with a permissive framework: disclose your AI use in the store page's legal section, and you're generally fine. itch.io took a different path. In a policy update that has been refined through 2025, the platform now requires creators to actively flag AI-generated content at the point of upload, and it distinguishes between "AI-assisted" and "AI-generated" in ways that have real consequences for discoverability.

The difference matters because itch.io is not a smaller Steam. It is the default storefront for game jams, prototypes, experimental narrative work, and the kind of projects that later get picked up by publishers. A shadowban or a page delisting on itch.io doesn't just cost you sales — it cuts off the feedback loop that many indie devs depend on. Since mid-2025, itch.io has also been surfacing AI disclosure status in its browse filters, which means an undisclosed AI asset isn't just an ethical problem; it's a visibility problem.

What itch.io Actually Counts as AI-Generated

The platform's working definition is broader than most developers assume. It is not limited to assets you generated with Midjourney or Stable Diffusion. Based on creator reports and the platform's own help documentation, the following all trigger the disclosure requirement:

• Generated art, sprites, or textures — including AI-upscaled assets that materially change the original image.
• AI voice acting — tools like Play.ht or Resemble AI used for character dialogue.
• AI music and ambience — Suno, Udio, or Soundraw output, even if heavily edited.
• AI-generated code — this is the gray zone. Most creators report that Copilot-style assistance doesn't require disclosure, but fully generated gameplay systems (e.g., an LLM-driven NPC dialogue engine) often do.
• AI-generated 3D assets — models from Tripo3D or Kaedim count, even if retopologized by hand.

The trap is the "materially change" clause. If you run a hand-drawn sprite through an AI upscaler and the result is visibly different, that's disclosure territory. If you use AI to remove a background and the sprite is otherwise untouched, most moderators treat it as a tool, not generation.

The Disclosure Mechanics

When you upload a project, itch.io presents an AI disclosure field that is separate from the general content warnings. You select from options that range from "no AI used" to "AI-generated assets used throughout." This selection is stored on the project metadata and is queryable through the itch.io API. That last detail is the one most developers miss: third-party tools and curation sites are already scraping this field to build "human-made" collections. If you mislabel, you don't just risk a takedown — you risk being quietly excluded from the curated lists that drive a meaningful share of itch.io traffic.

Where Developers Actually Get Caught

The enforcement stories from 2025 are instructive because they rarely involve a dramatic ban. The common pattern is a user report followed by a manual review, and the penalty is usually a disclosure requirement rather than a delisting. Three recurring failure modes stand out:

1. The asset pack problem. A developer buys a "hand-crafted" asset pack from a marketplace, ships it, and later discovers the pack was AI-generated. itch.io's position is that the developer is responsible for what they ship. In at least two documented cases in early 2025, creators were required to retroactively add AI disclosures after their asset sources were identified by the community.

2. The voice acting gap. AI voice work is the single most-reported category. A 2025 survey of itch.io creators conducted by the Indie Game Developers Association found that 34% of respondents who used AI voice tools had not disclosed it, often because they assumed "AI-assisted" editing of a human performance didn't count. It does if the human performance wasn't the primary source.

3. The jam loophole that closed. For years, game jams on itch.io operated in a disclosure gray area. Starting with the 2025 jam season, several major jams — including a few with tens of thousands of participants — added mandatory AI disclosure to their submission forms, and jam organizers can now filter submissions by disclosure status. This effectively ended the practice of quietly entering AI-heavy projects into "human-made" jams.

The data point that should worry anyone relying on ambiguity: itch.io's own transparency reports indicate that AI-related moderation actions increased roughly threefold between Q1 2024 and Q1 2025, even as overall project submissions grew at a much slower rate. Enforcement is scaling.

Practical Advice for Shipping on itch.io in 2026

• Disclose at the asset level, not the project level. If 90% of your game is hand-made but the background music is AIVA, say so specifically. Vague disclosures invite scrutiny; specific ones don't.
• Keep a provenance log. For every AI tool you use, record the tool name, version, date, and what it produced. If a moderation review happens six months after launch, you'll want receipts.
• Read the jam rules before you build. Many 2026 jams now require disclosure at submission time, and some prohibit AI assets entirely. Building first and reading later is how projects get disqualified.
• Don't rely on "AI-assisted" as a shield. The distinction itch.io cares about is whether the AI generated the asset or merely processed a human-made one. Be honest about which side of that line you're on.
• Check your asset packs. If you bought assets from a marketplace, verify their origin. The disclosure obligation sits with you, not the seller.
• Use the API field. If you're building a portfolio or a press kit, pull your own disclosure metadata and present it consistently. Transparency is now a marketing asset on itch.io, not just a compliance checkbox.

What to Expect Through 2026

itch.io is unlikely to move toward Steam's permissive model. The platform's identity is built on being the human-scale alternative to algorithm-driven storefronts, and its AI policy is a direct expression of that positioning. The more probable trajectory is finer-grained disclosure categories — separating art, audio, code, and writing — and tighter integration with jam organizers' filtering tools.

For developers, the strategic read is simple: treat disclosure as a permanent part of your publishing workflow, not a one-time policy hurdle. The creators who are thriving on itch.io in 2026 are the ones who disclose clearly, document their process, and use that transparency as part of their pitch. The ones getting caught are the ones still hoping nobody checks. Given that the checks are now automated, community-driven, and increasingly baked into the platform's discovery layer, that hope is no longer a strategy.