glTF to GLB

glTF in JSON form is nicely readable, but for sharing, uploading into viewers or using in AR the compact single-file form GLB is more practical: structure and binary buffer sit in one single binary file. This tool reads your glTF file and writes a valid GLB from it.

For this to work entirely locally and without a network, the glTF file must be self-contained: its buffer is included as an embedded base64 data URL. That is exactly what our GLB to glTF tool also produces. The embedded buffer is read out and repackaged as the GLB binary part; structure and geometry are preserved exactly.

Everything runs entirely locally in the browser - your model never leaves your device. Honest and important: a glTF file that references an external .bin file or external images cannot be processed (it would require fetching, which would break the local guarantee) - it is rejected with a clear message. Use a self-contained glTF file with an embedded buffer.

GLB is also more compact: where a self-contained glTF file embeds its binary buffer as base64 text and thereby grows by about a third, GLB stores the same data as raw bytes. A text file with that inflation becomes a lean single-file binary - exactly the shape that viewers and AR tools load most readily.

Specifications

In 3 steps

1. Drop a self-contained glTF file.
2. The conversion runs automatically.
3. Download the GLB (one compact file).

Limitations: Bundles a self-contained glTF file (buffer as an embedded base64 data URL) losslessly into a binary GLB; structure and geometry are preserved exactly. Like GLB to glTF, this is a pure container repackaging rather than a geometry extraction: materials, textures and any NORMAL attribute from the glTF JSON structure stay unchanged in the GLB. A glTF file that references an external .bin file or external images cannot be processed (no fetching, local guarantee) and is rejected with a clear error.

FAQ

Related tools

GLB to glTF · OBJ to GLB · STL to GLB · GLB to OBJ · YAML to TOML · TOML to YAML