GLB and glTF Viewer for Windows

Inspect glTF assets with real-time PBR rendering

Open binary .glb packages and JSON-based .gltf files on Windows. Tridi Viewer displays the supported scene through a real-time physically based rendering pipeline and keeps model processing on the local device.

glTF is designed for efficient runtime delivery. A .gltf file can reference separate binary buffers and images, while a GLB container can combine JSON and binary payloads in one file. The asset may still use extensions or external resources, so a single-file GLB is not automatically self-contained in every case.

Common GLB and glTF viewing use cases

• Review a web, game, AR, ecommerce, or real-time asset before publishing it.
• Check node hierarchy, PBR materials, texture channels, and UV sets after export.
• Play supported skeletal, transform, and morph animation and inspect individual clips.
• Use wireframe and render passes to isolate geometry, normal, roughness, metallic, or texture problems.

Supported GLB and glTF data

• Triangle geometry and hierarchy.
• Core PBR materials with PNG, JPEG, or WebP textures.
• UV0 and UV1 texture coordinates.
• Transform animation, skinning, and position, normal, or tangent morph targets.
• Object, material, texture, animation, wireframe, and render-pass inspection.

Dependencies and diagnostic checks

For a .gltf file, keep external .bin buffers and images at the relative paths written into the asset. Network image URLs are not loaded by the importer. If geometry appears but textures do not, check the referenced files and URI spelling before changing material settings.

The Materials and Textures panels show imported resources, UV View compares UV0 and UV1, and render passes isolate common PBR inputs. Solid Wireframe shows the source polygon boundaries available after import. These views make Tridi Viewer useful for diagnosis, but they do not replace schema validation or testing in the final runtime.

Compression and extension limits

Draco- or Meshopt-compressed geometry and KTX2/Basis textures require a supported fallback. Unsupported required extensions can prevent correct import, while optional extensions may fall back to core data when the asset provides it. For avatar-specific VRM behavior, see the VRM viewer guide.

Format reference: the Khronos glTF 2.0 specification describes JSON glTF, the GLB container, resources, materials, animation, and extensions.

Related viewer guides