Are my files uploaded to a server?

No. This conversion runs inside your browser using your own device’s processing power, and the file is not uploaded. Once a tool has been used once (video, text recognition and background removal download their engine from this site the first time), it keeps working when your connection drops.

Is anything lost converting GLB to glTF?

No. They are the same format with different packaging, so geometry, materials, textures and animation all survive exactly.

Why is the glTF so much larger?

Because the binary data is embedded as text, and text needs four characters for every three bytes. The model is the same; only its written form has changed.

Convert GLB to glTF

Runs on your device · Your file never leaves your device.

GLB and glTF are the same format wearing different clothes: GLB is one sealed binary file, glTF is readable JSON. Converting one to the other opens the model up so you can look at its structure, check what materials it declares, or edit something by hand.

Nothing is lost in the move. Geometry, materials, textures and animation all carry over — this is a repackaging, not a re-encoding. The binary data, texture images included, is written into the .gltf as text, which is why the file is about a third larger; Draco or meshopt compression in the GLB is kept as it was.

The conversion runs on your own machine, which for a 3D file is the whole point: a model is usually a client’s product, a scanned property or something not yet announced. Nothing is sent to a server, so there is nothing to delete afterwards and nothing to take anyone’s word for.

How to convert GLB to glTF

Drop the GLB file.
Check that glTF is selected.
Press Convert.
Download the .gltf file.

Supported formats and limits

Input: GLB, including Draco- or meshopt-compressed
Output: glTF (.gltf, readable JSON)
Keeps animation: Yes
Keeps textures: Yes, embedded in the file
Where it runs: In your browser; the model is never uploaded

Not for: Producing a .gltf with a separate .bin and loose texture files — the output is a single self-contained .gltf.

Which GLB files can be opened

GLB files compressed with Draco or meshopt open, using decoders served from this site, and so do files with quantized geometry, texture transforms, WebP, AVIF or KTX2 images, lights and instanced copies of a mesh. Because the GLB is unpacked rather than rebuilt, its compression and its images reach the .gltf exactly as they were.

What changes on the way through

Nothing in the model. The JSON part of the GLB is written out as it was, and the binary part, which holds the geometry, the animation keyframes and the texture images, becomes one buffer inside the .gltf. Meshes are not split, JPEG images are not compressed again, every scene is kept, and extensions this site does not understand pass through untouched. The result is a single file, with no .bin and no loose images to keep together.

Finding your way around the JSON

The .gltf is indented with two spaces, so it reads well in any text editor. Materials, nodes with their positions, rotations and scales, and the list of animations are plain JSON you can change by hand. The geometry, the animation keyframes and the images are not: they sit in one buffer, stored inside the file as base64 text, which takes about a third more space than the same bytes in a GLB. If you edit the JSON, leave the counts and offsets in accessors and bufferViews as they are, or the file will no longer match its buffer. To pack an edited file back into a GLB, use /gltf-to-glb.

Frequently asked questions

Are my files uploaded to a server?: No. This conversion runs inside your browser using your own device’s processing power, and the file is not uploaded. Once a tool has been used once (video, text recognition and background removal download their engine from this site the first time), it keeps working when your connection drops.
Is anything lost converting GLB to glTF?: No. They are the same format with different packaging, so geometry, materials, textures and animation all survive exactly.
Why is the glTF so much larger?: Because the binary data is embedded as text, and text needs four characters for every three bytes. The model is the same; only its written form has changed.