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
- How to convert STEP to STL, in order — the six steps from the extension and the declared unit through the quality setting to the byte count you should get back.
- How to verify a STEP to STL conversion — six checks you can run with a file size, an edge count and a bounding box, with no CAD licence and no second tool.
What the file stores, and how the output looks
- STEP vs STL — what the two formats actually store, why the output can be smaller or larger than the input, and why the reverse direction is a reconstruction rather than a conversion.
- A STEP file looks wrong — how to tell an ordinary faceted surface from a genuinely damaged file by judging the flat faces instead of the curved ones.
- Why a model comes out 25.4× too big — divide the bounding box by 25.4 and see whether the three axes land on whole inches. One of our own test files does, and it declares millimetres. The same test is then run on four IGES copies of one flange, written in mm, cm, m and inch.
When the result is not what you wanted
- STL to STEP is not really converting — the honest answer when the STEP file is gone: three paths the community actually takes, why paid reconstruction only gives you a working interpretation, and why we do not run that tool here.
- Can you edit an STL file? — the honest answer is that you can, and it will not do what you want. A rounded cube we run every test day is 40 triangles at Draft, 56 at Normal and 140 at Fine; changing that fillet means moving every one of them, by hand.
- Why is my STL file so big? — a binary STL is exactly 84 bytes of header plus 50 bytes per triangle. A flat cube stays 12 triangles and 684 bytes at every quality setting, while a conical surface goes 286 → 2,142 triangles from Draft to Fine, a factor of 7.5.
- Why won't my STEP file convert? — most CAD STEP files use NURBS surfaces that only a real CAD kernel can read. The self-test: a cone should give 286 triangles at Draft, 2,142 at Fine. If the count does not change, the tool was only relaying a mesh.
- Does my STL file have holes? — a closed shell spends every edge exactly twice: 12 triangles make 36 edge-uses ÷ 2 = 18 edges. Cut one face away and exactly 4 edges are used once — that list of edges is the hole, and conversion does not repair it.
The three things you choose: kernel, triangle budget, protocol
- Can I open a STEP file without CAD? — yes: the whole OpenCASCADE kernel ships as 7,604,031 bytes (7.25 MiB) of WebAssembly, fetched once per session; an 18-part, 433,606-byte assembly converts in the tab to 7,372 triangles and a 368,684-byte STL with nothing uploaded. Editing, feature trees and drawings stay on the seat.
- How many triangles does a part need? — budget by curvature, not file size: flat faces cost exactly 12 triangles at every setting, the cone runs 286 → 2,142 from Draft to Fine, whichever deviation binds first decides, and (bytes − 84) ÷ 50 recovers the count you paid for.
- What do AP203 and AP214 mean on a STEP file? — the header line names the protocol the file was written against. Both test assemblies carry a different flavour and run the same reader and tessellation; the count gap between them comes from the exporters, not the protocol.
The upload era
- Is it safe to upload a STEP file? — four rungs separate converters that can only promise deletion of a copy they already hold from the arrangement where the file never leaves the tab; the discriminator is transport versus retention, and a one-minute network-panel check verifies any converter, including this one.
- Why couldn't 2015's free online converters read STEP files? — two pages the era's own operators published answer it: a format board with 51 input extensions and no CAD format among them, and an archived report of 385,114 conversions with 292,073 successful, a 75.8% success rate. STL was already the second most requested output; today the whole OpenCASCADE kernel, 7,604,031 bytes, opens the same files in a tab.
The reverse direction and its price
- Turning an STL back into an editable model — rebuilding, not converting: the community's two-step (accept what the mesh holds, then rebuild in a parametric CAD package), a nine-year archive showing the rebuild was always sold as a human service, and the one published accuracy figure — 0.033 mm average deviation, somebody else's measurement, quoted with attribution.
- Why did old converters upload your CAD model? — the operator's own 2009 FAQ says why: resurfacing needed several gigabytes of RAM and a fast processor, so the job ran on their server, and free files were capped at 100,000 polygons because they paid for that server time. The same kernel is 7,604,031 bytes in a browser tab today.
- What does an outsourced rebuild cost? — the reverse direction carries a price because no kernel recovers a circle from triangles: a person rebuilds it. A 2020 capture of a US service priced that labour at $150 a file with most jobs done in under a day, while the forward direction this site runs is machine work, 7,604,031 bytes of kernel in the tab.
Limits, bytes and viewers
- Is there a file-size limit on an online STEP converter? — an upload ceiling, a batch rule and a retention window are three faces of compute running on someone else’s server. In a browser tab there is no ceiling to publish: a 433,606-byte 18-part assembly tessellates to 21,116 triangles in one tab, and nothing is uploaded.
- Binary or ASCII STL? — the same mesh, two writers: binary is a fixed 84-byte header plus 50 bytes per triangle, so a 12-triangle cube is 684 bytes, while the same cube as ASCII is 2,241 bytes. The ratio is a band, 3.276× to 4.030× across the test set, because ASCII pays for the coordinates and binary does not.
- Can a CAD viewer convert STEP to STL? — no: a viewer ends at pixels and a converter ends at a file. The archived viewer pages of 2010 and 2013 list import and navigation features with no export step, while a binary STL of the 12-triangle test cube is exactly 684 bytes when a writer really runs.
What other conversion services charged
- Which STL-to-STEP route should you choose? — three routes and three published prices: a free open-source project at $0, a browser tool at about $0.83 a conversion, and an outsourced rebuild quoted at as low as $150 a file in a 2020 capture. Only the free route can run on your own machine.
- What did a 2007 mesh-to-solid plugin write? — four mesh formats in, two solid formats out, zero STEP. A January 2007 product page names ACIS .sat and Rhinoceros .3dm as its only outputs, prices the licence at 195 USD and runs a 10-day or runs trial.
- Why did a $14/month cloud STEP to STL service end up as a viewer? — one plan at $14 a month in August 2015 became three tiers at $0 / $19 / $39 in February 2016, all read from captures; by July 2022 the same domain served a viewer and printed no price at all.
- Why did a 2006 converter sell format pairs — and why does this one run only one direction? — its two lists count fourteen input formats against twelve output formats, with two formats readable but unwritable: 168 ordered pairs, 144 reversible and 24 one-way, priced one input format at a time. This converter offers two pairs and one output, and the cube still ends at 12 triangles and 684 bytes.
- Was a converter ever priced on its own — a bundled extra in 2001, a door to paid tiers today? — the 2001 price page printed one product and one price and named the translator inside that line, so the converter owned zero rows; the bundled list counts fourteen readable names and sixteen spellings with no STEP and no IGES, and a current page sets four paid doors beside the convert button.
Geometry, pipeline and the bill
- Why does my STL come out lying down or in the wrong place? — the axes and origin are carried through, not chosen: a 200 × 150 × 84 mm assembly keeps that box at Draft, Normal and Fine while the triangle count moves 4,900 / 7,372 / 21,116, and a 100× scaling test leaves the mesh identical.
- Does a STEP to STL converter change the model while converting? — the middle of the pipeline is tessellation, not correction: a 10 mm cube is 12 triangles / 684 bytes at every setting, 36 vertex slots describe 8 distinct corners, and the 18-part assembly keeps 18 shells and 0 boundary edges at all three settings.
- Which step in a STEP to STL converter actually changes the format? — the format changes at the write station, where a triangle list becomes an 84-byte header plus 50 bytes per triangle: the 10 mm cube is 12 triangles and 684 bytes, the 18-part assembly is 7,372 and 368,684 at Normal, and all three settings still produce STL.
- Why was STEP a paid add-on in 2001 and a normal input for STEP to STL today? — in 2001 a viewer’s base import list carried six formats and STEP sat on the separately sold module line, while its only export was a picture; today STEP, STP, IGES and IGS come in and STL comes out, with the cube still at 12 triangles and 684 bytes.
- Why is a free STEP to STL converter free — and who pays for the capacity, the wait and the ad blocker? — a capacity ceiling, a queue and an ad-blocker term are three faces of the same cost: the machines that run the conversion. In a tab the bill is your own processor time, stated on the page: 7,604,031 bytes of engine once per session, 12 triangles and 684 bytes for the flat cube, 4,900 to 21,116 triangles for the 18-part assembly.
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.
- What is a 3MF file, and how do you turn it into STL? — a 3MF is a ZIP package whose model part already holds a mesh, so it needs no geometry kernel: a standalone JavaScript reader unpacks it, applies the build transform and the declared unit, and writes binary or ASCII STL with 0 bytes of engine downloaded. The bracket sample comes back as 2,696 triangles and a 134,884-byte STL, exactly 84 + 50 × 2,696.
- What an STL to 3MF conversion actually changes — the container, not the geometry: the same triangles are re-serialised as XML inside a ZIP package, with no colour, no materials and no print settings, because the STL held none of them. The 12-triangle control STL (684 bytes) becomes a 2,715-byte stored package or 1,318 bytes deflated.
Format lists and what they promise
- Is a converter's format list a promise or a catalogue — when the hub page omits a format its own leaf page serves? — a hub page can leave out a format whose own conversion page is live one level below it, and one leaf page labels a text format as binary while calling it text-based a few lines later, so a table is a catalogue of wiring rather than coverage. A promise is only checkable on the artefact: extension plus 84 + 50 × triangles bytes, which returns 12 triangles for 684 bytes and 7,372 for 368,684.
The quality knob and its label
- Is a converter's resolution setting a triangle count or a file cap — and what does the same knob hide when it prints both? — a cap falls as the setting refines and a triangle count rises, so one knob cannot rank both; a size label answers a question about the upload rather than the mesh. In a tab the cap disappears and the budget remains: the flat cube stays at 12 triangles and 684 bytes at every stop, a rounded cube runs 40 / 56 / 140 and a cone 286 / 516 / 2,142.
Who does the work and who decides
- Why does a repair service fix some files for free and quote others — and where is that line drawn today? — the seam is decidability, not price: a repair a rule can settle has no person’s time in it, while a repair that chooses between two valid reconstructions does. The archived order form put both exits inside one ordering row; on the mesh the split shows up as counts, 18 edges each used twice for a closed cube against 10 triangles and 17 edges with 4 used once when a face is missing.
Printing: what a slicer does with a STEP file
- Do Cura, Bambu Studio and PrusaSlicer open STEP files? — all three take the file and none keeps the surface: Cura leaves STEP off its native list and offers a separate import plug-in, Bambu Studio imports natively and names OpenCASCADE with two deflection parameters for the triangle count, and PrusaSlicer says the file is triangulated during import. The three vendor pages are quoted, and the one body that would not load is reported as unread rather than filled in.
Which one to read first
| Nothing converted yet | Start 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 proof | Go to verify a conversion. Check 1 alone tells you whether the file you were handed contains the triangles the converter claimed. |
| The preview looks faceted | Read a STEP file looks wrong. Faceting is normal; the page gives the number that separates “coarse setting” from “broken file”. |
| The size is wrong | Read 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 keep | Read 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 number | Any of them. Every page ends with a section named Where these numbers come from that says how each figure was produced. |
| No CAD installed | Read 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 setting | Read 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 AP214 | Read 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 file | Read 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 online | Read 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 survived | Read 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 mesh | Read 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 expected | Read 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 file | Read 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 mesh | Read 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 hand | Read 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 format | Read 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 extra | Read 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 pairs | Read 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 file | Read 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 free | Read 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 .step | Read 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 .3mf | Read 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 alone | Read 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 table | Read 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 megabytes | Read 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 price | Read 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 another | Read 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 large | Read 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 bigger | Read 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 file | Read 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 STEP | Read 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 solid | Read 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 cost | Read 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 way | Read 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 alone | Read 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 all | Read 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
- One page per question with a checkable answer. Questions that can only be answered by opinion, or that are really product advertising in disguise, do not get pages.
- Figures are measurements, not rules of thumb. Each page names its source at the bottom, and the test suite recomputes it rather than reading it back off the page.
- Pages get merged or retired when they overlap. When that happens the link is removed from this index and from the page footer on the same day, so nothing listed here is a dead end.
- What the tool itself accepts. STEP and IGES files —
.step,.stp,.iges,.igs— written out as STL, in millimetres by default, with your file never leaving the browser tab.
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.