Need size, fit, wall and volume guidance in one browser-local report? Run 3MF Print Preflight.
What the report means
Only supported resolved build geometry is analysed. Unplaced resources, unsupported required semantics and missing results cannot be treated as zero issues. Review intended parts and placements locally, or trace a missing item before mesh cleanup.
| Finding | Interpretation | Next action |
|---|---|---|
| Could not analyse this 3MF file | No completed mesh result. A corrupt archive, unresolved reference or unsupported package feature can prevent analysis. | Open the original in its producing application; re-export a supported mesh package. A failed check is not zero findings. |
| Open edge | An exposed boundary was found in a placed mesh. It can be a missing surface or an intended sheet. | Inspect the boundary against the source design before closing it. |
| Non-manifold edge | More than two faces share an edge. Repeated faces can cause this too. | Review duplicate findings and the affected region; distinguish redundant faces from intersecting solids. |
| Duplicate or degenerate triangle | A repeated face or face with no useful area was found. | Use supported 3MF cleanup only for an understood change, then recheck the saved package. |
| Inconsistent orientation | Neighbouring triangle winding disagrees. This is different from a display normal or an intentionally inward cavity wall. | Inspect the source surfaces and the reported location before changing winding. |
| No mesh problems found | The completed supported checks returned no listed findings. | Continue with size, wall, placement and sliced-layer review. Self-intersections, strength and print success remain unchecked. |
One mesh resource can produce two placed parts
These owned packages were run through the local server processor on 24 October 2026. Both declare millimetres. The repeated build places the same cube again at X + 40; it contains one stored mesh resource, two placed items and 24 analysed triangles. Separate build items are checked independently, so repeating a legitimate object is not itself a duplicate-triangle error.
| Exact input | Observed output | Retained report |
|---|---|---|
| One placed cube | 1 resource, 1 item, 12 triangles, 20 x 20 x 20 mm, no listed mesh findings. | JSON report |
| Two placed cubes | 1 resource, 2 items, 24 triangles, 60 x 20 x 20 mm, no listed mesh findings. | JSON report |
| Cube with a repeated face | 13 triangles, 1 duplicate triangle and 3 non-manifold edges. These findings describe the same redundant face from different checks. | JSON report |
The reports are reproducible software observations, not physical print tests or evidence that the deployed server is running this revision. Inputs, hashes and reproduction details. For size, nominal fit and sampled wall checks, use browser-local 3MF Print Preflight.
Questions about this check
Does this validate my slicer settings?
No. It checks supported mesh geometry, not embedded printer profiles, toolpaths, materials or every 3MF extension. Reopen the original project in its native slicer for those settings.
Which geometry did this report analyse?
Supported placed build items, including their resolved component and build transforms. Unplaced resources are not additional printed objects. Separate placements retain independent topology analysis on the server; browser-local combined-build checks can interpret coincident geometry differently.
What happens to units and placed items?
The report retains the declared source unit, or the format's millimetre default, and measures resolved placements in that unit. It does not rewrite the package. The local converter instead writes physical millimetre coordinates into its STL derivative, which has no unit declaration.
Why can volume be unavailable when the mesh check completes?
The server publishes volume only when its validity and single-component screen passes. Two separate valid cubes can therefore have unavailable volume without being invalid build items. Do not read an unavailable value as zero material.
Where is my file processed?
Submitting this checker uploads the selected file for server processing. Viewing a file locally or running local preflight is a separate action. Read the processing methods before choosing a workflow for confidential designs.