Move a profile from PrusaSlicer to Orca or Bambu Studio
Slicer profile converter: drop in an .ini from PrusaSlicer or a .json from OrcaSlicer or Bambu Studio, choose the slicer you move to and get a file with the translated settings and a table of every change.
Opens with a free account.
- 3 slicersPrusaSlicer, Orca and Bambu Studio
- .ini and .jsonthe files it reads
- A table of changesold and new value
- Free accountneeded to open it
What a slicer profile converter is
A slicer profile converter copies the settings of one slicer’s profile into a profile for another. Each slicer names a setting differently: the nozzle temperature is “temperature” in PrusaSlicer and “nozzle_temperature” in OrcaSlicer.
The screen offers PrusaSlicer, Cura, OrcaSlicer and Bambu Studio, but today PrusaSlicer, OrcaSlicer and Bambu Studio work. You drop in the file, pick the target slicer and download the new profile or copy the settings as text.
The file is read and translated in your browser and is not sent anywhere.
What the converter does with a PrusaSlicer, Orca or Bambu profile
Translates a profile from one slicer to another
Drop in an .ini from PrusaSlicer or a .json from Orca or Bambu Studio and download a file for the target slicer: .json for Orca and Bambu Studio, .ini for PrusaSlicer.
Shows every change in a table
The table compares the source and target value of each setting and labels it direct, renamed, computed or semantic.
Translates many files and many slicers
The “Групово преобразуване” (Bulk conversion) tab takes several files and returns one ZIP, and “Multi” translates one profile for several slicers.
Warns and suggests
It warns about a nozzle above 300 °C, a bed above 120 °C, a retraction above 10 mm or a missing layer height and offers up to six tips. “Приложи” (Apply) changes a value for three of them only; for ironing and tree supports it writes keys OrcaSlicer does not know.
When you need to move a profile to another slicer
You translate a profile when you change slicer and do not want to set everything again by hand.
Moving from PrusaSlicer to OrcaSlicer
You drop in the .ini file and get a .json profile for OrcaSlicer.
Moving to Bambu Studio
You translate the profile into a .json file. The nozzle temperature is written for the first layer only: check it in the file.
Preparing profiles for a whole class
Bulk conversion translates many files at once into one ZIP.
Comparing values before and after the translation
The table shows the value before and after, for example 110% becomes 0.44 mm with a 0.4 mm nozzle; the names of the setting in each slicer are not shown.
How a profile from one slicer becomes a profile for another
The translation follows a dictionary of 524 entries (about 400 different settings): each says what a setting is called in PrusaSlicer, Orca and Bambu Studio and how its value is converted. For Cura, 64 entries share one key.
The file is read
The extension picks the reader: .ini for PrusaSlicer, .json for Orca or Bambu Studio, .curaprofile for Cura (it does not read files from the real Cura yet).
Settings are looked up
Each setting is looked up in the dictionary and gets its name in the target slicer; missing ones are skipped.
Values are converted
Percents for line width become millimetres (eight settings); a percent for speed becomes a plain mm/s number. Booleans become 1 and 0, pattern and mode names are swapped by table (nine tables, 26 values); Cura names such as tetrahedral stay unchanged.
The file is written
The format of the target slicer: .ini for PrusaSlicer, .json for Orca and Bambu Studio, .curaprofile for Cura.
| Applies to | Formula | Meaning |
|---|---|---|
| Line width | mm = % ÷ 100 · nozzle diameter | 110% with a 0.4 mm nozzle becomes 0.44 mm (written as 0.44000000000000006) |
| Infill in percent | 15% → 15 | in the .json for Orca and Bambu the number gets its “%” back, in the .ini for PrusaSlicer it stays without “%” |
| Infill pattern | honeycomb → tetrahedral; stars → concentric | honeycomb becomes tetrahedral only in Cura, stars becomes concentric in Cura, Orca and Bambu Studio |
A table of every change and tips after the translation
You pick the source and the target slicer
You choose the source and the target slicer.
A table of every change
Each setting has its source value, target value and a kind label.
The file does not leave the browser
The translation happens in the browser, not on a server.
The file for PrusaSlicer does not load as it is: the app writes the infill density as a plain number (fill_density = 20), and PrusaSlicer 2.9.6 answers “Value out of range: fill_density”. With “fill_density = 20%” it loads, so add the “%” by hand.
Cura does not work yet: the reader looks inside a .curaprofile for a file with the .inst.cfg extension, but Cura 5.4.0 stores its files in the archive without an extension, so a profile exported from Cura is not read; and Cura 5.4.0 does not import the .curaprofile the app writes (by the Cura code, not tried in Cura itself).
The translation follows a dictionary and has not been checked setting by setting. A setting with a word instead of a number (fuzzy_skin = none) is flipped: “none” becomes 1, that is on, labelled “direct”. The nozzle temperature for Bambu Studio is written for the first layer only. The .json files have not been tried in Orca and Bambu Studio, G-code is copied as text, and an inherited system profile is translated only with what the file holds. The screen is in Bulgarian.
Questions about converting slicer profiles
How to convert PrusaSlicer profile to Orca Slicer?
Choose PrusaSlicer as the source and OrcaSlicer or Bambu Studio as the target, drop in the .ini file and download the .json profile and make a test print. Cura is not read yet.
Can I use PrusaSlicer profile in Orca Slicer?
In part: the converter translates the settings into a .json for Orca; importing it into Orca is untested. Compare the table and run a test print.
Which slicers work in the converter?
Profiles for PrusaSlicer, OrcaSlicer and Bambu Studio are read and written. The screen offers Cura too, but it does not work yet.
Can I convert several profiles at once?
Yes. Bulk conversion takes many files and returns one ZIP; Multi translates one profile for several slicers.
Is my profile uploaded to a server?
No. The file is read and translated in your browser.
Will the translated profile print the same as the old one?
Not guaranteed: some settings have no exact match. Compare the table and run a test print.
Is the converter in English?
No. The screen is in Bulgarian, with the tabs “Единичен файл” (Single file) and “Групово преобразуване” (Bulk conversion).
The slicer profile converter opens with a free account. Pro opens the rest
Pro costs 15 EUR a month and opens 45 Pro tools.
Related tools
SliceAGENT: slicer profiles3D printer slicer profiles: 4093 ready profiles for PrusaSlicer, OrcaSlicer, Bambu Studio and Cura plus an AI helper. Free account; an AI question is 3 credits.
Slicer settings visualizerSlicer settings explained: 90 settings with a drawing, 53 with a slider, the reason and the trap. Search by symptom. Free account. The screen is in Bulgarian.
Slicer profile generatorSlicer profile generator: an AI assistant builds slicer settings for your printer, material and goal as an .ini file with reasons. Ultra, 39 EUR a month.
First layer diagnosisFirst layer problems: pick what you see on the bed, your filament and printer, and get causes, fixes and a slicer profile. Needs a free account.
Take your settings to the new slicer
Opens with a free account.