Default line width (wall_line_width)

Default line width is a number in mm. PrusaSlicer, OrcaSlicer and Creality Print accept 0 to 1000 mm; Bambu Studio accepts 0 mm or more; Cura declares no range.

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 extrusion_width process
Bambu Studio line_width process
OrcaSlicer line_width process
Cura line_width process
Creality Print line_width process

What does each slicer say about it?

Each slicer offers its own values, so each gets its own line.

  • PrusaSlicer: Default line width in mm or percent of nozzle. 0 lets the slicer choose from the nozzle.
  • Bambu Studio: Default extrusion width in mm, used when a specific line width is 0. Range 0 to 10.
  • OrcaSlicer: Default extrusion width, in mm or % of nozzle diameter, used where a specific line width is 0.
  • Cura: Width of one extruded line, in mm. Usually set near the nozzle diameter; wider lines print stronger and faster.
  • Creality Print: Default extrusion width in mm or % of the nozzle, used when a feature width is 0. Wider lines are stronger.

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 extrusion_width and line_width, 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 floatOrPercent mm or % 0.4 0 to 1000
Bambu Studio float mm 0.45 0 or more
OrcaSlicer floatOrPercent mm or % 0.45 0 to 1000
Cura float mm 0.4 not declared
Creality Print floatsOrPercents mm or % 0.4 0 to 1000

Cura declares no range for this key, so nothing in the file bounds it.

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

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 default line width under its own name alongside the rest of the print settings. The file stays in your browser; see what leaves it.