DeslicebetaES

Process › Others› Post-processing scriptspost_process

Post-processing scripts

Your own scripts (small programs) that run on the freshly generated G-code, before it's saved, to modify it. Advanced users only.

How it works

Here you enter the paths to one or more scripts, separated by semicolons. When exporting, the slicer runs them and passes them the path to the G-code file; the script can read it and change it: insert commands, change temperatures by layer or add pauses.

A script with bugs leaves a broken file without anything warning you.

When to change it

  • For almost everything: empty (default).
  • You want to insert a specific command every 10 layers, or change the temperature in steps on a test tower, and you know how to code it: put your script's path here.

Typical values

ValueWhat for
EmptyDefaultdefault
Path to scriptYour own automations

Watch out for

  • The script also receives the slicer's settings as variables.
  • Before printing, always check the result in another program's preview.

Goes well with

Filename formatAdd line number
What Bambu Studio saysits help card, quoted

What Bambu Studio says

If you want to process the output G-code through custom scripts, just list their absolute paths here. Separate multiple scripts with a semicolon. Scripts will be passed the absolute path to the G-code file as the first argument, and variables of settings also can be read

Bambu Studio tooltip for this setting · AGPL-3.0

Read more at the official source

Bambu Lab wiki (index)

In other slicers

Orca Slicer
Post-processing ScriptsOthers › Post-processing Scripts
PrusaSlicer
Post-processing scriptsOutput options › Post-processing scripts
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