# SpotX: patching the Windows Spotify desktop client from PowerShell

> SpotX is a PowerShell patcher for the official Spotify desktop client on Windows. It blocks banner, video and audio ads, hides podcast and audiobook sections, and can freeze the client at a chosen version.

**SpotX-Official/SpotX** — SpotX patcher used for patching the desktop version of Spotify

- Repository: https://github.com/SpotX-Official/SpotX
- Stars: 22,505 · Forks: 1,131
- Language: PowerShell
- License: MIT
- Published: 2026-09-21 · Updated: 2026-09-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/spotx-official-spotx

## The problem SpotX addresses, and who it is actually for

The official Spotify desktop client on Windows shows banner, video and audio ads on free accounts, pushes podcast, episode and audiobook tiles onto the homepage, and updates itself on its own schedule. SpotX is a patcher that modifies the installed client so those behaviours change. The repository describes it as a "Patcher for Spotify Desktop Client on Windows", and the feature list is short and specific: block banner, video and audio ads, optionally hide podcasts, episodes and audiobooks from the homepage, optionally block automatic updates, change some native experimental features, and disable analytics sending.

The audience is narrow. The requirements section names Windows 7 through 11, the official desktop build of Spotify, and PowerShell 5.1 or above. It also states plainly that the Microsoft Store version is not suitable. That single line removes a large share of potential users, because the Store build is what many people get by default on Windows 11. If your Spotify came from the Store, this tool is not for you and the README does not offer a workaround.

There is a companion project, SpotX-Bash, linked from the README badges for Mac and Linux. The Windows patcher does not cover those platforms. Anyone searching for a Mac or Linux install should follow that separate repository instead, because the PowerShell script here is Windows-only by construction.

## How the patcher works: run.ps1, patches and helper directories

The entry point is run.ps1 at the repository root. The README's install commands all download that script and pipe it into Invoke-Expression, which is the PowerShell idiom iex "& { $(iwr -useb ...) }" with flags appended. So the user never clones the repository for a normal install: the script is fetched over HTTPS and executed in memory.

Alongside run.ps1 the repository layout shows directories named patches/, js-helper/, css-helper/, res/ and scripts/. The names line up with what a client patcher has to touch. Spotify's desktop client ships JavaScript and CSS assets, and the helper directories plus the patches directory are where the replacement or modified files live. The scripts/ directory holds the batch wrappers, including Install_Auto.bat referenced in the full-installation instructions.

What the script does at a high level, according to the README, is install or confirm a recommended version of Spotify, apply the chosen set of modifications, and optionally block updates and start the client. The flags control which of those steps run. For example -confirm_uninstall_ms_spoti removes a Microsoft Store copy if one is found, -confirm_spoti_recomended_over installs over an existing client, -podcasts_off hides podcast content, -block_update_on disables updates, and -start_spoti launches Spotify when the script finishes. Flags are the whole interface; there is no configuration file documented in the README.

## Installing SpotX on Windows and running a first patch

The README offers several install paths. The simplest for a new user is the new-theme install, which activates the current sidebar layout and includes all experimental features. You can either download Install_New_theme.bat and run it, or paste the PowerShell one-liner below. The script downloads run.ps1 and executes it with the -new_theme flag.

```ps1
iex "& { $(iwr -useb 'https://raw.githubusercontent.com/SpotX-Official/SpotX/refs/heads/main/run.ps1') } -new_theme"
```

During the run the README says you will be asked to confirm some actions. Expect prompts about the Spotify client it found and about the modifications it is about to apply. When it finishes, launch Spotify and check the sidebar: the new-theme install changes the right and left sidebar and some cover art.

If the GitHub raw URL is unreachable, the README provides a mirror hosted on the project's GitHub Pages site. The only difference is the -m flag and the different URL.

```ps1
iex "& { $(iwr -useb 'https://spotx-official.github.io/SpotX/run.ps1') } -m -new_theme"
```

For an unattended install the README gives a full command that removes a Store copy if present, installs the recommended Spotify version over any existing client, turns off podcasts, blocks updates, disables ad-like sections, sets the lyrics theme to spotify, applies the new theme, and starts the client at the end.

```ps1
iex "& { $(iwr -useb 'https://raw.githubusercontent.com/SpotX-Official/SpotX/refs/heads/main/run.ps1') } -confirm_uninstall_ms_spoti -confirm_spoti_recomended_over -podcasts_off -block_update_on -start_spoti -new_theme -adsections_off -lyrics_stat spotify"
```

There is also an old-theme path. The README notes that the old theme was removed in later Spotify versions, so that install forces version 1.2.13 and turns update blocking on by default. Treat it as a legacy option rather than the default choice, since it pins you to an old client.

To undo everything, the README points at Uninstall.bat, or at reinstalling Spotify, with a separate Uninstall-Spotify project recommended for a full removal.

## Where SpotX breaks down: Store builds, platforms and pinned versions

The most concrete limitation is the one the README states outright: the Microsoft Store version of Spotify is not suitable. That is not a preference, it is a structural constraint. The patcher expects the filesystem layout of the official desktop installer, and the Store package does not have it. If you are on a machine where Spotify arrived through the Store, the script's -confirm_uninstall_ms_spoti flag exists precisely to remove that copy before installing the desktop build instead. That is a bigger change than most people expect from an ad blocker.

