Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Modelling tools, slicers, game engines and web viewers each want a different file, and the differences between the formats are mostly about how much they carry besides the shape itself.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
6 formats in this category, 30 working conversions — 30 of them without your file leaving the device.
The 3D printing standard. Triangles only — no colour, no material, no texture.
A plain-text 3D mesh format every modelling program can read.
The scanner format. Carries per-point colour, which is why 3D scans arrive as PLY.
The 3D format for the web. Geometry, materials and animation in one JSON file.
glTF with its textures packed in. One file instead of a folder full of dependencies.
The modern replacement for STL. Keeps colour, materials and units instead of bare triangles.
STL stores triangles and nothing else — no colour, no texture, no material, not even a unit. It is what 3D printing has standardised on precisely because a printer needs a watertight shape and nothing more, and it is why converting a textured model to STL loses everything except the form.
OBJ adds materials and texture coordinates. GLB and glTF go further and are built for the web and for game engines: one file carrying geometry, materials, textures and animation together. Converting up from STL cannot invent the information STL never held, so a converted STL is a shape and stays a shape.
STL has no unit. The numbers in the file are just numbers, and whether they mean millimetres or inches is a convention between the tool that wrote it and the tool that reads it. This is why a model sometimes arrives in a slicer at twenty-five times the intended size, and it is a property of the format rather than of the conversion.
If a converted model comes out wrong by a suspiciously round factor, that is almost always what happened, and the fix is in your slicer rather than here.
Only into formats that can hold them. STL stores triangles and nothing else, so converting to it keeps the shape and discards materials and textures. GLB and OBJ carry them.
STL, which every slicer accepts, or 3MF where your slicer supports it — 3MF carries units and metadata that STL simply has no place for.
Because STL has no unit — the numbers are just numbers, and the meaning is a convention between tools. A wrong size by a round factor is almost always this, and the fix is in your slicer.
No. It is converted in your browser and never leaves your device, which for unreleased work or a client model under NDA is rather more than a convenience.