How to Export GLB Models for Godot, Unity and Unreal Engine

Understand scale and engine profiles

FORM 3D models in metres. Godot and Unity normally work well with metre-scale source assets. Unreal Engine commonly treats one unit as one centimetre, so the Unreal profile applies the relevant conversion for this workflow.

• Godot profile: metre-oriented scale 1.
• Unity profile: metre-oriented scale 1.
• Unreal profile: metres converted to centimetres.
• Other profile: explicit general glTF handoff without an engine-specific assumption.

Clean the source project

1. Delete abandoned experiments rather than relying only on visibility.
2. Confirm object names, parent-child relationships and pivots.
3. Check that animated parts remain separate and deforming meshes retain their skin or Shape States.
4. Review material base colour, roughness, metalness, opacity and texture resolution.
5. Save an editable project checkpoint before optimisation.

Choose export options deliberately

• Include animations only when the receiving project needs model clips.
• Include textures when painted or imported image data is part of the asset.
• FORM 3D preserves node transforms and keeps mesh vertices local so pivots remain usable in game engines.
• Reference images and editor helpers are excluded from GLB.
• Camera presets belong to rendered video rather than model export.

Use preflight and optimisation

1. Open Export and review errors, warnings, triangle count, texture count and animation count.
2. Fix missing targets, invalid hierarchy or non-finite transform errors.
3. Run Safe optimisation first.
4. Use Strong optimisation only when its more aggressive changes are acceptable.
5. Undo the optimisation if silhouette, paint or intended segment detail changes.
6. Download the export report for a reproducible asset record.

Verify and export GLB

1. Select Verify & export GLB.
2. Wait while the studio generates and parses the GLB back.
3. Do not rename or discard the editable project based on internal verification alone.
4. Open the GLB in an independent glTF viewer.
5. Import it into the target engine and inspect the generated scene or prefab.

Engine-specific acceptance checks

The project owner has confirmed a successful Godot import from the current FORM 3D export workflow. Treat that as a useful checkpoint rather than a guarantee for every Godot version, renderer and import setting; record your own engine version and repeat these checks for release assets.

• Godot: inspect imported scene scale, material resource settings, animation library and root node.
• Unity: inspect model scale factor, material extraction or remapping, animation clips and rig classification.
• Unreal Engine: inspect centimetre scale, material instances, skeletal/static mesh choice and animation sequences.
• Every engine: confirm front direction, pivot, hierarchy, texture colour space and loop settings.

Separate source files from delivery files

The FORM 3D project contains editor-specific state, history-compatible geometry and settings. The GLB is the portable delivery asset. Keep both, because importing the GLB later cannot reconstruct every parametric control or editor decision.