Save Project and Export Make Different Promises
File > Save Project writes a project file that keeps the objects, print settings and configurations you need to continue working. Export Model writes geometry instead — an STL mesh, or a generic 3MF that the OrcaSlicer wiki's import and export reference describes as carrying no printer, material or process information. Sliced output is a third thing: G-code or Gcode.3MF is print output, not an editable plate.
Orca Slicer treats those as two different jobs, not two names for the same file. That distinction is the whole decision.
The extension alone does not settle it. A .3mf can be a saved project, a generic geometry file, or a sliced plate package, depending on which command produced it. The same wiki page notes that some 3MF files contain printer, material and process information, that Orca Slicer will try to apply that information on import, and that incompatible information is ignored. So "it is a 3MF" tells you the container, not the contents.
The Five Formats, Matched to the Task
Task | Action | Retains | Not guaranteed |
|---|---|---|---|
Continue editing later | File > Save Project | Objects, print settings, configurations | Portability to another slicer or a future app version |
Share the model's geometry | Export Model > Generic 3MF | Object and assembly geometry | Printer, material or process information |
Share plain geometry | Export Model > STL | Triangulated surface geometry | Settings, colors, materials, modifiers, CAD feature history |
Print on one specific machine | Export sliced G-code | Toolpaths and print instructions | Editable geometry; correct behavior on a different printer |
Print or archive one sliced plate | Export Gcode.3MF | G-code plus printer, material and process information | A substitute for a deliberately saved editable project |
Read the middle columns carefully. These commands serve different handoffs. An STL or generic 3MF preserves geometry that a recipient can import and arrange again; generic 3MF may preserve multiple objects or assembly geometry, but it does not carry the printer, material or process information identified in the official documentation. Do not assume that geometry-only export preserves the original project's modifiers or complete editing state. Reapplying settings is redoing work, not restoring the saved project. Sliced G-code is different again: it contains printer toolpaths, not the original editable model scene, and viewing those toolpaths is not recovering the project.
Preset Bundles Are Settings, Not a Plate
Preset exports answer a different question. The same wiki reference lists a .orca_printer bundle that includes the printer and the filament and process presets belonging to it, a .orca_filaments bundle for your filament presets, and category .zip exports for printer, filament or process presets on their own. These are reusable configurations, not full plate projects: they do not carry the objects you arranged. If the real problem is a preset that will not appear after import, follow the missing filament profile checklist instead of switching export formats.
A Two-File Handoff That Keeps Both Doors Open
This example is illustrative, not a measured test. Suppose you have finished a bracket and expect one more revision.
- Save the editable version with Save Project as
bracket-edit.3mf. That file is for the next session: the objects, modifiers and settings you chose. - Export the print version separately —
bracket-print.gcode, or a supported sliced 3MF if you want the printer, material and process information bundled with the toolpath — after confirming the intended printer profile. - Use names that say which file is which, and do not overwrite the original project with the print file or the reverse.
Two separate files are a practical organisation choice, not a limit of the format: some 3MF packages can carry both project and sliced information. Deliberately named edit and print outputs simply make it obvious which file is which. The recipient's need still decides what you send. Someone who must reposition an object on the plate or change infill needs the project; a saved project preserves slicer-side objects and settings, but it does not carry parametric CAD wall editing or CAD feature history, so geometry changes still belong in the CAD source. Someone who only has to run the job needs output matched to their machine.
Menu wording can differ between Orca Slicer builds, so match the labels in your installed version against the current documentation rather than assuming the exact text. The release verification guide explains how to confirm which version you actually have. No plugin or pre-release build is required for the distinction above.
Verify the Saved Copy Before You Close the Session
Saving is not proof. Before you close the working session, open the saved copy in a separate session or window if your build supports it — or keep the original safely in place until the check is done — and confirm:
- the objects and modifiers you expect, including any negative or support parts;
- the printer and nozzle selection;
- the filament and process presets;
- object orientation and the plates you intend to use;
- the slice result again before sending anything.
Fill in a blank log yourself; a successful save dialog is not verification. A project that opens with the wrong printer profile is still the wrong file.
File | Action | Source version | Objects / modifiers | Printer / nozzle | Material / process | Result |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
Before You Print Someone Else's File
Two habits can reduce the risk. First, do not let an unfamiliar 3MF import its embedded machine settings without review. It may carry a configuration that is compatible enough to load and different enough to change your result. Second, do not print a G-code file that was sliced for another machine. Check the target printer, nozzle and material before you send it.
The short version: save a project when someone needs to keep editing, export geometry when someone needs the shape, and export sliced output only for a named machine. Keep both files, name them clearly, and reopen the project once before you close the session.
