glTF to GLB converter: every byte kept
Drop a .gltf, or a zip of its folder with the .bin and the images, and get one .glb. The buffers and the images are packed into the binary chunk as they are: nothing is decoded or re-encoded, so meshes, skins, morph targets, animations, Draco compression, VRM data and extensions arrive unchanged. Free, no account, nothing to install.
How do I convert glTF to GLB?
Drop the .gltf, or a zip of its folder, on this page and download one .glb. No 3D program opens the file on the way.
- 1Choose the .gltf if it carries everything inside, or zip the folder that holds the .gltf, its .bin and the images and choose the zip. Files up to 50 MB.
- 2The server checks every file the .gltf names, then packs the .bin and the images into one GLB and points the JSON at them. It takes seconds.
- 3Download the .glb. The upload and the result are deleted 3 days later.
- In:
- .gltf (or a zip of its folder)
- Out:
- one .glb file
- Keeps:
- everything: the JSON as it is and every binary byte
- Cost:
- free, no account
- A .gltf that names a file outside its folder, by an absolute path or a web address, is refused.
What survives the trip
A .gltf keeps its geometry in one or more .bin files and its images as separate files, all named by relative path. A GLB holds the same JSON with one binary chunk. The packer lays the buffers one after another in that chunk on 4-byte boundaries and moves each image into it as a buffer view with its type (PNG, JPEG, WebP or KTX2). Data URIs are decoded the same way.
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. GLB is what web viewers, three.js, model-viewer, Godot, Unity and Unreal importers read without a plug-in.
Which files are followed
Only relative paths that stay inside the uploaded folder, after the %-escapes are decoded. An absolute path, a web or file:// address, a backslash, or a path that climbs out of the zip gets the whole file refused before anything is read. A file the .gltf names that is not in the zip is reported by name, so you know what to add.
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.
A .gltf with files beside it comes as a zip
A .gltf names its .bin and its images by relative path. Uploaded alone it has no geometry, and the page refuses it with the names of the missing files. Zip the folder that holds the .gltf, the .bin and the images and upload the zip. Absolute paths and web addresses are refused.
References outside the folder are refused
A .gltf that names an image by a web address or by a path on another disk cannot be packed: nothing is fetched from the web or read outside the upload. Copy the files next to the .gltf, change the paths to plain relative names, then zip the folder.
The packed file stops at 300 MB
All the buffers and images together, measured before anything is read. A larger result is refused; shrink the textures first.
Uploads stop at 50 MB
A larger file is refused before anything is uploaded. A zip is measured as uploaded.
Frequently asked questions
Is anything lost?
No. The JSON keeps every field; only the list of buffers and the image entries that named files change, to point into the binary chunk. Geometry and image bytes are copied as they are. Several .bin files become one buffer. GLB to glTF converter →
Does it work with a VRM?
Yes. A VRM unpacked to glTF packs back into the same VRM data: the extensions are copied, not read. Rename the .glb to .vrm afterwards.
What if the zip holds several .gltf files?
The largest one is packed, with the files it names. Zip one model per upload to choose which.
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 glTF first?
Yes, without uploading anything: the GLB and glTF viewer draws it in your browser, a .gltf with its folder dropped alongside included. 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.
GLB to FBX
GLB in, FBX out, free: one file.
GLB to OBJ
GLB in, OBJ out, free: zipped with its files.
FBX to GLB
FBX in, GLB out, free: one file.
OBJ to GLB
OBJ in, GLB out, free: one file.
STL to GLB
STL in, GLB out, free: one file.
PLY to GLB
PLY in, GLB out, free: one file.
DAE to GLB
DAE in, GLB out, free: one file.
USDZ to GLB
USDZ in, GLB out, free: one file.
GLB to STL
GLB in, STL out, free: one file.
GLB to PLY
GLB in, PLY out, free: one file.
GLB to DAE
GLB in, DAE out, free: zipped with its files.
GLB to USDZ
GLB in, USDZ out, free: one file.
3MF to GLB
3MF in, GLB out, free: one file.
GLB to 3MF
GLB in, 3MF out, free: one file.
Blender (.blend) to GLB
Blender (.blend) in, GLB out, free: one file.
glTF to FBX
glTF in, FBX out, free: one file.
GLB to glTF
GLB in, glTF out, free: zipped with its files.
FBX to glTF
FBX in, glTF out, free: zipped with its files.
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