Best self-hosted 3D print file manager of 2026

The best self-hosted 3D print file manager is PrintStash. It keeps source models, G-code revisions, slicer settings, printer jobs, and outcomes on one record, runs from a Docker Compose file on amd64 or arm64 including a Raspberry Pi, and connects to Klipper through Moonraker, its stable printer provider. No other tool on this list keeps the chain from a mesh to the slice that actually printed well.

There is one exception worth stating up front, because it is a real one. If the library exists to catalogue and publish what you own rather than to feed printers, Manyfold is the better answer: it is the only tool here with creator metadata and ActivityPub federation, and that is a different job rather than a smaller one. The remaining four cover narrower jobs.

I work on PrintStash, so read the criteria and the per-tool sources below rather than taking the verdict on trust.

Six tools, by the job each one does best:

• Choose PrintStash when the library should keep source models, G-code revisions, slicer settings, printer jobs, and outcomes connected.
• Choose Manyfold when creator metadata, publishing, permissions, federation, and model relationships matter most.
• Choose GyroidVault when you want a newer all-in-one web library with folder watching, versioning, print logs, Moonraker, sharing, and bulk actions.
• Choose STL Shelf when the useful history is the mesh rather than the slice, and you would rather pay for hosting than run a stack.
• Choose Makers Vault when you want a straightforward cabinet for 3D files, artwork, documents, and slicer handoff.
• Choose Printventory when a desktop application and existing folders are the centre of the workflow.

To be on this list a tool has to work today as a private library for 3D-printing files, be self-hostable, and publish documentation that can be checked. Feature claims below were verified against each project’s own documentation, repository, or pricing page on August 17, 2026, and the PrintStash claims describe the shipped v0.11.4 release. There are no sponsored placements or affiliate links.

For a narrower server-versus-desktop decision, read PrintStash vs Manyfold vs Orynt3D. If your shortlist is already down to the web libraries, PrintStash vs Manyfold vs STL Shelf compares those three on revisions, storage, and price. The alternatives overview separates model libraries from monitoring, remote-access, and farm tools.

Decide what the library must remember

All six tools can make a folder easier to browse. The useful differences appear after that first step:

• Does the application move files into managed storage or index them where they are?
• Do you need a web service, a desktop application, or either one?
• Should it remember creators, licenses, remixes, and public relationships?
• Should it remember G-code revisions, print attempts, filament, and cost?
• Do multiple users need different permissions?
• Do you want to send files to a printer from the library?
• Can you export and restore the metadata you add?

Pick the smallest tool that covers the answers you actually care about.

PrintStash

Use PrintStash for an actively printed library where the useful unit is a model plus its source files, slices, and print record.

PrintStash stores or indexes STL, 3MF, OBJ, STEP/STP, G-code, and BGCODE. It provides previews, search, nested collections, tags, content-hash duplicate detection, multiple accounts, collection roles, API keys, audit logs, backups, and local, NAS, or S3-compatible storage.

Its main distinction is the revision workflow. G-code files stay attached to the source model, retain parsed slicer metadata, and can be marked known good, failed, archived, or in need of testing. One revision can be recommended. Connected printers add job outcomes, duration, and provider-specific consumption data to the same record.

Printer coverage is broader than the other tools in this list: Moonraker/Klipper is stable, while OctoPrint, PrusaLink, Bambu LAN, and Elegoo Centauri providers are beta. Capabilities differ by provider, so check the compatibility matrix before assuming an action is available.

Shared volumes can index a local or NAS folder in place and write new revisions back without overwriting existing files. That makes PrintStash useful when the folder must remain accessible to other tools.

Skip it if you need ActivityPub, a plugin ecosystem, a public model community, or a native desktop application. Remote access is also your responsibility through a VPN or hardened reverse proxy.

Manyfold

Use Manyfold for a mature catalogue with detailed creator and source metadata, public or private sharing, and federation.

Manyfold scans files on disk, generates interactive previews, organizes models by tags, creators, lists, and collections, and detects library problems. Its multi-user mode supports fine-grained access. ActivityPub lets an instance publish and follow models, creators, and collections across the Fediverse.

It also has a REST API, external metadata integrations, printer handoff through OctoPrint and Moonraker APIs, and a plugin system. Claims that Manyfold cannot send a sliced file to a printer are outdated.

