In this guide, we'll cover how to import profiles in PrusaSlicer that are not included with the software, and how to export your custom PrusaSlicer profiles. Some 3rd party vendor profiles are already included with PrusaSlicer (e.g. Lulzbot or Creality printers).
A profile is a combination of print settings, filament settings, and printer settings. A profile, or a bundle, is saved in .ini format.
How to import custom profiles
Navigate to File -> Import. There are three possible options for importing custom profiles.
- Import Config: import a single profile. This function accepts .ini, but also .gcode files. When importing a profile through a G-code, this has to be sliced using PrusaSlicer.
- Import Config from Project: import a single profile from a project file. This function accepts only projects saved with PrusaSlicer, with .3mf and .amf format.
- Import Config Bundle: imports all the configuration settings for multiple profiles. This function accepts .ini files.
How to export custom profiles
Navigate to File -> Export. There are three possible options for exporting custom profiles.
- Export Config: export current profile.
- Export Config Bundle: export all custom settings saved in your current PrusaSlicer version.
- Export Config Bundle with Physical Printers: export a Config Bundle, plus the API key and IP address.
8 comments
Log in to post a comment
filip.m3
•
I have a new computer, so I want to migrate all my settings to it. So I did the so-called "Export Config Bundle With Physical Printers". I imported this in the new computer PrusaSlicer app. It turns out that my custom filament - so called "User Presets", that I have created, that work well for certain filaments did all not transfer. I select the "add/remove filaments" and I get this huge 'wizard' that goes through 11 things, one of which is filaments, but its number 6 in the list, and I need to go through the to 5 first. I think, I don't want to do this, I could really screw something up here. I just want to move a couple presets. I want to migrate just these to a new computer, so I select them as if I want to slice, then I tried the so-called "Export Config", but on import they don't come through as-is with the names I gave them. They seem to modify others in the big list of filaments. I am just going to rekey them. Big Sad. I've had my Prusa printer (an upgraded MK2) for so long I don't remember. I can't imagine being a new printer owner and going through this.
BarrittWorks
•
I agree. I also struggle with the meanings, relationships, and management of the various settings, profiles, printers (physical printers), and configuration structures in PrusaSlicer. Clear as mud. Seems as if a serious redesign of these structures (and/or language along with support documentation) is in order.
BarrittWorks
•
Update some hours later: I've found some community discussion that made the intended structures clearer (such as here: https://forum.prusa3d.com/forum/prusaslicer/prusaslicer-2-3-printer-settings-physical-printers-confusion/paged/2/) and I've spent a few hours clearning out mistaken physical printer entries and regularizing the associated presents and profiles that had built up over the past years (and across a couple of printers). Back on track functionally now, but the concern about the communication about, and labeling, of these structures remains.
Martin Dravecky
•
To share printer, print & filament custom configurations (more possible with simple script update), I've created windows batch file, which redirects default configuration folders to some public path in filesystem, or even online synchronized filesystem path (e.g. GDrive). Execute it under each desired account of same computer, or with synced drive with as many physical computers as you want. Script is guided and allows binding or unbinding as desired.
1. Copy desired config folders from %APPDATA%\PrusaSlicer folder to shared folder, along with my link settings.bat script file.
2. Run script at all desired devices (to perform binding, "run as admin" is required) and select action to perform (bind|unbind)
1. Copy desired config folders from %APPDATA%\PrusaSlicer folder to shared folder, along with my link settings.bat script file.
2. Run script at all desired devices (to perform binding, "run as admin" is required) and select action to perform (bind|unbind)
SlicedShark
•
I have used one original laptop with Prusa Slicer installed on it for 3 years. I need to move all my created tuned print settings to a new laptop that I am now also using for Prusa Slicer. I agree with all the comments above, the help and instructions provided is perfectly unclear. Where are the .ini files stored in my original laptop automatically by Prusa Slicer? Are the configuration .ini files seperated into "Print Settings", "Filament Settings", and "Printer Settings" profiles or are they only part of existing .3mf files? Are the profile files extractable seperately from a .3mf file or only as a group from a specified .3mf file? Where to save them so Prusa slicer can use them. There must be an easy way to copy, extract, and/or import one or more tuned setting profiles users have created over the years for different filaments, prints and printers from, for example, an original computer to another computer so that different installs of Prusa Slicer can use the profiles on each computer. Please provide a link to an instruction location that explains how to do this.
ShelM
•
I agree - it all sounds logical enough, but I somehow can't grasp the required work flow. e.g. I have a profile that I want to use often - what type ini file should I save. Where should I store it? Are there any items which will end up not being saved (except for the .stl of course)? How does this relate to the selection of printer? Thank you muchly for any response you can give to this problem which is vexing me. 8^)
Jan Kratochvíl
•
Hello. If you want to use your custom profile more often, you don't have to save the .ini profile anywhere. You can create your profile and then save it in PrusaSlicer. Exporting is when you want to use that profile in different slicers or on different computers.