Skip to content

Output Options

Resources

Control how geometry buffers and texture images are laid out when exporting a .gltf file.

Back to Export Options Open Exporter Overview

Applies to: glTF exports only (not glb)
Default: Copy source files

This option only appears when File Format is set to glTF. It controls where the geometry data and texture images are stored relative to the .gltf JSON file.

Single .bin

All geometry buffers and images are packed into a single .bin sidecar file next to the .gltf.

Good for:

  • Keeping the number of loose files small while still having a readable JSON
  • Pipelines that expect the standard .gltf + .bin two-file layout

Copy source files

Textures are copied (or converted if texture conversion is active) into the same folder as the .gltf. Geometry buffers go into a .bin file.

Good for:

  • Workflows where you want to view and manage textures directly in the folder
  • Iterating on textures — you can replace an image file without re-exporting geometry

Embedded

All resources — buffers and images — are encoded as base64 and embedded directly inside the .gltf JSON.

Good for:

  • Sending a single self-describing file over a system that only handles text or JSON
  • Debugging — everything is visible in one place

Drawbacks:

  • Files become much larger than equivalent glb
  • Not efficient for delivery or runtime loading — most viewers prefer external or binary resources

Quick comparison

Option Textures Geometry File count
Single .bin Inside .bin Inside .bin 2
Copy source files Separate image files Inside .bin Many
Embedded Base64 in JSON Base64 in JSON 1 (large)