Where your data lives

The app never changes your asset files unless you ask it to (renaming, resolving duplicates). Everything it knows about them (folders, tags, collections, packs, rules) and its own preferences live in one data folder:

OS	Folder
macOS	`~/Library/Application Support/Salaryman Asset Manager/`
Windows	`%APPDATA%\Salaryman Asset Manager\`
Linux	`~/.local/share/Salaryman Asset Manager/`

On macOS, the Library folder in your home folder is hidden: in Finder, choose Go → Go to Folder… and paste the path. On Windows, paste %APPDATA% into the File Explorer address bar.

What’s in it

Path	What it holds	Safe to delete?
`library.db`	The library: folders, assets, tags, collections, packs, licenses, auto-tag rules.	No. This is your library. Back it up.
`library.db.bak-v<N>`	Copies made automatically before the app upgrades the library’s format. `<N>` is the format version before the upgrade. The newest 3 are kept.	Yes, once the upgraded library works.
`settings.cfg`	Preferences: UI scale, the window’s size and position, file watching, the Recently added window, the Blender path, the grid’s view, sort and thumbnail size, export choices and last-used folders.	Yes. You get the defaults back.
`extracted_packs/`	One folder per `.zip` you imported, holding its extracted files. Each is a library folder.	Only for zips whose folder you’ve removed from the library. Otherwise their assets become missing.
`cache/thumbs/`	Thumbnails.	Yes, with the app closed. They’re made again as you browse.
`cache/converted/`	`.blend` and `.dae` models converted by Blender for previews.	Yes. They’re converted again when needed.
`cache/extract/`	Files you opened from inside an archive in the inspector.	Yes.
`logs/`	Log files from the most recent runs.	Yes.

You may also see library.db-journal (or -wal and -shm) next to library.db while the app is running. They belong to the database: copy, move or delete them together with library.db, never on their own.

Other folders the engine creates there (such as shader caches) are safe to ignore.

Moving from version 0.2.0 or earlier

Version 0.2.0 and earlier kept this data in Godot’s default folder: …/Godot/app_userdata/Salaryman Asset Manager/ (…/godot/app_userdata/… on Linux), inside the same parent folder as above. The first launch of a newer version moves everything from there into the new folder, updates the paths of imported zips to match, and leaves a MOVED.txt in the old folder saying where the data went. You can delete the old folder afterwards.

The move never overwrites a library: if the new folder already has a library with anything in it, nothing is moved and the old folder is left as it was. If a move is interrupted, library.db is moved last, so the next launch tries again.

Back up your library

Quit the app.
Copy library.db (with any library.db-journal, -wal or -shm file next to it) somewhere safe.
If you imported any .zip packs, copy extracted_packs/ too. You can also re-import the original zips instead.
Optionally copy settings.cfg.

You don’t need the cache folders. Your asset files aren’t in this folder at all; back them up as you normally would.

To restore a backup, quit the app and copy the files back into the data folder, replacing what’s there.

Move to a new computer

Install the app on the new computer (Install).
Copy your asset folders to the new computer.
Copy library.db, settings.cfg and, if you have it, extracted_packs/ from the old data folder into the new one. Do this before you open the app there, or quit it first.
Open the app.

The library remembers each folder by its full path. Where the paths are the same on the new computer (same drive letters, same user name, same folder layout), everything just works. Where they aren’t, the next scan marks that folder’s assets as missing:

For a few files, use Locate… in Health → Missing files to point each asset at its new location. It keeps its tags and collections.
For a whole folder, you can add it again under its new path with Add to library… and remove the old one, but the new assets start without the old tags and collections.

The same applies to imported zips, whose extracted copies sit inside the data folder: if the data folder’s path changed (a different user name, or another OS), re-import those zips.

Start over

To start again with an empty library:

Quit the app.
Delete library.db (and any library.db-journal, -wal or -shm file next to it).
Optionally delete extracted_packs/, the library.db.bak-v* backups and cache/.
To reset your preferences too, delete settings.cfg.

The next launch opens on the empty first-run screen. None of this touches your asset files.

To keep your library but drop one folder, remove it from the library instead (see Settings → Folders + packs).