STEP→STL Your file stays in this tab · nothing is uploaded

Learn: how STEP to STL works, question by question

This is the index of every explainer on the site. Each page was written from measurements taken on the machine that wrote it. The figures are arithmetic you can check yourself — a binary STL is always 84 + 50 × its triangle count — and a number that cannot be checked that way does not appear here.

Start here: convert, then check the result

What the file stores, and how the output looks

When the result is not what you wanted

The three things you choose: kernel, triangle budget, protocol

The upload era

The reverse direction and its price

Limits, bytes and viewers

What other conversion services charged

Geometry, pipeline and the bill

The other mesh package: 3MF

Two pages, and only two: one reads a 3MF, one writes a 3MF. STEP↔STL stays the main line of this site.

Format lists and what they promise

The quality knob and its label

Who does the work and who decides

Printing: what a slicer does with a STEP file

Which one to read first

The situation you are in and the page that answers it
Nothing converted yetStart with the workflow. Its first screen is the whole procedure, and steps 2 and 3 (unit, quality setting) are the two choices that change the output.
Converted, want proofGo to verify a conversion. Check 1 alone tells you whether the file you were handed contains the triangles the converter claimed.
The preview looks facetedRead a STEP file looks wrong. Faceting is normal; the page gives the number that separates “coarse setting” from “broken file”.
The size is wrongRead why a model comes out 25.4× too big. If the reported bounding box divides into whole inches, the part was drawn in inches and the conversion was correct.
Choosing a format to keepRead STEP vs STL. It is the page that explains why you should keep the STEP file and treat the STL as disposable.
Arguing with a numberAny of them. Every page ends with a section named Where these numbers come from that says how each figure was produced.
No CAD installedRead opening a STEP file without CAD. The whole kernel is a 7.25 MiB browser download, and the seat’s features are exactly the ones it does not have.
Choosing a quality settingRead how many triangles a part needs. Flat faces make the choice free; curvature is where the tiers separate, and the count can be recovered from the byte size.
The header says AP203 or AP214Read what the flavour line means. It names the protocol the file was written against; the mesh answers to the quality setting, and either flavour converts.
Worried about handing over a fileRead whether uploading is safe. It separates retention promises from architecture claims and gives a one-minute network-panel check you can run on any converter.
Conversions keep failing onlineRead why 2015’s free converters could not read STEP. The era’s own operators published the numbers: a 51-extension input board with no CAD format on it, and 292,073 successes out of 385,114 conversions.
Only the STL survivedRead STL to STEP is not really converting. From here the job is reconstruction rather than conversion, and the page is honest about what each of the three routes actually returns.
Wanting to change a meshRead whether you can edit an STL. Yes, and it will not do what you want: a rounded cube is 40 triangles at Draft and 140 at Fine, and moving one fillet means moving all of them.
The file is larger than expectedRead why an STL file is so big. A binary STL is exactly 84 + 50 × triangles, so the lever is the quality preset — and a flat face never moves with it.
The converter refused the fileRead why a STEP file will not convert. Most CAD STEP files carry NURBS surfaces that only a real kernel can read; the cone test tells you whether a tool has one.
Suspecting holes in the meshRead whether an STL file has holes. A closed shell spends every edge exactly twice, so the edges used once are the hole — and conversion will not fill it.
Rebuilding an STL by handRead turning an STL back into an editable model. It is rebuilding rather than converting: accept what the mesh holds, then redraw the part in a parametric CAD package.
Wondering which step changes the formatRead which step actually changes the format. Only the write station produces bytes, so nothing before it can change what the file is; the cube arrives as 684 bytes and the assembly as 368,684 at Normal.
Wondering why STEP once cost extraRead why STEP was a paid add-on in 2001. A viewer’s base list carried six formats and STEP sat on the module line; today STEP and IGES are the inputs, STL is the output, and the cube still ends at 12 triangles and 684 bytes.
Wondering why one converter sold format pairsRead why a 2006 converter sold format pairs. Fourteen inputs against twelve outputs left two formats readable but unwritable, so 168 ordered pairs were sold one input format at a time; here two pairs and one output do the work, and the cube is still 684 bytes.
Wondering why a converter wants your fileRead why old converters uploaded your CAD model. The operator’s own FAQ gave the reason — server RAM and paid machine time — and the same kernel now fits in a browser tab.
Wondering how a free converter stays freeRead what pays for a free converter. A ceiling, a queue and an ad-blocker term are one server bill cut three ways; in the tab that bill is your own processor time, 7,604,031 bytes of engine once per session and 4,900 to 21,116 triangles on the 18-part assembly.
The file is a .3mf, not a .stepRead what a 3MF file is and how to turn it into STL. A 3MF is already a mesh in a ZIP package, so it needs no kernel: a plain JavaScript reader unpacks it and writes the STL with 0 bytes of engine downloaded.
You have an .stl and need a .3mfRead what an STL to 3MF conversion actually changes. It swaps the container and nothing else — the same triangles written as XML in a ZIP package, with no colour, materials or print settings invented along the way.
Wondering if converting was ever sold aloneRead whether a converter was ever priced on its own. The 2001 price page printed one product and one price, with the translator named inside that line, so the number of rows belonging to the converter was zero.
Doubting a converter’s format tableRead whether a format list is a promise. A hub page can leave out a format whose own page is live below it, and a table row can contradict the paragraph beneath it; the output file’s extension and length are the only checks that hold.
The quality slider says megabytesRead what the resolution knob is labelling. A cap falls as the setting refines while a triangle count rises, so one knob cannot rank both; in a tab the budget is all that is left, 12 triangles and 684 bytes on the flat cube at every stop.
Someone quoted you a priceRead what an outsourced rebuild cost. The reverse direction is priced as a person’s time — $150 a file in one 2020 capture — because no kernel recovers a circle from triangles.
A repair is free for one file and quoted for anotherRead where the free and quoted halves split. The seam is decidability rather than price: a closed cube has 18 edges each used twice, removing one face leaves 4 edges used once, and only the question a count cannot answer needs a person.
Worried the file is too largeRead whether there is a size limit. A server publishes an upload ceiling because the compute is its bill; in the tab the only limit is the machine in front of you.
Two STL files, one much biggerRead binary or ASCII STL. The same 12 triangles cost 684 bytes as binary and 2,241 as ASCII, and across the test set the gap runs from 3.276× to 4.030×.
A viewer showed the model but gave you no fileRead whether a viewer can convert. Looking ends at pixels and converting ends at a file; two archived viewer pages show the boundary from the vendor’s own feature lists.
Someone wants money to turn an STL into a STEPRead which STL-to-STEP route to choose. Three routes with three published prices: a free open-source project, about $0.83 a conversion, and a 2020 quote of $150 a file for a person to redraw it.
A vendor says a plug-in turns a mesh into a solidRead what a 2007 mesh-to-solid plugin wrote. The captured page lists four mesh inputs and two solid outputs, ACIS .sat and Rhinoceros .3dm, with no STEP writer at all — a solid yes, a STEP no.
Wondering what cloud conversion used to costRead the cloud price history. Four dated captures show a single plan at $14 a month become a free tier metered at 100 MB a month, and then a viewer page that prints no price at all.
The part faces the wrong wayRead why a converted model can look tipped over. The axes and origin are carried through, not chosen: a 200 × 150 × 84 mm assembly keeps that box at every quality setting, and a 100× scaling test leaves the mesh identical.
Not sure the converter left the model aloneRead what happens inside a converter. The output is 84 + 50 × triangles with no field for a repair: the cube’s 36 vertex slots describe 8 corners, and the 18-part assembly keeps 18 shells with 0 boundary edges at every setting.
Wondering whether your slicer reads STEP at allRead what the three slicers’ own documentation says. Cura keeps STEP off its native list and offers a plug-in, Bambu Studio imports it and names OpenCASCADE, and PrusaSlicer says it triangulates the file during import — none of them keeps the surface.

The one formula worth memorising

For a binary STL the size is fixed by the triangle count: 84 bytes of header plus 50 bytes per triangle, so the file length tells you what is inside it. The flat 10 mm test cube converts to 12 triangles at every quality setting and lands as exactly 684 bytes. Curved geometry is where the count moves: the same cone measures 286 triangles at Draft and 2,142 at Fine. Recovering the count from the byte length is the first of the six checks on the verification page, and it is the reason you never have to trust a converter’s word for what it produced.

How these pages are written

The converter is on the front page. Who runs it and what it will not do is on the about page; how your data is handled is in the privacy policy; a problem worth reporting is described on the contact page.