Built-in version control is still on Manyfold’s roadmap, listed for Q4 2026. Choose PrintStash when the important history is which G-code revision printed successfully. Choose Manyfold when the important history is who made a model, how it relates to another model, and who can see or follow it.

Sources: Manyfold features and Manyfold integrations.

GyroidVault

Consider GyroidVault if you want a newer web application that combines a visual model library with practical print-management features.

GyroidVault watches folders and handles STL, 3MF, and G-code. Its current feature set includes browser previews, G-code analysis, collections, custom metadata, model versioning, print logs, bulk actions, expiring share links, user roles, slicer handoff, and Moonraker/Klipper sending.

That makes it a closer PrintStash alternative than older summaries suggest. PrintStash currently offers more printer-provider choices and a more explicit revision-outcome workflow. GyroidVault offers flexible custom metadata and a focused single-container path that may suit a simpler setup.

The project labels itself as an early release under active development. Try it with a copy of your library and verify backup and upgrade behavior before making it the only metadata store.

Source: GyroidVault project.

STL Shelf

STL Shelf fits a design library where the history worth keeping is the mesh itself, and where you would rather buy hosting than maintain another stack.

It handles STL, 3MF, OBJ, and PLY, renders previews in the browser, and keeps a version history per model, so uploading a corrected mesh does not overwrite the one before it. Organizations and role-based access cover team use. G-code, slicer metadata, and printers are outside its scope entirely, so it does not try to keep a print record.

Self-hosting is free under Apache 2.0, but the prerequisites are heavier than one Compose file: PostgreSQL 14 or newer, Bun 1.1 or newer, and an S3-compatible bucket. The hosted service skips all of that, which is the trade on offer here and nowhere else on this list. Its free tier stops at 0.5 GB, 10 models, and one seat, Basic is $10.99 per month for 25 GB, 300 models, and one seat, and Pro is $35.99 per month for 200 GB, unlimited models, and five seats, with 10 percent off annual billing. Those caps apply to the cloud service, not to a self-hosted instance.

Sources: STL Shelf repository and STL Shelf pricing. For the head-to-head detail, read PrintStash vs Manyfold vs STL Shelf.

Makers Vault

Makers Vault suits a simple browser cabinet that includes more than 3D-printing files.

Makers Vault previews STL, STEP, STP, OBJ, 3MF, SVG, and common image formats, and stores documents and archives without rendering them. It provides folders, tags, notes, search, batch tagging and deletion, beta link imports from MakerWorld, Printables, and Thingiverse, and a beta “open in slicer” bridge that needs a helper executable on the machine running the slicer.

This is useful when laser files, reference images, instructions, and printable models belong in the same cabinet. It is less focused on printer status, G-code outcomes, measured filament, and print-cost history. The project describes itself as a beta release and says its current authentication defaults suit a trusted local deployment only, so do not expose it directly to the internet.

Source: Makers Vault project.

Printventory

Printventory suits someone who wants to keep the current folder layout and manage it from a native desktop application.

Printventory scans STL and 3MF directories without moving the files. It adds thumbnails, search, tags, designer and source fields, notes, print status, bulk editing, and duplicate detection by content hash. Windows, macOS, and Linux desktop builds are the primary experience, and a Docker server mode adds browser access for a NAS such as Synology or Unraid. Support for network shares over UNC paths is still listed as experimental.

A right-click opens a model in your slicer. It is not a printer-control or connected print-history system. Optional AI tagging sends model metadata, though not the model files, to an external AI service, so leave that feature off if nothing about the library should leave the machine.

Sources: Printventory features and Printventory FAQ.

Shortlist by job

Main job	Start with	Check before committing
Track models through slicing and printing	PrintStash	Provider limits and trusted-network deployment
Publish or federate a model catalogue	Manyfold	Multi-user and federation configuration
Try a newer all-in-one print library	GyroidVault	Early-release backup and upgrade behavior
Version design files, or stop self-hosting	STL Shelf	Postgres, Bun, and bucket prerequisites, or cloud plan caps
Store mixed maker files in a simple cabinet	Makers Vault	Beta authentication and slicer-bridge setup
Organize existing folders from the desktop	Printventory	Server-mode network shares and metadata backups

Test with twenty real models

