itch.io AI Game Policies in 2026: A Practical Guide for Indie Devs

Context: Why itch.io's AI Stance Matters Now

itch.io has long been the default home for experimental, personal, and small-team games. In 2024 it became one of the first major storefronts to require creators to disclose AI-generated content, and by 2026 that requirement has matured into a real moderation practice. For indie developers, this is not a distant policy debate: it affects whether your page goes live, whether it gets delisted after a report, and whether your storefront reputation survives a wave of community scrutiny.

The stakes rose in 2025 when Steam began rejecting games that use AI-generated assets without proper rights documentation, and when several high-profile AI art controversies pushed platforms to tighten enforcement. itch.io's approach is lighter-touch than Steam's, but it is not a free-for-all. Understanding the difference between "allowed" and "safe" is now part of shipping a game.

Core Analysis: How itch.io Actually Handles AI Content

The Disclosure Rule in Practice

itch.io's policy requires creators to flag AI-generated content on the project page. The platform does not ban AI assets outright; it asks for transparency. In practice, moderation is reactive: pages are reviewed when users report them, when they trend, or when they are submitted to jams with their own rules. That means the risk is not a pre-upload gate but a post-launch surprise.

The disclosure itself is simple: a checkbox and a short description of what was AI-generated and which tools were used. The harder question is scope. Does a Midjourney-generated background count if it was heavily painted over? Does an AI-assisted code completion count? itch.io's guidance leans toward disclosure when AI materially contributed to the final asset, not when it was a minor assist. Creators should err on the side of disclosure; a brief, honest note costs little and prevents accusations of concealment.

Moderation, Reports, and the Jam Factor

Game jams are where itch.io's AI policy gets messy. Many jams explicitly ban AI-generated art or require disclosure, and jam organizers can remove submissions. In 2025, several large jams updated their rules to require AI disclosure, and a few banned generative art entirely. If you are entering a jam, read its rules before you generate a single asset.

Outside jams, moderation is driven by community reports. A page that discloses AI use is far less likely to be actioned than one that hides it and gets caught. The platform's terms also prohibit content that infringes rights, so AI outputs that closely mimic a known artist or IP are a separate and more serious risk.

Real Cases and Data Points

• Steam's 2025 policy shift: Valve began requiring developers to disclose AI-generated content and to demonstrate rights to use it, rejecting games with unclear provenance. This set a stricter benchmark that itch.io has not fully copied, but it raised creator awareness across both platforms.
• itch.io's 2024 disclosure requirement: The platform added an AI disclosure field to project pages, making it one of the earliest storefront-level transparency requirements. By 2026, that field is a standard part of upload flow.
• Jam rule changes in 2025: Major itch.io-hosted jams, including several horror and narrative-focused events, added explicit AI disclosure or bans, forcing developers to plan assets around jam rules.
• Tool-level provenance: Tools such as Adobe Photoshop (AI) now embed content credentials, and Tripo3D and Kaedim generate 3D assets with export metadata. Keeping that metadata intact helps you document provenance if a report lands.

Practical Advice for Indie Developers

• Disclose early and specifically. Add a short AI disclosure to your project page before launch: which assets, which tools, and whether outputs were edited. A sentence or two is enough.
• Read jam rules before generating. Some jams ban AI art outright; others require disclosure. Check before you build.
• Keep provenance records. Save prompts, tool versions, and export metadata. If a report occurs, documentation shortens the review.
• Avoid style mimicry. Do not prompt for "in the style of [living artist]" or known IP. This is the fastest route to a takedown.
• Use AI where it is defensible. Code assistance, placeholder art, and iteration are lower-risk than final marketing art. Tools like Blender with AI plugins let you keep human authorship visible.
• Audit third-party assets. If you use AI-generated music from Soundraw or voice from Play.ht, confirm the license permits commercial use and disclosure.

Outlook

itch.io is unlikely to ban AI content outright; its identity is built on openness. But expect continued tightening around disclosure and rights, especially as Steam's stricter model pressures platforms to align. The practical path for developers is transparency plus documentation. Treat AI as a tool with a paper trail, not a shortcut to hide. Creators who disclose clearly and keep provenance will face fewer interruptions and build more durable storefronts.

Disclosure is not a penalty; it is a form of quality control. In 2026, the indie developers who thrive on itch.io will be those who treat AI policy as part of their production pipeline, not an afterthought.