Epic Games is working to remove restrictions from its EULA that currently prohibit AI training on outputs of Unreal Engine and MetaHuman, according to CEO Tim Sweeney. The change would mark a significant shift in the company's AI policy—Unreal Engine outputs have been off-limits for training datasets under the current terms.
However, the move comes with built-in opt-out mechanisms. Each game or project using Unreal Engine and MetaHuman "is released under terms of the developers' choosing which can allow or restrict AI training," Sweeney confirmed. On the Fab marketplace, Epic has introduced a NoAI tag that prevents tagged content from being "used in datasets, development, or training of Generative AI Programs."
The timing creates obvious tensions. While Epic works to permit AI training on its engine outputs, both Epic and Microsoft have issued DMCA takedowns against AI-generated game clones over the past month—including a Fortnite browser port created using AI, and Microsoft's takedowns against AI-created ports of Minecraft, Call of Duty, and Halo. The gaming community has flagged this as contradictory: Epic is restricting AI use when it threatens their own IP while preparing to allow AI training on content others create with their tools.
Sweeney has cited the Anthropic court ruling as legal precedent, noting that a federal court "found they were liable for copyright infringement when torrenting pirated content," but "found that the training itself was fair use." That framing glosses over a key detail: the Anthropic ruling did not establish a universal safe harbor for AI training. Its findings were specific to Anthropic's particular circumstances. A separate class-action settlement with Anthropic required destruction of files obtained from pirate sources, though that settlement's terms apply only through August 26, 2025.
For studios rendering client work in Unreal Engine, this shift has immediate practical implications. Rendered outputs and MetaHuman characters could eventually enter AI training datasets—unless you actively opt out through EULA terms. The default permission, once the restriction lifts, will favor AI training on your work.
If you build client projects in UE, clarify your licensing stance now. Negotiate AI training rights explicitly in contracts where IP ownership is at issue. Some clients may want exclusions; others may not care. The specifics matter.
Similarly, pay attention as Epic solidifies its approach to third-party assets. The NoAI tag system on Fab suggests the company will apply similar protections to marketplace content, which includes Archmodels and other licensable assets. Check licensing terms on any third-party content you use in client work—especially as policies crystallize—to ensure you can honor client commitments around AI usage.
Epic has not yet specified a timeline for the EULA change, whether it applies retroactively to existing projects, or exactly how developers will enforce opt-out terms. Expect those details to clarify in coming announcements.
Lead image: Gadget Review
LEAVE A COMMENT
COMMENTS