Local-first 3D print library manager

Your STL folder is a landfill.

Four thousand files, six hundred folders named files, and no memory of which settings actually worked. PrintVault indexes what you already have, in place, and turns it into something you can search.

No account. Nothing uploaded. Free and GPL-3.0.

NO ACCOUNTOpen it and start. There is nothing to sign up for.
NOTHING UPLOADEDYour files never leave the machine. There is no server.
NO TRACKINGNo analytics, no cookies, no third-party requests.
GPL-3.0Free software. Read it, fork it, run it forever.
01 / Capabilities

Four problems, and none of them are solved by another folder.

PrintVault reads the library you already have. No importing, no moving files, no re-organising into somebody else's structure.

FEATURE 01

Find the thing you know you downloaded

Point it at a folder and it walks the whole tree, groups loose files into models, and renders a preview for each one so you are browsing pictures instead of filenames.

  • Real 3D previews rendered from the mesh, not generic icons
  • Reuses the thumbnail your slicer already embedded in gcode and 3MF
  • Tags, collections, ratings, and search across creator and notes
  • Sees through wrapper folders, so Dragon/files/ becomes "Dragon"
PrintVault — Library — 1,284 models
3 GCODE
PRINTED 4×
1 GCODE
PRINTED 1×
FEATURE 02

Stop re-learning what already worked

Log a print when it comes off the bed. PrintVault reads the slicer settings straight out of your gcode, so the form is already filled in. Next time you open that model, last time is right there.

  • Reads PrusaSlicer, OrcaSlicer, BambuStudio and Cura headers
  • Time, grams, layer height, nozzle, infill, material, printer
  • Success, partial, or failed, with the note explaining why
  • Success rate per printer once you have logged a few
Log a print — prefilled from dragon_v3.gcode
RESULTSuccess2026-07-24
PRINTERPrusa MK4Sfrom gcode
FILAMENTPolymaker PLA · Galaxy Black
LAYER / NOZZLE0.20 mm/0.40 mm15% infill
USED88.4 gTIME6h 52m
NOTESBrim needed on the tail. Bed at 65 fixed the warping.
FEATURE 03

Get the disk space back

The same model downloaded three times, under three names, in three folders. PrintVault hashes them and proves they are identical before you delete anything.

  • SHA-256 verified, so a match is a match, not a guess
  • Only hashes files that share a byte size, so it skips almost everything
  • Finds zips still sitting next to the folder you extracted them into
  • Shows every full path and makes you confirm before it deletes
Duplicates — 34 groups — 8.7 GB reclaimable
3 copies62.4 MB each · a41f9c02b7e5124.8 MB
KeepPrints/Dragons/Articulated/body.stl
CopyDownloads/dragon(2)/body.stl
CopyDesktop/to sort/body_FINAL.stl
2 copies1.5 GB each · 77bd10e4aa931.5 GB
FEATURE 04

Know if you have the filament first

Track spools by what is actually left on them. Grams come off automatically as you log prints, and the queue totals up the whole batch before you commit to a fourteen hour job.

  • Remaining grams decrement as prints are logged
  • Low-spool warnings before you start, not halfway through
  • Queue rolls up total time and total grams across every item
  • Cost per print from spool price plus your electricity rate
Filament — 6 spools — 3.94 kg on hand
Polymaker PLA640 g
Prusament PETG95 g
Overture PLA880 g
Sunlu PETG410 g
QUEUE TOTAL13h 44m176.8 gfits
02 / Getting started

Three clicks from mess to library.

Nothing is copied, moved, renamed, or re-organised. PrintVault reads your folders where they sit and keeps its index separately.

STEP 01

Point it at a folder

Your browser asks permission once, per folder. Add as many as you like: the NAS share, the downloads pile, the drive you keep meaning to sort out.

STEP 02

Let it read

It walks the tree, groups files into models, pulls settings out of any gcode it finds, and renders a preview for everything it can.

STEP 03

Actually use it

Search, tag, log prints, kill duplicates, plan a batch. Rescan whenever you have added things, and your tags and history carry over.

03 / Datasheet

What it reads, and what it needs.

Mesh formats
STL binarySTL ascii3MFOBJ PLYSTEPAMF Solid chips render a 3D preview. Dashed chips are indexed and searchable but not rendered.
Slicer output
PrusaSlicerOrcaSlicerBambuStudioCuraSuperSlicer Print time, filament mass, layer height, nozzle, infill, material, printer profile.
Browser
ChromeEdgeBraveOpera FirefoxSafari Folder indexing needs the File System Access API, which Firefox and Safari do not implement.
Storage

Your index, tags, print history, filament, and previews live in this browser's IndexedDB. Your model files are never copied into it. Back the whole thing up to a JSON file whenever you want, and export print history as CSV.

Network

None. There is no backend, no API, no telemetry, and no third-party asset. Load the page once and you can pull the plug.

Price

Free, and licensed GPL-3.0-or-later. No tiers, no seats, no upsell, nothing to cancel.

04 / Questions

The obvious ones.

Does it move or change my files?
No. It reads them where they are and stores its index separately. The only time PrintVault writes to your disk is when you explicitly confirm a duplicate deletion, and it shows you every full path before it does.
Where does my data actually go?
Into your browser's local database, on your machine. There is no server to send it to. You can verify this: open the network tab, use the app, and watch nothing happen.
Why does it not work in Firefox?
Reading a folder from a web page requires the File System Access API, which only Chromium browsers implement today. Everything else in PrintVault works in any browser, but without folder access you would be entering models by hand, which rather defeats the point.
Do I have to re-add my folders every time?
No. The permission is remembered, but browsers require a click to reconnect after a restart, so the first scan of each session needs one press of the button. That is a browser security rule, not a PrintVault choice.
What happens if I clear my browser data?
The index goes with it, along with your tags and print history. Your actual model files are untouched. Use Settings → Export backup to keep a JSON copy; restoring it after a rescan puts everything back.
Can I run it on my own machine or NAS?
Yes. It is one HTML file. Drop it behind any web server and open it over https or http://localhost. It will not work from a file:// path, because browsers do not grant folder access outside a secure context.
Is it finished?
It is version 0.1.0 and honest about that. The parsers are tested against real slicer output and the core works, but it has not yet been run against every strange library layout in existence. If it trips over yours, that is worth hearing about.

You already own the files. Start owning the library.

Runs in Chrome, Edge, Brave and Opera. Nothing to install.