Guides
What to check when you view a 3D model: a seven-point inspection
The seven checks to run when you view a 3D model, from scale and pivot to topology, normals, UVs and materials, and what each problem means.
3 min read
Quick answer
What should you check when inspecting a 3D model?
Check seven things before trusting a model: scale against a known size, where its pivot sits, the wireframe and polygon count, face normals, UV layout, material channels, and the file format. Any free viewer shows most of these. Finding a problem now costs minutes, while finding it in an engine or print costs hours.
Why a pretty render is not enough
A model can look perfect in a lit, shaded preview and still be unusable. It may be a hundred times too big, made of half a million triangles where a few thousand would do, or have textures with shadows painted in. A viewer can show you all of this if you know what to switch on. Do these seven checks in Blender, Babylon.js Sandbox or any viewer with a wireframe mode.
1. Scale
Put the model next to something of known size, or read its dimensions. glTF files are defined in metres by the Khronos specification. FBX and OBJ are not, so a chair that is 90 units tall might be 90 centimetres or 90 metres. Fix scale before anything else. Physics, lighting and level of detail all depend on it.
2. Pivot and orientation
Where is the origin? A door should rotate around its hinge, a crate should sit on the floor at its base, and a character should stand at the origin facing forward. Check that the model's "up" is your tool's up. glTF uses +Y up, while Blender and Unreal use +Z.
3. Wireframe and polygon count
Turn on the wireframe. You are looking at two things:
- Density. Is the detail where the shape needs it, or is the whole surface covered in tiny triangles? Dense, uniform triangles usually mean a scan or an AI generation that has not been retopologised.
- Flow. For anything that will bend, such as a face or an elbow, you want loops of quads that follow the form.
Compare the count with your budget. A background prop in a mobile game might need a few hundred triangles, while a hero prop on PC can afford many thousands.
4. Normals
Normals say which way each face points. If faces disappear as you orbit, or render black, some normals are flipped. Most viewers can show back faces in a different colour. In Blender, Mesh › Normals › Recalculate Outside fixes most cases.
5. UVs
Open the UV view. Islands should not overlap unless they are meant to share texture, and should use the square sensibly. Stretched checker patterns on the model mean the UVs are distorted. Without good UVs, nothing you paint will look right. See UV mapping.
6. Materials and textures
Look at each texture map separately, not just the final render:
- Does the base colour have shadows or highlights painted in? That lighting will look wrong in every scene except the one it was baked for.
- Are there roughness, metallic and normal maps, or just colour? A full PBR material reacts properly to your lighting.
- Are textures a sensible size for where the model will be seen?
7. Format and extras
Is it in the format your destination wants? Does it carry anything you did not expect, such as hidden objects, cameras, lights or animation? Delete what you do not need before export.
Most problems point to the same fix
If a model fails checks 3, 5 and 6 together, it is usually a raw scan or a raw AI output. That is the problem Vi3W is built around: models are generated, then automatically retopologised from high-poly to low-poly, with PBR textures, and exported as GLB, FBX or OBJ. Run this checklist on the result yourself. That is what it is for.
Last reviewed