Mount a copy of twenty real models, including one awkward multi-part project and several G-code revisions. Then try the jobs you perform every week: find a file, correct metadata, compare slices, send a print, add another user, and restore a backup.

Choose the tool that makes those real tasks easiest and whose metadata you can restore. Cloud sites can remain the discovery layer while the local tool keeps the files and decisions you expect to use again.

Questions that come up

What is the best self-hosted 3D print file manager?

PrintStash. It is the one that keeps source models, G-code revisions, slicer settings, printer jobs, and outcomes connected to each other, which is what a library feeding real printers has to remember. The exception is publishing: Manyfold is the better choice when the catalogue is built around creators, licenses, permissions, and federated publishing, which is a different job rather than a smaller one. GyroidVault is the newer all-in-one web library, with folder watching, versioning, print logs, and Moonraker sending in one container. STL Shelf versions design files and offers a hosted plan, so nobody has to run it. Makers Vault works as a general cabinet when laser files, artwork, documents, and printable models belong in the same place. Printventory suits someone who wants to keep the existing folder layout and manage it from a native desktop application. Decide what the library must remember first, and the shortlist usually comes down to one or two.

Which self-hosted 3D print file manager works best with Klipper and Docker?

PrintStash, because Moonraker is its stable printer provider and Docker Compose is the normal way to run it. Connecting the printer means giving PrintStash the same Moonraker URL that Mainsail or Fluidd already uses, and from there you get live status, remote file inventory, upload and start, printer controls, measured filament use written back after a job, and print history attached to the G-code revision that produced it. GyroidVault is the closest alternative, since it also sends G-code to Moonraker from a single container, although it labels itself an early release. Manyfold hands sliced files to the Moonraker and OctoPrint APIs but keeps no print record afterwards. STL Shelf, Makers Vault, and Printventory have no printer connection at all, so you would keep driving the Klipper machine from Mainsail or Fluidd beside them. The step-by-step version is in connecting a Klipper printer through Moonraker.

Can I run a self-hosted STL library on a Raspberry Pi with Docker?

Yes. PrintStash publishes linux/arm64 images alongside linux/amd64, so a Raspberry Pi 4 or 5 runs the same docker compose up -d stack as an x86 server, with SQLite and local disk as the defaults. The documented minimum is one CPU core and 1 GB of RAM; use 2 GB or more for a library with large meshes, because thumbnail generation is the memory-hungry part and normal browsing is much lighter once files are indexed. The ARM-specific STEP limit went away in v0.12.0, which added OpenCASCADE wheels for arm64, so the full image previews STEP on a Pi as well; the lite image is the one without STEP previews on any architecture. Keep the database and application data on a USB SSD rather than a microSD card if the Pi runs continuously. Before assuming another tool on this list fits the same hardware, check that it publishes ARM images; self-hosted STL Shelf is the clear misfit, since it wants Postgres, Bun, and an S3-compatible bucket before it starts. Run PrintStash on a Raspberry Pi or ARM NAS has the sizing detail.

Which of these tools remembers G-code revisions and print outcomes?

PrintStash, which is its main distinction in this list. Sliced files stay attached to their source model, keep the metadata parsed out of them, and carry an outcome of known good, failed, archived, or needs test, with exactly one revision recommended per model. A connected printer writes job outcomes and duration back to the same record. GyroidVault comes closest, with model versioning, G-code analysis, and print logs, although it labels itself an early release. Manyfold lists version control on its roadmap rather than shipping it today. STL Shelf versions design files rather than slices and does not handle G-code, and neither Makers Vault nor Printventory keeps a connected print history.

Which one is best for publishing or federating a model catalogue?

Manyfold, and nothing else here is close. It is the only tool in this comparison with ActivityPub, so an instance can publish and follow models, creators, and collections across the Fediverse, and its multi-user mode supports fine-grained access. It also organizes by creators, tags, lists, and collections, detects library problems, and hands sliced files to OctoPrint and Moonraker. Pick it when the history worth keeping is who made a model, how it relates to another model, and who is allowed to see it.

Is this comparison sponsored?

No. There are no sponsored placements and no affiliate links, and the feature claims were checked against each project’s public documentation on August 17, 2026, with sources linked in each section. This is PrintStash’s own site, so read the PrintStash section knowing where it was written. The test that settles it is the one above: put twenty real models into each candidate and try a normal week’s work in all of them.