A 3MF can carry more information than an STL, but its extension does not prove that the information is present. STL principally describes a surface with triangles and does not declare a standard measurement unit. A 3MF can also record units, several objects, build placement and properties such as colour or material assignments. These are capabilities, not guarantees about your file.
Choose the format by checking the actual export and the information the recipient needs. Keep production agreements separately. This guide is not an upload or conversion service and does not demonstrate a physical print.
Download the English project worksheet. Open it as UTF-8 CSV, replace the guide context with your project inputs and record observations separately from acceptance decisions. Blank cells do not indicate a passed check.
Start with the recipient's decision
For a simple single-colour part, geometry, units and final size may be enough to begin an assessment. An assembly may also require object count, relative positions and colour assignments. Record final dimensions in millimetres, separate parts, fixed positions, functional versus preferred colours, visible faces and fits that must not change.
Without those requirements, a technically rich file can still be checked against the wrong criteria. A format does not replace a brief.
What an STL actually contains
STL approximates the surface with triangular facets. Ordinary STL does not provide standard units, colour, texture or material structure. Separate parts can be supplied as individual files or disconnected shells, but names and accompanying instructions must explain their relationship. Original sketches, parameters and CAD history are absent too.
Always check the STL's dimensions and object count. Renaming it to 3MF cannot recreate information. If you need STL from an existing 3MF, use the conversion and dimension checks. If you need editable design features, STL-to-STEP conversion has a different limitation.
What a 3MF can carry
The core package includes triangular mesh geometry and can declare units. It can define several objects and build instances with transformations. Properties and extensions can describe colours, materials and other production information. Software may write or read only some of those fields.
A 3MF does not automatically prove that it contains colour per face, validated material choices, a complete slicer profile, machine settings, a reproducible cross-software production project or original CAD features. Inspect the export in the receiving environment. Treat required but unsupported properties as a transfer failure.
| Information | STL | 3MF | Confirm separately |
|---|---|---|---|
| Triangle geometry | Yes | Yes | Intended, closed mesh |
| Explicit unit | Not standardised | Can be recorded | Final size in millimetres |
| Multiple parts | Files or shells | Objects and instances | Count and purpose |
| Relative placement | No complete project structure | Build transformations possible | Intended fixed positions |
| Colour/material assignments | Not ordinary STL properties | Properties/extensions possible | Recipient reads them correctly |
| Slicer or machine settings | No | Sometimes project-specific | Actual production agreement |
| Design history | No | Not automatic | Original CAD source |
Choose only the context you can verify
Use 3MF when its extra context matters and both parties can verify it. Use STL when a checked mesh is sufficient and you supply size and other requirements separately. Neither choice is production approval.
Worked planning example: a holder and two inserts
This fictional desktop exercise has one holder and two different inserts, with a total intended envelope of 120 × 65 × 30 mm. The holder is dark; the inserts use another colour. Their positions identify left and right. It is not a customer project or a print test.
Three STL files can provide the shapes, but need explicit units, dimensions, left/right names and colours. “Part1” and “part2” are inadequate for different inserts. A carefully prepared 3MF can keep the unit, three objects, placement and assignments together. The recipient must still see exactly three objects, the same envelope and the required colours. If their software ignores an assignment, the transfer is unproven.
Check export and reimport in order
Keep the original, export a new revision and reopen that exact exported file rather than trusting the design window. Count objects or shells; measure overall dimensions; confirm units; inspect transformations; check required colour and material assignments; record any settings that are only external agreements. Save the application and version where interpretations may differ.
Use a record with columns for required value, exported value, recipient's observation and decision. Write “unknown” explicitly. A blank cell is easily mistaken for “not applicable”. Stop for missing objects, unexpected merging, changed positions, uncertain units or required properties that the recipient cannot read. Request a new export or confirmed source information.
Send geometry and context together
With the checked revision, request a printing assessment. Include units, three dimensions, object count, software used for reimport and any unresolved requirements. For the holder example, identify each insert and its colour separately: a stored colour does not confirm available material or colour stock.
If you need the holder delivered complete, also specify who fits the inserts. Print & Assembly distinguishes loose prints, additional components and the delivered assembled state. Digital checks do not prove physical fit, strength, colour or finish; agree those acceptance checks before production.