Blender to Godot: export settings, scale, rotation and collision suffixes (measured in Godot 4.7)
We exported one test scene from Blender 4.2 LTS and 5.2 LTS as GLB and FBX, imported every file in Godot 4.7.2-stable and dumped the nodes it built: rotation, scale, size, and which name suffixes become collision shapes.
Short answer. Export GLB with Blender's default settings (+Y Up on): in Godot every node
came in with rotation 0 / 0 / 0, scale 1 / 1 / 1 and the right size. Blender's
default FBX came in with rotation -90 / 0 / 0 and scale 100 / 100 / 100 on every node. To get collisions, end the
object's name in Blender with -col (trimesh) or -convcol (convex); -colonly and
-convcolonly give a collision with no visible mesh, and -noimp leaves the object out.
What we measured
One Blender scene: a box 1 m wide, 2 m deep and 3 m tall (Crate_1x2x3, scale applied), the same box built
from a 2 x 4 x 6 mesh with an unapplied object scale of 0.5 placed at Blender (3, 1, 0), and eight more objects whose
names end in Godot's import suffixes. We exported it from Blender 5.2.4 LTS and from Blender 4.2.23 LTS in five ways, imported
every file in Godot 4.7.2-stable (official build, headless, default import settings) and dumped each node's class,
rotation, scale, position and mesh size with a script. Both Blender versions gave identical results in Godot.
Scripts: exportar_godot.py (Blender side), medir_godot.gd and
medir_godot.sh (Godot side).
Export settings: what Godot builds
| Export from Blender | Node rotation X / Y / Z (°) | Node scale | Mesh size X / Y / Z in Godot (m) | Height (Godot Y) | Scale of the unapplied-0.5 object | Position of the object at Blender (3, 1, 0) |
|---|---|---|---|---|---|---|
| GLB, +Y Up on (Blender's default) | 0 / 0 / 0 | 1 / 1 / 1 | 1 / 3 / 2 | 3 m | 0.5 / 0.5 / 0.5 | 3 / 0 / -1 |
| GLB, +Y Up off | 0 / 0 / 0 | 1 / 1 / 1 | 1 / 2 / 3 | 2 m | 0.5 / 0.5 / 0.5 | 3 / 1 / 0 |
| FBX, Blender's defaults (All Local) | -90 / 0 / 0 | 100 / 100 / 100 | 1 / 3 / 2 | 3 m | 50 / 50 / 50 | 3 / 0 / -1 |
| FBX, Apply Scalings: FBX All | -90 / 0 / 0 | 1 / 1 / 1 | 1 / 3 / 2 | 3 m | 0.5 / 0.5 / 0.5 | 3 / 0 / -1 |
| FBX, FBX All + Apply Transform | 0 / 0 / 0 | 1 / 1 / 1 | 1 / 3 / 2 | 3 m | 0.5 / 0.5 / 0.5 | 3 / 0 / -1 |
Godot is Y-up: the box should be 3 m along Godot's Y. Blender's +Y axis becomes Godot's -Z, which is why the object at Blender (3, 1, 0) lands at (3, 0, -1) when the export converts axes.
- GLB with +Y Up (the default): no rotation, no scale, correct size. This is the one to use.
- GLB with +Y Up off: no rotation either, but the model is still Z-up: our 3 m box is 2 m tall in Godot and the 6 x 6 m floor stands up like a wall (size 6 / 6 / 0.1).
- FBX with Blender's defaults: right size, but every node carries a -90° X rotation and a scale of 100 (the file is written in centimetres; see our FBX measurement). FBX All removes the 100; FBX All + Apply Transform also removes the rotation (Blender marks Apply Transform as experimental and broken with armatures and animation).
- Unapplied object scale survives every format: the 0.5 box arrived with a node scale of 0.5 (or 50 with default FBX). Apply scale in Blender first (Ctrl+A › Scale), especially for anything with a collision shape.
Collision and import suffixes
Godot reads hints from the end of each object's name. This is what Godot 4.7.2-stable built from the GLB (the FBX files produced the same nodes):
| Suffix | Object name in Blender | Nodes Godot created | Collision shape |
|---|---|---|---|
-col | Wall-col | MeshInstance3D Wall└ StaticBody3D StaticBody3D└ CollisionShape3D CollisionShape3D | ConcavePolygonShape3D (trimesh) |
_col | Floor_col | MeshInstance3D Floor└ StaticBody3D StaticBody3D└ CollisionShape3D CollisionShape3D | ConcavePolygonShape3D (trimesh) |
-COL (upper case) | Crate-COL | MeshInstance3D Crate└ StaticBody3D StaticBody3D└ CollisionShape3D CollisionShape3D | ConcavePolygonShape3D (trimesh) |
-convcol | Ramp-convcol | MeshInstance3D Ramp└ StaticBody3D StaticBody3D└ CollisionShape3D CollisionShape3D | ConvexPolygonShape3D (convex) |
-colonly | Barrel-colonly | StaticBody3D Barrel└ CollisionShape3D CollisionShape3D | ConcavePolygonShape3D (trimesh) no visible mesh |
-convcolonly | Rock-convcolonly | StaticBody3D Rock└ CollisionShape3D CollisionShape3D | ConvexPolygonShape3D (convex) no visible mesh |
-rigid | Box-rigid | RigidBody3D Box-rigid└ MeshInstance3D Box-rigid└ CollisionShape3D CollisionShape3D | ConvexPolygonShape3D (convex) |
-noimp | Helper-noimp | not imported (no node at all) | none |
- The suffix is removed from the node name (
Wall-colbecameWall), except with-rigid, which keptBox-rigidon both the RigidBody3D and its mesh. _colwith an underscore and-COLin upper case worked the same as-col.- A dot in a Blender name does not survive:
Crate_unapplied_0.5becameCrate_unapplied_0_5in Godot, so scripts that look nodes up by name need the underscore. -coland-colonlygive a trimesh shape (ConcavePolygonShape3D). Godot's class reference says this shape is meant for static bodies and "will likely not behave well" on a CharacterBody3D or a RigidBody3D that is not static (ConcavePolygonShape3D). For props that move, use-convcol,-convcolonlyor-rigid, which produced convex shapes.
Checking exports before they reach Godot
We make ExportProof, a Blender add-on that exports every selected mesh to its own file with a Godot preset (GLB) or a Unity, Unreal or Web preset, re-imports each file to confirm the size and triangle count did not change, and warns about unapplied or negative scale before exporting. It works on the file; it does not run Godot.