Reimport a GLB or glTF model in Unreal Engine 5 after tweaking it in Blender, and there's a real chance materials go missing, meshes end up under the map, or the reimport just hangs. Unlike FBX, there's no console variable to fall back to a legacy importer here — an Epic engineer confirmed on the forums that glTF is "100% supported by Interchange and there is no more legacy fallback for that file format." If reimport is breaking your scene, the fix isn't a setting you flip once. It's a workflow change.
Why glTF reimport has no safety net
FBX still has an escape hatch: setting `Interchange.FeatureFlags.Import.FBX False` in the console drops you back to the old importer, which is what most 5.4/5.5 workaround threads recommend. glTF was migrated to Interchange earlier and cleanly, so that plugin was removed outright — there's nothing to fall back to. That's fine for a first import. It's the reimport path that struggles, because Interchange has no reliable way to diff what changed inside the file. glTF and GLB carry no persistent node IDs the way FBX does with its scene graph, so Unreal can't tell "this mesh moved" from "this is a different mesh." It re-evaluates the whole file and sometimes gets the mapping wrong.
The three symptoms to recognize
If you've hit this, it usually looks like one of three things: a mesh keeps its old material slots but the material itself goes blank or gray, a mesh's transform resets or the object ends up scaled or positioned wrong, or the reimport dialog just spins and never completes. All three trace back to the same root cause — Interchange rebuilding the asset from scratch instead of patching it — so the fixes below apply to any of them.
| UE5 version | What happens on reimport | What actually works |
|---|---|---|
| 5.4 – 5.5 | Reimport frequently breaks materials/transforms or hangs | Delete the asset and do a fresh import, or import under a new filename |
| 5.6 | One reimport option added that respects existing settings | Enable it, but expect to lose manual tweaks made inside UE |
| 5.7 | Same reimport model as 5.6, no new safety net for glTF | Same workaround — treat glTF as write-once, edit in source |
The fix that actually works in 5.5-5.7
The workaround that consistently avoids corruption is to stop treating reimport as an update mechanism. Delete the existing asset in the Content Browser and do a clean import instead of using Reimport — under the hood, a full reimport already behaves the same way as delete-and-reimport, so you're not losing anything by making it explicit. If you're on 5.6 or later, there's a reimport option that preserves more of the original settings; turn it on, but verify materials and transforms afterward since it only reduces the failure rate, it doesn't eliminate it. The one thing to avoid is trusting the standard Reimport button on a glTF/GLB asset that already has manual changes in the level — that's the combination most likely to silently corrupt the scene.
A modular kit like a level corridor set is the worst case for this bug, since you'll touch the source file dozens of times while blocking out a level. BitSoul's Corridor Module is a good stand-in for testing your pipeline against this before you commit to it on a real level: import it, place a few instances, tweak materials in UE, then reimport after a Blender export and see which of the three symptoms shows up.
If you're pulling models from BitSoul into UE5 regularly, the Unreal Engine plugin sidesteps this entirely — it re-fetches and re-links assets through its own update path instead of routing through Interchange's glTF reimport, so you don't hit the delete-and-reimport dance at all.
Gotchas
Reimporting from a filename that matches exactly is what triggers the broken diff path — importing under a slightly different filename (`corridor_v2.glb` instead of overwriting `corridor.glb`) is functionally a clean import and dodges the bug, at the cost of manually swapping references. Skeletal meshes are worse than static meshes here: if your GLB carries an armature, reimport failures are more likely to scramble bone-driven transforms specifically, so treat rigged glTF assets as write-once even more strictly than static props. And if you're on a mixed Blender/Maxon pipeline, the same underlying Interchange diffing problem shows up for other formats too — it's not glTF-specific, glTF just has no legacy escape hatch to fall back on. A free BitSoul account's two monthly downloads cover evaluating a kit like this before you commit; commercial use is included with paid memberships — see pricing.
Before you build a level kit around GLB, check how your export step handles this from the Blender side in Blender 5.0 glTF export: what breaks in Unity, Godot, UE5, and if your models use armatures, fix scale issues before they compound with Fix Blender armature scale before it breaks bones on import. If you've also hit grayed-out parent materials on GLB imports, that's a related but separate Interchange quirk covered in Why Unreal Engine's parent material is grayed out for GLB files.
---
*This post is part of the Ultimate Guide to Free 3D Game Assets — BitSoul's complete reference for formats, texturing, rigging, optimization, and engine integration.*