STL file repair report

Turn a broken STL file into a clear repair report.

See what changed, what stayed risky, and what the current repair engine intentionally skipped.

  • Before/after score delta
  • Repair action groups
  • Private export path
Generate repair previewBrowser-local first pass

Diagnostic bench

Upload an STL file for a repair report

The workflow checks the original mesh first, then shows a safe repair preview and the paid export boundary.

Generate repair preview

Finding 01 · Check before export

Degenerate faces

64 → 0

Removed from the preview mesh and listed in the action log.

Safe preview

Finding 02 · Critical review

Non-manifold edges

11

Explained as manual review because automatic repair is risky.

Report only

Inspection focus

Repair reports for accountable workflows

This page focuses on evidence: what was repaired, what was skipped, and what can be exported.

  • Use before/after score and issue deltas to review changes.
  • Keep report-only items visible for customer or internal notes.
  • Create server repair artifacts only after local preview is understood.

Repair boundary

Report-first export boundary

Downloads should only happen after the server verifies ownership, file state, and plan entitlement.

Supported

  • Safe repair preview
  • Server repair artifact creation
  • JSON report export for Pro users

Report only

  • Manual CAD edits
  • Guaranteed customer acceptance
  • Hidden changes without action log

FAQ

Questions before the next print

What is included in an STL repair report?

The report includes score, issue counts, severity, repairability, before/after deltas, and action log entries.

Why show skipped repairs?

Skipped repairs make the boundary honest. They explain geometry that the current engine should not edit automatically.

When do I need a paid export?

Use paid export when you need a private server-created repaired STL or JSON report after reviewing the local preview.