How to Export and Import Settings in PrusaSlicer

PrusaSlicer settings move between computers through File > Export and File > Import. To migrate a full setup, use Export Config Bundle on the source machine and Import Config Bundle on the target. Once a profile is dialed in, you should not rebuild it on a second machine or lose it on a reinstall. This guide covers exporting, importing, why a bundle import sometimes looks empty, and where the files live.

Export a single config or the whole bundle

PrusaSlicer gives you two export choices under File > Export:

• Export Config: writes only the currently active configuration (the selected print, filament, and printer preset) to one .ini file. Good for sharing a single tuned profile.
• Export Config Bundle: writes all of your saved presets to one .ini bundle. This is what you want for moving or backing up an entire setup.

Import on the other machine

Match the import to how the file was exported, under File > Import:

• Import Config for a single .ini config.
• Import Config Bundle for a bundle.

Point it at the file and the presets appear in your print, filament, and printer dropdowns.

When the import looks empty

"Config bundle not importing anything" is almost always one of these:

• Wrong menu item. Importing a single config with Import Config Bundle, or a bundle with Import Config, can silently bring in nothing. Match the item to the export.
• Version gap. A bundle from a much newer PrusaSlicer can fail to import cleanly into an older one. Import with the same or a newer version.
• Nothing looks new. PrusaSlicer does not always pop a confirmation. Check the preset dropdowns directly; the profiles may already be there.

Where the profiles live

To copy files directly, PrusaSlicer keeps its configuration here:

• Windows: %APPDATA%/PrusaSlicer
• macOS: ~/Library/Application Support/PrusaSlicer
• Linux: ~/.config/PrusaSlicer

Your custom presets are in the print, filament, and printer subfolders. Copying the whole folder to another machine migrates everything, which is the most reliable option for backups or a clean reinstall.

Because PrusaSlicer is the root of the OrcaSlicer family (see OrcaSlicer forks compared), its .ini configs also import into OrcaSlicer and its forks in most cases.

Why this matters for a print farm

Export and import is the manual version of a problem that scales badly: keeping every machine on the same tuned profiles. Doing it by hand means exporting bundles, copying them around, and hoping no printer drifts out of sync. A farm needs one source of truth instead.

Printago imports your existing PrusaSlicer profiles into the cloud slicer and applies the one you tuned automatically on every printer in the queue, with no bundles to shuffle between machines. See the PrusaSlicer overview, how to set up a 3D print farm, and print farm slicing.