Where Does Spicetify Store Config and Themes?
Spicetify config, themes and extensions on every OS, and why Store Spotify breaks it.
Last updated
Spicetify centers on config-xpui.ini with spotify_path, prefs_path, current theme and the extensions pipe list: %APPDATA%\spicetify on Windows, ~/.config/spicetify on Mac and Linux ($XDG_CONFIG_HOME and $SPICETIFY_CONFIG respected). Themes/, Extensions/ and CustomApps/ sit beside it.
Home dir copies beat exe dir copies when both exist. Microsoft Store Spotify is unsupported: reinstall Spotify from the web installer first or every path autodetect fails. When prefs detection fails, set both paths by hand in the ini; spicetify config-dir prints the live root whenever unsure.
Where Spicetify stores this, by platform
%APPDATA%\spicetify\config-xpui.ini
Main config plus Themes/<name> (color.ini, user.css), Extensions/ and CustomApps/ alongside. Store Spotify unsupported; use the web installer. Find the root with spicetify config-dir.
~/.config/spicetify/config-xpui.ini
Same ini role (Mac uses ~/.config, not ~/Library, per Spicetify source). Same Themes/Extensions layout. Reset by deleting the ini and running spicetify again.
~/.config/spicetify/config-xpui.ini
Same role ($XDG_CONFIG_HOME or $SPICETIFY_CONFIG override). Set spotify_path and prefs_path manually if autodetect fails. Same Themes/Extensions layout.
Frequently asked questions
Why does Spicetify say Spotify not found?
Usually Store Spotify, which Spicetify cannot hook. Reinstall Spotify from its website, then set spotify_path and prefs_path by hand in config-xpui.ini if detection still misses.
How do I reset Spicetify to defaults?
Delete config-xpui.ini and run spicetify once. Themes and extensions stay in place; only the active selection and paths regenerate.
Notice an outdated path? Let us know.