Nozzle diameter (nozzle_diameter)

Nozzle diameter is a number in mm. Bambu Studio accepts up to 1 mm; OrcaSlicer and Creality Print accept up to 100 mm; PrusaSlicer and Cura declare 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 nozzle_diameter machine
Bambu Studio nozzle_diameter machine
OrcaSlicer nozzle_diameter machine
Cura machine_nozzle_size machine
Creality Print nozzle_diameter machine

What does each slicer say about it?

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

  • PrusaSlicer: Diameter of the nozzle in mm, such as 0.4. It sets line widths and layer height limits.
  • Bambu Studio: Hole size of the nozzle in mm, per extruder. Sets the base line width and the usable layer heights.
  • OrcaSlicer: Diameter of the nozzle opening in mm. Sets the line widths and layer heights you can print; match it to the installed nozzle.
  • Cura: Inner diameter of the nozzle, in mm. Match the installed nozzle; line widths are based on it.
  • Creality Print: Diameter of the nozzle in mm. Sets line widths and the layer heights you can print.

Where does it live in the file?

All five slicers agree on which preset this belongs to. A .3mf is a zip, so unzip it and search for nozzle_diameter and machine_nozzle_size, 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 floats mm not declared not declared
Bambu Studio floats mm not declared 1 or less
OrcaSlicer floats mm not declared 100 or less
Cura float mm 0.2 not declared
Creality Print floats mm not declared 100 or less

PrusaSlicer and Cura declare no range for this key, so nothing in the file bounds it.

The slicers disagree on the type: Cura as float, PrusaSlicer, Bambu Studio, OrcaSlicer and Creality Print as floats. 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 nozzle diameter under its own name alongside the rest of the print settings. The file stays in your browser; see what leaves it.