Can I convert STL back to STEP?

Not with this converter, and the reason is the format rather than a missing feature. STEP to STL is sampling: the exact surfaces are already defined and you are choosing how finely to walk them. STL to STEP is reconstruction: you have a flat list of triangles and would have to guess which surfaces a human originally intended. Many different surfaces fit the same triangles, so there is no correct answer to recover. The tessellator that chose 12 panels around a curve and one that chose 2,142 produce triangles that differ slightly, and both are valid tessellations of the same cone. Nothing in the STL records which one happened.

What do you actually get when you convert STL to STEP?

You get a STEP file, but it is not the one the author opened. A paid reconstruction tool with feature recognition will hand you a STEP where a fillet is now a spline, a round hole is now a spline-bound extrusion, and the feature tree is gone. The triangles themselves survive as a body, because STL records triangle boundaries; what does not survive is any surface that the tessellator chose to approximate. The colour, material, and part names also do not survive, because an STL file has nowhere to store them.

What should I actually do when I have an STL but need a STEP?

Three paths, from shortest to most work. First, accept the STL. It is the format most slicers read, and if the geometry is what you need, the tessellation is all that is required. Second, rebuild in CAD. Draw the part over the STL in your CAD tool, using the triangles as a trace. This is what three forums of engineers settled on as the honest answer when nothing better is available. Third, run a reconstruction tool and expect to do manual cleanup: grouping triangles that belong to the same feature, and re-editing any circular feature that the tool turned into a spline.

Why is STL to STEP not a feature here?

Because the engine this site ships reads STEP and IGES files and writes STL. That is the limit baked into the WebAssembly build: four readers and one writer. It will not take an STL as input, and we would rather say so than pretend. The reverse conversion is a different class of tool, one that interprets meshes and fits surfaces to them, and that is a deliberate decision rather than a checkbox on this page.

STL to STEP is not really converting

The one question the converter cannot answer, with the honest answer from three forums of engineers, the three paths they actually take, and why this page cannot point you to a solution that is not a reconstruction. Every forward-conversion number on this page still comes from npm test; no reverse-conversion number is claimed.

The short answer: STEP to STL and STL to STEP are not two directions of the same operation. The first is sampling: surfaces that already exist are walked into triangles. The second is reconstruction: triangles are present and you would have to guess which surfaces a human author originally intended. Many different surfaces fit the same triangles, so there is no correct answer to recover — only a best fit. What the community actually does with an STL when the STEP is gone falls into three paths, ordered by how much work they cost you.

Accept it. The STL is the format most slicers read, and if the geometry is what you need, the tessellation is all that is required. It is not broken just because it is not a STEP.
Rebuild in CAD. Draw the part over the STL in your CAD tool, using the triangles as a trace. This is the path three forums of engineers landed on when nothing better was available.
Run a reconstruction tool and expect cleanup. A paid tool with feature recognition will group triangles back into bodies, but a circle will become a spline and the feature tree is gone. It produces a working STEP, not the one you lost.

1. Why it is not the reverse

The STEP vs STL page already explains the core asymmetry. A STEP file stores surfaces as exact mathematical definitions — a cylinder is a radius, a height and a position. Converting STEP to STL walks those surfaces and writes down enough flat triangles to approximate each one. Our measured cone takes 286 triangles at Draft, 516 at Normal and 2,142 at Fine. All three tessellations describe the same cone, from the same STEP file, in the same session. Nothing in the STL records which count happened.

That is the gap the reverse conversion falls into. From the STL alone you cannot tell whether the author ran Draft or Fine, and you cannot tell whether the cylinder was drawn as a radius or built from a revolved sketch with a fillet on top. Two different tessellators choosing 12 panels and 2,142 panels produce triangles that differ slightly, and both are perfectly valid representations of the same shape. No rule decides which cylinder the tessellator happened to pick. A reconstruction tool fits surfaces to the triangles it is shown; it is an interpretation, not a recovery.

One definition produces many tessellations; from the tessellations you cannot recover which definition it was. The teal curve on the left is one cylinder, drawn from one radius. The orange panelled line on the right is an approximation of that same curve, but you cannot read back from the panels whether the author ran Draft, Fine, or whether the curve was a cylinder at all. A reconstruction tool fits the best surface it can to the triangles, and that is an interpretation rather than a recovery.

2. What is actually lost, item by item

Every line below is a thing that lives in a STEP file and does not survive into an STL. None of these things are guesses — the summary table on the STEP vs STL page lists the same losses in its row format, and the verification page names the five checks that only need what an STL actually contains.

