Clean OBJ + MTL
Standard Wavefront OBJ format. Optional MTL stub for modeling-tool import.
STL is a print format. OBJ is a modeling format. The trip from one to the other comes up whenever you want to refine a printed mesh in a modeling app. Morph parses the STL — binary or ASCII, doesn't matter — and writes an OBJ ready for the modeling tool. All in your browser tab via three.js. The STL stays where it was. The OBJ saves locally. Free for everything that runs on your device; AI is paid in credits.
Both formats parsed in-tab via three.js STLLoader. Auto-detected on the fly.
Vertices, faces, normals — all carried over to the OBJ. No information loss.
Standard Wavefront OBJ format. Optional MTL stub for modeling-tool import.
The STL stays where it was. The OBJ is a brand-new file. Nothing modified.
Print pipelines emit STL because that's what slicers want. Modeling pipelines want OBJ because OBJ supports texture coords and material assignments. The trip from one to the other is the most-googled hobbyist 3D conversion. Morph runs three.js STLLoader plus an OBJExporter in your tab — fast, format-agnostic, no install required.
Both supported. Auto-detected from the file header. Binary is more common, ASCII is human-readable.
STL has no UVs to carry over. The OBJ output is geometry-only — assign UVs in your modeling tool.
Carried from the STL where present. Otherwise computed per-face.
Both require install. Online tools queue. Morph runs three.js in your browser — no upload, no install.
Memory-bounded by RAM. Million-poly meshes work on most modern machines.
Yes. Everything that runs on your device is free with no cap. AI and server work is paid in credits, about a cent each.