GLB → STL · FREE · NO UPLOAD
GLB to STL Converter — Print AI-Generated & Web Models
Turn a .glb (binary glTF) into a printable .stl right here in the browser. Works with exports from Meshy, Tripo, Luma, Blender and game engines. No upload — your model stays on your device.
From Meshy or Tripo to your slicer, step by step
You generated a model in an AI tool and now you want it on the printer. The formats do not match: Meshy and Tripo hand you a GLB, while Bambu Studio and PrusaSlicer want a plain triangle mesh. This page is the hop in the middle. The sequence below is the one that actually works, including the scale check that most first-time prints miss.
- Generate the model in Meshy or Tripo. When you are happy with the result, use the Download control. In current versions that button offers format choices, and GLB is one of them. Choose GLB. That is the binary glTF file this converter accepts.
- Drop the file on the drop zone above. Nothing is uploaded; the mesh is parsed in this tab. Wait for the preview to appear so you can confirm you have the right object and that the whole figure showed up, not a fragment of a multi-mesh scene.
- Check scale against the bounds readout under the preview. glTF's spec unit is meters. Slicers assume STL numbers are millimeters. A 50 mm figurine authored as 0.05 meters will show bounds around 0.05 in this viewer and will import into the slicer as 0.05 mm — a speck — unless you scale it by 1000 on the plate. If the bounds already read in the tens or hundreds of units, the generator likely wrote millimeter-scale numbers and you can leave the size alone. Trust the numbers on this page, not a guess.
- Download the STL and open it in Bambu Studio or PrusaSlicer. Treat it like any other mesh you would drop onto a plate: orient it, add supports if the overhangs need them, and slice.
- AI meshes are often not watertight. If the slicer reports holes, non-manifold edges, or a failed slice, run its built-in repair on import. You can also check the file first on the STL repair page on this site, which reports open edges without sending the mesh anywhere.
That is the whole pipeline: generate, download GLB, convert here, download STL, open in the slicer. The only extra step that is worth doing every time is reading the bounds so the first print is the size you meant. If you later save a Bambu Studio project, that save is a .3mf; getting a plain mesh back out of it is a different conversion. For this inbound trip, GLB in and STL out is all you need.
From AI generator to 3D printer
AI 3D generators — Meshy, Tripo, Luma, Rodin and the rest — output GLB, the format of the web. Slicers — PrusaSlicer, Cura, Bambu Studio, Orca — want a plain triangle mesh, and their common language is STL. This page is the bridge:
- Export or download your model as GLB from the generator.
- Drop it above — the preview shows exactly what will be exported, with triangle count and size.
- Click Download STL and open the file in your slicer.
- If the size looks off by 1000×, scale in the slicer — glTF counts meters, slicers assume millimeters (details in the FAQ).
Going the other way for AR or web embeds? Use the STL to GLB converter. Have a 3MF project instead? That's the 3MF to STL page.
What survives the conversion
| In the GLB | In the exported STL |
|---|---|
| Triangle geometry (all meshes) | Kept exactly, world transforms applied |
| Scene hierarchy & node transforms | Baked into the triangles |
| Colors, materials, PBR textures | Dropped — STL cannot store them |
| Animations, cameras, lights | Dropped — meaningless for printing |
| Units (meters in glTF) | Numbers copied as-is; slicers read them as mm |
FAQ
Is my GLB file uploaded anywhere?+
No. The converter parses the GLB with the three.js glTF loader inside this tab and re-encodes the triangles as binary STL, also locally. There is no upload endpoint. Load the page, disconnect from the internet, and the conversion still works.
Can I print an AI-generated model this way?+
Yes — this is the most common use. Meshy, Tripo, Luma and similar AI generators export GLB, but slicers want STL. Drop the GLB here, download the STL, and open it in your slicer. One caveat: AI-generated meshes are sometimes not watertight; if your slicer reports holes or non-manifold edges, run its built-in repair on import.
What happens to colors, textures and materials?+
They are dropped — not by choice, but because the STL format stores only bare triangles. Geometry survives exactly: every mesh in the GLB scene is transformed to world space and written into one STL. If you need color 3D printing, keep the GLB or use 3MF; STL cannot carry that data.
The STL imports at the wrong size in my slicer. Why?+
glTF's unit is the meter; most slicers assume STL files are millimeters. A 0.05-unit-tall GLB (5 cm) becomes a 0.05 mm STL in that assumption. Check the bounding-box readout under the preview here: if it shows around 0.05 units, scale by 1000 in your slicer (or scale the source model). Many AI generators already export at mm scale, in which case no change is needed.
Does the converter merge multiple meshes?+
A GLB scene can hold many meshes; the exporter writes all of them into a single STL with their positions applied, so what you see in the preview is what prints. It does not perform boolean union — overlapping shells stay overlapping shells, which most slicers handle fine.
GLB vs GLTF — does it matter which one I have?+
GLB is the single-file binary form of glTF; .gltf is the JSON form that references external buffers and textures. This tool accepts .glb and self-contained .gltf files. A .gltf that references separate .bin or texture files can't bring those references along in a browser drop — export as GLB from your tool instead.