Orca Slicer in the Cloud for 3D Print Farms

Printago runs the real, unmodified Orca Slicer as a headless cloud engine behind your fleet. You don't have to export G-code ahead of time, and you don't even have to pick a printer before slicing. Upload a model, a parametric source, or a full 3MF project. Every time a job is assigned to a printer, Orca slices it fresh for that printer, that filament, that plate. Automatically.

One 3MF Project, Every Printer in Your Fleet

A 3MF project is tied to the machine it was sliced on. Printago decouples that. Upload a 3MF saved in Orca Slicer and the same file targets your X1C, P1S, A1, and A1 Mini. We swap in the right machine profile at slice time. All of your careful Orca Slicer work (tree supports, paint-on supports, seam painting, modifiers, multi-plate layouts, negative parts) is preserved and retargeted automatically.

• Machine profile resolved per printer, not baked into the file
• Tree supports, paint-on supports, seam painting preserved end-to-end
• Multi-plate projects slice plate by plate
• Same 3MF, different printer, correct G-code every time

Bring Your Own Orca Slicer Profiles. All of Them.

Every process, filament, and machine profile you've already tuned in Orca Slicer works in Printago. Nothing is stripped or simplified. We support Orca's full profile surface through two import paths:

• Cloud Sync: connect the Bambu Lab integration and profiles sync from your account in one click
• Manual import: upload .orca_printer, .orca_filament, and .bbscfg bundles directly, or drop in a ZIP of the lot
• Preserves inheritance: custom profiles that inherit from an Orca base profile keep their parent reference
• Auto-creates materials: imported filament profiles can seed new materials in your inventory, pre-linked for AMS matching

Re-Slices for Every Filament Color Change

Here's the one Printago does that a desktop slicer can't. When the same part runs on a printer with a different filament color, Printago re-slices with the right purge volumes for that transition. Red to dark red needs far less purging than black to white. A material variant swap automatically triggers a fresh slice, so you get clean color transitions without dialing purge volumes by hand, and without wasting filament on every job.

• Material variant overrides for color-specific filament settings
• Automatic re-slice when the assigned filament changes
• Right-sized purges per color transition, not a worst-case default
• Cache-aware: identical filament, part, and printer slice instantly from cache

Smart Caching for Faster, Consistent Prints

Cloud slicing sounds slower than having G-code on disk. Except Printago caches every slice, keyed on the exact inputs: part geometry, machine profile, process profile, filament profile, plate layout, and slicer version. If the same part runs on the same printer with the same filament a second time, we don't slice at all. We fetch the cached G-code and hand it to the printer. No recomputation. No waiting.

• Cache hits skip slicing entirely, with no "slicing…" delay at the head of the queue
• Byte-identical output every time the inputs match. The same repeat job serves the same G-code, not a re-slice that drifts.
• Automatic invalidation: any change to the part, the profiles, the printer, or the material busts the cache and triggers a fresh slice
• Warms as you work: your most-run SKUs stay hot across the fleet without any manual pre-slicing

Personalization That Slices Itself

Printago is the only platform that feeds parametric sources directly into Orca Slicer. OpenSCAD, ColorSCAD, CadQuery, and build123d files render on demand with per-order parameters, then pass straight into Orca. Every order can carry its own name, size, color map, or SKU variant, and the right geometry is generated and sliced at job time. No manual STL export, no desktop round-trip, no bespoke tooling. The parametric model becomes G-code through the same pipeline as any other part.

• OpenSCAD, ColorSCAD, CadQuery, build123d: upload the source, not an export
• Order-specific parameters like name, size, color, or SKU variant drive each render
• Orca slices the freshly-rendered geometry using your chosen profile
• One parametric source covers unlimited personalized variants without pre-exporting

Pin the Orca Slicer Version You Trust

Profile defaults drift between Orca Slicer releases. Printago keeps multiple Orca versions available and lets you pick which release's base profile values your profiles inherit from. Compare settings across versions side-by-side. Roll forward when you're ready, not when a new release happens to ship.

Headless, Automated, Integrated

Cloud slicing isn't a page you click "slice" on. It's the engine behind the entire Printago workflow. Orca Slicer slots in wherever G-code is needed.

• Smart Queue matches jobs to printers, then the cloud slicer runs Orca for that exact printer
• FabMatic Continuous Printing auto-ejects finished prints and queues the next slice without human input
• SKU Variants map e-commerce orders to parametric inputs, which Orca slices per order
• API Access lets you trigger jobs from any webhook, script, or external system, which then feed into the cloud slicing pipeline

Unmodified Upstream Orca Slicer

Printago runs the official Orca Slicer binary through its documented command-line interface. No fork, no reimplementation. G-code output is byte-for-byte what you'd get on your desktop with the same inputs. Print time, filament estimates, and quality match the desktop preview exactly.

• Real Orca Slicer, real CLI, real output
• Upstream releases roll out after a validation window, so you're always current and never surprised
• Bug fixes and features land in Printago as Orca ships them

Already Have G-code? Upload That Instead.

For teams that want absolute control over the artifact that hits the printer, Printago also accepts pre-sliced .gcode.3mf files directly. Skip the slicer entirely. Printago will hand your .gcode.3mf straight through to the assigned printer, still queued, still matched, still tracked, but without touching a byte of the G-code you produced yourself.

Also Available: Bambu Studio

Orca Slicer is one of two engines Printago runs. If you prefer Bambu Studio, for its native AMS handling, LIDAR calibration, or official Bambu profile parity, it works the same way here. Pick one as your default and override per part when you need to.

• Bambu Studio in the cloud →
• Compare the two engines →

Related Reading

• The Orca Slicer CLI, documented end-to-end
• How the 3MF file format actually works
• Calculating filament usage from G-code

Frequently Asked Questions

Does Printago modify Orca Slicer?

No. Printago invokes the official, unmodified Orca Slicer binary through its command-line interface. Output matches the desktop application exactly, byte-for-byte.

Can I use my existing Orca Slicer profiles?

Yes. Sync from your Bambu Lab cloud account with one click, or manually import .orca_printer, .orca_filament, and .bbscfg bundles you've exported from Orca Slicer.

Does cloud Orca Slicer work with paint-on supports and seam painting?

Yes. Upload a saved 3MF project from Orca Slicer and every brushed support, painted seam, modifier volume, and negative part is respected exactly where you placed it.

What if a new Orca Slicer release changes default behavior?

You can pin the Orca Slicer version your profiles inherit base values from. Compare versions side-by-side and roll forward only when you're ready.

How does color-aware re-slicing actually work?

Every material variant carries its own color and purge-volume configuration. When a job is assigned to a printer loaded with a different color than the last job, Printago re-slices with purge volumes tuned for that specific color transition. A small transition uses less purge, a large one uses more. You don't configure this per job. You configure your material variants once, and the cloud slicer handles the rest.

Can I mix Orca Slicer and Bambu Studio in the same farm?

Yes. Set an engine default for your store, then override per part. Different parts can target different engines, and Printago runs each through its chosen slicer.

Does cloud Orca Slicer work with Klipper, Prusa, or other printers?

Yes. One of the main reasons to pick Orca Slicer over Bambu Studio is its broad printer support. Orca ships profiles for Prusa, Voron, Creality, Sovol, Elegoo, Anycubic, and many other Klipper and Marlin machines that Bambu Studio doesn't cover. If you run a mixed-brand farm, Orca is the engine that keeps the whole fleet on one profile surface. That, plus the community-driven tuning and calibration tools, is why a lot of farms run Orca even when their printers are Bambu.