3D Mesh Converters
Drop a 3D model, get the format your toolchain wants. STL for printing, OBJ for editing in Blender or Maya, GLB for the web and AR/VR. Everything runs in your browser via three.js.
All 3d converters
Which format should I use?
STL is the 3D-printing default — every slicer (Cura, PrusaSlicer, Bambu) takes it natively. The format is intentionally minimal: a list of triangles with normals, no materials, no colors. OBJ is the Wavefront text format that's been the lingua franca of DCC tools (Blender, Maya, ZBrush, 3ds Max) for thirty years. It carries materials by reference to a .mtl sidecar file. GLB is binary glTF 2.0 — the modern web/AR/VR transport, designed to ship a complete asset (geometry + textures + materials + animation) in a single file. Convert STL→OBJ when you need to edit a print-ready model in Blender; OBJ→GLB when you need to drop a model into a web viewer or three.js scene; STL→GLB when a 3D-printing model needs to live in an AR product configurator.
| Format | Best for | Materials | Animation |
|---|---|---|---|
| STL | 3D printing, slicer input | No | No |
| OBJ | DCC tools (Blender, Maya, ZBrush) | Via .mtl sidecar | No |
| GLB | Web, AR/VR, three.js, model-viewer | Yes (PBR) | Yes |
Frequently asked questions
Are my models uploaded?
No. Conversion runs entirely in your browser via three.js loaders and exporters. Models containing proprietary geometry, scanned medical data, or unreleased product designs stay on your device.
Will materials and textures be preserved?
It depends on the destination. GLB carries materials and textures inline. OBJ output carries colors but textures need a separate .mtl sidecar (we keep colors). STL has no concept of materials, so anything→STL is geometry-only.
Does it support binary STL?
Yes for both reading and writing. The exporter writes binary STL by default — it's about 5x smaller than ASCII STL. The reader auto-detects either variant on input.
What happens with multi-mesh OBJ files?
The whole scene is preserved in OBJ→GLB output. STL flattens multiple meshes into a single triangle list, which is what slicers expect.
What about scaling and units?
We don't rescale — geometry is preserved in whatever units the source file uses. STL has no unit concept (slicers assume mm); OBJ and GLB optionally embed a metric. Dimension-critical workflows (CAD, manufacturing) should verify in the destination tool.
Why is there no GLTF (text) output?
GLB (binary glTF) is what virtually every modern toolchain wants — it's a single file with embedded buffers. Text glTF exists but requires shipping the .gltf, separate .bin buffers, and texture files together. If you specifically need text glTF, decode the GLB with the official glTF tools.