Where Does Mopidy Store Config and Library Data?
Where Mopidy reads mopidy.conf and keeps its cache, local scan data, and extension state on Linux.
Last updated
Mopidy reads mopidy.conf from the XDG config home (~/.config/mopidy/mopidy.conf), with /etc/mopidy/mopidy.conf serving system installs. Extensions add their own sections to the same file, and mopidy config prints the merged result.
State fans out from there: scan data in ~/.local/share/mopidy, transient cache in ~/.cache/mopidy. The config names every one of those paths, so the conf file is both settings and map. When tracks vanish, suspect the scan database before the config.
Where Mopidy stores this, by platform
~/.config/mopidy/mopidy.conf
mopidy.conf with [local], [mpd], [http], and extension sections. Honors $XDG_CONFIG_HOME. Systemd user units and system units read different files, so confirm which unit runs before editing.
Frequently asked questions
where is the mopidy music library database
In mopidy.conf via media_dirs plus the local scan database in the configured data_dir (~/.local/share/mopidy/local). Rescan with mopidy local scan after adding files. A stale scan database is the usual missing tracks culprit, not the config.
how do i see the effective mopidy config
In the [service] and extension sections of the same mopidy.conf. mopidy config prints the effective merged file with secrets redacted, which beats reading three candidate files. System services read /etc/mopidy/mopidy.conf instead of the user one.
where does mopidy keep cache and tokens
In cache/ and data dirs under ~/.cache/mopidy and ~/.local/share/mopidy. Deleting them with Mopidy stopped forces clean rebuilds. API tokens for Spotify and friends live in the conf, so keep that file private.
Notice an outdated path? Let us know.