GLB to glTF converter: every byte kept

Drop a .glb and get a zip with a .gltf and its .bin. This is a change of container, not a conversion: the JSON stays as it was and the binary data is copied byte for byte, so meshes, skins, morph targets, animations, Draco compression, VRM data and extensions arrive unchanged. Free, no account, nothing to install.

Free · no account neededNeed a VRM avatar instead? →

How do I convert GLB to glTF?

Drop the .glb on this page and download a zip with the .gltf and its .bin. No 3D program opens the file on the way.

  1. 1Choose a .glb. A VRM is a GLB too: rename it to .glb. Files up to 50 MB.
  2. 2The server splits the file into its two parts: the JSON becomes model.gltf, the binary chunk becomes model.bin, and the .gltf is pointed at the .bin. It takes seconds.
  3. 3Download the zip and unpack it into one folder. The upload and the result are deleted 3 days later.
In:
.glb
Out:
a zip with model.gltf and model.bin
Keeps:
everything: the JSON as it is and every binary byte
Cost:
free, no account
  • Images stay inside the .bin, addressed by buffer view, as the GLB stored them. That is valid glTF, but a tool that wants image files beside the .gltf will not find them.

What survives the trip

A GLB is a glTF document and its binary buffer in one file. Here the two are written as two files: the JSON as model.gltf, indented for reading, and the buffer as model.bin. The only edit to the JSON is the line that tells the first buffer where its bytes are now.

Nothing is decoded or re-encoded, so the trip keeps the skeleton and the skin weights, the shape keys, the materials and the textures, vertex colours where the file has them and Draco compression, VRM data and every extension: meshes, skins, morph targets, animations, materials and extras are the same bytes in the result, and Draco or meshopt geometry stays compressed. Animation is carried too, because nothing reads it. glTF is what web viewers, three.js, Babylon.js, Godot and Blender read, and a text editor opens.

Images the GLB carried stay in the .bin, addressed by buffer view, because that is where the GLB kept them. glTF allows it, and three.js, Blender and Babylon.js read it; the result is two files, not a folder of textures.

Why unpack a GLB

To read or edit the JSON in a text editor: change a material value, rename a node, see what an exporter wrote. To compare two versions of a model in Git. Or because a pipeline asks for .gltf. The glTF to GLB page puts it back into one file afterwards.

What this conversion cannot do

Measured on real files, not assumed. Everything below is a property of the formats or of the pipeline, and knowing it beforehand is cheaper than discovering it in your 3D tool.

Images are not split out

Textures stay inside model.bin, the way the GLB stored them. A tool that reads only image files beside the .gltf will not find them; open the file in Blender and export it as glTF Separate to get them as files.

A GLB that points at other files is refused

A GLB whose buffers or images name outside files (rare, but allowed) needs those files, and they cannot come with one .glb upload. Such a file is refused with the name of what it points at.

Only well-formed GLB 2.0

The container is read strictly: the glTF signature, version 2, chunk lengths that match the file. A file cut short in the download, or glTF 1.0, is refused rather than guessed at.

Uploads stop at 50 MB

A larger file is refused before anything is uploaded.

Frequently asked questions

Is anything lost?

No. The JSON is kept field for field and the binary data byte for byte; the one change is the uri that points the first buffer at model.bin. Packed back on the glTF to GLB page, the result has the same JSON and the same accessor bytes as the GLB you started from. glTF to GLB converter →

Does it work with a VRM?

Yes. A VRM is a GLB with VRM extensions, and they are kept as they are. Rename the .vrm to .glb to upload it; the glTF to GLB page packs the result back into the same VRM data, to be renamed .vrm again.

Is Draco geometry decompressed?

No. The compressed geometry is copied as it is, with the extension that declares it, so the .gltf needs a Draco-capable reader just as the .glb did.

Is anything uploaded, and for how long?

Yes: the file you drop goes to our server in New York, is converted there, and both the upload and the result are deleted 3 days after the conversion. Nothing is shared with anyone.

Can I look at the GLB first?

Yes, without uploading anything: the GLB and glTF viewer draws it in your browser. Open the GLB and glTF viewer →

The other format pairs

All 57 are free, all run the same pipeline, and all say what they drop.

Only want to look at the file? GLB viewer, FBX viewer and OBJ viewer all run on your own device — nothing is uploaded.

Is your model going into VTubing?

Converting because the model is going into VTubing? VSeeFace, Warudo and VNyan load .vrm, not .glb or .gltf. A rigged model becomes a VRM with its humanoid bones mapped and its materials converted, in one step on the FBX to VRM converter.

Open the VRM converter

More tools for this format