Structure
A GLB file starts with a 12-byte header whose first four bytes spell "glTF" [1]. Chunks follow: first the JSON part with the scene description, then a binary part with geometry and embedded images [1]. JSON and binary data thus share one file without base64 encoding [1].
Why a single file helps
- One request instead of many: the browser loads the model in one go.
- Nothing goes missing: no texture forgotten during upload.
- Easy to pass on: many viewers, shop systems and tools accept GLB directly.
Compression
A GLB file can carry compressed geometry, for example with Meshopt [2] or Draco, and GPU-ready textures in KTX2. The viewer then needs the matching decoder; in three.js it is registered with the GLTFLoader [3].
How to check a GLB file
- File size relative to the product: a simple part does not need 20 MB.
- Scale: glTF works in metres; if the product looks huge or tiny in a viewer, the units are wrong.
- Structure: are parts separate and named, or is everything one lump?
- Extensions: which extensions are marked as required, and does your viewer support them?
For comparison: the GLB of our planetary gearhead (example configurator, fictional product) is about 1.3 MB with more than 200 named nodes. The 3D product viewer page explains how a model gets onto your site.