Beyond three.js: other engines

GLB is the portable part of a pack. The same model can be used outside three.js when the target application supports the glTF features present in that file. Optional React components and browser showrooms do not carry over.

Start with an individual GLB#

Current low-poly individual bundle files are commonly uncompressed, making them the simplest choice for another engine or DCC tool. Typical import paths include:

• Babylon.js — SceneLoader.ImportMeshAsync or AppendSceneAsync;
• <model-viewer> — set the GLB as src;
• Godot — use its glTF/GLB importer; and
• Blender — choose File → Import → glTF 2.0.

Exact material, animation, and extension support changes by application and version. Test one representative model before committing a project to the workflow.

Check compression and textures#

Combined catalogs and some prebuilds use Draco. Before importing one, verify Draco support in the exact target version or decompress a working copy with a glTF tool. The optional combined catalog is joined for inspection and does not restore independently editable assets after import.

If a GLB uses KTX2 textures, verify Basis/KTX2 support as well. Current texture-free low-poly files do not need it, but that does not apply to every pack.

See Individual GLBs vs the combined catalog for file-selection guidance.

Materials and colours#

Environment models commonly store colour in vertex attributes. Configurator models instead expose named materials. A global tint can carry across engines, but flattened vertex colours do not retain per-key palette identity. Use the material and node names found in the actual GLB rather than relying on a three.js component.

Scale and pivots#

Y-up, +Z forward, metric height conventions, and grounded pivots are common targets, not a substitute for the pack README. Confirm the imported bounding box, origin, and forward direction before building physics, navigation, or snapping around a model. See scale, orientation & pivots.

Unity and Unreal#

Packs do not promise FBX files, Unity prefabs, Unreal assets, or engine-native materials. GLB support in those engines depends on plugins and versions. Validate geometry, materials, compression, animations, collisions, and licensing before choosing a pack for that workflow.

Related#

• What's in an asset pack — understand optional bundle contents.
• Individual GLBs vs the combined catalog — choose a portable file.
• Scale, orientation & pivots — verify placement conventions.