Bundle a self-contained glTF file into a compact binary GLB locally - one file for web, AR and viewers. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
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.
| Input formats | GLTF |
|---|---|
| Output format | GLB |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
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. 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.
With self-contained glTF files (buffer as an embedded data URL). If the file references an external .bin, it cannot be processed locally.
Yes. It is a pure repackaging from JSON to binary; structure and geometry stay unchanged.
Because that would require fetching over the network - this contradicts the guarantee that your file never leaves the device.
No, the conversion happens entirely locally in the browser; your model never leaves your device.