3MF vs STL: Which File Should You Send Your Printer?

STL dates to 1987 and 3D Systems' original stereolithography machines. It was designed to feed one machine one part, and it does that with admirable economy: a list of triangles, each with three vertices and a normal vector nobody trusts. There is no header for units, no colour, no way to say "these forty triangles are a separate object", and no place to record who made the file or what it is.

3MF was published in 2015 by the 3MF Consortium, whose founding members included Microsoft, HP, Autodesk, Dassault Systemes, Netfabb, SLM Solutions and Shapeways alongside the two companies that invented the processes STL was written for, 3D Systems and Stratasys. Structurally it is a ZIP archive containing XML, in the same family as .docx. That gives it room to carry things STL cannot represent at all.

An STL file contains bare numbers with no statement of what they mean. A vertex at x=2.5 might be 2.5 millimetres or 2.5 inches, and the file has no opinion. Every piece of software that opens it applies its own default, and almost all slicers default to millimetres.

So when a CAD package exports in inches, the resulting model arrives 25.4 times too small. The reverse happens too, and a part meant to be 60mm across turns up wanting a 1.5 metre build volume. This is by a wide margin the most common file problem a print service sees, and it costs a round of messages every time.

3MF removes the ambiguity by declaring the unit in the model element itself. That is a genuine improvement, and it is the strongest single argument for the format.

It is not a substitute for saying it out loud, though. Whatever format you send, put one real dimension in your message: "the flange should measure 62mm across". A maker can check that against the file in ten seconds, and it catches scale errors that no format prevents, such as a model that was drawn at the wrong scale in the first place. Our guide on preparing a 3D model for printing covers the rest of the pre-flight checks.

Binary STL has a fixed cost per triangle, which makes its size entirely predictable: an 84-byte header plus 50 bytes for every triangle. No compression, no vertex sharing, so each vertex is written out once for every triangle that touches it, typically six times over.

3MF avoids both wastes. It writes each vertex once and refers to it by index, then deflates the whole XML inside the ZIP container. To put a real number on it, we wrote the same 502,600-triangle sphere mesh out to all three formats and measured the results.

Two caveats on that ratio. It varies with mesh complexity, and a model that is mostly large flat faces compresses better than a dense organic scan. The ASCII figure varies too, because it depends on how many digits the exporter writes per coordinate; ours averaged 254 bytes per facet against binary's fixed 50. And ASCII STL, the worst of the three, is still what some older CAD tools export by default. If your STL is unexpectedly enormous, open it in a text editor. If you can read words in it, re-export as binary and cut it by about 80 percent for free.

This catches people constantly. When you hit save in PrusaSlicer, OrcaSlicer or Bambu Studio, you get a .3mf. When you export a model from Fusion or Onshape, you also get a .3mf. They are not the same thing, and the extension does not tell you which is which.

A slicer project file is a 3MF with vendor extensions embedded: a specific printer profile, a specific nozzle size, filament selections, manual support placement, paint-on settings and modifier meshes. Handed to a maker running a different machine, all of that is either wrong or has to be stripped. Some slicers will import it and silently apply your printer profile to their printer, which is the worst outcome available.

There is a good use for one. If you have already tuned a print on the same model of machine the maker runs, sending the project saves them real work. Otherwise send a plain model export and describe what you want in words. Either way, say in your message which of the two you attached.

Both STL and 3MF are mesh formats. They describe a surface approximated by flat triangles, and in doing so they throw away the design that produced it. A 20mm hole becomes a polygon with some number of sides, and nobody downstream can tell whether you meant 20mm or 19.8mm.

STEP files (.step or .stp) store exact boundary representation geometry: real cylinders, real planes, real fillets. That matters when a part has to fit something. If your bore comes out 0.3mm tight for a bearing, a maker with a STEP file can adjust the feature and re-export. With only a mesh, they either scale the whole part, which breaks every other dimension, or remodel it and charge you for the time.

The practical rule: decorative and artistic models go as 3MF or STL, and functional engineered parts go as STEP plus a mesh as a fallback. If your CAD tool can export STEP, include it. It costs nothing and occasionally saves the entire job.

If you are working from files you did not create and have no CAD source at all, our guide on what to do with STL files when you have no printer covers the options.