The second constraint is the platform. This repository is PowerShell and Windows. Searches for SpotX on Mac, Linux, Android or iOS do not map onto this codebase; the README links SpotX-Bash for Mac and Linux, and nothing here addresses mobile.

The third is version pinning. Blocking updates is offered as a feature, and the old-theme install forces Spotify 1.2.13 because the old theme no longer exists in later builds. Pinning protects the patch from being overwritten by an update, but it also means you stay on whatever client version the patch was written against. The README does not document a rollback path other than uninstalling, and it does not describe how patches are kept in step with new Spotify releases. That is a maintenance risk the user carries, not the project.

Finally, the disclaimer describes SpotX as modifying the official client and being provided as an evaluation version, used at the user's own risk. That is the project's own framing, and it should be read literally.

## SpotX versus SpotX-Bash: the same idea, two codebases

The obvious alternative is the project's own sibling, SpotX-Bash, which the README links for Mac and Linux. The difference is not a matter of taste: it is a different shell and a different set of client file paths. SpotX-Bash is written for bash, so the install commands, the flag syntax and the surrounding tooling all differ from the PowerShell one-liners shown here. If you are on macOS or Linux, SpotX-Bash is the relevant project and this Windows patcher is the wrong tool.

Within Windows, the alternative to patching is simply not patching: keep the official client as shipped, accept the ads on a free account, or pay for Premium. The README acknowledges that second path directly by offering a premium install mode, which applies the theme and experimental features but disables only audio ads in podcasts rather than blocking ads generally. If you already pay for Spotify, that mode is the honest fit.

A third alternative is a DNS-level or system-wide ad blocker. That approach filters traffic before it reaches the client, which means it does not touch Spotify's files and survives client updates. The trade-off runs the other way: it cannot hide homepage sections, cannot change experimental features, and cannot pin the client version, because it never modifies the client. SpotX changes the client itself, which is why it can do those things and why uninstalling it means restoring or reinstalling Spotify.

## Licence, maintenance and the cost of staying patched

The repository is MIT licensed. In practical terms that is permissive: you can read, modify and redistribute the code, and the LICENSE file at the repository root carries the terms. Note the split between the licence on the patcher code and the status of the Spotify client it modifies. MIT covers SpotX's own source, not Spotify's binaries, and the README's disclaimer frames the patched client as an evaluation version used at your own risk. That is a statement about the project's posture, not legal advice, and anyone distributing a patched client commercially should look at the licence and disclaimer themselves rather than take this paragraph as guidance.

The last push to the repository was on 2026-09-09, so the project is not dormant. Release tags are much sparser: 1.9 in January 2025, 1.8 in August 2023, 1.7 in December 2022. The gap between continuous commits and rare tagged releases matters if you depend on versioned artifacts. The install instructions do not point at a release tag; they fetch run.ps1 from the main branch. That means every install pulls whatever is current on main, and there is no documented way to pin the patcher itself to release 1.9.

The upgrade cost is asymmetric. Updating the patcher is cheap: rerun the same one-liner. Keeping the patch working against a moving Spotify client is the expensive part, and the README's answer to that is the -block_update_on flag, which trades currency for stability. If you do not block updates, expect to rerun the patcher after Spotify updates itself.

## Conclusion

SpotX fits Windows users running the official Spotify desktop client who want ad blocking and are willing to let a script modify that client's files. It is not for Mac, Linux, Android or iOS users, not for Microsoft Store installs, and not for anyone who wants to keep Spotify's automatic updates. Before running it, confirm your client came from the official desktop download rather than the Store, check that PowerShell 5.1 or newer is available, and read the parameters discussion linked from the README if you want anything other than the default new-theme install. Uninstalling is a separate script, Uninstall.bat, and the README treats a full Spotify reinstall as the alternative.

## FAQ

### What is SpotX?

SpotX is a PowerShell patcher for the official Spotify desktop client on Windows. It blocks banner, video and audio ads, can hide podcasts, episodes and audiobooks from the homepage, and can block Spotify's automatic updates.

### How to install SpotX on Windows?

Download and run Install_New_theme.bat, or run the PowerShell command from the README that fetches run.ps1 and passes -new_theme. The README states you need Windows 7 to 11, the official desktop version of Spotify, and PowerShell 5.1 or above.

### How to use SpotX?

Run the install command with the flags for the behaviour you want, for example -podcasts_off to hide podcasts, -block_update_on to stop Spotify updating, and -start_spoti to launch the client when the script finishes. The README points to a separate discussion page for the full parameter list.

### Can I install SpotX on Linux or Mac?

Not with this repository, which is a Windows PowerShell patcher. The README links SpotX-Bash for Mac and Linux, and that is the project to use on those platforms.

### How do I install SpotX on Android?

This repository does not cover Android. It is a PowerShell patcher for the Spotify desktop client on Windows, and the README only links SpotX-Bash for Mac and Linux as a companion project.

## Sources

- [Issues](https://github.com/SpotX-Official/SpotX/issues)
- [License: MIT](https://github.com/SpotX-Official/SpotX/blob/main/LICENSE)
- [README](https://github.com/SpotX-Official/SpotX/blob/main/README.md)
- [Releases](https://github.com/SpotX-Official/SpotX/releases)
- [SpotX-Official/SpotX on GitHub](https://github.com/SpotX-Official/SpotX)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/spotx-official-spotx