MetaHuman Creator Web Access Ends as Epic Opens a Final Retrieval Window

November 5, 2026, is the final access date for the browser-based MetaHuman Creator application. Epic Games announced the retirement timetable back on March 5, so the shutdown is a previously scheduled milestone rather than a new product announcement. The practical consequence is immediate: developers who still have characters stored in the legacy web gallery should determine which files and projects need preserving.

Epic says the transition follows the integration of MetaHuman Creator into Unreal Engine beginning with version 5.6. The retired web tool remained associated with an older authoring workflow, while the supported path for continuing to work on characters is the in-editor MetaHuman Creator. Existing MetaHumans that were already exported into Unreal projects remain usable; closing the browser does not automatically erase the copies already stored in those projects.

The company's notice allows a further 90 days after November 5 to retrieve MetaHumans from the web gallery. Epic identifies Quixel Bridge as the retrieval route for Unreal Engine assets, while mentioning the MetaHuman Importer specifically in the context of Unreal Editor for Fortnite. UEFN and the general Unreal Engine editor are different products, so their import options should not be treated as interchangeable. After the retrieval period, Epic says remaining gallery data will be deleted.

Migration is also more involved than downloading a file and assuming all versions can edit it. Epic's guidance directs developers who want to continue authoring older characters to upgrade them to the UE 5.5 web selection before migrating into the UE 5.6-or-newer editor workflow. The original notice makes clear that MetaHumans from UE 4.27 cannot be upgraded through that path. Production teams should therefore separate preservation of existing assets from the ability to modify them using newer tools.

One useful project audit would list all MetaHuman-dependent scenes, the engine version used for each character, whether a local copy exists, and whether the character still needs authoring changes. Back up the project before migration, export any missing gallery characters while retrieval remains available, and open one duplicated character in a supported modern engine project. Verify its appearance, clothing, animation, and materials before planning a wider migration. These are recommended checks, not results of a completed Kynris test.