Open preslice Docs

Brim type (brim_type)

Brim type is one of a fixed set of names. This controls the generation of the brim at outer and/or inner side of models.

What does each slicer call it?

Five slicers, five spellings of one setting. The scope column is which preset the key belongs to, which is what decides whether changing it follows the printer, the filament, or the print profile.

Slicer Key Scope
PrusaSlicer brim_type process
Bambu Studio brim_type process
OrcaSlicer brim_type process
Cura adhesion_type process
Creality Print brim_type process

Where does it live in the file?

All five slicers file this under the process preset, so its value follows the print profile rather than the model. A .3mf is a zip, so unzip it and search for brim_type and adhesion_type, or open the file in preslice and read the Raw tab, which searches every member at once.

Four of the five slicers write their settings into a sidecar part beside the geometry. Cura writes them into the model XML itself, so there is no config part to open.

Slicer Part Format
PrusaSlicer Metadata/Slic3r_PE.config INI, one key = value per line
Bambu Studio Metadata/project_settings.config JSON, one flat object
OrcaSlicer Metadata/project_settings.config JSON, one flat object
Cura 3D/3dmodel.model XML metadata inside the model part, under a cura namespace
Creality Print Metadata/project_settings.config JSON, one flat object

What values are valid?

Each slicer declares its own type, default, and bounds for its key. They do not always agree, and where they disagree the file is still valid in both: the slicer that wrote it is the one that enforced its own rule.

Slicer Type Unit Default Range
PrusaSlicer enum not declared not declared 4 named values
Bambu Studio enum not declared not declared 6 named values
OrcaSlicer string not declared auto_brim 7 named values
Cura enum not declared brim 4 named values
Creality Print string not declared not declared 7 named values

This value is not a number, so PrusaSlicer, Bambu Studio, OrcaSlicer, Cura and Creality Print declare no unit for it.

The slicers disagree on the type: PrusaSlicer, Bambu Studio and Cura as enum, OrcaSlicer and Creality Print as string. preslice reads all of them.

The slicers do not accept the same names, which is what a value has to survive when a file moves between them:

  • Bambu Studio accepts auto_brim, brim_ears, outer_only, inner_only, outer_and_inner, no_brim
  • OrcaSlicer and Creality Print accept auto_brim, brim_ears, painted, outer_only, inner_only, outer_and_inner, no_brim
  • Cura accepts brim, none, raft, skirt
  • PrusaSlicer accepts no_brim, outer_only, inner_only, outer_and_inner

Every type, default, and bound above is read from the slicer's own field definitions rather than from measurement: PrusaSlicer's PrintConfig.cpp, Bambu Studio's PrintConfig.cpp, OrcaSlicer's PrintConfig.cpp, Cura's fdmprinter.def.json and Creality Print's PrintConfig.cpp.

Can I read it from my own file?

Yes, without installing a slicer. Open preslice and drop a .3mf on the page. It unzips and parses the file in your browser, and shows brim type under its own name alongside the rest of the print settings. The file never leaves your machine, and nothing uploads.