glTF Viewer

Open .gltf files with their .bin buffers and textures, check Blender exports and play animations. Free, no upload.

A glTF viewer for .gltf, .bin and texture files

This glTF viewer opens glTF 2.0 models in the browser, including the multi-file kind: a .gltf JSON file with one or more .bin buffers and a folder of texture images. Select all of the files together, or drag them onto the page at once, and the scene loads with its materials and animations. Nothing is uploaded.

It is useful for checking an export from Blender or another tool before you hand it to a developer, for looking at a model you downloaded, and for working out why a glTF looks different from what you expected.

How a multi-file glTF is laid out

glTF is an open standard from the Khronos Group, the body behind OpenGL and Vulkan. Version 2.0 came out in 2017 and was published as the ISO/IEC 12113 standard in 2022. It was designed for delivering 3D content efficiently, which is why it is often described as "the JPEG of 3D".

In its separate-files form, a glTF model is several files that refer to each other:

If your model is a single binary file instead, the GLB Viewer explains what is packed inside it.

.gltf: A JSON file describing the scene: nodes, meshes, materials, animations, skins, cameras. It contains no heavy data itself, only references.
.bin: Binary buffers with vertex positions, normals, UVs, indices, skin weights and animation keyframes. The .gltf points to it through a "uri" in its "buffers" list.
Textures: Usually PNG or JPEG files, referenced from the "images" list. Base color, metallic-roughness, normal, occlusion and emissive maps.

Opening a glTF that comes in several files

If you open only the .gltf, the viewer cannot find the buffers and textures it refers to. Select the .gltf, every .bin and every image together. The viewer matches the references by file name, so it does not matter that the images were in a "textures" subfolder; they just have to be in the selection.

If a .bin file is missing, the viewer says which file names it was looking for. A missing texture does not stop the model from loading; that surface is simply drawn without it. To see everything a model expects, open the .gltf in a text editor and search for "uri". Each value is a file the model needs.

Some .gltf files contain everything inline as base64 data URIs instead of separate files. Those open on their own, but they are about a third larger than the same data stored in binary.

Debugging glTF exports from Blender and other tools

Blender's built-in exporter offers "glTF Separate" (.gltf + .bin + textures) and "glTF Binary" (.glb). The separate form is handy while debugging because you can read the JSON. Open the export here to check a few things quickly:

Materials look flat or white: the exporter only translates Principled BSDF materials and a few simple node setups. Procedural textures and complex node trees are not exported; bake them to image textures first.

Model is sideways or the wrong size: Blender is Z-up and glTF is Y-up. The exporter's "+Y Up" option handles this and should normally stay on. glTF uses meters, so check the bounding-box size in the info panel.

Animation missing or wrong: check the clip list. Each Blender action (or NLA track, depending on export settings) becomes a separate clip. An empty list means no animation was exported.

Too many triangles or vertices: the info panel counts them, so you can see whether modifiers such as Subdivision Surface were applied at export.

This viewer shows whether a file loads and looks right. For checking strict compliance with the specification, use the official Khronos glTF Validator.

Extensions and what this viewer supports

glTF adds features through named extensions listed in the file's "extensionsUsed" and "extensionsRequired" arrays. If a file lists an extension under "extensionsRequired" that a viewer does not support, it cannot be displayed correctly.

To pack a .gltf and all its files into one file, use glTF to GLB.

KHR_draco_mesh_compression: Supported. Geometry compressed with Draco, decoded in the browser.
EXT_meshopt_compression: Supported. Geometry and animation compressed with meshoptimizer.
KHR_texture_basisu: Not supported. A file that requires it won't open; one that only uses it opens without those textures.
glTF 1.0: Not supported. Files from before 2017 need to be upgraded to glTF 2.0.

Frequently asked questions

Why does my glTF file show no textures or fail to load?

The .gltf refers to separate .bin and image files. Select all of them together when opening the model. Search the .gltf for "uri" to see exactly which files it expects.

What is the difference between glTF and GLB?

They hold the same data. A .gltf is a JSON text file that references separate binary and image files; a .glb packs the JSON, the buffers and the images into one binary file. glTF is easier to inspect and edit, GLB is easier to share.

Can this glTF viewer open Draco-compressed files?

Yes. Draco and Meshopt compressed glTF files are supported and decoded in your browser; the model stays on your device.

Is my model uploaded when I use the glTF viewer?

No. The files are read and rendered locally by your browser.

Does the viewer validate glTF files?

It shows whether the model loads and how it looks, along with counts of meshes, materials, textures and animations. It does not check every rule of the specification. For that, run the file through the Khronos glTF Validator.

Can I open glTF 1.0 files?

No. Only glTF 2.0 is supported. glTF 1.0 used a different material system and is rarely produced today.

Why does my glTF look different in Blender and here?

Usually the material. glTF uses a metallic-roughness PBR model, and Blender only exports what maps onto it. Lighting also differs between programs. Check that your Blender material is a Principled BSDF with image textures.