Loading converter…
Updated August 2026
Print mesh in. glTF JSON out.
Same as STL to GLB with a JSON pack. Prefer GLB unless a tool names .gltf. There is still no color in the source.
Source STL, target glTF, drop, download JSON.
1
Source is STL. The File API reads it in this tab. Nothing is posted. Keep it under 80 MB.
2
glTF JSON wraps the STL mesh.
3
Pack to GLB if you need a single attachment.
This page is only STL → glTF. Other pairs have their own keep and lose notes so they do not repeat this conversion.
| On this conversion | What happens |
|---|---|
| Keeps | Triangles in a glTF scene. |
| Drops | Nothing STL had beyond triangles. |
| Next step | Pack to GLB for sharing. Keep STL for slicing. |
| Attribute | Result on the reference scene |
|---|---|
| Separate objects | Kept as 2 |
| UV coordinates | Kept |
| Vertex colour | Kept |
| Material names | Kept |
| Vertices on the reference scene | 48 of 48 |
| Mesh | Source | glTF | Change | Vertices written |
|---|---|---|---|---|
| mug.glb | 880 KB | 1,564 KB | 1.8x | 25,000 |
| lion.glb | 8,768 KB | 15,587 KB | 1.8x | 249,369 |
STL as the source: Default material on export. Source has no PBR to keep. Measured 2026-08-27 by running this converter’s own loaders and exporters headlessly. How every format was measured.
STL is parsed with the File API. glTF is written in memory. Nothing STL had beyond triangles. That is a format rule, not an upload. Files over 80 MB are refused because RAM is the limit.
Same as STL to GLB with a JSON pack. Prefer GLB unless a tool names .gltf. There is still no color in the source.
Source STL, target glTF, drop, download JSON. No Blender and no account.
GLB for one file. glTF JSON only if the next tool requires it.
No. STL never stored it.
No. STL is parsed here and glTF is written in memory. There is no convert API.
Yes. Open the STL viewer if you only need to orbit. Convert when the next tool actually wants glTF.
Pack to GLB for sharing. Keep STL for slicing.