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

Convert STEP to STL in your browserNo CAD to install, no upload — and every number it prints can be checked.

Convert .step / .stp / .iges / .igs to .stl — 12 tri / 684 B baseline, measured on your machine. A .3mf is converted on its own page.

Engine not loaded yet — it starts downloading as soon as you press this box, or a few idle seconds after the page settles.

The file you get can be checked before you open it: every binary STL this page writes is exactly 84 + 50 × triangles bytes, so the size alone gives you the triangle count.

Quality
STL flavour
Output unit
Advanced deflection engine request caps — leave blank to stay on the preset

These two values are passed straight to the OpenCASCADE mesher — they cap how far the mesh may stray from the true surface. They are the engine’s request limits, not measured deviations; the measured chordal deviation on our analytic cone sample is pinned in the tests. Empty fields follow the selected preset.

Changing any control re-runs the conversion on the file that is already loaded.

Have a .3mf?3MF is a mesh package — it is converted on its own page. Open the 3MF converter →

Triangles in the reference-cube STL
12
Bytes that STL weighs — 84 + 50 × 12
684
Bytes of WebAssembly kernel, cached after first load
7,604,031
The size identity, any triangle count
84+50×n
Runs in this tab WebAssembly kernel, no backend File never leaves this browser tab, nothing uploaded Numbers you can check any binary STL is 84 + 50 × triangles

Your slicer refuses the file. A slicer eats meshes, not boundary-representation solids — a native STEP goes straight to the reject pile. Convert it here first, then hand the STL to the slicer.

A client sent you a STEP file. You need to print it once or check a fit, not open a CAD seat for it. This tab reads the file and hands you the mesh with its measured size.

You don’t want to install CAD. One conversion is not a reason for a gigabyte-scale install and a licence. The OpenCASCADE kernel runs here instead — 7,604,031 bytes of wasm, cached after the first load.

How to convert a STEP file to STL

  1. Drop the file. The page routes by extension: .step and .stp go to the STEP reader, .iges and .igs to the IGES reader, anything else is refused with a message. The test files behind the numbers below are public NIST AS1 conformance models (AP203 and AP214) plus small cubes and curved parts.
  2. Pick a quality. Normal is the right starting point for 3D printing. Choose Draft for a quick fit check or a large assembly you only need to eyeball, Fine when curved surfaces have to print smooth.
  3. Download and check the number. Compare the bounding box this page prints against your slicer. If they disagree by exactly 25.4×, a millimetre/inch unit mismatch is the cause, not a broken conversion.

What this converter supports

Supported inputs, outputs and settings
InputSTEP (.step, .stp) and IGES (.iges, .igs), read by the OpenCASCADE kernel. The files verified on this page are ISO 10303 AP203 and AP214 models (the two NIST AS1 assemblies, 18 parts each) plus small cubes, two curved parts and one IGES cube; AP242 and other protocols are not covered by a test file here. One file per conversion.
OutputSTL, binary (default) or ASCII. Written by this page from the triangles the engine returns; the engine itself has no STL writer.
QualityThree presets that set the engine’s tessellation parameters. Draft = 0.02 bounding-box ratio, 0.5 angular. Normal = 0.005 / 0.3. Fine = 0.001 / 0.1. These are this page’s own choices, not a CAD standard.
UnitEverything is measured in millimetres (linearUnit: millimeter, the engine default). OpenCASCADE applies the unit declared inside your STEP file before the numbers reach this page. The optional inch output re-expresses the coordinate values as millimetres ÷ 25.4; it rewrites numbers only, it does not scale the geometry.
Engineocct-import-js 0.0.23, a WebAssembly build of OpenCASCADE Technology, 7,604,031 bytes of wasm (7.25 MiB) measured on this machine, LGPL-2.1.
NetworkYour model file is never sent anywhere: the bytes are read into memory in this tab, tessellated by the wasm engine here, and written back out as an STL here. The requests the page does make are its own script, stylesheet, worker, engine glue and wasm file, one Google Analytics script that counts the page view, plus, where shown, third-party advertising. The privacy policy names them.

Limits you need to know

The main line of this site is two input families into one output direction: STEP, STP, IGES or IGS through the OpenCASCADE kernel, and 3MF through its own JavaScript reader, with STL out either way — millimetres, coordinates untouched. The reverse container swap, STL to 3MF, has its own page. That is two 3MF pages in total, one reading and one writing, and there will not be a third: the domain is about step and stl, and 3MF stays a side door. One conversion done verifiably beats twenty done halfway — that is the whole product. The formats this page will not accept, and the reasons, are listed once on the verification page. Why so many other converters ask you to upload the file first is a separate question, answered in this breakdown of their workflow.

Questions people actually ask

Is this an online STEP to STL converter, or does it really convert step files locally?

