Five coloured parts in metres
A GLB that follows the specification. x1000 gives the right size in millimetres, and the five meshes and their colours become one grey STL.
Drop in a GLB or glTF file and get an STL back. The conversion runs in your browser, so nothing is uploaded. The panel shows the size the STL will have in millimetres, which is the part most converters leave you to discover in the slicer.
Drag and drop a GLB file here, or
Accepts .glb and .gltf. Nothing is uploaded.
glTF measures distance in metres. STL carries no unit at all, and slicers read it as millimetres, so x1000 is the correct factor for a file that follows the spec. Compare the output size against the size you expect before downloading.
Checked in your browser. Nothing is uploaded.
The file is read and converted on your device. It is never uploaded to a server.
A GLB that follows the specification. x1000 gives the right size in millimetres, and the five meshes and their colours become one grey STL.
Some exporters ignore the specification. x1000 would make this robot 62 metres wide, so the output line is your cue to pick x1.
Our Stable Fast 3D figurine converts to 94 cm tall. The factor is right; the size is the generator's guess, so scale it to what you want.
glTF is in metres, STL has no unit and slicers read millimetres. Multiplying by 1000 fixes any file that follows the specification.
STL has no idea of separate objects, so every mesh in the GLB is merged into one. The mesh count in the panel tells you how many.
Binary STL spends 50 bytes per triangle; ASCII writes the same numbers as text and comes out several times larger. Slicers read both.
No. The GLB is parsed and the STL is written by JavaScript running in your own browser tab, so the file never leaves your device. You can confirm this by opening the network tab of your browser developer tools during a conversion, or by disconnecting from the internet after the page has loaded and converting anyway.
Because STL has no standard way to store colour, textures or materials. Two non-standard conventions reuse the attribute byte pair in binary STL for a per-triangle colour, but they are not part of the format and support is inconsistent. For a coloured print, 3MF is the format to use instead, since it carries colour and is read by current slicers.
Not necessarily. The conversion preserves the geometry exactly as it was, including any problems it already had. A mesh that is not watertight, has flipped normals or has non-manifold edges will carry all of that into the STL, and the slicer will report it there rather than here.
There is no server-side limit because there is no server involved. The practical ceiling is your device memory, since the model is held in RAM while it is converted. Files of a few hundred megabytes are usually fine on a desktop machine and may fail on a phone.