STL Is Watertight but Still Won’t Slice: What to Check Next

Closed does not always mean one valid solid

A boundary check asks whether every surface edge has a neighbor. It does not determine whether faces pass through each other, whether two closed shells overlap, whether an internal wall divides the volume ambiguously, or whether separate parts touch only at a point. Any of those conditions can confuse inside-versus-outside classification.

The slicer may attempt to union, discard, or reinterpret ambiguous regions. Different engines can make different decisions, so a preview that appears acceptable in one application is not proof that the source geometry is sound.

Use a diagnostic order that narrows the cause

1. Confirm dimensions

   Check the bounding box in millimeters and verify that no axis is effectively zero or far outside the expected scale.

2. Inspect shell count

   Identify separate components, internal debris, duplicated shells, and pieces that merely overlap.

3. Check orientation and volume

   Find locally flipped faces, fully inverted shells, and regions where signed volume is inconsistent.

4. Locate intersections

   Inspect self-intersections and coincident surfaces, especially around booleans, mirrored parts, and converted CAD geometry.

5. Check printable thickness

   A mathematically valid wall may be thinner than the active nozzle, line width, or resin process can reproduce.

6. Slice a controlled copy

   Use a new export and default-safe slicer profile so unrelated project settings do not hide the geometry problem.

Match the slice symptom to a likely cause

• Whole model disappears

  Check scale, inverted outer shell, invalid coordinates, and whether the object sits outside the build plate.

• One region disappears

  Look for zero thickness, a local inverted patch, a tiny disconnected shell, or detail below process resolution.

• Unexpected solid fill

  Inspect internal faces, intersecting shells, and openings that a repair or slicer closed.

• Random holes in layers

  Check self-intersections, degenerate triangles, and inconsistent orientation around the affected height.

• Different slicers disagree

  Treat the model as ambiguous and repair the source rather than choosing the most convenient interpretation.

Prove the repaired export is the one you sliced

Save to a new filename, reopen it, and repeat the same checks. Compare dimensions, shell count, boundaries, orientation, and changed regions against the source. Then import that exact file into the production slicer and inspect layers around the original failure.