Bring files in
Upload STL, 3MF, OBJ, and G-code, or let OrcaSlicer push exported G-code after slicing. Duplicate uploads are caught by content hash instead of becoming another mystery file.
Most print libraries start out tidy. Then a few months pass and you have
hinge-final.gcode, hinge-final-fixed.gcode, and a folder called old maybe.
The slicer remembers some settings, the printer remembers what is on its disk,
and your file browser remembers almost nothing useful.
PrintStash is the missing notebook for that mess. It keeps the model, the sliced revisions, the thumbnail, the parser metadata, the printer copy, and your “this one worked” note together. It is still a small self-hosted project, but it is meant to be useful in a real home workflow today.
Bring files in
Upload STL, 3MF, OBJ, and G-code, or let OrcaSlicer push exported G-code after slicing. Duplicate uploads are caught by content hash instead of becoming another mystery file.
See what you sliced
Open the mesh, scrub the G-code toolpath, and check the slicer settings the file actually contains. Missing fields usually mean the slicer did not write them, not that you did anything wrong.
Remember the good one
Mark the recommended revision, keep quick notes, compare settings, and log what happened when it came off the bed.
Mirror a folder or NAS
Already have everything in a folder or on a NAS? Point PrintStash at it and it indexes files in place — no copying, no second source of truth. Local folders sync in real time; everything else runs on a schedule. See Shared volumes.
Run it yourself
Docker Compose, first-run setup, local disk by default, SQLite by default, no cloud account, and export/backup paths when you need to move it.
Keep it honest
Soft-delete trash with retention, scheduled backups (local or S3/R2), and an upgrade path that doesn’t ask you to hand-migrate data.
You get to choose, per setup:
The two coexist: most people run a vault and link a shared volume or two on top.