Do You Need to Delete Spotify Before Installing Spicetify?

If you've landed here, you're probably ready to customize Spotify with Spicetify and wondering whether you need to wipe your existing Spotify installation first. The short answer is: no, you generally don't need to delete Spotify before installing Spicetify — but that comes with important context about how Spicetify works, what it actually modifies, and where things can go wrong depending on your setup.

What Spicetify Actually Does to Spotify

Spicetify is a command-line tool that patches the Spotify desktop client rather than replacing it. It reads Spotify's local app files — primarily the JavaScript and CSS bundles that control the app's interface — and injects custom themes, extensions, and modifications directly into those files.

This means Spicetify doesn't install a separate application. It wraps around your existing Spotify installation. For Spicetify to function correctly, Spotify must already be installed on your machine. If you deleted Spotify first, you'd need to reinstall it before Spicetify could do anything.

Why the "Delete First" Question Comes Up

The confusion usually stems from a few real scenarios:

• Previous failed Spicetify installs — If an earlier attempt broke something or left corrupted patches, a clean Spotify reinstall can clear the state before trying again.
• Spotify version mismatches — Spicetify is sensitive to specific Spotify versions. If you're running a version that's too new or too old for your current Spicetify build, things may not apply correctly.
• Leftover Spicetify config files — Even if Spicetify itself is removed, its configuration folder (typically in your user profile directory) can persist and conflict with a fresh setup.

None of these situations require deleting Spotify before a first-time Spicetify install. They're more relevant when troubleshooting or starting over after a broken state.

How a Standard First-Time Installation Works

For most users doing a clean Spicetify setup, the process looks like this:

1. Spotify is already installed and working normally
2. Spicetify is installed via a package manager (like winget or scoop on Windows, or brew on macOS) or directly via its install script
3. Spicetify's backup command saves a copy of Spotify's original files
4. Spicetify's apply command patches those files with your chosen theme and extensions
5. Spotify relaunches with the modifications active

At no point in this standard flow is uninstalling Spotify a required or recommended step.

When Reinstalling Spotify First Actually Makes Sense 🛠️

There are legitimate cases where starting with a fresh Spotify install improves your outcome:

Pinning a Spotify version is worth highlighting separately. Spotify auto-updates aggressively, and Spicetify patches can break after an update because the underlying JavaScript bundle changes. Some users deliberately block Spotify updates and work from a known compatible version. In that workflow, uninstalling first gives you control over which version you're working with.

The Backup Command Is Your Safety Net

One thing that catches new users off guard: Spicetify's backup command stores a snapshot of Spotify's original, unpatched files. If anything goes wrong with your patches, running spicetify restore rolls your Spotify installation back to that backed-up state — no reinstall needed.

This is why the backup step matters and why skipping it creates problems. If you don't have a clean backup (because Spotify updated, or because you skipped the step), you lose that safety net and a full Spotify reinstall becomes the easiest recovery path.

Variables That Change the Answer for Your Setup

Whether your install goes smoothly or requires extra steps depends on several factors:

• Operating system — The Spicetify install path and file locations differ between Windows, macOS, and Linux. Some package managers handle this more cleanly than others.
• Spotify installation type — On Windows, Spotify can be installed as a user-level app (the default) or system-wide. Spicetify typically expects the user-level install. Using the Microsoft Store version of Spotify is a known compatibility issue — Spicetify doesn't support it.
• Spotify version — Newer Spotify releases occasionally restructure internal files in ways that break Spicetify until the tool is updated to match. Running the latest Spotify isn't always the right move when using Spicetify.
• Prior Spicetify history on the machine — Existing config files, leftover backups, or partially applied patches from a previous setup all affect how a new install behaves.
• Technical comfort level — The command-line nature of Spicetify means errors surface as text output, and interpreting those messages correctly changes what your next step should be. 🖥️

What Happens With the Microsoft Store Version

This is worth calling out directly: if your Spotify was installed through the Microsoft Store, Spicetify cannot patch it. The Store version of Spotify is sandboxed in a way that prevents external tools from modifying its files. In this specific case, you would need to uninstall that version and reinstall Spotify using the standalone installer from Spotify's website before Spicetify can work at all.

This is one of the clearer situations where the version of Spotify you have installed genuinely determines whether any of this works — not just how smoothly it works. ⚙️

The Factor This Article Can't Resolve

The steps above describe how Spicetify works in general terms, and they hold for most standard setups. But your specific situation — which OS you're on, how Spotify was installed, whether you've attempted this before, and which Spicetify version you're running — shapes whether a straightforward install or a clean-slate approach is the right call for you.