AI-Generated Game Assets: What Game Studios Actually Own — and What They Can't Protect

Game studios are generating concept art, textures, background music, NPC dialogue, and even code snippets with AI tools at a pace that would have been unimaginable two years ago. The speed and cost advantages are real. But underneath the productivity gains lies a legal question that too many studios are ignoring: when AI creates your game assets, what do you actually own?

The answer, as of 2026, is sobering. If an AI tool generates art, music, or code with minimal human creative direction, you likely cannot copyright that output. That means competitors can legally copy it. And if you are publishing on Steam, Unity, or Unreal Engine, you are now subject to AI-specific disclosure and usage rules that can affect your ability to ship — or even keep your engine license.

We have written about AI-generated game assets and the legal landscape before, and covered the 2025 Copyright Office Report's implications for studios. This article is the 2026 update — incorporating the Supreme Court's denial of cert in Thaler v. Perlmutter, Steam's actively enforced AI disclosure requirements, Unity's July 2026 terms update, and Epic's Fab marketplace AI tagging mandate — with practical guidance for studios that need to know what they can protect and what they cannot.

The Copyright Framework: Human Authorship Is Still the Gatekeeper

The Copyright Office Part 2 Report (January 2025)

On January 29, 2025, the U.S. Copyright Office released Part 2 of its Report on Copyright and Artificial Intelligence: Copyrightability. The report confirms what many in the industry suspected but few had internalized: purely AI-generated content is not copyrightable.

The Office's framework is straightforward. Copyright protection extends to AI-assisted works only where a human author has determined sufficient expressive elements. This can include situations where a human-authored work is perceptible in the AI output, or where a human makes creative arrangements or modifications of the output. What does not qualify? "The mere provision of prompts," the report states. Telling Midjourney to "generate a dark fantasy castle texture, 4K, seamless" — no matter how detailed the prompt — does not make you the author of the resulting image.

Crucially, the Office also confirmed that using AI as part of a creative process, or including AI-generated material within a larger human-generated work, does not automatically bar copyright for the whole work. The human-authored portions remain protectable. But the AI-generated portions? Those are in the public domain unless a human's creative modifications rise to the level of authorship.

Thaler v. Perlmutter: The Supreme Court Closes the Door

For studios hoping the courts might push back on the Copyright Office's position, the Supreme Court delivered a definitive answer on March 2, 2026. The Court denied certiorari in Thaler v. Perlmutter, letting stand the D.C. Circuit's ruling that works generated entirely by an AI system — without any human authorial contribution — cannot be copyrighted under the Copyright Act.

The practical takeaway: the "human authorship requirement" is now settled law. There is no pending litigation or legislative initiative that is likely to change it in the near term. If your studio is shipping assets that were generated by AI with only prompt-level human input, those assets are unprotectable. Competitors can copy them, and you have no federal copyright claim to stop them.

What Game Studios Can Actually Protect

So what can you copyright when AI is involved in your pipeline? The answer depends on where the human creativity lives.

Protectable: Human-Arranged and Human-Modified AI Output

If a human artist takes an AI-generated texture and substantially modifies it — painting over details, adjusting color grading, compositing it into a hand-built scene, or making creative selections about which AI outputs to use and how to arrange them — the resulting work may be copyrightable. The key is that the human's contributions must be more than mechanical. They must involve creative judgment about expressive elements.

Similarly, if your team writes original code and uses AI tools like GitHub Copilot or Cursor to assist with boilerplate or autocomplete, the human-authored portions of the code remain copyrightable. We have written a separate guide on registering AI-assisted code with the Copyright Office that walks through how to disclaim AI-generated portions in a registration application while protecting the human-authored elements.

Unprotectable: Prompt-Only AI Generation

If your workflow is: prompt → generate → ship, with no meaningful human modification, the output is almost certainly in the public domain. This is true for AI-generated character art, music tracks, sound effects, NPC dialogue, and code snippets. You can use them in your game, but you cannot prevent others from copying and using them too.

The Gray Zone: AI as a Tool vs. AI as an Author

The Copyright Office was careful to distinguish between AI as a tool that assists human creativity (like a camera or Photoshop) and AI as a standalone author. The distinction matters for game studios because it affects how you document your creative process. If a human concept artist uses an AI tool to generate reference images and then hand-paints a final character design based on those references, the final painting is protectable. The AI-generated references are not. If you can show a clear paper trail of human creative decisions — iterations, manual edits, artistic choices — you strengthen your position significantly.

Platform Policies: Steam, Unity, and Unreal Engine

Steam's AI Disclosure Requirements

Valve now requires all developers publishing on Steam to complete a content survey that includes a dedicated section on generative AI. Developers must disclose whether their game includes AI-generated content and describe how it is used — whether in pre-production, live-generated content during gameplay, or both. This disclosure is visible to consumers on the store page.

Valve has also clarified and updated these rules to distinguish between AI-generated content bundled into the game at release ("pre-generated") and content generated by AI in real time during gameplay ("live-generated"). Both categories require disclosure, but live-generated content carries additional scrutiny because Valve needs to understand what the AI might produce at runtime and whether it could generate content that violates Steam's content policies.

