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

Why itch.io's AI stance matters more in 2026 than it did in 2023

itch.io has never banned AI-generated games. That single fact makes it the default landing pad for solo developers who use generative tools and don't want to fight a storefront over provenance. When Steam tightened its AI disclosure process in January 2024 — requiring developers to declare pre-generated and live-generated content separately during the build review — a meaningful slice of small teams simply stopped bothering and published on itch.io instead.

The platform's own posture has been consistent. In a July 2023 post on its official devlog, itch.io said it would not ban AI-assisted games outright but reserved the right to remove projects that "flood" the storefront or misrepresent how they were made. That is a content-moderation position, not a production-standard position. As of early 2026, no public policy update has replaced it. The itch.io content rules page still centers on harassment, hate speech, doxxing, and illegal content rather than toolchain disclosure.

So the practical question for a developer in 2026 is not "is AI allowed?" It is "what behavior gets a page hidden or an account flagged, and how do I avoid tripping those wires while keeping my pipeline fast?" The answer is more about curation signals and metadata honesty than about model choice.

What itch.io actually enforces, and what it leaves to you

The gap between itch.io's written rules and its moderation behavior is the whole story. Nothing in the public documentation requires a disclosure field for AI assets. There is no equivalent to Steam's AI declaration form, no mandatory tag, and no review queue that checks whether a sprite came from a diffusion model. That absence is the platform's selling point — and its main risk for developers who assume "no rules" means "no consequences."

The three triggers that get AI games flagged

In practice, removals and visibility throttling cluster around three patterns. First, bulk uploads: accounts that publish dozens of near-identical AI-generated titles in a short window get treated as spam, which is exactly the "flooding" language from the 2023 devlog. Second, misrepresentation: describing a game as fully hand-drawn when its store page art is obviously model output invites user reports, and itch.io acts on reports. Third, asset provenance disputes: if a game ships assets that look like they were generated from a named artist's style without consent, that becomes a takedown issue under the same rules that cover any copyright complaint.

None of these require itch.io to take a position on AI itself. They are enforcement actions against spam, deception, and infringement — categories that predate generative models by decades.

Disclosure is a reputational tool, not a compliance requirement

Because there is no mandatory field, disclosure on itch.io is a choice. But it is a choice with asymmetric payoff. Players browsing itch.io are unusually tolerant of AI-assisted projects when the developer is upfront, and unusually hostile when they discover it after the fact. A short, specific note in the project description — which model or tool handled which asset class — costs nothing and defuses the most common complaint pattern. Vague phrases like "some AI was used" tend to read as hiding something, because they are.

The same logic applies to store page art. If your capsule image is AI-generated, say so or accept that a portion of your audience will treat the reveal as a bait-and-switch.

How itch.io compares to Steam, and why the difference shapes your pipeline

The two platforms now represent genuinely different compliance regimes, and that difference should drive where you publish what.

Steam's disclosure process, introduced in January 2024, asks developers to describe how AI was used and, for live-generated content, to implement guardrails that prevent illegal output. Valve's own example was a game whose AI art was found to be infringing; the policy exists partly because that happened. The disclosure is reviewed before release, so a Steam launch has a real gate. itch.io has no gate. You upload, the page goes live, and moderation is reactive.

That asymmetry has a second-order effect on tooling. Developers targeting both platforms increasingly keep two builds: a clean-asset build for Steam and a disclosed-AI build for itch.io, or they simply standardize on tools whose output they can document. For asset generation specifically, image-to-3D and text-to-3D pipelines are the hardest to document because provenance is diffuse — a mesh from Tripo3D or Kaedim may pass through several refinement steps before it ships. Audio is easier: AIVA and Soundraw both produce royalty-free output with clear terms, which makes disclosure straightforward.

If you use AI as a production accelerator rather than a content generator — upscaling textures, converting pixel art to vectors with Vectorizer.ai, or auto-rigging characters — you are in the least contested zone. The disputes that actually escalate are almost always about final shipped assets that a player can point at, not about middleware.

A pre-upload compliance checklist for itch.io

Run through this before you hit publish. It is ordered by how often each item causes real problems.

• Cap your upload cadence. If you are shipping multiple AI-heavy projects, space them out. A single account publishing five generative games in a week reads as a content farm regardless of quality.
• Write a specific AI disclosure in the project description. Name the tool and the asset class. "Character portraits generated with Stable Diffusion, edited in Krita; music by Suno" is the right level of detail. Avoid the word "some."
• Keep generation logs and seed files. If a takedown complaint arrives, being able to show your prompts, model version, and timestamps is the difference between a resolved dispute and a removed page.
• Do not claim hand-made work you didn't hand-make. This is the fastest route to a user report, and itch.io responds to reports.
• Audit for style mimicry. If your prompts named a living artist, rework the assets. This is the one area where itch.io's reactive moderation can still end your page.
• Separate your Steam and itch.io builds if you are launching on both, so the Steam disclosure covers exactly what ships there.
• Use the AI tag honestly. It costs you some clicks and buys you a lot of goodwill with the audience that cares most about the issue.

What to expect through 2026 and into 2027

itch.io is unlikely to add a mandatory AI disclosure field. The platform's identity is built on low friction and permissive publishing, and a formal review gate would undermine the thing that makes it attractive to the developers who fled Steam's process. The more probable trajectory is continued reactive moderation: more automated spam detection, faster response to user reports, and occasional high-profile removals that serve as informal precedent rather than written policy.

For developers, that means the compliance burden on itch.io stays low but the reputational burden stays high. The platform will not stop you from uploading an AI-heavy game. Your players might. The developers who do well in this environment are the ones who treat disclosure as marketing — a signal of confidence in their pipeline — rather than as a legal chore. That is a durable advantage, because it works on every storefront, not just the one with the loosest rules.