Blender FBX to Unity: why the scale is 100 and the rotation is -90 (measured)

We exported the same 1 x 2 x 3 m box from Blender 4.2 LTS and 5.2 LTS with every Apply Scalings option and read the FBX files back. Where the 100 scale and the -90° X rotation come from, and the settings that avoid them.

Short answer. With Blender's default FBX settings (Apply Scalings: All Local) the file is written in centimetres and every exported object gets a scale of 100 to keep its size. Set Apply Scalings to FBX All (or FBX Units Scale) and the file is written in metres with a scale of 1. The -90° X rotation is the conversion from Blender's Z-up to the file's Y-up, and Blender writes it on every object. Ticking Apply Transform (static meshes) bakes it into the mesh instead: rotation 0, same size.

What we measured

A box that is 1 m wide (X), 2 m deep (Y) and 3 m tall (Z) in Blender, with its scale applied (Crate_1x2x3), and a second box of the same size built from a 2 x 4 x 6 mesh with an unapplied object scale of 0.5 (Crate_unapplied_0.5). We exported both with each option below, then read every FBX back with the FBX parser that ships with Blender (io_scene_fbx/parse_fbx.py) and printed what the file really contains: the unit (UnitScaleFactor, in centimetres per unit), the declared up axis, and each object's rotation and scale. The last column multiplies it all out: the box's height along the up axis the file declares, in metres. It should be 3 m.

Blender 5.2.4 LTS and Blender 4.2.23 LTS produced identical files for every row. Forward and up axes are the defaults (-Z Forward, Y Up) unless the row says otherwise.

Apply Scalings / optionsFile unit (UnitScaleFactor)Up axis in fileObject rotation X / Y / Z (°)Object scaleScale of the unapplied-0.5 objectMesh size in file unitsHeight along the file's up axis
All Local (Blender's default)centimetres (1.0)Y-90 / 0 / 0100 / 100 / 10050 / 50 / 501 / 2 / 33 m
FBX Units Scalemetres (100.0)Y-90 / 0 / 01 / 1 / 10.5 / 0.5 / 0.51 / 2 / 33 m
FBX Allmetres (100.0)Y-90 / 0 / 01 / 1 / 10.5 / 0.5 / 0.51 / 2 / 33 m
FBX Custom Scalecentimetres (1.0)Y-90 / 0 / 0100 / 100 / 10050 / 50 / 501 / 2 / 33 m
All Local, Apply Unit offcentimetres (1.0)Y-90 / 0 / 0100 / 100 / 10050 / 50 / 501 / 2 / 33 m
All Local + Apply Transformcentimetres (1.0)Y0 / 0 / 01 / 1 / 10.5 / 0.5 / 0.5100 / 300 / 2003 m
FBX All + Apply Transformmetres (100.0)Y0 / 0 / 01 / 1 / 10.5 / 0.5 / 0.51 / 3 / 23 m
FBX All, Use Space Transform offmetres (100.0)Y0 / 0 / 01 / 1 / 10.5 / 0.5 / 0.51 / 2 / 32 m
FBX All, Up: Z, Forward: Ymetres (100.0)Z0 / 0 / 01 / 1 / 10.5 / 0.5 / 0.51 / 2 / 33 m

Apply Unit off wrote the same file as the default because the test scene keeps Blender's default Unit Scale of 1.0; Blender's tooltip says the option takes the scene's unit settings into account, so it only matters if you changed Scene › Units › Unit Scale. Rotations are rounded to 0.01°: the file actually stores -90.000003° because of floating-point precision. Measurement script: medir_fbx.py (run it with blender -b --factory-startup --python medir_fbx.py -- out.json).

Where the scale of 100 comes from

FBX files carry their own unit. With All Local, Blender leaves the file unit at 1.0, which in FBX means one unit = 1 cm, and compensates by scaling each object by 100: the box is still 3 m tall, but the object now has a scale of 100 / 100 / 100. That is the "scale 100" people see. With FBX All or FBX Units Scale, Blender writes the unit as metres (100.0) and the object scale stays at 1 / 1 / 1.

Unity's FBX importer has Convert Units turned on by default, which "converts the model scaling defined in the model file to Unity's scale", and a Scale Factor for anything that is still off (Unity manual, FBX importer Model tab). Fixing the file in Blender is simpler than compensating in every import.

Where the -90° X rotation comes from

Blender is Z-up; with the default axes the file says Y-up. With Use Space Transform on (the default), Blender rotates every object by -90° on X so it stands upright in a Y-up world, and that rotation is stored on the object itself. Nothing on the Unity side added it: it is in the file.

Apply Transform bakes that rotation into the mesh instead: in our test the rotation became 0 / 0 / 0 and the height stayed at 3 m. Blender itself labels this option "experimental, use at own risk, known to be broken with armatures/animations", so use it for static meshes only.

The other route goes through Unity. Exported with Up: Z Up, the file declares Z-up and the objects carry no rotation (last row of the table). Unity's support article explains that for Z-up files Unity adds a root rotation, usually -90° on X, and that Bake Axis Conversion on the Model tab bakes it into the asset and zeroes the root. It also warns to use that option only on models that import with a rotation on the root: on a model that is already Y-up it adds a -90° rotation instead (Unity support). We did not run Unity for this page; the Unity behaviour here is from Unity's documentation.

Two settings that look like fixes but are not

Turning off Use Space Transform. The rotation disappears (0 / 0 / 0), but the file still says Y-up while the mesh is still Z-up: our 3 m tall box measured 2 m along the up axis. It is lying on its back.

Leaving an object scale unapplied. The object scale goes into the file as it is: our 0.5 box came out with a scale of 0.5 / 0.5 / 0.5 with FBX All and 50 / 50 / 50 with the default settings. The size is right, but colliders, child objects and anything you scale later inherit that number. Apply it in Blender first (Object › Apply › Scale).

Settings we use for static meshes going to Unity

Checking a whole folder of exports

We make ExportProof, a Blender add-on that exports every selected mesh to its own GLB, FBX or OBJ file with a Unity, Unreal, Godot or Web preset (the Unity preset uses the settings above, with Apply Transform off), then re-imports each file and checks that the size and triangle count still match the scene. It warns about unapplied or negative scale before exporting. It does not run Unity: it checks the file, which is where all of the problems on this page live.

ExportProof on Gumroad · USD 7