Guides
Why does my GLB look fine in one viewer but broken in another?
Why a GLB renders differently across viewers, from compression and extensions to colour space and lighting, and how to troubleshoot exports.
5 min read

Quick answer
Why does my GLB look fine in one viewer but broken in another?
Because viewers support different parts of glTF. One may decode Draco or KTX2 textures, read material extensions like transmission or clearcoat, and light the scene with an HDR environment, while another doesn't. Run the file through the Khronos glTF Validator, compare it in the Khronos Sample Viewer, then re-export without the extensions your target can't read.
Why a GLB can look fine in one viewer and broken in another
A GLB looks fine in one viewer and broken in another because glTF is a core format plus optional extensions, and no two viewers support exactly the same set. The glTF 2.0 specification lets a file list extensions it needs in extensionsRequired, and says a client that doesn't support one should not load the asset. Blender's glTF manual says it bluntly: "Not all glTF readers support all extensions."
On top of that, viewers make their own choices about lighting, transparency and back faces. Same file, different renderer, different picture. The fix is to find out which difference you're looking at.
Step 1: validate the file
Open the Khronos glTF Validator and drop the GLB in. Validation runs locally in your browser, so the file isn't uploaded. The report lists every issue it finds, plus stats about the asset.
- Errors (broken buffers, bad accessors, invalid images) mean the export itself is faulty. Strict viewers refuse it, lenient ones guess. Fix the export before anything else.
- The extensions the file declares tell you what a viewer must support. They sit in the file's
extensionsUsedandextensionsRequiredlists (the spec requires every extension used to be listed). Note anything likeKHR_draco_mesh_compression,EXT_meshopt_compression,KHR_texture_basisu,EXT_texture_webporKHR_materials_*.
Step 2: compare against a reference viewer
Open the file in the Khronos glTF Sample Viewer, the official Khronos viewer. Its README lists a long set of supported extensions, including Draco, meshopt and most material extensions.
- Looks right there, wrong elsewhere: the other viewer lacks support for something. Go to Step 3.
- Looks wrong there too: the export is wrong. Go to Step 4.
A second opinion helps: Babylon.js Sandbox and the three.js editor both open GLB files in the browser. See free 3D file viewers for more.
Step 3: the usual differences between viewers

Work down this list. Each has a recognisable symptom.
- Nothing loads, or an empty scene. Usually compression. Draco and meshopt compress the mesh; a viewer without the decoder can't read it at all.
- Black, pink or missing textures. Often a texture format the viewer can't decode: KTX2 (Basis Universal) or WebP. Blender's exporter warns that if WebP is chosen, "all textures will be saved as WebP, without any png/jpg fallback".
- Glass looks solid, coatings vanish. Material extensions such as transmission, volume, clearcoat, sheen or iridescence are ignored by viewers that don't support them. The Blender manual notes support for the transmission extension "is not yet widespread".
- Too dark, too bright, or washed out. Two causes. First, lighting: one viewer uses an HDR environment, another uses a single light, and metallic surfaces look black without reflections. Second, colour space: the spec requires the base colour texture to be sRGB, while data maps (normal, roughness, metallic) are linear. A map tagged wrong at export looks wrong everywhere strict.
- Holes where faces should be. Back-face culling. With
doubleSidedfalse, the spec says "only front-facing triangles are rendered". Flipped normals or single-sided leaves disappear from one side. - Transparent parts flicker or turn solid.
alphaModeBLEND "varies" between renderers, per the spec. MASK is more consistent for leaves and cut-outs. - Colours look right but there's no shading. The material is unlit (
KHR_materials_unlit), which some viewers honour and others don't.
Step 4: fix the export
If the file came from an AI generator or another tool, import it into Blender with File ‣ Import ‣ glTF 2.0 and re-export with conservative settings. In File ‣ Export ‣ glTF 2.0, per the Blender glTF manual:
- Format: glTF Binary (.glb).
- Images: PNG (lossless) or JPEG (smaller). Not WebP, unless you know the target reads it.
- Compression: leave Draco and meshopt off for a test. Add them back only if the target supports them.
- Materials: use Principled BSDF. Blender's exporter builds glTF materials from Principled BSDF inputs; other node setups may export as plain colour.
- Data maps: set normal, roughness and metallic Image Texture nodes to Non-Color before export.
- Back faces: recalculate normals (Mesh ‣ Normals ‣ Recalculate Outside) instead of relying on double-sided materials.
Validate again, then test in the viewer that failed.
Which viewer should you trust?
- Khronos glTF Sample Viewer. The reference implementation. Use it to settle "is the file wrong or the viewer?"
- Babylon.js Sandbox and three.js editor. Good everyday checks that resemble how many websites render GLB.
- Blender. Best for fixing, not judging. It imports most extensions, but its lighting is not a web viewer's lighting.
- Your actual target. A game engine, a website's viewer, a slicer or an AR app. This is the only one that matters in the end.
When not to chase a perfect match
You can't make a GLB look identical everywhere. Lighting, tone mapping and environment maps are viewer settings, not file settings. Aim for a file that validates cleanly and looks right in the reference viewer and in your real target. If the target only supports basic metal-rough PBR, design for that instead of adding glass or clearcoat that will be ignored. For heavy files, reduce GLB file size shows safer ways to slim down than compression the target can't read.
Where Vi3W fits
Vi3W generates models from text, sketches or images with AI PBR textures and exports GLB, FBX or OBJ. If a Vi3W GLB renders differently between two viewers, the steps above apply: validate, compare in the Khronos viewer, and test in your target. Vi3W doesn't control the lighting of the viewer you open it in. Try Vi3W.
Frequently asked questions
my generated glb looks fine in one viewer but broken in another—missing textures or wrong material settings. how do i troubleshoot exports?
Validate first, then compare. Drop the GLB into the Khronos glTF Validator to catch broken data and check which extensions it declares. Open it in the Khronos glTF Sample Viewer as a reference. If it looks right there, the other viewer lacks support for something: usually mesh or texture compression, WebP or KTX2 images, or a material extension. Re-export with plain PNG or JPEG textures and no compression, and test again.
Last reviewed

