PlayForgePlayForge
Back to News
Industry News

itch.io AI Game Policies: A 2026 Compliance and Disclosure Guide for Indie Devs

A practical breakdown of itch.io's AI content rules as of 2026: what triggers disclosure, how the platform's trust-based review works, and how to prepare store pages for AI art, voice, and code before you upload.

10/10/2026Source: PlayForge Editorial75 views
itch.io AI Game Policies: A 2026 Compliance and Disclosure Guide for Indie Devs

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

itch.io has become the de facto home for experimental and small-team games, and that role now collides with the AI content boom. The platform's official stance, published on its creator FAQ and quality guidelines, is deliberately permissive: AI-assisted games are allowed, provided the creator discloses AI use on the project page and does not pass off generated assets as wholly human-made. That sounds simple. In practice, it creates a gray zone that indie developers keep misreading — sometimes to their cost.

The stakes rose through 2025. Steam's disclosure system, introduced in January 2024, forced a public reckoning over how many shipped games used generative tools, and the resulting wave of coverage made platforms sensitive to user backlash. itch.io did not mirror Steam's formal form-based disclosure, but it did tighten its quality guidelines language and began relying more heavily on its report button and human moderators. For a solo developer, the practical consequence is this: itch.io is not scanning your build for AI assets, but your audience and competitors are watching your page. Getting disclosure right is now a marketing and community-management problem as much as a compliance one.

What itch.io actually requires

Disclosure is a page-level obligation, not a technical gate

itch.io does not ask you to upload model weights, prompt logs, or asset provenance. There is no checkbox that blocks publication. The requirement in the quality guidelines is that projects using AI-generated content must say so. The most reliable place is the project description itself — a short, plain-language section near the top. The platform's moderation is reactive: reports from users trigger review, and repeated misrepresentation can get a page delisted.

This is different from Steam, where Valve requires developers to fill out a disclosure section covering pre-generated and live-generated content, and shows it on the store page. Steam's system is structured and auditable; itch.io's is conversational. That means your risk is less about automated enforcement and more about a Discord thread or a Reddit post calling out a mismatch between your trailer and your credits.

The distinction that trips people up: assistance vs. generation

In practice, moderators and audiences draw a line between AI used as a tool inside a human workflow and AI used as the primary author of shipped assets. Retouching a hand-painted sprite with generative fill, or using an AI upscaler on textures you drew, is generally treated as tool use. Shipping a visual novel where every background and character is raw text-to-image output is treated as AI-generated content and needs clear labeling. Voice is the most sensitive category — AI voice cloning of a real person without consent is the fastest route to a takedown and reputational damage, regardless of what any platform policy says.

When you generate art, the cleanest production habit is to keep the pipeline traceable. Tools like Adobe Photoshop (AI) keep generative edits inside a layered, versioned file, and Krita lets you run local generation through plugins so the source assets stay on your machine. That traceability is what lets you describe your process honestly on the page instead of guessing.

Real cases and data points

Steam's January 2024 disclosure mandate set the benchmark. Valve's requirement that developers disclose AI use, combined with a live-generation guardrail added in January 2024 that blocks content that is illegal or infringes copyright, produced the first large-scale public dataset of AI usage in commercial games. By mid-2024, reporting on Steam's own disclosure data suggested a meaningful share of new releases used generative tools, with the figure climbing through 2025. itch.io developers who also ship on Steam often discover their disclosure habits need to satisfy both platforms.

itch.io's quality guidelines remain the primary enforcement text. The platform has repeatedly emphasized that it is curated by humans and that low-effort, mass-uploaded asset-flip projects are the target — not AI use per se. That framing matters: a well-made game with disclosed AI art is inside the rules; a spammy page with ten near-identical AI-generated games is not.

The 2025 backlash cycle shaped audience expectations. High-profile controversies over AI-generated store art and cloned voices pushed many indie communities to demand explicit labeling. Developers who disclosed early reported less friction than those who were discovered later — a pattern consistent with how the Steam disclosure rollout played out, where hidden AI use generated more anger than disclosed use.

Tool-level provenance is becoming a selling point. Engines and asset tools increasingly advertise auditability. Tripo3D and Kaedim generate 3D assets with game-ready topology, and both are commonly used alongside manual cleanup in Blender — a workflow you can describe accurately as "AI-assisted, human-finished." That phrasing satisfies most audiences and matches itch.io's tool-use framing.

Practical advice for shipping on itch.io

  • Write a dedicated AI disclosure block. Two to four sentences near the top of your project description: what tools you used, for which assets, and what humans did. Do not bury it in a credits file.
  • Separate generated from assisted in your own records. Keep a simple spreadsheet mapping asset to tool to human edit. You will need it for Steam, press, and any moderation question.
  • Never ship cloned voices without written consent. Use licensed voice actors or clearly synthetic voices from tools like Play.ht or Murf, and label them.
  • Match your trailer to your disclosure. The most common report trigger is a trailer that implies hand-made art while the page quietly admits AI generation.
  • Avoid asset-flip patterns. Multiple near-identical AI-generated projects from one account read as spam and invite review.
  • Check engine and marketplace terms too. Unity, Unreal, and asset stores have their own AI clauses; itch.io compliance does not cover them.
  • Date your disclosure. Adding "AI disclosure, updated [month year]" signals good faith and helps if policies shift.

Outlook

itch.io is unlikely to build a Steam-style formal disclosure form in 2026. Its identity depends on being low-friction for small creators, and a rigid compliance system would work against that. The more probable path is continued reliance on human moderation plus incremental guideline language, with pressure coming from audience expectations rather than platform automation.

For developers, the strategic read is straightforward: treat disclosure as a trust asset, not a tax. The cost of a clear paragraph is near zero; the cost of a discovered omission is a review-bombed page and a damaged reputation that follows you to the next release. As AI tooling becomes standard in indie pipelines, the differentiator will not be whether you used AI — it will be whether you were honest about it.

# itch.io# AI disclosure# indie games# platform policy

Related Articles

Comments

Log in to join the discussion