New licenses go to $39.99 on Oct 28

Roundup

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

By Petros, who builds Meshory · Updated Sep 29, 2026 · 9 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.

Every claim below comes from the vendor's own site, documentation or repository, checked on September 18, 2026. Where something is not documented, this page says so instead of guessing.

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

ToolCopies files in?Writes into your folders?Renames files?Platforms and license
MeshoryNoNoOnly when you run a renamemacOS, Windows, Linux. One-time
TroveNoNoNo: indexing is read-onlyDesktop, MIT, free
SerpentNo: linked folders keep the originalNot documentedNomacOS, Windows. MIT, free
MorfyLibNoNoNoWindows. Free, or a paid Pro tier
LocalFabNoNoNomacOS. Paid early access
PrintventoryNoNo: metadata in its own databaseNoWindows, macOS, Linux. Free, open source
ModelistNoNoNomacOS, Windows, Linux. Free to 100 files
MeshVaultNoNoNoWindows, Linux. One-time
Orynt3DNoYes: small metadata filesNoWindows, macOS, Linux. Free
TagSpacesNoYes: sidecar JSON in a hidden folderYes, in one of its two modesDesktop. 3D viewer is Pro only
EagleYesNo: it works on its own copyOnly its copy, never your originalWindows, macOS. One-time

The ones that genuinely index in place

Meshory keeps every promise on this page that matters for a print library: it indexes in place, copies nothing, writes nothing into your folders, and renames or trashes a file only when you run that command yourself. It also renders STL, 3MF, OBJ, FBX, GLB, STEP and 3DM, reads inside ZIP, RAR, 7Z and TAR archives without extracting them, and matches duplicates by content and by mesh geometry. The details are further down.

Trove is a young, free MIT-licensed desktop app whose indexing is read-only by design, and it covers four formats: STL, 3MF, OBJ and STEP.

MorfyLib (Windows) and LocalFab (macOS) come from the design and VFX side, both state plainly that source files stay where they are, and neither documents 3MF, so neither fits slicer projects.

Serpent is a free MIT asset manager for macOS and Windows that links folders rather than copying them, and it does not publish its 3D format list.

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.

None of the three 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 a general creative-asset library that often gets 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 built for a curated visual library, not 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.

Orynt3D writes metadata files into your folders

Orynt3D is a free desktop organizer, and it does not copy or move anything. It does write small metadata files into the folders it indexes, which 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. They are built for a library shared across several machines, 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

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, GLB, 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.

On question 4, Meshory never changes a file on its own. Renaming a file or moving one to your system Trash happens only when you run that command, which is what lets you clean up a duplicate from the same window you found it in, instead of hunting for it again in Finder or Explorer. Everything else, the thumbnails, the tags and the index, lives in Meshory's own storage.

Questions about indexing in place

What does it mean for a 3D model manager to index files in place?

It means the app reads your existing folders and builds its own catalogue of what it found, while the model files stay exactly where they are. Thumbnails, tags and search live in the app's own database. The opposite is an import model, where the app copies files into storage it controls and your originals become a second copy.

Which offline 3D model managers do not move or copy your files?

Meshory, Trove, Serpent, MorfyLib, LocalFab, Printventory, Modelist and MeshVault all index in place. Eagle copies files into its library, and its own support documentation says so. Orynt3D and TagSpaces do not copy, but both write into your folders.

Does Eagle move my files?

Eagle does not move them, it copies them. Its support site has an article titled "Eagle imports files by copying rather than indexing the original files". Your originals stay put and a duplicate lives in Eagle's library, so the library costs roughly what the source folder costs. For a terabyte model hoard that is a second terabyte.

Do any of these need an internet connection?

The desktop apps here index, render and search entirely on your machine. Check the extras rather than the core: Printventory's AI tagging runs through third-party cloud providers, Meshory's is opt-in and uses your own OpenRouter key, and the self-hosted tools need a network only to reach the server you run.

Can I still reorganize my folders after indexing?

Yes with any in-place tool, though what happens next differs. Some detect the move and relink, some report the source as missing until you point them at the new path, and some lose tags across drives. Test it with a throwaway folder before reorganizing a real library, using the six steps above.

Point it at a folder and compare the folder afterwards.

That is the whole test, and it is the one Meshory is built to pass. Nothing moves, nothing uploads, and your directories look the same after the scan as before it.