Output Options
File Format
Choose between a single self-contained .glb binary or a JSON-based .gltf file with separate resources.
Default: glb
glb
A single binary file that bundles the scene description, geometry buffers, and textures together. One file to copy, one file to upload, one file to share.
Use glb when:
- Handing off to a client or uploading to a platform
- Loading into a web viewer, model-viewer, or real-time application
- You want a clean single-file deliverable with no loose dependencies
glTF
A JSON text file that references external resources. Geometry and textures exist as separate files next to the .gltf.
Use glTF when:
- You need to inspect or edit the scene JSON directly
- A pipeline script reads or modifies the glTF structure
- You want to swap or update textures without re-exporting geometry
- You need to control exactly how resources are laid out — see Resources
Quick comparison
| glb | glTF | |
|---|---|---|
| File count | 1 | Multiple |
| Textures | Packaged inside | External or embedded |
| Human-readable | No | Yes |
| Best for | Delivery and runtime | Pipelines and inspection |
Tip
When in doubt, choose glb. It is the most widely supported format for handoff and runtime use. Switch to glTF only when your workflow specifically benefits from separate resource files.