Turn a 3MF model into an STL mesh for slicers and other triangle-based tools. The conversion applies build placements, converts declared units to millimetres and independently compares the saved output with the source.

What the conversion does

A 3MF file is a structured package. It can contain mesh resources, a build section that places those resources, component assemblies and optional colors or materials. Reading only the raw vertex coordinates can lose the position of an object in the build. This converter loads the placed mesh instances, applies their transforms, scales their coordinates to millimetres and writes the resulting triangles to STL.

The input and output are both reopened from disk during quality assurance. The independent checks compare the triangle coordinates as an unordered set, verify overall dimensions and check that each placed mesh instance has a corresponding named STL solid group. The result preview is generated from the saved STL, not from a temporary in-memory mesh.

Unit conversion is explicit

3MF can declare microns, millimetres, centimetres, inches, feet or metres. The converter applies the appropriate scale factor before creating STL geometry, so a model declared in inches is measured in millimetres in the output and result summary. The QA report records the input unit, output unit, object counts and bounding dimensions in millimetres.

A 3MF model may omit the unit attribute. The format specifies millimetres as the default, so the converter applies that default but does not call it a declared unit. The QA result includes a warning that the unit was absent and that the specification default was used. Invalid or unsupported unit values are rejected instead of silently guessed.

Placed objects remain distinct in the STL file

A build can place the same mesh resource more than once or combine separate resources into an assembly. The conversion applies each build and component transform, including translations and rotations, and writes each resulting mesh instance into a separately named solid block in an ASCII STL. This makes the output grouping and object count inspectable and avoids welding one input object into another during writing.

STL has no universally enforced assembly structure. Some downstream applications flatten solid groups into one mesh, and STL cannot carry object names as dependable metadata. The QA report therefore describes the saved output groups it measured; it does not promise that every later application will preserve those labels.

Appearance and other data that STL cannot carry

STL represents triangle surfaces. It has no standard fields for the 3MF model's colors, base materials, textures, texture coordinates, build metadata or declared physical units. Appearance information is omitted from the STL result and a warning is shown in the quality report. Triangle geometry and placed coordinates are checked independently; a successful geometric comparison does not mean that non-geometric data was retained.

If appearance is important, keep the original 3MF as your source and use a 3MF-aware application for printing or visualization. You can also inspect the original in the browser-based 3MF viewer before converting it. For the reverse direction, STL to 3MF creates one millimetre-based geometry object but cannot reconstruct colors or units that were never stored in the STL.

Review the result before paying

Choose a 3MF file, wait for the preview and review the verified triangle count, dimensions, input unit and object counts. The upload has limits for archive size, expanded ZIP contents, file count and triangle count because 3MF is a compressed XML package. Unsafe paths, external component references, unsupported compression methods and malformed XML are rejected before the worker processes geometry.

If the output fails independent verification, checkout is not offered. A passing result can include warnings about omitted appearance data or a missing unit attribute; those warnings describe format limitations, not a silent change to triangle coordinates. Keep the original file until you have opened the STL in the application where you plan to use it.

Frequently asked questions

Are build placements applied before conversion?

Yes. Build and component transforms are applied to each placed mesh instance before STL is written, then the saved triangles and bounds are checked independently.

How does the converter handle units?

Supported declared units are converted to millimetres. If the unit is missing, the 3MF specification default of millimetres is applied and disclosed in QA.

Does STL keep 3MF colors or materials?

No. STL has no standard color, material or texture storage. The result warning reports that 3MF appearance data is omitted.

Are separate objects kept separate?

Placed mesh instances are written as distinct named STL solid groups and their count is checked. Some STL applications may flatten those groups.

What happens if verification fails?

The result is marked as failed and checkout is unavailable. The preview is created only from a saved output that passes the independent checks.