Infill extruder (infill_extruder)
Infill extruder is a slot number, counted from one. PrusaSlicer accepts 1 or more; Bambu Studio and Creality Print accept 0 or more; OrcaSlicer 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 | infill_extruder |
process |
| Bambu Studio | sparse_infill_filament |
process |
| OrcaSlicer | sparse_infill_filament |
process |
| Cura | infill_extruder_nr |
process |
| Creality Print | sparse_infill_filament |
process |
What does each slicer say about it?
Each slicer offers its own values, so each gets its own line.
- PrusaSlicer: Extruder number that prints infill on multi-material printers. The first is 1.
- Bambu Studio: Which filament slot prints sparse infill. 0 uses the object's filament.
- OrcaSlicer: Extruder number used for sparse infill. Zero uses the object's own extruder.
- Cura: Which extruder prints infill. -1 uses the default extruder.
- Creality Print: Which filament prints sparse infill. Zero uses the object's main filament.
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 infill_extruder, sparse_infill_filament and infill_extruder_nr, 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 | int | not declared | 1 |
1 or more |
| Bambu Studio | int | not declared | 0 |
0 or more |
| OrcaSlicer | float | not declared | 0 |
not declared |
| Cura | int | not declared | -1 |
not declared |
| Creality Print | int | not declared | 0 |
0 or more |
OrcaSlicer and Cura declare no range for this key, so nothing in the file bounds it.
PrusaSlicer, Bambu Studio, OrcaSlicer, Cura and Creality Print declare no unit for it either, so the bare number is read as a slot number, counted from one.
The slicers disagree on the type: OrcaSlicer as float, PrusaSlicer, Bambu Studio, Cura and Creality Print as int. 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 infill extruder under its own name alongside the rest of the print settings. The file stays in your browser; see what leaves it.