
What should game studios do after the MetaHuman Creator web app shutdown?
Epic set November 5, 2026 as the closure date for the legacy MetaHuman Creator web app. If your characters are still in its online gallery, check Quixel Bridge now. Epic announced a 90-day retrieval window after closure. If the character already lives in an Unreal project, first make a protected copy of that project and decide whether you need to keep using that asset or continue editing it in the current Creator.
This guide walks a game team through retrieval, an editable migration where the character qualifies, and a one-character test on target hardware. The checklist also helps producers identify what to send a character production partner when the original rig, wardrobe or performance budget needs extra work.
Table of Contents
What the shutdown means for your library

Epic’s shutdown announcement says the old Creator interface closed on November 5, 2026, with a further 90 days to recover characters. The announcement describes Quixel Bridge and, for UEFN, the MetaHuman Importer as retrieval paths that end after the window. Schedule retrieval as a production task now, especially if your library is spread across individual Epic accounts.
Make an inventory with a row for each character. Record its exact gallery name, the account associated with it, any Unreal projects that already contain it, and whether the team needs an editable character or only the assembled asset. Add project references for custom clothing, grooms, texture edits and animation. A gallery download may miss changes that live only in your project or source-control depot.
Keep a restorable copy in a team-controlled location. Include project dependencies, documentation of the engine and plugin versions, and a reference render or clip from the last accepted build. Check that a second teammate can open the copy and find the asset. If an older character still appears in Bridge but fails the prerequisites for editable migration, preserve any available export and consult Epic’s guidance for that version before committing to a rebuild. Plan around the files you can actually recover.
Where several teams share a roster, give one person responsibility for confirming which characters have been retrieved. Keep a separate status for an asset that appears in an account, an asset that has been copied, and an asset that a teammate has opened successfully. For duplicates, keep the gallery name as well as the in-project name so a later download is not mistaken for the version art direction already approved. If the original artist has left the project, resolve account access through the organization’s usual ownership process while the retrieval window is still open.
If the current build is stable and there is no immediate need to edit the face or body, document that decision and retain the working asset in its existing branch. The first priority is preserving the roster. Once the team has verified its copies, it can schedule appearance changes, engine upgrades and optimization as separate work with their own acceptance checks.
Choose import, migration or both
For ongoing authoring, use MetaHuman Creator in Unreal Engine. It has been integrated into Unreal since 5.6. The current migration guide describes an Unreal Engine 5.7 or newer test project with the MetaHuman Creator plugin enabled, and a source character compatible with 5.6. Follow the documentation version that matches the destination engine and confirm the source asset qualifies before you plan the work.
In the documented workflow, open Quixel Bridge from inside Unreal and sign in to the account that owns the gallery. Find the character, choose Cinematic (Complete) at download, then select Add. Epic documents three options. Import brings in assembled assets with the legacy workflow. Migrate creates an editable MetaHuman Character asset that you can assemble again. Import and Migrate produces both and is the documented route when you need to transfer grooms and clothing into the new workflow.
Epic says the groom is reapplied automatically when using the combined route, while clothing needs to be assigned manually. Inspect bindings and fit after assembly. If the project depends on a particular jacket, hairstyle or material setup, run that dependency through the test branch before promising it will carry across. Our MetaHuman vs bespoke character guide can help if the test reveals that a heavily customized character needs a different production approach.
Run this work in a test project or a branch with a clean change history. Record the original engine build, installed plugins and the exact migration option selected. For a hero used in an existing level, keep both asset paths during the test so you can switch references and compare builds. Before merging, agree which asset will become the source for future edits and who owns reassembly. That decision prevents a vendor and an internal artist from refining two different versions of the same face or outfit.
Validate one character on target hardware

