Convert FBX to STL
Convert FBX to STL in your browser. The conversion runs on this page and the file never leaves your computer.
Result
Before you convert: what this keeps and what it destroys
Preserved
- The geometry, triangle for triangle
- Overall dimensions and proportions
- Watertightness, where the input is watertight
Destroyed
- A recorded unit: STL stores none
- Colour
- The separation between parts, merged into one body
- Animation, rigs, cameras and lights, if the file has them
Why people convert FBX to STL
You do this when someone has sent you a game or animation asset and you want the shape.
FBX carries rigs, animation, cameras and materials. None of that means anything to a slicer, so all of it is dropped. What comes through is the geometry and, where present, the node transforms.
Scale is what catches people. FBX stores a unit scale factor in centimetres per file unit, and 3ds Max, Maya and Unity all default differently. A part that arrives 100 times too large crossed a centimetre-to-metre boundary somewhere upstream.
What you get
You get a binary STL file containing the same triangles the FBX file described. No geometry is added, removed or approximated: mesh-to-mesh conversion is a change of container, and this site's tests check that the triangle count comes out identical.
Not carried across by this conversion: a recorded unit, colour, the assembly structure.
The conversion runs in your browser. Your file stays on your computer and is not uploaded.
What to check afterwards
- FBX declares its unit in the file. Check the output dimensions in the receiving application, especially when its import settings can override the unit.
- Colour is lost. STL has nowhere to store it. If colour matters, pick a target that keeps it: 3MF, GLB, PLY or USDZ.
- Separate parts merge into one body. FBX can describe an assembly and STL cannot, so a multi-part model arrives as a single mesh. 3MF and GLB both keep the structure if you need it.
- Coordinates are stored as 32-bit floats. For a part measured in millimetres that's far finer than any machine tolerance. For a model spanning hundreds of thousands of units it isn't.
If you need something this conversion cannot give you
If the unit has to be unambiguous, convert to 3MF instead. It records the unit in the file, so nobody downstream has to assume millimetres and nobody has to scale by 25.4 after the fact.
If colour has to survive, convert to 3MF for printing, GLB for the web, or PLY if the colour is per-vertex scan data.
If the parts must stay separate, convert to 3MF or GLB. Both keep a real structure, so a five-part assembly arrives as five parts rather than one merged body.
If your slicer accepts 3MF, consider it when you need a unit declaration or separate components in the output. Keep the original project for its print settings.
Going the other way
This site reads FBX but does not write it. For the reverse conversion, use an application that can export FBX.
How we know this conversion works
This pair was checked against 2 files from the test corpus on 2026-09-04. Each run parses its own output back in and compares the bounding box, the triangle count and, for closed solids, the volume against the input.
A pair that fails those checks doesn't get a page. That's why this site lists 120 conversions and not the several hundred a format-times-format grid would suggest.