Transform & optimize/Optimize
Split mesh into parts (local)
Split a mesh into edge-connected parts and download them as separate binary STL files in one ZIP. The Worker accepts STL, OBJ, PLY, 3MF, GLB, or self-contained glTF and never uploads the model.
Split mesh
No uploadSplit mesh
Components are connected through shared edges; islands that only touch at a vertex become separate parts. The ZIP contains stored binary STL files named part-001, part-002, ….
Drop a mesh to split
STL, OBJ, PLY, 3MF, GLB, or a self-contained glTF. Edge-connected components are written as separate STL files in a ZIP.
Drop a mesh to split
STL, OBJ, PLY, 3MF, GLB, or a self-contained glTF. Edge-connected components are written as separate STL files in a ZIP.
Choose a fileMax file size: 500 MB · No upload
No upload · File.slice() / ArrayBuffer → Worker → parts ZIP.
How it works
- 1
Drop a mesh file in any supported format.
- 2
The Worker parses the mesh, welds unindexed sources if needed, and groups triangles that share edges.
- 3
Each component is written as a separate part-NNN.stl inside a ZIP.
- 4
Download the parts ZIP locally. No upload is performed.
What the numbers mean
Components are connected through shared edges. Two surfaces that only touch at a vertex, or do not touch at all, become separate parts. Non-manifold connections remain in one component.
The ZIP contains stored binary STL files named part-001.stl, part-002.stl, and so on. Each part keeps its original coordinates; no recentering or scaling is applied.
Printing notes
- Use separate parts when the slicer needs distinct objects; run manifold-check on each part if needed.
- Parts may overlap in the original coordinate space; arrange them before printing.
- Keep the original source until the split ZIP is verified.
Questions
References
- · ISO/ASTM 52900
- · Mesh connectivity and connected components