Drop your .gltf (+ .bin + textures) file — we convert it to .glb right in your browser. Files never leave your computer.
The JSON-based twin of GLB. Same spec, just split into a human-readable .gltf plus external .bin and texture files.
Binary glTF — the JPEG of 3D. Self-contained, small, and loads natively on the web, in AR, and in every modern 3D engine.
A .gltf is fragile — it references external .bin and texture files, and one missing file breaks everything. A .glb bundles it all into one binary: simpler to email, embed, or upload to a CDN.
No — GLB is the same glTF spec, just packaged as binary. PBR materials, animations, extensions, everything carries over exactly.
Usually slightly smaller (saves on base-64 overhead and JSON whitespace), but the main win is operational simplicity rather than size.
Your source .gltf probably references textures by a path the browser couldn't find. The converter only sees files you drop. If your .gltf has external textures, pre-embed them in the .gltf (most exporters have a "embedded" option) or use the main 3D viewer which accepts folder drops.
No. Three.js' GLTFLoader and GLTFExporter handle everything client-side.