STL repair

Repair common STL file issues without over-promising the result.

Run a mesh check first, apply safe repairs only where they are supported, and keep complex geometry visible in the repair report.

  • Safe repair preview
  • Before/after diagnostics
  • Clear report-only boundary
Check STL before repair浏览器本地初检

诊断台

Start with a repair-readiness check

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 repair

发现 01 · 导出前检查

Degenerate faces

44 → 0

Low-risk triangle cleanup candidate.

安全预览

发现 02 · 严重问题

Self intersections

not checked

Requires a stronger geometry engine or manual CAD review.

仅报告

检查重点

Repair workflow for real print risk

The goal is to reduce failed prints while avoiding unsafe automatic edits.

  • Check mesh health before choosing a repair path.
  • Preview safe repair deltas before download.
  • Keep unsupported geometry visible in the report.

修复边界

What V1 repair should include

V1 repair stays conservative and can later be upgraded with stronger native or agent-backed repair jobs.

支持

  • Degenerate face removal
  • Duplicate triangle cleanup
  • Normal recalculation preview

仅报告

  • Guaranteed watertight repair
  • Complex self-intersection repair
  • Wall thickness or slicer simulation

常见问题

下次打印前需要了解的问题

Where does STL repair run?

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.

When should credits be deducted?

Public checking should stay free. Credits should start at private server repair exports, saved reports, larger files, or batch workflows.

Is the repaired STL guaranteed print-ready?

No. The report explains mesh health and safe changes, but slicer settings, material, support, orientation, and printer limits still matter.