Ten formats are ten formats only if you know which one you want. Below is what each target expects — and what the file actually carries.
⬢
3D printing
STL3MF
Any slicer — PrusaSlicer, Bambu Studio, Cura, Orca. 3MF carries the unit in the file; STL does not, so the answer is millimetres.
Run „Print check“ first: a slicer must know what is inside and what is outside, and AI or scanned models usually are not closed.
◆
Unreal Engine
FBXGLB
FBX is the usual way in; GLB works too. Our FBX records millimetres and Z-up in the file itself, so nothing has to be guessed.
Unreal counts in CENTIMETRES. We have not tested the import ourselves, so check the size of the first object you bring in.
◇
Unity and Godot
FBXGLB
FBX or GLB. Godot reads GLB natively; Unity takes both.
Both count in metres with Y up — neither of the two things a print file carries. We have tested neither engine ourselves: check size and up-direction on the first object.
◐
Blender
GLBFBXOBJ
GLB, FBX or OBJ. This is the one we do test: a gate opens our FBX in Blender on every change and compares the size.
Measured: a 20 × 30 × 40 mm cube opens as 0.02 × 0.03 × 0.04 m — Blender works in metres, so that is the same thing.
Units and which way is up
This is the most common reason a model arrives a thousand times too small or lying on its side. It is a property of the format, not of our export.
FormatUnitUpIn the file
STLmmZ
no
3MFmmZ
yes
OBJmmY
no
PLYmmZ
no
GLB / glTFmY
yes
FBXmmZ
yes
DAEmmZ
yes
„In the file“ means the program can read it and does not have to assume. Where it says no, the program guesses — and different programs guess differently.