OrcaSlicer Import
Bring your profiles. PrusaSlicer profiles import natively. OrcaSlicer profiles go through a 230+ setting mapping engine with value transforms, G-code macro translation, and inheritance resolution. A detailed report shows exactly what transferred, what was converted, and what was dropped.
Setting Expectations
No two slicers share the same settings. OrcaSlicer has over 140 settings that are exclusive to Orca and have no equivalent in any other slicer. They can't be imported because there's nothing to import them into. The same is true in reverse: preFlight has exclusive settings that no other slicer has.
Cross-product profile import is rare for good reason. preFlight maps everything it can, and reports everything it can't. That report isn't a list of failures. It's a transparency log so you know exactly where your profile stands after import.
Not a Copy-Paste
Switching slicers shouldn't mean starting over from scratch. preFlight imports OrcaSlicer printer, filament, and process profiles directly from .orca_printer, .orca_filament, and .zip bundles. But it doesn't just dump settings into a config file and hope for the best. Every setting passes through a mapping engine that translates, converts, and validates, then tells you exactly what happened.
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
The transformed mappings are where the real work happens. These aren't approximations. Each one has specific conversion logic:
| 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 |
enable_arc_fitting = 1 | arc_fitting = "emit_center" | 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 supports multiple bed plate types (Cool Plate, Engineering Plate, High Temp Plate, and more) with separate temperatures for each. preFlight uses a single bed temperature per profile. The importer intelligently selects from your configured temperatures, preferring non-zero values in priority order, and reports the mapping as lossy so you can verify the result.
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 via a ~90-entry alias map, 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 system profile defaults. When your profile references a parent like Generic PLA @Creality, preFlight looks up that parent and fills in any settings your profile didn't explicitly set. It tracks which settings were intentionally customized vs. inherited so the merge never clobbers your overrides.
If a parent can't be resolved, that's reported too. Nothing gets silently lost.
The Import Results Dialog
This is what sets preFlight's import apart. After processing your bundle, you get a full categorized breakdown:
Imported Profiles
A list of every printer, filament, and process profile that was successfully created, with a count of how many settings mapped cleanly for each.
Lossy Mappings
Settings that imported but with reduced fidelity. You see exactly which setting, which profile, and what information was lost. Common examples: multiple bed plate temperatures collapsed to one value, or a range setting mapped to a single point.
Orca-Exclusive Settings
Settings that exist only in OrcaSlicer and have no preFlight equivalent. These are clearly labeled "Orca-Exclusive" with an explanation of why they were skipped. Every key is listed so you know exactly what wasn't carried over and why.
G-code 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, you're prompted before anything gets overwritten. "Yes to All / No to All" buttons handle large imports without clicking through every duplicate. Your existing work is never silently replaced.
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. Select what you want to import, and the engine handles the rest.