Convert a binary GLB into a readable glTF file locally - with an embedded buffer, a single file. 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 comes in two forms: GLB is the compact binary form in one file, glTF the text-based JSON form. If you want to inspect a model's structure, adjust it or process it with tools that expect JSON, you need the glTF form. This tool splits the GLB apart and writes the contained JSON as a nicely readable glTF file.
So the result stays a single, self-contained file, the binary buffer from the GLB is embedded directly into the glTF file (as a base64 data URL). That way there is no loose companion file and the glTF opens anywhere without a missing external .bin file. The geometry and all structure entries are preserved exactly.
Everything runs entirely locally in the browser - your model never leaves your device. This is a lossless repackaging: the same content, just as JSON instead of binary. An invalid GLB file is rejected with a clear message instead of producing a broken output.
| Input formats | GLB |
|---|---|
| Output format | GLTF |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Converts a binary GLB losslessly into a text-based glTF file; the binary buffer is embedded as a base64 data URL so a single self-contained file results (no external .bin). Structure and geometry are preserved exactly. An invalid GLB file is rejected with a clear error.
No. The binary buffer is embedded as a base64 data URL in the glTF file, so a single self-contained file results.
Yes. It is a pure repackaging from binary to JSON; structure and geometry stay unchanged.
glTF as JSON is readable and can be inspected or edited with many tools; GLB is binary and compact.
No, the conversion happens entirely locally in the browser; your model never leaves your device.