FBX to STL converter
Drop your .fbx file — we convert it to .stl right in your browser. Files never leave your computer.
Why convert FBX to STL?
FBX scenes from Unity / Unreal / Mixamo often contain a single printable prop buried in a rigged character. Extracting it to STL is how that prop ends up on a physical printer — as merch, as a figurine, or as a display piece.
Who runs this conversion
Game artists printing in-game props as physical merch, indie devs making character statues from their own assets, and Mixamo users grabbing a T-pose mesh for printing.
Things that commonly go wrong
- FBX rigs, animations, and morph targets do not survive — STL is a static triangle soup frozen in bind pose.
- Multi-mesh FBX scenes flatten into one STL; if you need separate parts, split in Blender first.
- Game assets often have non-manifold geometry (overlapping shells, inverted faces) that fails slicer import — run Mesh → Clean Up before printing.
Technical note for this tool
FBXLoader produces a rigged Group; we snapshot the current pose into a single BufferGeometry, then STLExporter writes binary STL.
FBX vs STL— what's the difference?
Autodesk's proprietary interchange format — the de-facto standard for moving rigged, animated characters between Maya, Max, Blender, Unity, and Unreal.
- Carries skeletal animation, blend shapes, cameras, lights
- Supported by every major DCC and game engine
- Binary or ASCII flavours
- Closed, Autodesk-controlled spec — SDK-only for authoritative reads
- No universal web viewer — typically converted to GLB for the browser
Triangle-mesh format that every 3D printer slicer understands. Geometry only — no units, colours, or assemblies.
- Universal 3D printing format — Cura, PrusaSlicer, Bambu Studio all speak STL
- Tiny, simple, extremely fast to load
- Great for meshing workflows, simulation pre-processors, quick previews
- Triangulated approximation — curved surfaces lose precision
- No colour, material, or assembly data
- One shell per file by convention (multi-body gets flattened)
Deeper context on the formats
FBX — where it came from
Originally developed by Kaydara in 1996 for their Filmbox motion-capture software. Alias bought them, Autodesk bought Alias, and FBX became the default handoff between Maya, Max, MotionBuilder, and every game engine built in the last two decades. The spec is technically closed, but the FBX SDK is freely downloadable and maintained.
- FBX version mismatches are the #1 support ticket — a Unity project expecting FBX 2020 may refuse FBX 2013 binary. When in doubt, re-export as FBX 2020 ASCII.
- Embedded textures (vs referenced) balloon file size; uncheck "Embed media" unless you are shipping a self-contained asset pack.
- Scale inheritance settings differ between Maya and Max — rig scales can distort on re-import. Bake scale to 1.0 before export.
Real-world use: Character animation pipelines (Mixamo, Rokoko, Adobe Character Animator outputs), game-engine import (Unity, Unreal, Godot all accept FBX natively), VFX houses moving assets between Maya and Houdini. If the asset has a skeleton, the probability it travels as FBX is roughly 80%.
STL — where it came from
Invented by 3D Systems in 1987 for the first commercial stereolithography machine (hence the name — "STereoLithography"). It was supposed to be a throwaway internal format; nearly four decades later it is still the default hand-off between CAD and every slicer on the market, simply because nothing else got universal support in time.
- STL has no units — a file authored in inches and re-opened in a metric slicer prints at 1/25.4 scale. Always confirm the source units before slicing.
- Non-manifold meshes (holes, flipped normals, internal walls) slice silently but print as unsolvable garbage. Run the mesh-repair tool before wasting filament.
- ASCII STL is ~5× larger than binary STL with zero benefit — always export binary unless you specifically need to diff the file.
Real-world use: Every FDM and SLA slicer (Cura, PrusaSlicer, Bambu Studio, Lychee, Chitubox) reads STL as a first-class input. Simulation pre-processors (Ansys, Abaqus) also consume STL for meshing. Fabrication-on-demand services (Shapeways, JLCPCB's 3D print arm, Protolabs) accept STL uploads directly.
How to convert FBX to STL
- 1Drop a .fbx file on the page — binary or ASCII FBX both work. Everything runs locally.
- 2Preview the geometry in 3D. If the model has multiple parts, the Scene Tree on the left lets you toggle which ones go into the STL.
- 3Click Download .STL to save a binary STL. Open in Cura, PrusaSlicer, or Bambu Studio and print.
FAQ
Does the animation / rig survive?
No — STL is geometry only. The mesh is frozen in its bind pose at export. If the FBX has multiple animated frames, only the current pose is captured. Bake animation in your DCC first if you need a specific frame.
Will materials and textures be preserved?
No, STL has no material or texture data. If you need colour-capable 3D printing (Bambu AMS, Polyjet), export to 3MF or GLB instead.
Is the mesh watertight for printing?
STL itself doesn't care, but slicers do. If the FBX mesh has holes or flipped normals your slicer will complain. Check in Blender → Mesh → Clean Up → Merge by Distance before printing.
What about scale?
FBX unit metadata is respected when present. If the model comes out at 1mm instead of 10cm, check the FBX Units setting in the source DCC — Maya and 3ds Max default differently.
Is my FBX uploaded?
No. Everything runs in-browser via Three.js' FBXLoader and STLExporter.