itch.io AI Game Policies in 2026: A Submission Workflow for Indie Devs

Why itch.io's AI rules matter more in 2026

itch.io has become the default home for experimental, small-team, and solo-developed games. That makes its content policy the de facto front door for AI-assisted indie work. The platform's approach has stayed consistent in spirit since it first addressed generative tools: it does not ban AI, but it requires creators to disclose how AI was used and to keep the storefront honest for players. In practice, the policy is enforced through manual review and community reporting rather than automated scanning, which means the burden falls on the developer to get the paperwork right before publishing.

The stakes rose through 2025 and into 2026. Steam's disclosure form, introduced in January 2024, normalized the idea that storefronts ask for AI usage details at upload. itch.io's own guidance has evolved alongside that norm, and the platform has been explicit that undisclosed AI content—especially in paid games—can lead to delisting. For indie devs, the practical question is no longer "is AI allowed?" but "what exactly do I need to declare, and when?"

What the policy actually asks for

Disclosure, not prohibition

itch.io's position is best read as a transparency requirement. If you used generative AI to produce assets, code, dialogue, or audio, you are expected to say so on the project page. The platform distinguishes between AI used as a tool in your pipeline (for example, an AI-assisted texture pass refined by hand) and AI used to generate the bulk of the content. The former still warrants a note; the latter needs a clearer statement so buyers know what they are getting.

The disclosure belongs in the project description or a dedicated credits/notes section, not buried in a comment. Reviewers and players look for it there. A short, plain-language paragraph—"Background music generated with [tool], then edited in a DAW"—is usually sufficient. Vague statements like "some AI was used" invite follow-up questions and can slow review.

What triggers scrutiny

Three things reliably draw attention: paid games with AI-generated art or voice, projects whose storefront copy reads as machine-written, and assets that closely resemble known copyrighted work. itch.io does not publish a checklist, but its moderation behavior tracks the same concerns Steam formalized: likeness rights, training-data provenance, and whether the storefront misrepresents the product.

A useful mental model is that itch.io cares about the buyer's ability to make an informed purchase. If a player pays for a game and later discovers the character portraits were AI-generated with no mention, that is the failure mode the policy exists to prevent. Disclosure is cheap; a refund dispute or delisting is not.

A repeatable submission workflow

Step 1: Inventory your AI usage

Before you touch the upload form, list every asset category and mark whether AI touched it: code (Copilot, Cursor), 2D art (Photoshop (AI), Midjourney, Stable Diffusion), 3D models (Tripo3D, Kaedim), audio (Suno, Play.ht), and writing. Keep this inventory in your repo. It doubles as your credits file and your defense if a claim is questioned later.

Step 2: Write the disclosure in plain language

Draft two or three sentences per category. Name the tool and describe the human contribution. "Character sprites generated with Stable Diffusion, then repainted and animated by hand in Krita" tells a reviewer and a player exactly what happened. Avoid both overclaiming ("fully hand-drawn") and hand-waving ("AI-assisted").

Step 3: Check provenance and licensing

Confirm that the model or service you used permits commercial output. Most major image and audio tools now grant commercial rights on paid tiers, but the terms differ and change. Keep receipts—subscription records and the license text at the time of generation. If you used a model trained on scraped data, be ready to explain your position; itch.io is more likely to act on a specific complaint than to audit proactively.

Step 4: Publish, then monitor

After upload, watch your project's comments and the platform's moderation messages for the first week. If a reviewer asks for clarification, respond with your inventory and the exact disclosure text. Most issues at this stage are documentation gaps, not policy violations.

Real cases and data points

Steam's AI disclosure form went live in January 2024 and by 2025 covered tens of thousands of titles, establishing the disclosure-at-upload pattern that itch.io's guidance mirrors. Valve's own framing—separating "pre-generated" from "live-generated" content—is a useful template even where itch.io's language is less formal.

On the tooling side, Adobe's Firefly model, integrated into Photoshop since 2023, ships with commercial indemnification for enterprise customers, which is why many indie studios route AI image work through Photoshop (AI) rather than raw diffusion models. Audio is similar: Suno and Udio both updated their commercial terms in 2024 and 2025, and studios now routinely document which tier they generated on.

A concrete failure pattern is worth noting. Through 2024 and 2025, several itch.io projects were delisted or forced to update their pages after players identified uncredited AI voice or art. The common thread was not the AI itself but the mismatch between the storefront's claims and the actual pipeline. That is the risk the policy is designed to catch.

Practical advice for indie devs

• Keep an AI usage inventory in your repository from day one; retrofitting disclosures before launch is where mistakes happen.
• Disclose by category and name the tool—reviewers and players respond better to specifics than to blanket statements.
• Prefer tools with clear commercial terms and keep subscription receipts; provenance questions are easier to answer with documentation.
• Do not let AI write your storefront copy unedited; machine-written descriptions are a common trigger for scrutiny and read poorly to players.
• If you use AI voice or likeness, secure consent for any real person referenced, and say so in the disclosure.
• Treat the disclosure as marketing, not confession—players increasingly reward transparency about production methods.
• Respond to moderation messages within days and include your inventory; most disputes resolve at the documentation stage.

Outlook

Expect itch.io's guidance to converge further with Steam's disclosure model rather than diverge. The direction of travel across storefronts is structured disclosure at upload, clearer separation of pre-generated and live-generated content, and more attention to likeness and provenance complaints. For indie devs, the winning strategy is unglamorous: document your pipeline, name your tools, and write disclosures a player would actually understand. Studios that treat transparency as part of the craft will keep shipping on itch.io without friction; those that treat it as paperwork will keep discovering the policy the hard way.