Guide
glTF units and scale explained
glTF stores every length in meters with Y pointing up. STL has no units and slicers assume millimeters with Z up. Get those two facts right and scale problems disappear.
Most failed GLB to STL conversions are not failures at all. The mesh is fine; it is just 1,000 times too small, or lying on its back. This guide explains the conventions behind both problems. FurniMesh (furnimesh.com), our own product, notes on its converter page that real-world units are dropped in a GLB to STL conversion, which is exactly why you should set the scale yourself.

What the glTF specification says
The glTF 2.0 specification is explicit. The units for all linear distances are meters. Angles are in radians. The coordinate system is right-handed, with +Y up, +Z forward and -X to the right, so the front of an asset faces +Z. Any program that writes valid glTF must convert its own units into meters on export, so a 45 cm chair seat should be stored as 0.45.
That rule is what makes glTF predictable. When you open a GLB from any source, the numbers in the bounding box are meters, and a model whose numbers do not make sense in meters was exported incorrectly.
Why STL has no unit
STL predates any common agreement on units. A binary STL stores 32-bit floating-point coordinates and nothing else: no unit field, no up axis, no scale. The meaning of the numbers is left to the program reading them, and slicers almost universally read them as millimeters.
So a correct glTF chair that is 0.4566 m wide, copied straight into STL, is a 0.4566 mm chair to your slicer. PrusaSlicer detects very small imports and asks whether the object's dimensions were defined in meters or inches, offering to recalculate them. Other slicers simply show a speck on the bed, or report that the object is too small to slice.
The conversion factors you need
| Source unit | To millimeters | When you see it |
|---|---|---|
| Meters (glTF standard) | x 1000 | Any correctly exported GLB |
| Centimeters | x 10 | Files from tools that work in cm and skipped unit conversion |
| Inches | x 25.4 | Models authored in US units without conversion |
| Millimeters | x 1 | CAD exports that wrote mm values into glTF |
Our converter covers the first and last rows directly with "Meters to millimeters" and "Keep numbers as they are". For the others, or whenever you know the real size, use "Fit longest side" and type the length in millimeters.
How to tell which unit a file really uses
Load the file and read the bounding box. Compare it with what the object is in real life:
- A dining chair reading about 0.45 x 0.9 x 0.5 is correct meters. Use x1000.
- The same chair reading 45 x 90 x 50 was written in centimeters. At x1 you get 45 mm; type the real height into "fit longest side" instead.
- A reading of 450 x 900 x 500 was written in millimeters. Use "keep numbers as they are".
- A reading near 1 x 2 x 1 for a chair is a model normalized to fit a unit box, common in AI-generated and game assets. There is no real size to recover, so fit it to a measured length.
The Model panel also shows the same box converted to millimeters, so you can sanity check the result before you download.
Scale models: the arithmetic
For a scale model, divide the real size by the scale number. A real armchair 826.6 mm wide, such as the SheenChair sample model, is 68.9 mm wide at 1:12 and 34.4 mm at 1:24. Type that length into "fit longest side" and the converter computes the factor. For SheenChair at 1:12, typing 68.88 gives x83.33, which is the 1,000 for meters to millimeters divided by 12.
Fit to size uses the longest side after rotation, so the three dimensions keep their proportions. If you want a specific height rather than the longest side, compute the factor yourself: target height divided by the height in meters. Then pick "Keep numbers as they are" and scale in your slicer by that percentage.
Y-up versus Z-up
glTF uses Y for up. Slicers, Blender and most CAD tools use Z for up. Copy the coordinates straight across and a model that stood upright in a web viewer lies on its back in the slicer, with its front facing the ceiling.
The fix is a 90 degree rotation about the X axis, which maps the old Y to the new Z and the old Z to the new negative Y. That is what "Rotate Y-up to Z-up" does. Because it is a pure rotation, it keeps the mesh's handedness, so triangles still face outward. Blender's glTF importer performs the same conversion automatically, which is why a GLB opened in Blender stands up correctly.
Transforms hide scale too
Not all scale lives in the vertex numbers. glTF nodes carry their own scale, and a common export pattern stores the mesh in centimeters with a 0.01 scale on the parent node. Viewers apply the node scale and show the right size. A converter that ignores node transforms writes the raw centimeter values and gets the size wrong by 100 times.
Keep "Apply node transforms" ticked to avoid this. It bakes every translation, rotation and scale from the node tree into the vertices, so the STL matches what you see in a viewer. Mirrored nodes, those with a negative scale, are handled too: the converter reverses their triangle winding so faces still point outward.
A two-minute check before printing
Before you commit hours of printing, print the converted file's size readout next to your expectation. If the converter says 68.9 x 47.5 x 57.2 mm and your slicer says the same, scale is right. If they disagree, check whether the slicer applied its own scaling on import. A quick 5-minute test print of a simple box, like the one pictured above, also tells you whether your printer's steps per millimeter are calibrated, which matters more for scale models than any converter setting.