PrusaSlicer Post-process Config Helper

This webpage can automatically do the preparation of the .ini file as described in the installation instructions for my FFCP PrusaSlicer config bundle.

First enter your PATH value here:
Optional: enter the full final path where you placed the bed model STL file:
Optional: enter the full final path where you placed the bed texture PNG file:

Now select the appropriate .ini file you downloaded from the repository:

And then click this button to obtain the transformed file:

A download should start automatically, the file will have the same name as the one you selected, but with “transformed” appended.
If your browser refuses to download the file due to the .ini extension, you can either temporarily disable this protection (e.g., ‘SmartScreen’ in Edge), or try this button instead: . This provides the result as a plain text file. After downloading it, you must change its extension from “.txt” back to “.ini”.

When you have your modified INI file, you can proceed according to the instructions.


If for some reason you only want to do the conversion between PATH and trans_PATH, you can use these buttons: and

The trans_PATH value will appear here:

Background info

What this does, is updating all lines starting with “post_process =” with the PATH value, after inserting the correct escape characters. You can use this tool in any scenario where you need to change the post-processing script to the same path for all print settings in an exported config bundle.

If the “240°C” checkbox is not enabled, the script will also cap all temperatures in the ini file to 240°C, to avoid frying PTFE liners in stock extruders. You will not have optimal results with certain materials in this case, and you should not even attempt to print polycarbonate. If you have upgraded to all-metal hot-ends, enable this checkbox to preserve the higher temperatures in the config.

This all runs within your browser and assumes you are using a relatively modern browser. If you are using some antique version of IE, it will likely not work.
Providing the download of the modified file works by the grace of FileSaver.js.