How PrintStash fits alongside OctoPrint, Fluidd and Mainsail
Keep OctoPrint, Fluidd, or Mainsail for printer control. Add PrintStash when you need a searchable library, G-code revisions, and print history.
If Fluidd, Mainsail, or OctoPrint already runs your printer well, keep it. PrintStash belongs beside that interface, not in place of it.
The controller handles the machine in front of you. PrintStash handles the files and decisions that build up around it.
The practical split
Open Fluidd, Mainsail, or OctoPrint to watch temperatures, use the webcam, send a manual command, or intervene while a job is running.
Open PrintStash to find the model, compare its G-code revisions, check slicer settings, review earlier outcomes, or choose the known-good file. It keeps the source files and print history together even when you replace a printer or change controller software.
Fluidd and Mainsail use the Moonraker path
Fluidd and Mainsail are web interfaces for a Klipper setup. Both talk to Moonraker, and PrintStash uses that same API.
When you send a G-code revision from PrintStash, it uploads the file to Moonraker and can start it. Fluidd or Mainsail sees the same job. PrintStash receives status, progress, temperatures, and the final result through the provider connection.
Moonraker is the stable and most complete provider. It also supports remote file inventory, starting a file already stored on the printer, raw G-code, emergency stop, and measured filament consumption.
Is there a better Moonraker file browser covers when switching front-end fixes a file-browsing complaint and when the missing piece is a library.
OctoPrint uses its own provider
OctoPrint does not use Moonraker. Add it to PrintStash with its local URL and an API key. The beta provider supports live status, upload and start, remote file inventory and deletion, plus pause, resume, and cancel.
Keep OctoPrint open for its webcam, terminal, movement controls, scripts, and plugins. The provider does not pass measured filament consumption to PrintStash, so measured grams and Spoolman write-back are Moonraker-only. The PrintStash vs OctoPrint comparison covers that setup in more detail.
A simple day-to-day workflow
- Keep the source model and useful G-code revisions in PrintStash.
- Let the OrcaSlicer hook add new slices, or upload them through the browser.
- Choose a revision and send it to the printer from PrintStash.
- Use Fluidd, Mainsail, or OctoPrint for hands-on control during the job.
- Return to PrintStash to record the outcome and mark the revision you would use again.
This workflow makes PrintStash the library without forcing it to become the only route to the printer. You can still upload directly through the controller when that is more convenient. Those files will not have the same model and revision context unless you also add them to PrintStash.
What PrintStash does not replace
PrintStash is not a slicer, firmware interface, webcam dashboard, terminal, or full print queue. It gives the controller a better-organized source of files and keeps the result attached to the model. For most home setups, that is a cleaner boundary than trying to make one application do both jobs.