Connecting a Klipper printer to PrintStash through Moonraker
Connect PrintStash to Moonraker for live status, remote files, upload and start, printer controls, measured filament use, and print history.
Connecting one printer through Moonraker is also the first step toward managing files across several Klipper machines from one place. Up to two printers, per-machine uploads in Mainsail or Fluidd stay the simplest answer; past that, a library with a fleet queue removes the per-machine copy loop. This guide covers the connection itself.
If Mainsail or Fluidd already controls your Klipper printer, Moonraker is already part of the setup. PrintStash connects to that API directly.
Moonraker is the stable provider and has the broadest PrintStash capability set.
Adding the printer
Open Printers -> Add printer, choose Moonraker/Klipper, and enter the URL reachable from the PrintStash server, for example http://192.168.1.50:7125. Add the Moonraker API key if your instance requires one.
Open the printer’s Diagnostics tab after saving. It reports configuration, connectivity, declared capabilities, and unsupported actions without returning stored secrets.
When connected, the printer page shows state, current file, progress, elapsed time, temperatures, and the remote G-code inventory.
Sending a print
A G-code revision can be uploaded without starting or uploaded and started in one action. PrintStash can also start an existing remote file and pause, resume, or cancel the active job.
Moonraker also enables hotend and bed targets, PLA/PETG/ABS preheat presets, cooldown, homing, raw G-code, and emergency stop. Capability-aware controls stay hidden or disabled on providers that cannot perform those actions.
Run a safe smoke test
- Confirm that live status changes when the printer state changes.
- Sync the remote file list.
- Upload a small known-good file without auto-start.
- Confirm it appears in Mainsail or Fluidd.
- Test start and job controls only when the printer is clear.
Keep Mainsail or Fluidd available for the webcam, console, configuration, and hands-on troubleshooting. PrintStash is the library and job record, not a firmware dashboard.
Measured print records
Moonraker reports the completed duration and filament used by the job. PrintStash stores those measured values with the model instead of relying only on the original slicer estimate.
Measured grams improve cost history. If a Spoolman spool was selected and write-back is enabled, PrintStash can decrement it once after the job. It checks for Moonraker’s own Spoolman integration to avoid counting the same print twice.
A successful job can also mark an unset or needs-test revision as known good. This behavior is configurable and never overrides a manual failed or archived verdict.
What Moonraker’s file browser does not keep
Mainsail and Fluidd both browse Moonraker’s gcodes directory, and for uploading a file and pressing print that is all anyone needs. The limits show up later, and they are limits of the data rather than of the interface: the list is per machine, keyed on filenames, and holds no link back to the model a file was sliced from. Print statistics attach to a filename on that printer, so re-uploading under a new name or slicing a fourth variant breaks the connection.
A library sits behind that browser rather than replacing it. It keeps each slice as a revision of its source model with the slicer settings parsed out of the file, one outcome per revision, and a history that survives deleting the file from the printer. PrintStash can also read the printer’s file list back and mark which entries it recognizes, which is covered in syncing printer files with a library.
Keep Mainsail or Fluidd for browsing what is on the machine right now. That is a different question from what you printed in March.
A note on the OrcaSlicer hook
The OrcaSlicer post-processing hook can send each exported G-code file to PrintStash. From there, choose the revision, send it to Moonraker, and monitor the machine in Mainsail or Fluidd.
This keeps useful slices in the model history. Use the shortest safe path for one-off calibration and maintenance files when adding them to the library would create noise.
The controller overview explains how PrintStash shares Moonraker with Fluidd and Mainsail. Use the compatibility matrix when comparing this provider with a mixed fleet.