Skip to main content
All posts
Guide

4 pitfalls when importing an AI-generated GLB into Blender

The specific mistakes people make bringing a Sculptly output into Blender, and how the glTF importer already handles most of them.

We wrote a full import guide for Blender, but a few mistakes come up often enough that they're worth calling out on their own.

1. Manually rotating for the Y-up/Z-up mismatch

glTF (and GLB) files use a Y-up coordinate system; Blender's world is Z-up. The instinct, if you've hand-rotated models between engines before, is to rotate the imported object 90° yourself. Don't — Blender's built-in glTF importer (File → Import → glTF 2.0 (.glb/.gltf)) already performs that conversion during import. Rotating again just puts the model on its side.

2. Assuming the mesh is watertight because it's AI-generated

There's a common assumption that an AI-generated model is somehow "pre-verified" the way a CAD export is. It isn't. A single-image reconstruction can come back non-manifold — see why single-image reconstruction makes holes for the geometric reason why. Before you rely on the mesh being solid (for boolean operations, for 3D printing, for physics simulation), run Mesh → Clean Up and check the results, or run it through our free mesh-repair tool before it ever reaches Blender.

3. Not checking scale before you start modeling around it

Generated model scale is normalized during generation — it isn't guaranteed to match the units in your existing scene. Import, then immediately check the N-panel → Item tab for the object's real dimensions before you build anything relative to it. Skipping this is the single most common reason people end up rescaling everything at the end of a session instead of the start.

4. Expecting a real-time-ready triangle budget out of the box

Generated meshes are optimized for visual fidelity from the reconstruction, not for a specific triangle budget. If the model is headed into a game engine or a real-time scene, expect to run a decimation pass yourself — the mesh coming in higher-poly than you need isn't a defect, it's just not pre-tuned for your target platform.

The material side is the one thing that just works

Unlike the geometry gotchas above, materials are close to zero-effort: Blender's glTF importer maps standard PBR textures directly into the Principled BSDF node setup, so you don't need to manually rebuild texture links after import. You may still want to tune roughness/metallic values for your specific lighting setup, but the base material comes in correctly wired.