Finding 01 · Check before export
Degenerate faces
Low-risk triangle cleanup candidate.
Safe preview
STL repair
Run a mesh check first, apply safe repairs only where they are supported, and keep complex geometry visible in the repair report.
Diagnostic bench
Use the STL checker to identify duplicate faces, degenerate triangles, normal mismatches, open-boundary hole signals, and non-manifold topology before choosing a repair path.
Check STL before repairFinding 01 · Check before export
Low-risk triangle cleanup candidate.
Safe preview
Finding 02 · Critical review
Requires a stronger geometry engine or manual CAD review.
Report only
Inspection focus
The goal is to reduce failed prints while avoiding unsafe automatic edits.
Repair boundary
V1 repair stays conservative and can later be upgraded with stronger native or agent-backed repair jobs.
Supported
Report only
FAQ
The first phase keeps checking and safe repair preview browser-first and Worker-compatible. Heavy native repair can move to a separate backend only after demand is validated.
Public checking should stay free. Credits should start at private server repair exports, saved reports, larger files, or batch workflows.
No. The report explains mesh health and safe changes, but slicer settings, material, support, orientation, and printer limits still matter.
Related diagnostics
Repair STL files online with a browser-local checker, safe repair preview, and report-only boundaries for open edges and non-manifold geometry.
Find why an STL file fails in a slicer and preview safe fixes for duplicate faces, degenerate triangles, and normal mismatches.
Generate an STL file repair report with issue severity, safe repair actions, before/after deltas, and export boundaries.