Pick a character that exposes your actual risk. For a dialogue-heavy game, a hero with custom hair and facial animation is a better test than the least complex NPC. For a crowd-heavy game, choose a common outfit and profile a scene at the expected on-screen density. Write down the acceptance criteria before the first import so the team has a common point of comparison.
Start with a baseline from the existing build. Capture the same dialogue close-up, standard gameplay view and a transition between distances. Compare silhouette, expression, eyes and teeth, outfit fit and materials under your own lighting. Epic notes that a migrated character may look different because the underlying technology changed. A controlled comparison helps art direction decide which differences matter.
Replay representative body and facial animations through the real gameplay Blueprint or Sequencer setup. Look for retargeting offsets, lost curves, clothing clipping and groom problems at LOD changes. If the character will carry existing dialogue, the facial mocap handoff guide explains what to preserve from the performance pipeline. The character rigging guide covers the skeleton and deformation checks worth adding to acceptance.
Package a build and record frame time, memory and visible quality on the weakest supported target. Check animation, materials, hair and LODs with lighting, effects and other characters active. Compare with your own allocation for the character and entire scene. For a broader workflow, see our game asset optimization guide.
Write up the test with enough detail that another team can reproduce it. Record the build configuration, hardware, camera path, number of visible characters and any quality overrides. Keep the before and after clips alongside the profiling capture. If animation time rises while rendering stays flat, ask the technical artist to isolate the rig or update cadence. If the issue appears only during a distance transition, reproduce it at that transition before changing mesh or material budgets for the whole roster.
Example migration and handoff checklist

Imagine a studio moving one speaking hero and several background NPCs to a newer Unreal version. The hero already has a custom jacket, a groom and approved dialogue. The producer starts with the hero and assigns one artist to recreate the jacket setup in a migration branch, one animator to compare the dialogue shot, and one technical artist to profile the gameplay build. The NPC batch waits for those results.
If the hero looks right in a close-up but exceeds the gameplay budget, the team can retain its approved cinematic setup while testing a separate gameplay assembly. If the risk is facial compatibility, it can isolate one dialogue sequence, record which curves or bindings changed and estimate the repair from that sample. Use the result to set the scope of the roster migration instead of assuming each character needs the same work.
For an internal handoff or studio quote, send the source and target Unreal versions, asset locations, character count by role, existing rigs and animation, wearable and groom dependencies, reference shots, supported hardware and acceptance criteria. Include the required delivery format and who will merge and test the result. As a project reference for a different real-time character pipeline, Caliverse shows how Mimic’s character work sat within an interactive VR production.
Separate assets that only need retrieval from characters that need editable authoring, cleanup or rebuilding. This gives a partner a scope they can assess against your milestone. Our game art outsourcing brief provides more detail on how to specify deliverables and reviews.
For the NPCs in this example, test a group in a representative gameplay scene before approving the batch. Characters that share an outfit or body setup may be able to share parts of the validation. Heroes with unique wardrobe or extensive dialogue deserve individual review. Record exceptions in the handoff and agree what constitutes a change request. If the studio hires a partner, a small paid pilot can define the expected quality, who fixes integration defects and what evidence will accompany each approved character.
Frequently asked questions
When did Epic set the MetaHuman Creator web app shutdown?
Epic set November 5, 2026 as the closure date and announced a further 90 days for retrieval. Check the announcement for the current guidance before planning around the end of that window.
Does the shutdown affect MetaHuman Creator inside Unreal Engine?
The closure applies to the legacy browser application. The current MetaHuman Creator is integrated into Unreal Engine, beginning with version 5.6.
Can I still retrieve my characters after the shutdown?
Epic announced a temporary retrieval route via Quixel Bridge. Check the account that owns each character and verify that the files are available to you while the window is open.
Will my exported MetaHuman disappear from my project?
Already exported project files are separate from your online gallery. Preserve a working project copy with its dependencies and confirm that it opens before you make any changes.
Can every older character become editable again?
Epic’s current migration procedure has source and destination version requirements. If the source character does not qualify, check what files you can retrieve and scope a rebuild only after assessing those files.
Does a migration preserve the exact appearance?
Epic cautions that results may look different after migration. Compare fixed reference shots, face poses, outfit fit and lighting against your accepted build.
What happens to custom clothing and hair?
Epic documents the combined Import and Migrate route for carrying grooms and clothing across. The groom is reapplied automatically in that workflow. Clothing needs to be assigned manually and reviewed for fit.
What should I send to a character production studio?
Send your Unreal versions, character count and roles, available files, target hardware, a representative scene and the changes you need. Mention any upcoming milestone and who will approve or integrate the deliverables.
Plan your character migration
Check your gallery while retrieval is still available, then validate one character before moving the rest. A small test gives art, animation and engineering a shared basis for deciding what to keep, what to optimize and what to rebuild. Keep the original branch available until the replacement passes those checks and the team can reproduce the approved build.
Need help preparing characters for an active Unreal project? Explore Custom Character Creation or discuss your character project. Share your Unreal Engine version, target platform, character count and the assets you already have.
November 23, 2025
June 10, 2026