Roundup

Offline 3D model managers that read your files without moving them

By Petros, who builds Meshory · Updated Sep 18, 2026 · 10 min read

"Reads your files without moving them" sounds like one promise. It is four, and a tool can keep three and break the one you cared about. It can copy your library into its own storage. It can leave your files where they are but write its own files into your folders. It can rename your files to store tags in the filename. Or it can index in place and touch nothing. Several tools that get recommended for this exact requirement do one of the first three, sometimes while saying so in their own documentation. This page checks eleven offline managers against all four questions, on evidence from each vendor, and ends with a test you can run yourself in about two minutes.

The four questions behind one phrase

Ask these in order. Most comparison pages answer only the first, which is why the recommendations so often miss.

1. 1Does it copy my files into its own library? The loudest failure and the easiest to spot: you add a folder, and now the models exist twice, once where you put them and once inside the app's storage.
2. 2Does it write its own files into my folders? Subtler. Your models never move, but the tool drops metadata files, sidecar JSON or hidden folders alongside them, so your directories are no longer only yours.
3. 3Does it rename my files? Some tagging tools store tags in the filename itself. Nothing is copied and nothing moves, and your filenames are still not what they were.
4. 4Can it change anything without being told to? The strictest version is read-only: the app can never write to your library at all, even by accident, even if you click the wrong thing.

A tool can pass 1 and fail 2. A tool can pass 1, 2 and 3 and still not be read-only. Which of the four actually matters depends on why you asked. If the worry is disk space, question 1 is the whole thing. If the worry is that a future tool, or no tool, should still see a clean folder tree, question 2 and 3 are what you meant.

Eleven tools against the four questions

The ones that genuinely index in place

Trove is the strictest answer to the question as asked, and stricter than Meshory. It is a free MIT-licensed desktop app built in Rust and Tauri that indexes STL, 3MF and STEP from folders you point it at, with a 3D viewer, automatic tagging from filenames and folder structure, and collections across scattered files. Its indexing is read-only by design, so it has no path to writing in your library at all. It is a young project, at 69 commits, and covers three formats rather than a dozen. If read-only is a hard requirement rather than a preference, look there first.

MorfyLib and LocalFab both come from the design and VFX side rather than 3D printing, and both state the position plainly. MorfyLib: "Nothing is copied or moved. The index just points at where your files already live, so re-organizing your library is safe even if MorfyLib is closed." LocalFab: "Source files remain untouched in their original locations." MorfyLib is Windows only, free with a $29 one-time Pro tier, and reaches glTF, GLB, OBJ, FBX, STL and PLY plus HDRIs and .blend, .hip and .c4d project files. LocalFab is macOS only at $49 during early access, covering OBJ, FBX, GLTF, GLB, STL, DAE and USDZ with textures. Neither documents 3MF, so neither is a fit for slicer projects.

Serpent is a free MIT asset manager for macOS and Windows built on the same idea: "import a folder as a link to keep working against the original directory", with "source changes refresh previews and metadata without copying files in". It does not publish its 3D format list, so check that before committing. Printventory, Modelist and MeshVault all index print libraries in place and keep their metadata in their own databases; the best STL organizer roundup covers how they differ on everything else.

Three that get recommended for this and answer a different question

All three are good software. None is a good answer to "without moving them", and in two cases the vendor's own documentation is where you find that out.

Eagle copies your files in

Eagle is the general creative-asset library most often named in this category, and its own support site has an article titled "Eagle imports files by copying rather than indexing the original files". That is the answer to question 1, from the vendor, in a headline. Your originals stay where they are and a second copy lives inside Eagle's library, which for a terabyte-scale model hoard is a second terabyte. Eagle is a fine tool for a curated visual library and the wrong tool for indexing a large folder tree in place.

TagSpaces stores tags in your filenames or in your folders

TagSpaces is built to work on top of ordinary folders, which is why it gets recommended here, and the mechanism is the problem. It has two tagging modes. One writes tags into the filename, so a file tagged vacation and alps becomes IMG-2653[vacation alps].jpg. The other writes a sidecar .json file per model into a hidden .ts folder inside your directories. Nothing is copied and nothing moves, and after a year your filenames or your folders are not what they were. Its 3D viewer covers GLB, GLTF, STL and OBJ, and is Pro only.

Orynt3D writes metadata files into your folders

Orynt3D is a free desktop organizer with the most developed tagging and boolean search of the free tools in this category, and it does not copy or move anything. It does write small metadata files into the folders it indexes. For many people that is a fair trade, and it has a real upside: the organizing travels with the files if you move the drive. It is worth knowing before you point it at a library you want left untouched, and it is not what most people mean by the question. Thumbnails are also captured by hand, one model at a time, which is a separate problem at scale.

Self-hosted tools: in place, but now you run a server

Manyfold, PrintStash, GyroidVault and the containerized 3D Model Manager all scan paths you mount into them, so they pass question 1. The cost sits elsewhere: they are Docker services with databases to back up rather than applications you install, and several of them want archives imported and extracted rather than read where they sit. If a shared library across several machines is the goal they are the right shape, and whether you need a server at all works through the trade honestly.

How to check any tool in two minutes

Vendor claims are a starting point. This is the test, and it works on anything.

1. 1Copy 20 models into a fresh throwaway folder. Never test on your real library.
2. 2Note the folder's size and file count, and take a screenshot of the file listing so you have the exact filenames.
3. 3Point the tool at that folder and let it finish indexing, thumbnails included.
4. 4Look at the folder again. New files, new hidden folders, changed filenames or a changed file count all answer questions 2 and 3 immediately.
5. 5Check your disk. If free space dropped by roughly the size of the folder, the tool copied it, and the answer to question 1 is yes whatever the marketing says.
6. 6Quit the tool, rename the folder, and reopen it. A tool that indexes in place will report the source as missing. A tool that copied your files will carry on as if nothing happened, which tells you where it is really reading from.

Where Meshory fits, and where Trove is stricter

Meshory indexes folders in place on macOS, Windows and Linux, and writes nothing into them. Thumbnails, the index and every piece of metadata live in Meshory's own storage, so your directories after a scan hold exactly what they held before it. Nothing uploads. It renders STL, 3MF, OBJ, FBX, STEP and Rhino 3DM, reads inside ZIP, RAR, 7Z and TAR archives without extracting them, and matches duplicates by content and by mesh geometry. $34.99 one-time, no account.

Being precise on question 4, because it is the one where Meshory is not the strictest option: Meshory is not read-only. It can rename a file and it can move one to your system Trash, and it does either only when you run that command yourself. Trove's indexing is read-only by design and therefore has no such path at all. If you want a tool that structurally cannot write to your library, that is a real difference and Trove is the better fit. If you want one that leaves your folders alone but can still rename things when you ask, that is what Meshory is.