itch.io AI Game Policies in 2026: A Disclosure-First Guide for Indie Devs

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

In 2026, itch.io remains the default storefront for indie experiments, game jams, and small commercial releases. That position makes its AI policy the de facto first gate for most developers testing AI-assisted workflows. The platform's approach has stayed consistent in principle since its 2023 wave of AI disclosure requirements: creators must label AI-generated content, and the storefront reserves the right to delist or hide pages that misrepresent how assets were made. What has changed is the volume of submissions and the specificity of enforcement.

itch.io is not Steam. Valve's 2024 policy shift required developers to disclose AI use at the app level and introduced a review layer for live-generated content. itch.io's model is lighter-touch but more reputation-driven: a disclosure field on the project page, community visibility, and a moderation team that responds to reports. For developers, the practical consequence is that your project page is your compliance document. If a buyer, jam organizer, or moderator can't tell what was AI-assisted, you're exposed.

The stakes are higher now because AI tooling has moved from concept art into shipped pipelines. A 2025 survey of indie developers by the Game Developers Conference found that roughly a third of respondents had used generative AI in some part of their workflow, up sharply from prior years. On itch.io, that shows up in asset packs, visual novels with AI-assisted backgrounds, and jam entries built with text-to-3D tools. The platform's rules aren't designed to ban those games. They're designed to make the provenance legible.

What itch.io Actually Requires

itch.io's policy, as it has evolved, centers on three obligations. First, disclose AI-generated content on the project page when it's a material part of the game — art, audio, text, code, or marketing assets. Second, don't misrepresent AI output as human-made, particularly in asset packs and commissioned work. Third, respect the terms of the underlying models and the rights of artists whose work may have informed them. The platform has repeatedly emphasized that it is not adjudicating the ethics of AI training; it is asking creators to be honest about what they used.

The disclosure is not a scarlet letter. Many successful itch.io pages now carry a short "AI disclosure" section listing which tools touched which assets. The failure mode isn't using AI — it's leaving a buyer to discover it later. That's when pages get reported, refunds get requested, and jam organizers get involved.

The gray zones developers keep hitting

Three areas cause most of the confusion. Code assistants are the biggest: if Copilot or Cursor wrote part of your gameplay script, does that count? In practice, itch.io moderators have focused on player-facing content — art, audio, narrative text — rather than IDE autocomplete. But if your game's core mechanic is an LLM-driven NPC, that is player-facing and should be disclosed. The second gray zone is AI-assisted versus AI-generated. Using Photoshop's Firefly tools to remove a background from a hand-painted sprite is different from prompting an entire character sheet. Disclose the latter, and be specific about the former if a reasonable buyer might assume otherwise. The third is asset packs: if you sell a pack on itch.io that includes AI-generated textures or 3D models, the disclosure needs to be on the product page, not buried in a readme.

Real Cases and Data Points

Steam's January 2024 policy update is the reference point the whole industry now navigates. Valve required developers to disclose AI use in the store submission process and added a live-generated content category with its own guardrails. itch.io did not copy that structure, but the two platforms now share a norm: disclosure at the point of listing. Developers shipping to both should treat the stricter disclosure as their baseline.

The asset side has its own documented friction. In 2024, itch.io saw public disputes over AI-generated asset packs, with artists and buyers pressing for clearer labeling. The platform's response was not a ban but a reinforcement of its existing content rules and reporting mechanisms. That pattern has held: itch.io prefers community moderation plus creator honesty over pre-publication review.

Tooling has also matured in ways that make disclosure easier. Text-to-3D services like Tripo3D and Kaedim now produce game-ready topology and PBR materials, which means the output is closer to a conventional asset pipeline — and easier to describe accurately. Audio is similar: Soundraw and AIVA generate royalty-free tracks with clear licensing terms, so a disclosure line can name the tool and the license. The more specific your toolchain, the less room for a moderator or buyer to assume the worst.

One concrete signal of scale: itch.io hosts tens of thousands of game jam entries each year, and jams increasingly publish their own AI rules on top of the platform's. Ludum Dare and several large annual jams have added explicit AI disclosure requirements to their submission forms. That means a developer's compliance surface is now the platform plus each jam's rules — and the jam rules are often stricter.

Practical Advice for Developers

• Write a disclosure block before you upload. A three-line section on the project page — tools used, assets affected, and whether output was edited by a human — covers most cases. Keep it factual, not apologetic.
• Separate AI-assisted from AI-generated in your own notes. Track which files came from prompts versus which were human-made and lightly edited. You'll need this for jam forms and for buyer questions.
• Disclose player-facing LLM features explicitly. If your NPC dialogue is generated at runtime, say so on the page and in the game's credits. Runtime generation is the category most likely to draw scrutiny.
• Check model licenses against your monetization. Selling a game that uses an AI-generated soundtrack requires the music tool's commercial terms to permit it. Play.ht and similar voice platforms publish their commercial-use rules; read them before you price your game.
• Keep asset-pack pages unambiguous. If a pack is mixed human and AI content, label each category. Buyers on itch.io are vocal about this, and a clear label protects your ratings.
• Don't rely on silence. The most common enforcement trigger is a buyer discovering AI use that wasn't disclosed. A short, honest disclosure costs you almost nothing and removes that trigger.

Outlook

itch.io is unlikely to build a Steam-style pre-review pipeline for AI content. Its scale and culture favor lightweight rules plus community reporting, and that model has held through several years of AI tooling growth. The more likely shift is pressure from jams and from buyers: expect more jam organizers to require disclosure forms, and expect AI-generated asset packs to face continued labeling scrutiny.

For developers, the strategic read is straightforward. Disclosure is becoming a normal part of the store page, like content warnings or system requirements. The studios that treat it as routine documentation — naming tools, scoping what was affected, keeping licenses in order — will ship with less friction than those who treat it as a legal risk to be minimized. The policy isn't going away, and it isn't designed to punish AI use. It's designed to make the marketplace legible, which is ultimately good for anyone trying to sell there.