mesh in · print-ready stl

OBJ to STL OBJ in. STL out.

Your slicer takes STL. Your model came out of a modeling app or some marketplace as OBJ. Spinning up a full 3D app just for the export is overkill. Morph parses the OBJ — vertices, normals, faces — and writes a binary STL ready for the slicer. All in your browser tab via three.js geometry parsers. The OBJ stays where it was. The STL saves locally. Free for everything that runs on your device; AI is paid in credits.

Drop a file here
OBJ → STL
Choose a file
Reads and writes inside this tab. Nothing is sent anywhere.

What it actually does

01
PARSE

OBJ tokenized

Vertices, normals, texture coords, faces — all walked in-tab via three.js OBJLoader.

02
MESH

Geometry rebuilt

BufferGeometry constructed in browser memory. Normals computed where missing. Faces triangulated.

03
WRITE

Binary STL out

Compact binary STL — what every slicer expects. Or ASCII STL if you need to diff it.

04
KEEP

Original untouched

The OBJ stays where it was. The STL is a brand-new file. Nothing modified, nothing logged.

How it works

  1. Open morph.cool — browser only.
  2. Drop the .obj file (and the .mtl if you have it).
  3. Pick STL as the output. Choose binary or ASCII.
  4. The .stl downloads, ready for the slicer.
  5. The OBJ stays where it was. Nothing uploaded.
0Upload
∞Batch limit
1-clickExport

Why people leave the upload-and-queue tools

Three-D printing pipelines fragmented into a dozen file formats — STL won the slicer war, OBJ won the modeling-marketplace war, and the two camps still don't talk to each other cleanly. Spinning up a full 3D app just to export is overkill for a five-second job. Morph runs three.js geometry parsers in your tab — fast enough for million-poly meshes, no install, no upload.

Frequently asked

How is this different from desktop 3D apps or online tools?

Desktop 3D apps require install. Online tools queue. Morph runs three.js parsers in your browser — drag, drop, download.

Binary STL or ASCII?

Both. Binary (default) is compact, every slicer reads it. ASCII is human-readable for debugging.

OBJ with .mtl materials?

Materials don't survive — STL has no material concept. Geometry only.

Texture coordinates?

Stripped — STL is geometry-only. If you need textures, see GLTF/glb.

Big meshes — million polygons?

Works. Memory bounded by your RAM, not by an arbitrary cap.

Is there a free tier?

Yes. Everything that runs on your device is free with no cap. AI and server work is paid in credits, about a cent each.

Convert OBJ → STL
Convert OBJ → STL
Nothing leaves your device · Free for what you make, credits for what we run