Where Is the MPD Config File?
MPD musicpd.conf locations on Linux for user and system-wide daemon setups.
Last updated
MPD reads its music directory, playlists, database and audio outputs from musicpd.conf, in either a user config or the system /etc path. The database and state files land wherever the config points.
User services and system services use different files, which causes half of all MPD confusion. Check which unit runs before editing or changes apply to the wrong daemon.
Where MPD stores this, by platform
~/.config/mpd/mpd.conf
User-level config for systemd user services and manual launches. System-wide installs use /etc/mpd.conf instead with state under /var/lib/mpd. Confirm which daemon runs with systemctl status before editing. Copy the config plus database and playlists to migrate.
Frequently asked questions
MPD ignores my config changes. Why?
You edited the user file while the system service runs, or vice versa. Match the file above to the active unit and restart that one.
Where is the MPD database?
Wherever db_file points in the config above, commonly ~/.local/share/mpd/database. Delete it to force a full rescan.
Notice an outdated path? Let us know.