Infill/wall overlap (infill_wall_overlap)

Infill/wall overlap is a number in percent. No slicer declares a 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_overlap process
Bambu Studio infill_wall_overlap process
OrcaSlicer infill_wall_overlap process
Cura infill_overlap process
Creality Print infill_wall_overlap process

What does each slicer say about it?

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

  • PrusaSlicer: How far infill pushes into the walls, in mm or percent of line width. More overlap bonds better but can bulge.
  • Bambu Studio: How far infill reaches into the walls, as a percent of infill line width. More improves bonding; too much shows outside.
  • OrcaSlicer: How far infill extends into the walls, as a % of line width. More overlap bonds better but can show on walls.
  • Cura: How far infill reaches into walls, as a % of line width. A bit of overlap bonds them.
  • Creality Print: How far infill extends into the walls, as a % of line width. More overlap bonds better but can bulge walls.

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_overlap and infill_wall_overlap, 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 % 10 not declared
Bambu Studio percent % 23 not declared
OrcaSlicer percent % 15 not declared
Cura float % 0 not declared
Creality Print percent % 23 not declared

PrusaSlicer, Bambu Studio, OrcaSlicer, Cura and Creality Print declare no range for this key, so nothing in the file bounds it.

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