Run one broad mesh check to see which supported findings exist before you edit the STL. The report separates boundaries, over-shared edges, exact duplicates, degenerate faces and winding findings; a clean result is not a complete slicer or print test.
Choose a known 20-unit control
Download first; downloading does not submit your model. STL declares no physical unit, so interpret these coordinates as millimetres only when you choose that assumption.
| Control | Actual report meaning |
|---|
| Closed cube | 12 triangles, zero listed edge or face issues. Baseline only, not print approval. |
| Missing-face cube | 10 triangles and four boundary edges; the known square face is absent. |
| Duplicate-face cube | 13 triangles, one exact duplicate and three over-shared edges. |
| Malformed file | Parsing fails. It must not be read as a clean zero-finding report. |
Want to inspect the model first?
Open in STL Viewer to rotate and inspect your STL locally before running a quality check.
Turn a finding into one next action
The server compares exact stored coordinates and excludes degenerate triangles from edge counts. Its report components join through shared vertices; local STL Repair part selection uses shared edges. A clean report means only that supported checks found no listed blockers. Volume is unavailable for open or inconsistent reports; even a reported closed-mesh value cannot establish that untested spatial crossings or cavity intent are correct. If two closed surfaces overlap despite a clean edge count, compare them with the crossing-surface guide before changing the source model.