The format the thing at the other end wants
Format Conversion
glTF, FBX, USDZ, OBJ, STL and 3MF, converted from any model in your library — without a round trip through a DCC application to change a container.
What it does
Six formats
glTF for the web and real-time engines, FBX for animation pipelines, USDZ for Apple’s AR, OBJ for anything that reads it, and STL or 3MF for printing.
3MF as well as STL
STL carries geometry and nothing else. 3MF carries colour and material information with it, which matters the moment a printer can use them.
It runs quietly underneath, too
Tools that need a particular format get it automatically. Rigging wants FBX; you are never asked to produce one first.
The original stays
A conversion is a new library model, so you keep both.
How it works
- Pick a modelGenerated or uploaded, it makes no difference.
- Choose the target formatRequired for a conversion and ignored everywhere else.
- DownloadOBJ arrives as an archive, because an OBJ is never one file — the material definition and its textures travel with it.
What people use it for
- Handing a printer an STL or a 3MF from a model generated for a game
- Getting a USDZ for an AR product viewer on iOS
- Getting an FBX for an animation pipeline that will not read glTF
- Delivering the format a client specified without opening a modeller
What it cannot do
- A conversion carries what the target format supports. Animation does not survive a trip through OBJ, and nothing survives a trip through STL but geometry
- It changes the container, not the contents. A model with no textures converts to a model with no textures
- Print formats are output only — they can be produced and are not sensible to ingest, since they carry no UVs to bring back
The details
- Writes
- glTF, FBX, USDZ, OBJ, STL, 3MF
- Reads
- GLB, OBJ, FBX
- OBJ packaging
- Archive, with materials and textures
- Automatic
- Yes — tools convert their own inputs
Last reviewed