OrcaSlicer Import
PrusaSlicer and SuperSlicer profiles import natively. OrcaSlicer profiles go through a 230+ setting mapping engine that converts values, translates G-code macros and resolves profile inheritance, then reports every setting it dropped and every value it had to collapse.
Setting Expectations
No two slicers share the same settings. OrcaSlicer has over 140 settings with no preFlight counterpart. Most exist only in Orca, and a few control features preFlight deliberately does not offer, such as arc fitting. They can't be imported because there's nothing to import them into. The same is true in reverse: preFlight has settings no other slicer has.
Cross-product profile import is rare for good reason. preFlight maps everything it can, reports everything it cannot, and tells you which settings need a look before you print.
How the Mapping Works
preFlight imports OrcaSlicer printer, filament and process profiles directly from .orca_printer, .orca_filament and .zip bundles. Every setting passes through a mapping engine that translates the key, converts the value where the two slicers disagree on units or meaning, and records what it did.
The engine handles 230+ OrcaSlicer settings across three tiers:
- Direct: Same key name, compatible value. No translation needed.
- Renamed: Different key name, same value semantics.
retraction_lengthbecomesretract_length. - Transformed: Different name and/or value format. Enum translations, boolean-to-enum conversions, percentage-to-absolute acceleration math, and more.
Value Transforms
Transformed mappings carry specific conversion logic for each setting:
| Orca Setting | preFlight Setting | Transform |
|---|---|---|
wall_sequence = "outer wall first" | external_perimeters_first = 1 | Enum to boolean |
print_sequence = "by object" | complete_objects = 1 | Enum to boolean |
only_one_wall_top = 1 | top_one_perimeter_type = "top_surfaces" | Boolean to enum |
emit_machine_limits_to_gcode = 1 | machine_limits_usage = "emit_to_gcode" | Boolean to enum |
wall_generator = "arachne" | perimeter_generator = "Arachne" | Case normalization |
sparse_infill_pattern = "zig-zag" | fill_pattern = "rectilinear" | Pattern name translation |
Other automatic transforms include shrinkage compensation scale inversion (OrcaSlicer's 100% = no shrinkage vs. preFlight's 0% = no compensation) and acceleration percentage resolution (OrcaSlicer's percentage-of-default converted to absolute mm/s²).
Bed Temperature Mapping
OrcaSlicer keeps a separate bed temperature for each plate type (Cool Plate, Engineering Plate, High Temp Plate, and more). preFlight has one bed temperature per profile. The importer takes the first non-zero value in a fixed plate order and reports the mapping as lossy so you can check it.
Custom G-code
OrcaSlicer and preFlight use different names for many of the same settings. preFlight's G-code engine resolves Orca variable names automatically through an alias map of more than 100 entries, so [nozzle_temperature_initial_layer] resolves to first_layer_temperature at slicing time without any import-time conversion. This works in both [bracket] and {brace} syntax.
The importer still handles brace-syntax vector index fixup (appending [0] to vector variables that need it) and flags any Orca-only placeholders that have no preFlight equivalent so you can address them manually.
Inheritance Resolution
OrcaSlicer profiles often inherit from @System parent profiles. Your filament config might only define the settings you changed, relying on the parent for everything else. preFlight resolves this inheritance chain during import so your imported profile is complete and self-contained.
The importer ships with a bundled database of OrcaSlicer's generic filament defaults. When a filament references a parent like Generic PLA @System, preFlight looks it up there and fills in any settings your profile didn't explicitly set. Vendor parents, Generic PLA @Creality for example, resolve when they are in the same bundle or already installed. Either way it tracks which settings you customized and which were inherited, so the merge never clobbers your overrides.
If a parent cannot be resolved, the report says which one.
The Import Results Dialog
After processing your bundle, preFlight shows a breakdown in five groups:
Imported Successfully
Every printer, filament and process profile that was created, grouped by type.
Imported with Changes
Settings that imported with a value preFlight had to collapse. Today that is the bed temperature: the entry names the profile, the plate whose value was kept and the plates that were ignored.
Skipped Settings
Keys with no preFlight counterpart, either because they exist only in OrcaSlicer or because they control a feature preFlight does not offer. Every skipped key is named so you know exactly what was not carried over.
Unresolved Inheritance
Profiles whose parent could not be found in the bundle, in your installed presets or in the bundled defaults. Check those profiles' settings before printing.
GCode Warnings
Any G-code placeholders that couldn't be fully translated. Each warning shows the profile name, the G-code field, and the specific placeholder that needs attention.
Overwrite Protection
If a profile with the same name already exists, preFlight asks before overwriting it. "Yes to All" and "No to All" cover a large import without a click per duplicate.
What Doesn't Import
Some OrcaSlicer features don't have preFlight equivalents, and we don't pretend they do. Settings related to Orca's multi-plate system, SoftFever-specific acceleration models, and certain Klipper-exclusive features are recognized but intentionally excluded. They show up clearly in the dropped settings report so you can decide how to handle them in your new workflow.
Supported Formats
| Format | Contents |
|---|---|
.orca_printer | Single printer profile bundle |
.orca_filament | Single filament profile bundle |
.zip | Multi-profile bundle (any combination of printer, filament, process) |
Import via File > Import > Import OrcaSlicer Bundle and pick the profiles you want from the bundle.
SuperSlicer config bundles import as well. Blank extrusion widths fall back to auto and a host type of "klipper" maps to Moonraker. Importing a bundle from another slicer warns that its settings may not translate exactly.