Uninstallation
To remove Spicetify, restore Spotify, then delete Spicetify’s files. If you only want to stop one module, disable it in the Module Store instead.
Restore Spotify
Run restore:
spicetify restorerestore stops the daemon, removes its auto-start entry, and puts back the stock client, including one that Spicetify v2 patched. The v2 CLI can’t undo a v3 apply.
If Spotify is already stock, restore says so and leaves the daemon in place. Run spicetify daemon stop to stop it and remove its auto-start entry.
Remove the files
spicetify path prints the config folder. Delete these:
- The config folder:
~/.config/spicetifyon macOS and Linux. It holdsconfig.toml, every installed module, and the Module Store’s records. To reinstall later with the same modules, keep it. - The install folder:
~/.spicetify, or%LOCALAPPDATA%\spicetifyon Windows. On Windows, this is also the config folder. If you installed with mise, runmise unuse -g 'packslip:github.com/spicetify/cli[prerelease=true]'instead. - The
PATHentry the installer added to your shell profile. On Windows, it’s in your userPATHenvironment variable. - The
spicetify://link handler thatapplyregistered:- macOS:
~/Applications/Spicetify.app - Linux:
~/.local/share/applications/spicetify-protocol.desktop - Windows: the registry key
HKEY_CURRENT_USER\Software\Classes\spicetify
- macOS:
Going back to v2
Restore with v3 first, then install v2 and apply with it. v3 never changes v2’s config-xpui.ini. See the v2 guide.