Why did my glTF upload fail?

Almost always because the asset was uploaded without its companions. A .gltf references an external .bin buffer and separate image files; upload a ZIP containing all of them together.

Will converting to GLB change how the model looks?

No. Both are glTF 2.0. The materials, textures and animation are the same data — GLB just stores them inside one file instead of next to it.

Is a GLB smaller than the original glTF?

Close to the same, and not reliably smaller. Texture data dominates the size in both, and that data is re-encoded on the way into the binary chunk. Two things do cut the file down: an image longer than 4096 px on its largest edge is resized, and hidden objects are omitted from the output.

glTF to GLB Converter

Bundle a glTF asset — .gltf, .bin and images — into one self-contained GLB for the web and game engines. Runs in your browser.

Drag & drop your GLTF file here

or click to browse

Supported Formats

.glb.gltf.obj.fbx.stl.ply.3mf.off.zip

Format Information

Source Format

glTF.gltf

glTF (JSON)

glTF 2.0 in its JSON form. The .gltf file is a readable text document that describes the scene and references an external .bin buffer plus separate image files, so a finished asset is a folder rather than a single file.

What it carries: The same scene data as GLB — PBR materials, image textures, node hierarchy, skinning, morph targets, keyframe animation, cameras and lights — but expressed as external file references instead of an embedded payload.

Open a glTF file in the viewer

Target Format

GLB.glb

GLB (glTF Binary)

GLB is the binary packaging of glTF 2.0. Meshes, materials, image textures, animation and the node hierarchy are all written into one file, so an asset can be dropped into an engine or a web page without shipping a folder of sidecar files.

What it carries: Vertex positions, normals, UVs and vertex colours, full PBR materials (base colour, metallic/roughness, normal, occlusion, emissive), embedded image textures, node hierarchy, skinning, morph targets, keyframe animation, cameras and lights.

Open a GLB file in the viewer

About this conversion

This is the conversion most web projects need. The multi-file glTF asset is loaded — JSON, binary buffer and every image — and re-exported as one self-contained GLB that can be fetched with a single request.

Why convert glTF to GLB

Replace a folder of sidecar files with one request on the web. A GLB removes the .bin lookup and the separate texture fetches entirely.
Drop the asset into a game engine, AR viewer or React Three Fiber scene without setting up a resource loader.
Reduce the number of files you have to version, cache and keep in sync.

What happens during the conversion

Geometry

Nothing about the surface changes. Vertex positions, indices, normals, UVs, vertex colours, the node hierarchy and skinning are read from the glTF and written back out with the same structure.

Materials and textures

PBR materials survive intact — base colour, metallic/roughness, normal, occlusion and emissive maps all carry over. The images that were separate files become embedded inside the GLB, which is the whole point of the conversion.

Animation

Keyframe animation, skinning and morph targets are preserved. GLB and glTF share the animation model exactly, so nothing is approximated.

Common use cases

Shipping a web or game asset over HTTP without managing companion files.
Handing a single file to an engine, an AR viewer or a colleague.
Simplifying deployment: one file instead of a folder of assets.

Limitations of this conversion

The glTF must be uploaded complete. A bare .gltf whose .bin or images are missing will fail; upload a ZIP containing the .gltf, the .bin and the image files.
Images are re-encoded into the binary chunk, and any texture longer than 4096 px on its largest edge is resized.
Objects hidden in the source scene are not written, so a glTF that relies on visibility toggles produces a smaller GLB.

How to convert glTF to GLB

Three steps in the browser. Nothing is uploaded to a server, so an unwieldy file is limited only by your own device's memory.

STEP 1

Upload the whole glTF asset

Zip the .gltf, its .bin and all image files together and drop the ZIP in, or upload a .gltf whose buffers and textures are already embedded as data URIs.

STEP 2

Convert to GLB

The JSON, buffer and images are combined into a single binary glTF.

STEP 3

Replace your old asset with the .glb

Update the URL and the file extension. You no longer need to serve the .bin or the images separately.