File name format
The template used to name the file when you export the G-code: model name, filament, time… The words in curly braces are replaced with the real data.
How it works
When exporting, the slicer builds the file name from this template. Each {field} is replaced with its real value: {input_filename_base} is the model name; {filament_type[0]}, the type of the first filament; {print_time}, the estimated time; {layer_height}, the layer height; and {printer_model}, the printer.
The A1 profile uses name, filament and time, so two exports of the same model with different settings don't get the same name.
When to change it
- If you don't export files by hand, leave it as is (it isn't used when printing from the program).
- You keep several versions of the same part with different layer heights on an SD card: add {layer_height}mm and {printer_model} to tell them apart.
Typical values
| Value | What for |
|---|---|
| {input_filename_base}_{filament_type[0]}_{print_time}.gcode | Defaultdefault |
| {input_filename_base}.gcode | Name only |
Watch out for
- Only visible in developer mode.
- A misspelled field in curly braces makes the export fail.
Goes well with
What Bambu Studio saysits help card, quoted
What Bambu Studio says
User can self-define the project file name when export
Bambu Studio tooltip for this setting · AGPL-3.0
Read more at the official source
In other slicers
- Orca Slicer
- Filename formatOthers › G-code output
- PrusaSlicer
- Output filename formatOutput options › Output file
- Cura
- No clear equivalent.
Names taken from each program's code (Orca Slicer 2.4.2, PrusaSlicer 2.9.6, Cura 5.13.0). Credits