First-layer bed temperature (first_layer_bed_temp)

First-layer bed temperature is a number in °C. Bed temperature of the initial layer.

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.

Where does it live in the file?

All five slicers file this under the filament preset, so its value follows the filament rather than the model. A .3mf is a zip, so unzip it and search for first_layer_bed_temperature, hot_plate_temp_initial_layer and material_bed_temperature_layer_0, 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.

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.

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

The slicers disagree on the type: PrusaSlicer and Cura as float, 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 first-layer bed temperature under its own name alongside the rest of the print settings. The file never leaves your machine, and nothing uploads.