Skip to main content

Cloud Slicer

Key Concepts

The cloud slicer is Printago's on-demand G-code generation system. Instead of pre-slicing your models for every possible printer and material combination, Printago slices each job just in time—only after a specific printer has been assigned by the queue. The slicer combines three profile sources (machine, process, and filament) to produce G-code optimized for the exact printer, nozzle, and material being used. Results are intelligently cached, so repeat jobs with the same configuration slice instantly on subsequent prints. This approach means a single uploaded part works on any compatible printer in your fleet without manual re-slicing, and changing a profile or material automatically produces fresh G-code on the next print. For print farms, cloud slicing eliminates the burden of maintaining separate G-code files for each printer model and dramatically simplifies profile management.

How It Works

The Cloud Slicer is triggered automatically by Gutenb3d when a queued job is matched and assigned to a specific printer. This just-in-time approach ensures optimal slicing settings for each printer while maintaining efficient queue processing.

Slicing Workflow

Profile Resolution

When slicing a job, the Cloud Slicer combines three profile sources to generate printer-specific GCODE. Importantly, these profiles are always resolved from Printago's configuration—not extracted from uploaded 3MF files (with one exception for process profiles noted below).

1. Machine Profile

The machine (printer) profile always comes from what is configured on the printer itself in Printago, never from an uploaded 3MF file. This ensures the slicer uses the correct hardware settings for the actual printer receiving the job:

  • Printer model and capabilities
  • Bed size and type (Smooth PEI, Textured, etc.)
  • Nozzle diameter and configuration
  • AMS settings and filament handling

Machine profiles are synchronized from your Bambu Lab Integration or configured in Printer Management.

2. Process Profile

The process (print quality) profile is resolved in this priority order:

  1. Embedded 3MF Profile — if you chose "Embedded 3MF Profile" when creating the part, the process settings saved inside the 3MF file are used
  2. Part-specific override — if you selected a specific process profile on the part
  3. Printer default process profile — if the part is set to "Printer Default," the default process profile configured on the assigned printer is used (configured in Printer Management)

3. Filament Profile

The filament profile always comes from the material that matched the job on the assigned printer—never from a 3MF file. When a job is matched to a printer, Printago looks up the slicing profile assigned to that material (or material variant) for the printer's model and nozzle size:

  1. Material Variant's profile override (color-specific adjustments, if configured)
  2. Base Material's filament profile (configured in Materials)

Intelligent Caching

The Cloud Slicer implements smart caching to optimize performance and reduce slicing time. If anything on the part, printer, build plate, or related settings changes, it triggers a reslice of the file.

Cache Benefits

Intelligent caching means identical parts with the same settings slice instantly on subsequent prints, dramatically reducing queue processing time for repeat jobs.

Slicer Selection

Printago supports multiple slicer engines to accommodate different workflows and preferences:

Available Slicers

  • OrcaSlicer (Community-driven) - Open-source with advanced optimization features
  • Bambu Studio (Official Bambu) - Optimized specifically for Bambu Lab printers
  • PrusaSlicer (Coming Soon) - Official Prusa Research slicer
  • SuperSlicer (Coming Soon) - Feature-rich PrusaSlicer fork

Slicer Configuration

  • Default Slicer: Set your preferred slicer in Account Settings
  • Per-Part Override: Choose specific slicers when adding parts to your library
  • Profile Synchronization: Managed through the Bambu Lab Integration flow
    • Syncs machine, process, and material profiles from your Bambu account
    • Requires "Cloud Sync" enabled in Bambu Studio or Orca Slicer
    • Profiles refresh when running the integration flow

GCODE Access

After slicing completes, printer-specific GCODE becomes available:

Download Method

  1. Print Queue Interface: Click any job thumbnail → Download GCODE button

File Format

GCODE is packaged as a 3MF file containing:

  • Printer-specific GCODE instructions
  • Print thumbnails for printer display
  • Metadata about slicing settings used

Slicing Failures

If a job fails during slicing, it moves to the "Errored" tab in the Print Queue. Common causes:

  • Part too large for printer bed
  • Incompatible material/printer combination
  • Missing or corrupted slicer profiles

Accessing Slicer Logs

To troubleshoot slicing failures, you can view detailed slicer logs:

  1. Navigate to the job in the Print Queue (usually in the "Errored" tab)
  2. Click on the job to open the job details
  3. Click the "View Slicer Logs" button (shown as a log icon or button)
  4. Review the logs for specific error messages

The slicer logs contain detailed information about what went wrong during the slicing process, including error messages from the slicer engine itself.

Getting Help

If you can't resolve a slicing issue from the logs, share the logs in our Discord community for assistance from the team and community members.

Profile Issues

Ensure your slicer profiles are current by either running the Bambu Lab Integration flow to refresh cloud-synced profiles, or importing profiles manually from Bambu Studio or OrcaSlicer.

Need help? Join our Discord community for latest info and support!