3MF file guide
Does 3MF Keep Colours, Materials and Print Settings?
Substantially updated 2026-10-27. First published 2026-09-15.
A property can be present in a 3MF package, recognised by an application and still be interpreted differently at the receiving step. Record what the handoff requires and what was actually observed. A grey geometry preview is not a complete audit of the source's appearance data.
One property-portability matrix
| Required information | Possible representation | What InspectMesh establishes | What the receiver must verify |
|---|---|---|---|
| Geometry and units | Core meshes, components and declared unit | Supported local resolved surfaces, physical bounds and unit interpretation | Named dimensions and actual imported geometry |
| Build identity and placement | Resource definitions and build-item transforms | Supported top-level identities before flattening; selected/all-build bounds | Expected inventory, coordinate location and any recentering |
| Display appearance | Core base-material display colour or defined property/texture extensions | Geometry preview is not a complete property audit; appearance preservation untested | Required face assignments, texture paths/orientation and visual interpretation |
| Requested manufactured material/colour | Supported property data plus agreed process mapping | Does not validate physical material or machine mapping | Actual material/tool assignments and process requirements |
| Preparation state | Application-specific settings, profiles and plate/support data | Does not certify slicer project or printer profile | Exact application/version import and suitability of each required setting |
Core base-material entries can include display colour; appearance is not all one universal extension. A rendering colour also does not promise the manufactured part's colour or formulation. Optional unsupported properties, required unsupported semantics and vendor-private project state need different treatment. A successful geometry load cannot produce a global compatibility score.
Record one real path, leave unknown properties unknown
The two-placed-cubes control tests core geometry and placement. The 27 October 2026 local resolver → scoped STL writer → reopened STL check retains the second placement at X=40..60 mm and all-build X=0..60 mm. It verifies intended triangles under the converter's Float32 basis, as recorded in the filled evidence record.
| Requirement | Reference / observation | Remaining check |
|---|---|---|
| Second placement geometry | 12 triangles; X=40..60 mm; local saved-byte verification passed | External receiver import options remain untested |
| Original build identity | Two placements reference one resource in 3MF | STL derivative has no editable resource/build records |
| Appearance | No appearance preservation observation from this geometry-only path | Untested; use a representative property-bearing package |
| Printer profile / project state | Not tested by the internal derivative check | Review in the exact producing/receiving slicer |
One receiving verification procedure
Use 3MF Viewer for supported local geometry and placement references, then inspect required appearance and project properties in the actual receiving application.
- Keep the original project and name required properties and revision before export.
- Record producing/receiving application versions and exact operations. Reopen the export in the producer when the workflow requires it.
- Import into the receiver and compare named geometry references, placement, appearance and required assignments.
- For each property record preserved, changed, missing or untested with evidence and import options. A missing entry remains unanswered.
- Resolve unmapped project settings in the receiving slicer and inspect final layers for the intended printer/material. Repeat a representative interoperability check after relevant application changes.
Use the shared receiving-file record instead of creating another property form. The consortium compatibility matrix supplies reported application-support context, not an observed test of your file or versions.
Retain the original when distributing a derivative
A geometry export can bake resolved placement into STL vertex coordinates. STL lacks separate build transforms, resource identity, declared units, standard colours/materials and preparation settings. The receiver can then move or rescale it; record that operation. A millimetre convention must accompany InspectMesh's STL download.
Choose combined or individual placed geometry when only those surfaces are required. Keep the original project for future changes. A basic STL-to-3MF package cannot create missing colours, materials, supports or profiles. The format comparison owns the representation choice; this page owns verification of the required properties.
Reviewed 27 October 2026 against the 3MF Core Specification 1.4.0 and specification suite. No external appearance, project or physical test is claimed for the cube control.
FAQ
Does every 3MF preserve slicer settings?
No. Project settings can be application-specific, ignored or mapped differently. Verify the exact receiver and intended printer/material.
Does an STL export keep placement?
Its vertex coordinates can retain resolved locations, but separate build transforms, resource identities and units are absent. STL is not a project backup.
Does a grey preview prove colour data is missing?
No. A geometry preview is not a full audit of source properties. Inspect the required appearance in a supporting receiving application.