Your Slicer Says Non-Manifold — Here's What That Means
Every slicer words it differently, and three of the four major ones can only repair the file if you're on Windows. This page covers what each message means and what to do when the built-in fix isn't available to you.
Drop your STL file here
or
Nothing is uploaded — the repair runs on your own machine.
Find the message you're seeing
The wording differs by slicer, which is why searching the exact phrase often turns up nothing useful.
Bambu Studio
Shows a warning symbol next to the object name in the object list, with a message like "Error 11376 non-manifold edges". Repair is offered by right-clicking the object and choosing Fix Model, or clicking Repair in the warning itself.
That number is not an error code — it's the count. "Error 776 non-manifold edges" means the file has 776 non-manifold edges. Seeing five digits is not a worse kind of error, it just means a denser mesh with more of them. This trips people up constantly, because it looks like a code you could look up.
PrusaSlicer
Reports "Auto-repaired (N errors)" on import, with a triangle-and-exclamation-mark icon next to the model name. Hovering it says right click to fix through Netfabb. Note that auto-repair on import and the Netfabb fix are two different things — the first is a lighter built-in attempt, the second hands the file to Autodesk's service.
Orca Slicer
Reports non-manifold edges and offers a repair prompt, relying on the same Windows repair facility that Bambu Studio uses.
Cura
Talks about the model not being watertight rather than using the word manifold. Cura has no built-in repair at all — you need the Mesh Tools plugin from the marketplace, then right-click the model and use check mesh, fix model normals and fix simple holes.
Why your slicer often can't fix it
Here is the part that catches most people out: PrusaSlicer, Bambu Studio and Orca Slicer do not repair meshes themselves. They hand the file to a repair service that ships with Windows — Autodesk's Netfabb, exposed through Microsoft's 3D model APIs.
That has two consequences. On Windows it can be slow — on a complex model the dialog spins for a long time while it waits for the Windows service, and people regularly assume it has crashed. And on macOS or Linux the option is simply not there. PrusaSlicer's official answer for Mac users is to upload the file to Netfabb's web service manually. Orca users have circulated video workarounds titled, literally, "repair workaround if you don't have Windows."
So if you're on a Mac and the repair button is missing or greyed out, nothing is wrong with your install. The feature was never available to you.
What to do instead
The tool at the top of this page runs the repair in your browser, which means it behaves the same on Windows, macOS and Linux. It closes boundary loops, separates non-manifold edges and pinched vertices, re-orients inverted faces, strips degenerate and duplicate triangles, and resolves self-intersections with a boolean union.
Two differences from the web services your slicer points you at: your file is never uploaded — the engine is compiled to WebAssembly and runs on your own machine — and you get told what was actually changed, rather than just receiving a file back. If it sealed four holes and turned twelve faces around, the report says so.
Check that it actually worked
Re-import the repaired file into your slicer. The warning icon should be gone and the preview should show continuous walls with infill inside them. That is the test that matters — more than any number a repair tool gives you, including ours.
If the warning comes back, the usual cause is that the model has a genuine design problem rather than a mesh defect: zero-thickness walls, or surfaces that were never meant to enclose a volume. No repair tool can turn a surface into a solid it was never modelled as.
Frequently asked questions
What does "Error 11376 non-manifold edges" mean in Bambu Studio?
The number is the count of non-manifold edges found in your model, not an error code to look up. 11,376 means the mesh has that many edges where the topology is ambiguous — usually a dense model with a systematic export problem rather than 11,376 separate mistakes.
Why is "Fix through Netfabb" missing in PrusaSlicer on my Mac?
Because it relies on a repair service that ships with Windows. It is not available on macOS, and nothing is wrong with your installation. Prusa's own guidance for Mac users is to use Netfabb's web service, which requires uploading your file. A browser-based repair tool avoids both problems.
Should I just let the slicer auto-repair it?
If it works, yes — it is the fastest path. The problems are that it is unavailable on macOS and Linux, it can hang for a long time on complex models, and it does not tell you what it changed. If the auto-repair silently alters geometry you care about, you have no record of it.
Cura doesn't mention manifold at all — is that the same problem?
Usually yes. Cura describes it as the model not being watertight, which is the same underlying issue seen from a different angle: the surface does not fully enclose a volume, so the slicer cannot decide what is inside. Cura has no built-in repair; the Mesh Tools plugin adds basic checks and fixes.