Your project. Any slicer.
Bambu Studio and its family — OrcaSlicer, Snapmaker Orca, FlashForge Studio, ElegooSlicer, Anycubic Slicer Next, Creality Print, QIDI Studio — store projects in one shared format, but each only loads the settings when the file looks like its own and names a printer it knows. This rewrites that part for the target machine and leaves the geometry alone.
- 8
- slicers
- 418
- printer models
- 68
- brands
Printer
Loading printers…
The file is read and converted on your machine — nothing is uploaded.
How it works
It rewrites the settings and never touches the geometry.
All eight slicers here grew out of Bambu Studio's code, so their projects share one layout: the meshes with painted supports, seams and colours in 3D/, per-object and plate settings in model_settings.config, and every print setting in one JSON file. They differ in three places: the “Application” line that tells the program who saved the file — get it wrong and only the geometry loads; which settings each slicer has, and how it spells their values; and the names of the printer, process and filament presets.
The tool rebuilds the settings file over the target's own system presets: printer settings are the target machine's, whole; process and filament settings are the source's wherever the target has that setting and the value is legal there — re-spelled where two slicers name the same choice differently, like Bambu's “zig-zag” and Orca's “rectilinear”. Then it lists every key that differs from the stock preset in different_settings_to_system — without that list the slicer quietly resets everything you carried back to its preset.
The printer data, setting schemas and the way each slicer writes its file are read straight from the source code and profiles each slicer ships, not typed by hand. ZORVA opened and sliced converted files with the command-line builds of Bambu Studio 2.8, OrcaSlicer 2.4.2, ElegooSlicer 1.5.3, QIDI Studio 2.07, Creality Print 7.3 and FlashForge Studio 1.7.18 — including a two-plate project moved onto a smaller bed. Snapmaker Orca 2.4.0's command line crashes on every 3MF project, its own files included, and Anycubic Slicer Next has not been checked with Anycubic's own build; files for those two follow the same checked layout, but slice once before you print.
Why does another slicer load only the geometry from a Bambu file?
Each slicer reads the “Application” line in the file to decide whether to trust the settings. Bambu Studio only loads settings from files that say “BambuStudio-…”, and even then it needs printer, process and filament names it actually has. This tool writes exactly those for the slicer you pick.
Do painted supports, seams and multi-colour survive?
Yes. They live in the meshes under 3D/, and all eight slicers read the same painting format. The tool leaves those files alone — it only renames the namespace when going to or from QIDI Studio, which uses its own.
What if the target bed is smaller?
A plate that still fits moves as a group, keeping its offset from the bed centre. A plate that no longer fits is repacked in rows — leaving room for brims, the machine's excluded zone and the wipe tower — with any overflow on new plates at the end, checked against the bed's real shape, round delta beds included. A part bigger than the new bed is not scaled — the report names it and its size so you can decide.
What about PrusaSlicer?
PrusaSlicer stores projects in a different format altogether (Slic3r_PE.config), not the layout these eight share. Orca-family slicers already open the geometry and painting of a PrusaSlicer file; the print settings have no safe path across, so the tool doesn't pretend.
Is my file uploaded anywhere?
No. The file is read and converted inside your browser tab. The only thing fetched from ZORVA is the printer list and presets of the slicer you pick.