itch.io AI Game Policies in 2026: A Pre-Upload Checklist for Indie Devs

Why itch.io's AI Rules Matter More in 2026

itch.io has never published a single, stable "AI policy" page the way Steam has. Instead, the platform's expectations live in its Content Rules, its FAQ, and the moderation decisions that follow reports from users and creators. That ambiguity is the problem: developers uploading an AI-assisted game in 2026 are not checking a box, they are guessing at a moving target.

The pressure has increased from both directions. On the buyer side, itch.io's audience skews toward experimental, art-forward, and often explicitly anti-generative-AI work. A storefront page that hides AI involvement can turn a launch into a comment-section fight faster than a bad build. On the seller side, the platform's payout and moderation systems are small and human, which means ambiguous cases get handled by a person reading your page, not an automated classifier. The practical result is that disclosure quality matters more than disclosure quantity.

This guide is not legal advice, and itch.io's rules can change without a changelog. It is a pre-upload checklist built around how the platform actually behaves: what gets flagged, what gets ignored, and where indie developers most often get caught out.

The Core Analysis

What itch.io actually asks for

itch.io's Content Rules require that games not misrepresent their content, and its broader moderation approach treats storefront pages as the primary artifact under review. There is no dedicated "AI disclosure" form. Instead, the expectation is that if generative AI materially contributed to your game's art, audio, writing, or code, the storefront page should say so in plain language — typically in the description or a dedicated credits section.

The distinction that matters is between "AI-assisted" and "AI-generated." A developer who uses Krita with an AI inpainting plugin to clean up a hand-painted background is in a different category from one who ships a Midjourney-generated sprite sheet. itch.io's moderators and community have been more tolerant of the former and more critical of the latter, especially when the AI output is the visible product being sold.

What actually triggers a problem

In practice, three things get developers into trouble on itch.io:

1. Undisclosed AI art on the storefront thumbnail. The cover image is the most-scrutinized asset on any itch.io page. If it looks generated and the page does not say so, expect reports.
2. AI voice or music presented as commissioned work. Crediting a fictional composer or voice actor when the audio came from Play.ht or Suno is the fastest route to a credibility problem that follows the developer across platforms.
3. AI-generated code sold as a framework or template. itch.io hosts a large market for code assets. A "hand-written" Godot or Unity system that was largely LLM-generated is a recurring complaint category in developer communities.

The pattern is consistent: the issue is rarely the use of AI itself, it is the mismatch between what the page implies and what the build contains.

Real Cases and Data Points

Steam's approach offers the clearest contrast. Valve began requiring AI disclosure in January 2024 and has since processed tens of thousands of submissions under that regime, with a public-facing disclosure field on each store page. That visibility has made "AI disclosed" a searchable attribute, which in turn has made non-disclosure on other platforms more conspicuous by comparison. itch.io has not built an equivalent field, so the burden falls on the developer's description text.

On the tooling side, the disclosure question has become more complex as pipelines have matured. Adobe Firefly's commercially safe model, integrated into Photoshop since 2023, is trained on licensed and public-domain content, which is why some developers now treat Firefly output differently from Midjourney or Stable Diffusion output in their credits. Similarly, Scenario's game-asset training tools and Tripo3D's text-to-3D pipeline have made it possible to generate a full set of 3D props in an afternoon — a workflow that would have been unthinkable for a solo developer in 2022 and that now requires explicit disclosure if the props ship in a paid game.

A concrete data point worth internalizing: itch.io's own creator day events and seasonal jams routinely feature hundreds of entries, and jam hosts increasingly add their own AI rules on top of the platform's. A 2025 narrative jam, for example, explicitly banned AI-generated writing while permitting AI-assisted coding tools. Developers who assumed platform-level rules were the only rules got disqualified. The lesson is that on itch.io, the jam page and the storefront page are separate contracts.

Practical Advice

• Write an explicit AI section in your description. A short paragraph listing which tools touched which assets is enough. Name the tool category (image generation, voice synthesis, code assistance) and the scope (concept art, final assets, placeholder only).
• Keep a build manifest. Before upload, list every asset and its provenance. This takes an hour and saves a moderation thread later. If a tool like Soundraw produced your OST, say so in the credits.
• Separate placeholders from shipped assets. AI-generated placeholders that never ship do not need disclosure, but be ready to prove it if asked. Keep the placeholder folder in your repo history.
• Check jam rules separately. Read the jam page's AI clause before entering. Platform rules do not override jam-specific rules.
• Do not invent human credits. If a voice is synthetic, credit the tool. Fabricated credits are the single most damaging disclosure failure because they read as intentional deception.
• Use the cover image honestly. If the thumbnail is AI-generated, disclose it in the first screen of the description, not buried in a credits block.
• Be specific about code assistance. "AI-assisted scripting" is vague; "LLM-assisted dialogue system, human-reviewed" is defensible.
• Prepare for comments. itch.io's community will ask. A pinned FAQ comment answering the AI question preemptively is worth more than a defensive reply later.

Outlook

The most likely near-term change is not a formal itch.io AI policy page but tighter enforcement through community reporting and jam-level rules. The platform's small moderation team makes automated AI detection unlikely; human reports will remain the trigger. Developers should expect the disclosure bar to rise for paid games and stay loose for free jam entries, mirroring the pattern already visible on Steam.

The strategic move for indie developers is to treat disclosure as a storefront feature rather than a compliance cost. Pages that state their AI use clearly are increasingly the ones that avoid the comment-section spiral, and in a marketplace where trust is the main currency, that clarity is worth more than the assets it describes.