Where Does Sitala Save User Kits?
Sitala saves user kits as .sitala files to its kits library, with samples referenced from your folders.
Last updated
Sitala ships factory kits (808, retro pop, hip hop) inside the plugin. Your own kits save as .sitala files to the user kits library from the kit menu. Samples can stay in your own sample folders, since kits reference them by path.
That reference model matters for backup. Copy the .sitala kit plus every sample folder it points at. The missing sample finder leans on Spotlight or Windows Search, so keep names stable when moving libraries between machines.
Where Sitala stores this, by platform
User kits library (in-app, .sitala files)
Save from the kit menu, then keep exported .sitala files with your samples. VST lives in the standard Steinberg plugin folder. Kits and plugin are separate backups.
User kits library (in-app, .sitala files)
Same kit model across VST, AU, and standalone. Export kits you share with collaborators. iOS kits load on desktop and back, which helps round trips.
User kits library (in-app, .sitala files)
Plugin .so sits in the LXVST path. Keep .sitala kits plus samples in a versioned folder. Moving samples without the finder index breaks kit loads.
Frequently asked questions
What file do I share for a Sitala kit?
The .sitala kit file plus the samples it uses, or a folder with both. Factory kits travel with the installer. Custom kits need their sample folders alongside.
Why does Sitala say samples are missing?
The kit references moved files. Point the finder at the new folder or restore original paths. Its search uses system indexing, so let indexing finish on big sample drives.
Notice an outdated path? Let us know.