Where Does cmus Store Config and Library?
Where cmus keeps its config, library cache, and playlists on Linux systems.
Last updated
cmus keeps a small home dir at ~/.config/cmus: an rc file for bindings and options, a cache file with scanned metadata, and playlist files beside them. Older builds used ~/.cmus instead.
The cache is disposable; the rc and playlists are not. Rescanning with :update-cache rebuilds metadata from disk. Keep music on stable mount paths since the cache keys off filenames.
Where cmus stores this, by platform
~/.config/cmus/
rc config, cache metadata, and playlist files together. Legacy ~/.cmus/ seen on old installs. Rebuild with :add plus :update-cache after wiping cache.
Frequently asked questions
How do I rebuild the cmus library?
Quit cmus, delete the cache file below, and relaunch, then :add your music dir again. Playlists in the same folder survive a cache wipe. A corrupt cache shows as an empty library despite files existing.
Where are playlists versus config?
Playlists live as plain files in the same config dir (one per list). Back them up with the rc file. Keybindings and theme lines sit in the rc; the cache file holds only scanned metadata.
Notice an outdated path? Let us know.