Understanding What Polar Cloud Sends to the Printer
What Gets Sent
When a print starts, Polar Cloud sends the printer a command to begin printing along with references to the job’s assets.
That typically includes:
The G-code file that will be executed
A thumbnail or preview image of the object
Basic job metadata so the printer knows what it’s printing and how to report status
The printer downloads and runs the G-code exactly as provided.
What Does
Not
Get Sent
Print configurations do not go to the printer.
Things like layer height settings, infill choices, support options, and slicer parameters are only used during slicing. Once G-code is generated, those settings have already done their job.
At that point, the printer only cares about instructions it can execute.
Why This Separation Matters
This design keeps the system predictable.
The printer doesn’t interpret slicer settings. It doesn’t make decisions. It simply runs the G-code it’s given. That means:
Uploaded G-code is never reinterpreted
Printer behavior is consistent and repeatable
What you preview is what gets printed
It also allows Polar Cloud to support many printer types without forcing them to understand slicer-specific concepts.
Slicing vs Printing Are Distinct Phases
Think of slicing and printing as two separate steps.
Slicing happens in Polar Cloud, using configurations and settings you choose. Printing happens on the printer, using the resulting G-code.
Once slicing is complete, the configuration is no longer part of the process.
The Practical Takeaway
Polar Cloud doesn’t push slicer logic onto your printer.
It sends a clear instruction to print, provides the files needed to do it, and then steps out of the way. Your printer executes exactly what it’s told, and nothing is hidden or changed along the way.
That clarity is what makes the system reliable.