GLB has quietly become the default 3D interchange format. It's what AI generators output, what web viewers expect, and what most modern engines load without complaint. But Blender users still trip over the import process — wrong scale, missing textures, materials that don't look quite right.
This guide walks through importing a GLB into Blender 3.x or 4.x, fixing the issues you'll actually hit, and exporting it back out so the result survives the round-trip.
Why GLB, Not FBX or OBJ
If you've been in 3D for a while, FBX probably feels like the default. It isn't anymore. GLB (the binary version of glTF 2.0) packs the mesh, textures, materials, and animations into a single file. No missing texture folders, no path drama, no proprietary Autodesk SDK in the middle.
OBJ doesn't carry PBR materials or animations at all. FBX does, but the spec is closed and every exporter implements it slightly differently. glTF is an open Khronos standard, materials map directly to Blender's Principled BSDF, and the format was designed for modern PBR from the start. For AI-generated assets — like the ones from photo-to-3D pipelines — GLB is the only output worth caring about.
Step 1: Import via File > Import > glTF 2.0
In Blender 3.x and 4.x, the importer is built in — no add-on needed:
- File > Import > glTF 2.0 (.glb/.gltf)
- Navigate to your GLB file and check the import sidebar on the right
- Click Import glTF 2.0
The model appears at the world origin. If you don't see it, press Numpad . with the object selected to frame it — AI-generated GLBs sometimes come in very small or very large depending on the source.
Step 2: The Import Settings That Matter
Most defaults are fine. The ones worth knowing:
- Import Pack Images — leave on. Embeds textures in the .blend so they don't go missing
- Merge Vertices — turn on if the mesh has visible seams along UV islands
- Shading: Smooth / Flat — leave on Smooth unless you want faceted shading
- Bone Direction / Guess Original Bind Pose — only relevant for rigged or skinned meshes
Blender treats glTF units as meters. If a model imports at one-hundredth or one-hundred-times the expected size, the source file is wrong, not Blender.
Step 3: Verify Materials and Textures
Switch to Material Preview shading (third sphere icon, top-right of the viewport). If the model looks right here, the PBR pipeline is working. Open the Shader Editor with your mesh selected — you should see a Principled BSDF node wired to image textures for Base Color, Metallic/Roughness (packed in one image), Normal, and possibly Emission.
This is the mapping the glTF spec defines. If textures look pink, the image data didn't import — usually because the GLB was exported without Pack Images. Re-importing with Import Pack Images on usually fixes it. For a refresher on what each map does, see PBR textures explained.
Step 4: Fix Scale and Origin
Two common issues with AI-generated GLBs:
- Scale is off — press N, check Item > Dimensions. A real car should be ~4.5 m long. S to scale, Ctrl+A > Apply Scale to bake it
- Origin is at the world center, not the object — right-click the mesh, Set Origin > Origin to Geometry
Editing AI-Generated Models
AI 3D models usually need light cleanup, not a full retopology pass. Typical edits:
- Smooth shading + Auto Smooth — set Normals > Auto Smooth to 30-60° to clean up faceting without losing hard edges
- Decimate modifier — if the mesh is denser than you need (common with TRELLIS output at high settings), Decimate at ratio 0.5 halves the polycount
- Remesh modifier — for sculpting on top of the AI output, voxel remesh at 0.02 m gives clean uniform topology
For mobile or web targets, see optimizing 3D models for mobile games — the same poly-budget rules apply.
Re-exporting GLB from Blender
File > Export > glTF 2.0 (.glb/.gltf). Settings that matter:
- Format: glTF Binary (.glb) — single self-contained file
- Transform > +Y Up — required by glTF; Blender handles the conversion
- Geometry > Apply Modifiers — bakes Decimate, Subdivision, etc. into the export
- Compression: Draco — level 6 for ~80% smaller files. Skip for Unity assets without glTFast
- Images: Automatic / JPEG — JPEG for color, PNG for normal maps with fine detail
Common Problems and Fixes
- Missing textures (pink material) — re-export source GLB with images packed, or use File > External Data > Pack Resources before exporting
- Flipped normals (dark spots) — Edit Mode, A to select all, Mesh > Normals > Recalculate Outside (Shift+N)
- Wrong scale on re-import in Unity/Unreal — always Ctrl+A > Apply All Transforms before exporting
- Doubled geometry — Edit Mode > select all > Mesh > Clean Up > Merge by Distance at 0.0001 m
The Round-Trip Workflow
Generate with AI, import to Blender, clean up, export back. Five minutes from photo to polished asset. Try the HiGen3D generator, pull the GLB into Blender, and use this guide to take it the rest of the way. Share what you make on the community gallery, or check pricing if you need more generations than the free tier allows. For where AI generation fits into a real production workflow, see the indie AI 3D pipeline guide.