What STEP stores and STL loses, row by row
Feature tree	Gone. A STEP records that the fillet is applied after the extrusion, that the hole is a linear pattern, and that the part has a name. STL records none of this. A reconstruction tool can group triangles back into bodies, but the history of how they were made is not there to recover.
Circular geometry	Become splines. A paid reconstruction tool with feature recognition will turn a circular edge into a spline curve that follows the triangles closely. It will not know to write a circle, because from the STL alone it cannot prove the curve was intended to be circular.
Units	Gone. An STL record is 50 bytes of coordinates and nothing else, so there is nowhere inside the format to say whether a coordinate of 10 means 10 mm or 10 inches. That is why a wrong reading shows up as a clean factor of 25.4 rather than a vague drift — the unit was never in the STL to begin with.
Colour and material	Gone. The 16-bit attribute field exists in binary STL but has never been standardised, so a converter will not trust it even if it finds something there.
Part names	Gone. A STEP file names each assembly and each solid. An STL does not.

3. What the community actually does: three paths

Three forums of engineers landed on the same three paths when asked what to do with an STL they needed as a STEP. The paths are not opinions: they are the answer people actually gave, ordered from shortest to most work.

Path 1 — accept it. The STL is the format most slicers read. If what you need is a printable part, a display mesh or an exchange format that your downstream tool already takes, the tessellation is all that is required. It is not broken because it is not a STEP. This is the path the 2-vote comment on the FreeCAD thread stated outright: “STL is a delivery format, it was never intended to be an edit format.”
Path 2 — rebuild in CAD. If you need a parametric part you can still change, open your CAD tool and draw over the STL as a trace. The 18-vote Fusion 360 comment put it this way: accept the reality first, then rebuild. It is not fast, but it is the only path that gives you back the feature tree, the history, and a STEP file that behaves like the original one.
Path 3 — run a reconstruction tool and clean up. Paid tools with feature recognition exist: they group triangles back into bodies and sketch bodies. The 3-vote comment on the Bambu Lab thread notes that the result is a working STEP, but you still have to re-group the bodies by hand and expect circles to have become splines. This is an interpretation, not a recovery.

4. Why this converter will not do it, and what we do say

The converter on the front page reads STEP and IGES files and writes STL. Extensions .step, .stp, .iges and .igs go in; STL comes out. An STL cannot be dropped back in, and we would rather say so than pretend. The limit sits in the engine — the shipped WebAssembly build exports four readers and one writer, and an STL is not among the things it will accept.

This page exists because the question is a real one. Three search bundles land in a high-volume cluster: stl to step at 2,400 monthly searches, stl to step converter at 1,000, and convert stl to step at 880. All three sit in a cluster where people already own 3D printing and modelling tools and want to go the other way out of them. This converter does not solve that cluster, so this page gives you the honest answer instead of pretending it can.

If you arrived here from a search looking for a tool that takes an STL and hands you a STEP, the straight answer is that we do not run that tool. But the community answer that three forums landed on is still the one that matters: the tessellation is what survives, the surfaces are gone, and your three paths forward are accept, rebuild, or run a reconstruction tool and expect cleanup.

The whole thing on one screen

Reverse-direction facts, every row labelled and honest
What STEP to STL is	Sampling. A surface that already exists is walked into triangles. Our measured cone takes 286, 516 or 2,142 triangles depending on which quality setting you pick.
What STL to STEP is	Reconstruction. You have triangles and you guess which surfaces a human author intended. Many surfaces fit the same triangles; no rule picks the correct one.
What is lost when the tessellation is done	Feature tree, circular geometry, units, colour, material and part names. The STL has nowhere to store them, so they stop existing at the boundary.
What a paid reconstruction tool gives back	A STEP file with bodies and spline curves. Not the one you lost, but a working interpretation of the mesh.
What this converter will not do	Take an STL as input. It reads STEP and IGES only and writes STL.

Where these numbers come from

286 / 516 / 2,142 triangles on the cone — produced by running the shipped engine (occt-import-js 0.0.23, a WebAssembly build of OpenCASCADE) over the project’s conical surface test file at Draft, Normal and Fine settings. npm test re-runs all three conversions and fails on a mismatch.
The reverse-direction search volumes — taken from one round of Google Keyword Planner output, run on 2026-10-04, in American English. The three figures are the monthly averages for stl to step, stl to step converter and convert stl to step. We do not run this search ourselves; the data comes from the keyword planner and is reused here as-is.
What a STEP stores and what an STL loses — derived directly from the binary STL field layout (80-byte header + 4-byte triangle count + 50 bytes per triangle) and the fact that STEP is a text format with a hierarchical structure. The STEP vs STL page carries the same losses in its summary table, and the verification page notes the five checks that only need what an STL actually contains.
The three paths forward — summarised from three Reddit threads in the Fusion 360, FreeCAD and Bambu Lab communities, with date and identifier recorded in the ammo list. We do not cite vote counts from those threads on this page, because the counts have not been cross-checked against the live post. We do cite the positions the comments landed on, because those are the honest answer people gave.
What we do not claim — we do not claim to have run a reverse conversion ourselves. No number on this page describes the output of an STL-to-STEP tool, because we did not run one on this machine. What we say is what the community says, and what the forward converter actually produces when we run it.

The STEP vs STL page gives the full forward-direction asymmetry, and the verification page names the five checks you can run on a finished STL. This page is honest about what the forward converter will not do, and about what the community actually does when the STEP file is gone.