Degenerate Triangles and Duplicate Faces in STL Files

Can STLFixer fix this?

  • Try it for exact duplicate faces or triangles with repeated vertex positions. The automatic cleanup can remove those redundant elements. Distinct collinear triangles can remain and block output; partial overlaps are not geometrically joined.
  • Keep thin walls and intended detail. A lower triangle count does not prove that the right surface remains. Use a mesh editor when you need to choose which face to remove or restore a damaged boundary.
  • Start with Upload STL. Inspect the diagnosis, review the small-hole option and select Repair STL. Compare Before and After, then verify the downloaded file's dimensions, thin features and layer preview in your slicer.

What the slicer reports

Degenerate triangles and duplicate faces belong in the same investigation, but they are different findings. A duplicate can repeat a valid triangle with nonzero area; a degenerate triangle has collinear vertex positions and no area.

At stlfixer.io, the diagnostic separates these categories: collinearity identifies degeneracy, while identical coordinate-based vertex sets identify duplicates regardless of winding. Partial overlap is not the same test as an exact duplicate.

Keep the label with its count. A list of degenerate faces does not describe how edges connect, and a list of duplicates does not measure how much visible shape is missing. The product reports non-manifold edges and vertices separately from these face findings.

Ask what the diagnostic actually tested before deciding that a smaller number means a better model. Record the affected region, preserve the original file, and check whether the candidate cleanup changes a surface you intended to keep. Treat the warning as a starting point for inspection, with acceptance based on the resulting shape and slice.

How to confirm it's a real defect

Why can a file with degenerate faces sometimes continue through a slicing workflow? Bambu Studio's source has an STL import repair path, enabled by its repair parameter, that invokes an exact facet check before proceeding.

That check removes triangles containing repeated vertex positions and updates connectivity; it does not establish removal of every triangle whose distinct vertices happen to be collinear.

The workflow can therefore continue after removing that kind of defect. A large incoming count alone does not tell you whether cleanup leaves a usable boundary. Check the resulting layer paths; continuing through import does not guarantee a successful print.

Geometry and connectivity need independent checks. CGAL's combinatorial manifold definition does not exclude degenerate geometry or self-intersections, so passing that definition alone cannot clear those findings.

Conversely, do not assume degenerates and duplicates can never accompany a topology problem. Inspect the affected surface and its connections rather than assigning safety from the category name.

For a manual inspection, Blender 4.0's 3D Print Toolbox separates Degenerate, Intersections, and Solid checks; clicking a result in Edit Mode selects the affected elements.

Compare that selection with the original design. Inspect a section through nearby walls and passages, then review the intended slice. A face count alone cannot answer whether the remaining surface still bounds the intended material.

What causes it

Trace the operation history before assigning a cause. A defect in the exported file may have arisen during modeling, simplification, numerical processing, or later import.

Decimation and contraction

In Simplifying Triangle Meshes in the Wild, vertex-pair contraction can create degenerate or duplicate intermediate elements; the described algorithm removes them during processing. Contraction supplies a mechanism, not proof that every decimated STL retains those elements.

Overlapping modeling geometry

Blender documents duplicate geometry when Solidify produces zero final vertex thickness. Cancelling movement after Blender's Extrude also leaves newly created faces in place. Inspect overlapping regions, but reserve “duplicate” for the actual repeated vertex cycle; partial overlap is a different finding.

Precision and the processing stage

CGAL documents that rounding exact intersection coordinates to floating-point values can introduce degenerate faces and new intersections. That establishes finite-precision risk without identifying an STL serialization fault.

In a PrusaSlicer 2.3.0 report, holes disappeared after slicing; the linked corrective commit addresses near-degenerate faces becoming degenerate after translation or rotation and rebuilds connectivity after removal. The identified failure stage was a mesh transformation. Keep the exported file unchanged while testing a different import or placement, so the comparison isolates that stage. Compare source, exported mesh, and imported result before blaming an export precision setting: the stage where a warning appears need not be where the geometry first collapsed.

