GLB is the web and real-time file.

When GLB is the right file

GLB is the safest drop-in for a web viewer and for a real-time scene that already accepts it. One file holds the mesh and the materials, so there is no sidecar texture to lose in the handoff.

Use another format when the importer expects FBX or when a slicer is the destination. GLB itself supports skinning and animation; Objectify lists rigged FBX as its rigging export. Those are different questions. Match the actual export to the receiving tool.

What it carries

A GLB from Objectify carries the mesh, the UVs, and the PBR maps: base color, roughness, metallic, and normal. That is the same map set the generation and the texture pass produce.

It does not add a skeleton. If the character has to walk, rig it first and export the rigged FBX. A viewer that only orbits the model should stay on GLB and skip the rig.

Which plan exports it

Pro exports GLB, FBX, OBJ, STL, USDZ, and 3MF. You do not pick a plan to unlock one format over another.

Studio adds the rigged FBX, the API, and a shared workspace. The format choice itself stays on Pro.

Limits to check before delivery

GLB can include embedded resources, skins, and animations, but a valid container does not guarantee every extension is supported by a viewer. Unity and Unreal import paths vary by installed tooling. Objectify's rigged FBX offer is separate from GLB's format capabilities.

• Khronos — glTF 2.0 specification
• Godot documentation — available 3D formats
• Blender Manual — glTF 2.0 import and export

Handoff checklist

Open the actual file in the target viewer. Check materials, scale, orientation, texture presence, and silhouette. If resources are external, retain them with the file. Compare the received model with the approved source and record any unsupported extensions.