If your library needs recovery
Updated Aug 14, 2026 · 1 min read
What the recovery window offers when the library database can't be opened or upgraded, and where the backups live.
Your library (sources, tags, collections, notes, duplicate results) lives in a small database on your machine, next to the thumbnail cache. Your models are not in it. The worst case for a damaged database is that Meshory has to be pointed at your folders again, never that a model is lost.
Meshory backs that database up before it upgrades it, keeping the most recent couple of copies, and a failed upgrade at startup is never silent. A recovery window opens instead: it says what went wrong, shows the backups folder with a button to reveal it, keeps the technical detail on hand to copy, and can collect a diagnostics bundle for support.
Diagnostics bundles hide your file and folder names by default. What support actually reads (counts, settings, which drive a source sits on, the scan lifecycle in the logs) survives that, so you can send one without sending your library's contents.
After installing an older version
A library written by a newer Meshory can't be read by an older one, so on a downgrade the window says so rather than touching your data. Where a usable backup exists, it offers to restore the most recent one the installed version can actually open; otherwise it points you at the current release so you can get back to where you were.
Beta builds
A prerelease build keeps its own copy of the library, so trying a beta can never upgrade the database your stable install depends on. The first beta launch offers to create that copy, and going back to stable offers to prepare a stable library from it.
None of this touches your model files. Recovery only ever swaps which database Meshory reads.