GLB to glTF converter
This GLB to glTF converter extracts the glTF JSON and its BIN file from one self-contained GLB, in your browser. Download the ZIP and keep its files together.
Repackage locally
Select local files.
What is in your downloaded ZIP?
This tool extracts the glTF JSON and the BIN file from a GLB. The JSON is readable text. Mesh and image data stay in the BIN.
The download is called gltf-local-resources.zip. It holds up to three files:
| File | What it holds |
|---|---|
| model.gltf | The scene description from your GLB as readable JSON: nodes, meshes, materials, animations and where each piece of data sits in the BIN. Its buffer now points to model.bin. |
| model.bin | The binary data: geometry, animation values and the bytes of any embedded images. Only present when the GLB has a binary buffer. |
| README.txt | A short handoff note: keep the two files together, images stay in the BIN, nothing was regenerated, and review the metadata before sharing. |
File names read from the converter code on 9 November 2026.
Keep model.gltf and model.bin together in the same folder, with the same names. The JSON finds the BIN by its file name, so renaming or separating them breaks the link. Images do not become separate texture files. Your original GLB is not changed. The extracted files still need validating and inspecting before handoff.
Separate resources or embedded glTF?
A glTF can be handed over in two ways. This route gives the first: a JSON file plus a separate BIN. Other tools offer the second: one self-contained .gltf with the binary data written inside the JSON as encoded text. Neither is wrong. Ask the person or application receiving the file which one it expects.
| JSON plus separate BIN (this route) | One embedded .gltf | |
|---|---|---|
| Files | model.gltf and model.bin, kept together | One .gltf file |
| Binary data | Stored as bytes in the BIN | Stored as encoded text inside the JSON |
| Readable | The JSON is readable; the BIN is not | The JSON is readable; the encoded data is not |
| Typical risk | The BIN gets lost or renamed | Encoded text makes the file larger than the binary data |
A readable JSON file does not make mesh or image data readable: those stay binary. Neither packaging guarantees the model looks the same in every viewer. To go the other way, pack a glTF handoff back into GLB. Repacking does not recover anything that was missing from the files.
Prepare the input
Choose one self-contained GLB: a single .glb file with its buffer and images embedded. A BIN file on its own cannot be converted. It has no scene description, so start from a self-contained GLB.
These are the limits of this extraction route, read from the converter code. The 128-file and 8 MiB figures elsewhere in Labs belong to the glTF to GLB packing route, not this one.
| Limit | This route |
|---|---|
| Files | One .glb file |
| File size | Up to 64 MiB |
| JSON inside the GLB | Up to 4 MiB |
| Version | glTF 2.0 only |
| Resources | Embedded only. Buffers or images that point to an external file or a data URI are refused. |
| ZIP output | Up to 70 MiB |
Read from the converter code on 9 November 2026. These are this tool's bounds, not limits of the glTF format.
The tool does not check every possible fault in a GLB. A file it accepts can still fail validation or look wrong in the receiving application.
What is kept and what is not changed
Extraction repackages the GLB. It is not re-rendering, re-encoding, simplification or repair. Within the supported input, this is what happens to each part:
| Part of the GLB | What happens |
|---|---|
| Geometry and animation values | Copied into model.bin unchanged. Nothing is regenerated. |
| Materials | Copied into model.gltf as they were. |
| Embedded images | The bytes stay in their buffer views inside model.bin. No separate image files are written. |
| Extensions | Copied into model.gltf as declared. The tool does not check that the receiving application supports them. |
| Names and metadata | Kept in model.gltf, including the generator and any custom extras. Review them before sharing. |
| Container padding | Removed from the end of model.bin. |
Read from the converter code on 9 November 2026.
This does not mean every extension, texture, animation or importer will behave the same afterwards. Test the result where it will be used.
Why was the source rejected?
If the tool refuses a file, it shows one message and produces no download. Keep the original, find out which source application made it, and export a supported self-contained GLB from there. These are the main messages, read from the converter code:
| Message | What it means | What to try |
|---|---|---|
| Choose one self-contained GLB file. | The tool needs exactly one file. | Select a single .glb file. |
| Choose up to 128 local files totalling no more than 64 MiB. | This route shares the message with the packing route. For a GLB it means the file is over 64 MiB. | Export a smaller GLB, for example with smaller embedded images. |
| This is not a complete GLB 2.0 file. | The file is truncated, or it is not a binary GLB. | Export the GLB again from the source application. |
| The GLB JSON is too large for this tool. | The JSON inside the GLB is over 4 MiB. | Keep the original and extract it with a desktop glTF tool. |
| Use a self-contained GLB with embedded images. | A buffer or image points to an external file or a data URI. | Export with the images embedded in the GLB. |
| Unsupported buffer structure. | The GLB uses more than one buffer, or a layout this tool does not read. | Export a standard single-buffer GLB. |
Read from the converter code on 9 November 2026. Some files may fail for other reasons; an exported copy is not guaranteed to work.
Inspect before handing off
Extraction does not tell you whether the result is correct. Check it in this order:
- Keep the original GLB.
- Extract the ZIP and keep model.gltf and model.bin together.
- Run the files through a formal glTF validator, such as the glTF and GLB Validator, and read its errors and warnings.
- Open the result in the actual receiving viewer or application, not only a general viewer.
- Compare it with the original: one identifiable shape, part placement, material appearance, animation where relevant, and one known dimension.
- Review the JSON metadata before sharing it outside your team.
A validator finds structural problems. It does not certify visual quality, security, production readiness or support in a particular piece of software. To compare appearance first, inspect the original in the GLB viewer.
Recommended workflow
- Select a self-contained GLB. Choose one GLB with embedded buffers and images.
- Extract the original data. Run locally and download the output. Your source files stay unchanged.
- Validate and inspect. Use the formal glTF validator for structural checks, then inspect appearance and scale in the destination viewer.
Other conversions from GLB
Need a different output? These Labs routes start from a GLB: GLB to OBJ, GLB to STL and GLB to FBX. Starting from FBX instead, use FBX to GLB. Each route lists its own limits and losses. Choose a different 3D file route, or compare delivery formats first.
Guides for this tool
Frequently asked questions
Can I get JSON from a GLB?
Yes. This tool extracts the glTF JSON from a self-contained GLB into a ZIP, with the binary data as a separate BIN file. The JSON is readable text. Geometry and image bytes stay in the BIN, and nothing is regenerated or optimised.
What is included in the extracted ZIP?
The glTF JSON, its original BIN data when present and a short handoff note. Image data remains in the BIN buffer views.
Can I convert a BIN file on its own?
No. A BIN file holds only binary data, without the scene description that says what it contains. Start from a self-contained GLB.
Does this rebuild or simplify my model?
No. It repackages glTF scene data and binary resources. It does not decimate meshes or re-encode textures.
What are the limits?
One self-contained GLB up to 64 MiB, with JSON up to 4 MiB, glTF 2.0 only and every resource embedded. The ZIP can be up to 70 MiB. These are this tool's bounds, not format limits.
Are files uploaded?
No. Selected model resources are read locally in your browser; remote URLs are not fetched.
Related conversions
This converter is free to use. Check the downloaded file in its destination application. Use the 3D File Format Converter Guide to plan the handoff, or discuss a production brief with XO3D.