For studios, the risk is not just reputational. Failing to disclose AI-generated content when required can result in Valve removing your game from the store. And misrepresenting your AI usage — claiming content is human-authored when it was AI-generated — could expose your studio to contractual liability under your Steamworks agreement.

Unity's Terms of Service: AI Training and Automated Access Restrictions

Unity updated its Terms of Service on July 1, 2026, with significant new AI-related restrictions. Under Section 17.2 of the updated terms, training machine learning or AI models on Unity data — or any data derived from it — now requires prior written authorization from Unity. The terms also restrict automated access to the Unity platform through scrapers, bots, AI agents, and large language models unless they operate through frameworks specifically designated or operated by Unity.

For most studios using Unity as a game engine, this does not prevent you from using AI-generated art, music, or code in your Unity project. The restrictions target AI training on Unity's proprietary data and automated scraping of Unity's platform, not the use of AI-generated assets within a Unity-built game. But if your studio is also an AI developer — for example, if you are training a model on Unity's documentation, asset store data, or platform content — you need explicit permission from Unity before proceeding.

The terms also state that users remain responsible for any automated systems acting on their behalf, and that breaches may result in account suspension. This means studios should audit their AI tool integrations to ensure they are not inadvertently violating Unity's automated access restrictions.

Epic Games and the Fab Marketplace: NoAI and CreatedWithAI Tags

Epic Games has taken a different but equally significant approach. On its Fab marketplace (which replaced the Unreal Engine Marketplace and Sketchfab), Epic introduced two AI-related mechanisms: a "NoAI" meta tag and a "Created with AI" self-declaration.

The NoAI tag allows asset creators to indicate that their products should not be used for generative AI data collection. The "Created with AI" flag is mandatory: Fab publishers who use AI to generate content for distribution on the marketplace must enable this flag on those products. Epic states that all assets created and distributed on Fab belong to the creator and that Epic will not use creator artwork for generative AI programs — but the transparency requirement is binding on sellers.

For studios buying assets on Fab, the "Created with AI" tag is a critical signal. If you purchase an asset marked as AI-created and incorporate it into your game, you should assume that the underlying asset may not be copyrightable by the seller — which means any exclusive license the seller purports to grant may be worth less than you think. Always review the asset's license terms and consider whether the seller had sufficient human authorship to grant meaningful IP rights.

Publisher Agreements and IP Assignment Gaps

Beyond copyright and platform rules, game studios face a less obvious but equally dangerous problem: standard publisher and employment agreements were not drafted with AI-generated content in mind.

Most publishing agreements include IP assignment clauses where the developer warrants that they own all deliverables and assigns them to the publisher. But if a portion of those deliverables was generated by AI with minimal human input, the developer may not actually own that portion — and cannot validly assign what they do not own. This creates a gap in the IP chain that publishers are increasingly scrutinizing during due diligence.

Similarly, employment and contractor agreements typically include "work made for hire" provisions and IP assignment language. But work made for hire under U.S. copyright law requires a human author. If a contractor delivers AI-generated assets, the work-made-for-hire doctrine may not apply to those assets, regardless of what the contract says.

Studios should audit their existing contracts — publishing agreements, employment agreements, contractor agreements, and vendor agreements — and update them to address AI-generated content explicitly. At minimum, contracts should require disclosure of AI usage, include warranties that human-authored portions are original, and address how AI-generated portions will be treated in the IP assignment framework.

Actionable Next Steps

If your studio is using AI tools to generate game assets — and most are — here is what we recommend doing now:

1. Audit your asset pipeline. Identify which assets in your current or upcoming projects were generated by AI and classify them by level of human involvement. Assets with prompt-only generation are public domain. Assets with substantial human modification may be protectable. Document the creative process for the latter.
2. Disclose on Steam. Complete the AI content survey accurately for every Steam listing. Distinguish between pre-generated and live-generated AI content. Do not misrepresent AI-generated content as human-authored — the contractual and reputational risk is not worth it.
3. Review engine terms. If you are using Unity, ensure your AI integrations comply with the July 2026 terms update — particularly if any of your tools involve automated access or AI training on Unity data. If you are using Unreal Engine and purchasing assets on Fab, check for the "Created with AI" flag and evaluate what IP rights you are actually acquiring.
4. Update your contracts. Revise publisher, employment, and contractor agreements to address AI-generated content. Require AI usage disclosure, warrant human authorship for assigned IP, and carve out treatment for AI-generated portions that cannot be assigned.
5. Register what you can. For assets that include meaningful human authorship, file copyright registrations that disclaim AI-generated portions while protecting the human-authored elements. This preserves your ability to enforce copyright against infringers for the portions you actually own.
6. Build an AI asset policy. Create an internal policy that defines acceptable AI use, requires documentation of human creative contributions, and establishes a review process for AI-generated content before it ships. This protects you in due diligence and in any future dispute.

The AI tools are not going away, and they should not — they genuinely transform what small studios can produce. But using them without understanding the legal landscape is building your game on a foundation you do not own. The studios that thrive will be the ones that use AI aggressively while documenting their human creative contributions carefully, disclosing honestly, and structuring their contracts to account for what is protectable and what is not.