It is a static web page. The conversion is done by a WebAssembly build of OpenCASCADE that runs inside a worker thread of the tab. Read the source of app.js and engine/worker.js: the worker uses one XMLHttpRequest for the engine’s own wasm file from the same folder, and then Blob URLs. There is no API endpoint and no form POST, and this page sets no cookies of its own. One Google Analytics 4 script counts page views and sets two first-party cookies; it never sees your file or its name. Your model file is never uploaded. The privacy policy lists every request the page makes.

How do I convert stp to stl for 3D printing without a CAD program?

Drop the file here, leave quality on Normal, download the binary STL, open it in your slicer. If the part prints at the wrong scale, check the bounding box this page measured against the size in the slicer before you blame the conversion.

Should I pick binary or ASCII STL?

Binary. It stores each triangle in a fixed 50 bytes plus an 84-byte header, so a 12-triangle cube is exactly 684 bytes; the same cube written as ASCII is 2,241 bytes — 3.28× larger. Across all 27 sample-and-quality combinations in our test set, ASCII runs 3.3× to 4.0× the binary size for the same geometry (the AP203 18-part assembly at Normal: 304,484 B binary against 1,226,556 B ASCII, the binary side being 84 + 50 × 6,088). Choose ASCII only when a tool explicitly asks for a text STL you can open in an editor.

What do I get when I convert a multi-body STEP file to STL?

One .stl holding every body in the file. The worker walks all the meshes the engine returns and writes them into a single triangle list, so nothing is split into per-part files. The Solid parts row in the stats grid counts those meshes: the AP203 18-part assembly (as1_pe_203.stp) in the table below reports 18 there, and at Normal it comes out as 6,088 triangles and exactly 304,484 bytes, which is 84 + 50 × 6,088 — any binary STL you download can be checked the same way. A shell that arrives open stays open: this page triangulates, it does not repair.

Which quality should I use?

Normal for printing. Draft when you only need to check fit or orientation on a heavy assembly, Fine when a fillet or a cylindrical face looks faceted in the preview. The triangle counts from our test run show what that costs: a rounded 10 mm cube goes 40 → 56 → 140 triangles across the three presets, a conical part goes 286 → 516 → 2,142.

Can I convert iges to stl as well, or only step?

Both. The engine exposes a STEP reader and an IGES reader, and this page picks between them by extension. Our IGES test cube converts to a closed shell: 12 triangles, 18 edges with every edge shared by exactly two triangles, one connected piece, 684 bytes — the same counts as its STEP twin. IGES stores surfaces rather than a solid, and this page writes every mesh it receives into one STL without stitching them together, so surfaces that do not meet in the file stay separate pieces in the output.

Does it work on a phone?

Yes, down to 390 px wide, with the file picker and the download working through the browser. The engine download is the expensive part, and a heavy assembly can outgrow a phone browser’s memory sooner than a desktop one.

Why does my converted file have no flat bottom or the wrong orientation?

Nothing is rotated, aligned, centred or re-scaled here. The triangles land in the STL in the same coordinate system the model had in the STEP file. Orientation is your slicer’s job.

The numbers on this page, and where they come from

Every figure is measured, not assumed.

Measured with occt-import-js 0.0.23 (OpenCASCADE) in Node.js on this machine. The last column is 84 + 50 × the Normal triangle count in every row. Conversion time is not listed here because it is measured per run on your own machine.
Test fileBytesDraft triNormal triFine triNormal binary STL
simple-cube.stp8,010121212684 B
cube-10x10.stp9,138121212684 B
conical-surface.step9,3912865162,14225,884 B
rounded-cube.step20,53240561402,884 B
cube-10x10.igs (IGES)11,421121212684 B
as1_pe_203.stp (18 parts)136,6633,8486,08817,848304,484 B
as1-oc-214.stp (18 parts)433,6064,9007,37221,116368,684 B
One cube conversion, from the STEP file that goes in to the STL that comes out A 9,138-byte STEP file is read in the tab and a 12-triangle STL comes out at exactly 684 bytes. The 684 is not a separate measurement: a binary STL is an 84-byte header plus 50 bytes per triangle, so 84 plus 50 times 12 is 684, and the byte count is the triangle count written another way. One conversion, start to finish STEP in cube-10x10.stp 9,138 bytes STL out 12 triangles 684 bytes read in this tab — nothing uploaded 84 + 50 × 12 = 684 a binary STL is an 84-byte header plus 50 bytes per triangle, so the file size is the triangle count written another way.
What the tool hands back. The numbers on the left and right of the arrow are the same conversion: a 9,138-byte STEP file goes in, and the STL that comes out is 12 triangles and exactly 684 bytes. Those two output figures are not independent measurements — the bottom line is why. Every binary STL is an 84-byte header plus 50 bytes for each triangle, so once you know the triangle count you already know the byte count, and the reverse holds too: divide a file by 50, subtract 84, and you have recovered the triangle count. The table above is the same identity applied to seven real parts.

Latest explainers

Have a STEP or IGES file waiting?

Drop it in the converter at the top of this page. It reads the file in this tab, writes the STL here, and prints the triangle count and byte size — so you can check the download against 84 + 50 × triangles before your slicer ever sees it.

Back to the converter