STL repair guide
Fix a Non-Manifold STL: Choose the Right Repair
Substantially updated 2026-10-15. First published 2026-09-05.
A non-manifold warning describes a mesh relationship, not one universal repair. First determine whether the finding is an open boundary, an edge shared by too many triangles, a point-only contact or crossing surfaces. Keep the original file. Make one edit that matches the intended design, then recheck the saved copy and its sliced layers.
Identify the finding before editing
The server quality report compares the exact stored vertex coordinates. It counts triangles around each edge and connects report components through shared vertices. The local STL Repair part selector uses complete shared edges instead. Neither method performs a spatial intersection test. CGAL's mesh-processing reference likewise separates topological checks from self-intersection tests.
| Control and finding | What it supports | Design question and narrow action | Stop when |
|---|---|---|---|
| Closed 20-unit cube: 12 faces, no open or over-shared edges | Edge baseline | Is the outside correct? Compare source and slice. | The shape differs from the design. |
| Open-face cube: 10 faces, four boundary edges | A missing square in this known control | Was this face intended? Restore its known two triangles in a copy. | The missing surface cannot be reconstructed confidently. |
| Duplicate-face cube: 13 faces, one exact repeat and three over-shared edges | Extra incidence from the repeated triangle | Is one copy redundant? Use reviewed standard cleanup. | The coincident face belongs to a different intended body. |
| Separate cubes: 24 faces, two reported components, no edge defect | Two vertex-disconnected surfaces | Are these two intended parts? Keep or export them separately. | A union would erase clearance or assembly meaning. |
| Crossing cubes: 24 faces, two components, no edge defect | No shared-edge warning | Do the volumes really need a union? Inspect in CAD. | Only the designer can choose the resulting solid. |
A zero over-shared-edge count for crossing cubes does not disprove intersection. Vertex-only contact also requires visual or source-CAD inspection: the server's vertex-connected component count can join the touching groups, while local edge-connected selection separates them.
Three worked corrections
- Download the open-face cube and closed reference. The known removed square consists of two triangles. Restoring those exact faces in a deliberate CAD or mesh copy gives 12 faces and zero boundary edges. A generic fill on an unknown opening could instead seal a designed passage.
- Download the 13-face duplicate cube. Standard STL Repair removes the one exact repeated triangle, then writes a 12-face copy with the same 20 × 20 × 20 bounds and no over-shared edges. That action also permits degenerate-face removal and safe local winding corrections, so read the complete repair report.
- Download the crossing cube pair. Each closed cube has 12 triangles; together the report shows 24, zero open and zero over-shared edges. No site intersection detector ran. A Boolean operation or revised source design is needed only if the intended object is a true union.
When a union is unsafe
A point or edge touch is not automatically a usable physical joint. A print-in-place gap and two intentionally separate parts must retain their clearance. A nested surface might be a required cavity wall. A blanket union can erase any of these design features while still yielding apparently clean edge counts.
Use the separate-shell guide to decide which pieces belong; use the crossing-surface guide when edges look clean but volumes overlap.
Verify the exact derivative
Download the edited STL under a new name, reopen those bytes, and compare triangle count, coordinate bounds, open and over-shared edges, winding conflicts, intended openings and the first affected slicer layers. A clean edge count cannot certify vertices, hidden crossings, cavity meaning or print success. If correction requires guessing a load-bearing joint or missing shape, stop and return to source CAD or a reviewed manual edit.
FAQ
Can zero over-shared edges rule out crossing solids?
No. The crossing-cube control has no over-shared edges, and this edge-count report does not run an intersection test.
Should I accept a slicer repair instead of changing the STL?
Only after checking the generated layers against the intended design. A slicer can reinterpret geometry without correcting the source file.