When you should leave it alone

Keep the original when the proposed “repair” reduces wanted geometry instead of removing a confirmed redundant element. A smaller file does not demonstrate a more faithful surface. In the original building-mesh simplification study, thin double-sheet structures collapsed into a plane and a ground channel became a step. This is an external model experiment showing possible loss of structure, not a failure of this browser tool or proof that every simplifier removes thin walls.

Leave a thin structure unchanged if its separation, thickness, or contour belongs to the design and the candidate no longer preserves it. Check a section through that feature and compare its slice before accepting a reduction. Do not choose a triangle target as a substitute for deciding which surfaces must survive.

Recovery depends on what you retain. PrusaSlicer permits Undo after applying its Simplify model operation. The Simplifying Triangle Meshes in the Wild research also stores a refinement sequence that can reverse contractions. If only the final simplified mesh remains, with no original, undo history, or refinement data, it cannot uniquely specify the discarded geometry. Keep those recovery paths before reducing detail; “all simplification is irreversible” would miss them.

The current repair path does not decimate. It merges identical points, deletes repeated-point invalid triangles, and reduces exact duplicate faces to a surviving copy even when winding differs. Partial overlaps are not geometrically unioned. Distinct collinear triangles can remain and block output rather than being removed by that cleanup.

Review the retained material boundary after any removal. Neither a smaller file nor cleaner diagnostic counts establish that an intentional thin surface remains represented.

How to fix it

Work on a copy and locate the suspect geometry before applying a cleanup command. Decide whether the selection contains a redundant copy, a collapsed face, or distinct surfaces that should remain separate.

  • In Blender 4.0's 3D Print Toolbox, click a check result in Edit Mode, then use View Selected to focus the affected elements.
  • For confirmed surplus copies, Blender's Mesh > Delete > Only Faces removes selected faces while retaining orphaned edges and vertices.
  • Blender's Mesh > Clean Up > Degenerate Dissolve collapses selected short edges and removes small faces according to its distance threshold.
  • Mesh > Clean Up > Merge by Distance merges nearby selected vertices, so choose its distance with the intended separation in mind.

Do not substitute a broad selection for a diagnosis. Review the changed surface and surrounding openings before accepting the edit, and return to the source model if you cannot identify which copy is surplus.

After deleting a surplus face, inspect the remaining boundary for unintended gaps before choosing a distance-based operation on adjacent vertices.

For an automatic attempt, open this browser-based STL repair tool and inspect the original diagnosis. Exact duplicates can be reduced to a surviving copy, while repeated-point degenerates have a supported cleanup path; distinct collinear triangles may remain and prevent output.

Input is limited to 50 MB and basic processing to 1,000,000 faces; local intersection processing has a separate 100,000-face ceiling and eligibility checks. Cleanup must still pass the final geometry checks. Selecting a file enables preview, while downloading requires a completed repair or verification operation. A failed attempt offers no repaired output.

How to verify the fix

Compare the original and candidate around every region you meant to change. Look at the surrounding wall or passage, not just the place where a diagnostic highlight disappeared. Keep the source model available while checking whether a surface was removed, joined, or left in place as intended.

The product rechecks topology after cleanup and diagnoses the exported bytes again; its removed-face messages describe count differences, not a verified print or proof that every design detail survived.

Reject a candidate that fails the intended shape or slice, even if its counts look cleaner. The final output gates cover closed manifold geometry, winding, intersections, and remaining degenerates or duplicates; they do not establish the model's design intent or wall thickness.

If simplification was involved elsewhere, inspect subtle contours as well as thin structures: the CWF research compares methods that preserve weak shape features differently.

Review the saved file in the slicing workflow you intend to use before committing to a print.

Inspect the original geometry before choosing what to remove. Keep duplicate copies, collapsed faces, and intentional thin structures distinct in your diagnosis, then compare the candidate with the design and intended slice. Preserve the original whenever cleanup leaves a surface's purpose unclear or a smaller file has lost wanted detail.

Repair an STL file