Mesh repair diagnostics

A mesh repair workflow built around inspection first.

The safest repair starts with topology diagnostics: count the issues, explain their print risk, and only apply supported edits.

  • Topology-first report
  • Watertightness signals
  • Repairability labels
Check mesh healthBrowser-local first pass

Diagnostic bench

Check mesh topology before slicing

Inspect open boundaries, non-manifold edges, duplicate faces, degenerate triangles, and normal mismatches in one STL workflow.

Check mesh health

Finding 01 · Critical review

Open boundary edges

26

Possible hole or shell gap; detection only in the current engine.

Report only

Finding 02 · Check before export

Inverted normals

19

Normal recalculation can be previewed safely.

Safe preview

Inspection focus

Mesh diagnostics before repair

The mesh page focuses on issue families that decide whether an STL is safe to repair automatically.

  • Detect open boundaries and non-manifold topology.
  • Separate normals and duplicate faces from serious topology risk.
  • Use the report to pick browser, Worker, or future backend processing.

Repair boundary

Mesh repair boundary

Not every mesh problem should be fixed by a V1 web tool. The report keeps high-risk geometry explicit.

Supported

  • Duplicate face cleanup
  • Degenerate triangle cleanup
  • Normal direction preview

Report only

  • Non-manifold reconstruction
  • Boolean/self-intersection repair
  • Slicer-specific printability guarantee

FAQ

Questions before the next print

What makes a mesh non-watertight?

Open boundary edges, shell gaps, and non-manifold topology can make a mesh non-watertight and risky for slicing.

Can mesh repair stay on Cloudflare Workers?

Lightweight TypeScript diagnostics and safe cleanup can stay browser/Worker compatible. Heavy geometry reconstruction should wait for validated demand.

What should be paid?

Charge for private repair exports, larger files, saved reports, and batch processing rather than the first diagnostic check.