3MF pre-print workflow
How to Check a 3MF File Before Slicing
Substantially updated 2026-10-25. First published 2026-09-05.
Start with the first stage that fails: opening the package, resolving its intended build, interpreting a mesh finding or generating the expected sliced layers. Each stage needs different evidence. A supported geometry result does not validate every 3MF extension or embedded slicer setting.
| First failing stage | What to establish | Next destination |
|---|---|---|
| Cannot read the package | Whether the original opens in its producing application | Source application; do not start triangle cleanup. |
| Opens, but items are missing or misplaced | Intended resources, build references, supported transforms and units | Missing-object investigation or local 3MF Viewer. |
| Build resolves, mesh findings remain | Which supported finding ran and what region/design decision it describes | Closure check or topology check. |
| A bounded redundant-face change is appropriate | Exact selected removal and resource references affected | Local 3MF Repair. |
| Geometry screens complete, slicing remains unexpected | Required features in actual profile and affected layers | Native slicer/source design. |
Choose a method deliberately
3MF Print Preflight resolves supported geometry locally and provides several preparation screens. The server quality and specialist checks are separate explicit submissions. Compare method, settings and supported scope when their outputs differ. An unsupported or failed check is not zero findings.
Server topology is inspected per supported build item and aggregated; local preflight inspects combined resolved geometry. Neither result certifies every required extension, vendor project setting or intended physical connection. Local 3MF preflight does not run the bounded intersection screen available in STL preflight. Read the method explanation when comparing reports.
Confirm size, build and sampled-check limits
Read the source unit and compare resolved bounds with a known physical dimension. Repeated references, nested components and transforms can change the placed build without changing the stored resource. Use 3MF dimensions for a focused size check. A nominal rectangular fit does not include every brim, support or slicer reservation; scaling a functional part also changes its clearances.
Wall thickness uses bounded samples, so zero thin samples does not prove every region suitable. Use sampled wall inspection for important features and compare the target layer preview. Volume has its own validity gates: it may be unavailable for several closed parts as well as for open, duplicate, degenerate, over-shared or winding-conflicted geometry. Unavailable is not zero. Follow the volume interpretation before estimating material.
Retain a short investigation record
Record the source revision, first failing stage, tool and method, unit/build assumptions, finding and next action. Keep unresolved checks explicit. Use the existing printable preflight record rather than treating a complete mesh report as permission to skip slicer or physical requirements.
Review the final sliced layers
Reopen the saved copy, confirm required placements and inspect affected perimeters, cavities, material assignments and profile settings in the receiving application. Local triangle cleanup does not fill holes or correct winding. When a missing surface or intended join is uncertain, use the repair decision guide and return to the source model. A software check does not settle wall strength, support removal or physical print success.