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

Do Cura, Bambu Studio and PrusaSlicer open STEP files?

Three slicers, three official pages, one question. This page quotes each vendor’s own documentation as it stood when the page was written, and nothing else: no forum posts, no reviews, no secondhand claims, and no product verdicts. Where a document could not be read, the gap is stated rather than filled. Every number about this site was measured on the machine that wrote the page and is re-run by npm test before publishing.

The short answer

All three will take a STEP file, and none of them keeps it as a surface. What differs is where the entrance sits. UltiMaker Cura leaves STEP and IGES out of its native format list and offers them through a separate import plug-in; Bambu Studio imports STEP with a kernel its own wiki names, OpenCASCADE; PrusaSlicer states in one sentence that the STEP file is triangulated during import. Three routes, one destination — a triangle table, which is what a slicer slices.

What each slicer’s own documentation says about STEP input
SlicerWhere STEP sits in its documentationCan the triangle count be adjusted?
UltiMaker CuraNot in the native 3D list; a separate article is titled “STEP and IGES Import Plug-in”Not stated in anything this page could read
Bambu StudioNative import, “based on OpenCASCADE”Yes: linear deflection and angle deflection
PrusaSlicerNative import, “triangulated during import”Not stated in the supported-formats entry

UltiMaker Cura: outside the native list, behind a plug-in

Cura’s support site answers the format question directly. Its FAQ entry, dated Jun 19, 2023, opens by saying the program “natively supports loading a wide range of file types”, then lists the 3D models it means. That list has eleven entries and it is worth reading the whole way down, because the absence is the answer.

Not from its native list. Cura's own FAQ lists its native 3D models as 3MF, AMF, COLLADA (.dae), Compressed COLLADA (.zae), Open Compressed Triangle Mesh (.ctm), STL, Stanford Triangle Format (.ply), Wavefront OBJ, X3D, glTF Binary (.glb) and glTF Embedded JSON (.gltf), and neither STEP nor IGES is among them. The same support site carries a separate article titled UltiMaker Cura - STEP and IGES Import Plug-in; its body did not load when this page was written, so only the title-level fact is recorded here.

Two things about that gap are worth separating. The first is what the list is made of: every name on it is a mesh container or a mesh-exchanging scene format, and STL is sitting in the middle of them. A STEP file is not one of those; it declares surfaces and needs a kernel to turn them into triangles, which is the subject of the no-CAD page. The second is the shape of the second article: its title puts STEP and IGES on the plug-in line, which is an entrance rather than a native capability, and that is the whole of what can be said from the title alone.

This page will not fill in the rest. The plug-in article is dated Jan 16, 2026 and its body is loaded by script; two reads, the second with a scroll and a nine-second wait, returned the page header and the title and nothing else. So there is no statement here about whether the plug-in costs anything, which versions carry it, or what size of file it accepts. A page that printed those numbers would be printing something it did not read.

Bambu Studio: a kernel named in the documentation

Bambu Lab’s wiki takes the opposite position from Cura’s, and it does so in one short paragraph. The STEP Format page states that Bambu Studio imports models and assemblies from STEP files, then names the machinery: the import “is based on OpenCASCADE”. That is the same kernel family this site ships, and naming it is unusual — most slicer pages describe the feature without saying what performs it.

Yes. Bambu Lab's wiki says Bambu Studio supports importing models and assembly from STEP files, and that this is based on OpenCASCADE. Its documentation adds that imported quality is adjusted through two parameters, linear deflection and angle deflection, and that smaller values give smoother surfaces and more generated triangles.

The second half of that quotation is the part worth keeping. Two deflection parameters are a tolerance, and the documentation says plainly which way the tolerance moves the output: smaller values, smoother surfaces, more triangles. That is the same trade this site’s quality control makes, and it is measurable here without a slicer — the project’s cone test file measures 286 triangles at Draft and 2,142 at Fine, a 7.5× spread from the tolerance alone. The triangle-budget page works that trade through by curvature.

PrusaSlicer: one sentence, and it is the whole answer

Prusa Research’s supported-formats article is the tersest of the three. The STEP entry does not describe an importer, a plug-in or a setting; it states the operation.

It triangulates the file during import. The vendor's supported-formats article gives the whole STEP entry as one sentence: The STEP file is triangulated during import. The same article's STL entry reads Both binary an ASCII format is supported, quoted here as printed, including the 'an'.

“During import” is the phrase that settles the question of this page. If the triangulation happens while the file is being read, then the surface is consumed at the door and what the slicer holds afterwards is triangles. Nothing in the entry describes keeping the declared geometry, and nothing suggests the read can be undone. The typo in the STL line is quoted as printed for the same reason the rest is: this page is reporting what a vendor wrote, not tidying it.

The rule all three share

Set the three side by side and the differences are about the entrance, not the destination. Cura keeps STEP outside the native list and offers a plug-in; Bambu imports it natively and names the kernel, with two knobs for the triangle count; Prusa imports it natively and describes the triangulation in one sentence. No vendor describes holding a declared surface after import, and none of them claims to write STEP back out. A slicer’s job starts where a mesh starts, so the read is always a one-way sampling: surfaces in, triangles out.

That leaves exactly two variables a reader can act on. Who provides the entrance — a plug-in, a native importer, or a separate tool. And whether the triangle count can be steered — Bambu publishes two deflection parameters, Prusa’s entry states the operation without offering one, and Cura’s entry was unreadable here. On the third question, what the entrance costs, this page prints nothing, because none of the three pages it could read answers it.

Why Bambu naming OpenCASCADE matters here

A vendor that says its STEP import “is based on OpenCASCADE” is describing an independent implementation of the same two steps this site performs: evaluate the declared surfaces with a geometry kernel, then sample them into triangles. This site ships occt-import-js 0.0.23, a WebAssembly build of OpenCASCADE, as 7,604,031 bytes (7.25 MiB) fetched once per browser session. From that point the read is local: the largest file verified here, a 433,606-byte assembly of 18 solids, tessellates to 7,372 triangles and writes a 368,684-byte binary STL, which is exactly 84 + 50 × 7,372.

The practical consequence is about where the triangle table comes from, not about which slicer is better. A slicer receives triangles either way; if what you need is that table as a file, producing it does not require the slicer’s importer at all. The converter does the same sampling in the tab with the file never leaving it, and the verification page gives the six checks that confirm the result — the byte identity above is check 1.

Where these quotations come from

npm test

The command above re-runs every site number on this page, and the test suite also checks the four quotations against this page verbatim. The vendor pages themselves are linked in the list above and were read on 2026-11-11; they can change, and the quotations here describe that day. For what a slicer is on the receiving end of, the STEP vs STL page covers the format boundary, and the verification page owns the read-what, refuse-what answer.