🎉 WIN a Snapmaker U1 Printer! Enter FREE now

--export-stl

Output Orca SlicerBambu Studio

Export each loaded object as its own binary STL -- volumes and all instances merged into one mesh per object -- without slicing, placing files into a stl/ subdirectory of the output directory (or the current working directory if none is set).

Details

When --export-stl is passed, the CLI exports the loaded model geometry to binary STL files without slicing. It is a boolean switch that takes no argument. Before writing, the engine ensures that any object without a placed instance receives a default identity-transform instance, so no objects are silently skipped.

Despite the tooltip's wording, the flag does not produce a single file for the entire project. It produces one .stl file per loaded object. Within each file, the geometry is a true merge: all non-modifier volumes of the object are unioned into one raw mesh, every instance of that object is then transformed and merged into that mesh, and the result is written as a single contiguous binary STL. An object that has been duplicated three times on the build plate therefore produces one STL file containing all three copies laid out at their placed positions.

Output files are named obj_<N>_<objectname>.stl (N is a 1-based counter) and are placed in a stl/ subdirectory. If --outputdir is set, the stl/ directory is created under it; otherwise it is created in the current working directory. The subdirectory is made automatically if it does not already exist. The flag is also the implied fallback action after --cut: if a cut operation completes and no other action was requested, the CLI automatically adds the STL export step, so the cut pieces are emitted as STL without a separate flag.

Watch out for

  • One file is written per loaded object, not one file for the whole scene. A 3MF with three separate objects produces three `.stl` files.
  • Multiple instances of the same object are merged into one STL at their placed positions -- they do not become separate files. Downstream tools that expect one-instance-per-file will receive blended geometry.
  • The underlying write routine has a known defect noted in the source: it returns success even when the file write fails. A failed export may therefore exit 0 with no output rather than with an error code.

Sign up for free today

No credit card required. Connect unlimited printers and get production automation running in minutes.