spicetify-themes: What You Get From the Community Theme Collection

What spicetify-themes is for, and who should skip it

spicetify-themes is a repository of CSS themes for the Spicetify CLI, the command-line tool the README describes as a way to customize Spotify. The repository holds one folder per theme at the top level: Blossom, BurntSienna, Default, Dreary, Dribbblish, Flow, Matte, Nightlight, Onepunch, SharkBlue, Sleek, StarryNight, Turntable and Ziro. Each folder carries the CSS and any assets that theme needs. The README points to THEMES.md for previews of all of them.

The audience is narrow and specific. You need Spotify installed, the Spicetify CLI installed, and a willingness to run shell commands and edit Spicetify's configuration. If you want a theme without installing Spicetify first, this repository will not help you: it ships no installer of its own and no standalone application. The README states plainly that the themes require the latest version of Spotify and the latest version of Spicetify, and that the Spotify ad-blocked version is not supported. That last line rules out a common setup, so read it before cloning.

One structural detail matters for expectations. This is a collection, not a single theme with a configuration file. Quality and maintenance differ folder by folder, and the README treats Dribbblish and Turntable as special cases that need their own READMEs followed instead of the generic steps.

How the themes reach Spotify: folders, config keys, CSS injection

The mechanism is file placement plus a config key. Spicetify reads themes from a Themes directory inside its configuration folder. The repository does not patch that directory itself; you copy theme folders into it, then tell Spicetify which folder to use by name.

Two config keys do the work. current_theme selects the theme folder, and color_scheme selects a variant within it. The README notes that some themes have two or more color schemes, which is why the second key exists. The value you pass to current_theme is the folder name, so the names in the repository listing are the names you type.

The styling itself is CSS. The primary language of the repository is CSS, and the theme folders contain the stylesheets that restyle Spotify's interface after Spicetify applies them. The _Extra folder sits outside the theme folders and, per the README, holds additional resources for tweaking the look. Its own README carries the details.

The manifest.json at the top level and the .github folder are repository infrastructure rather than theme content. If you are browsing to pick a theme, ignore them and start from THEMES.md.

Installing spicetify-themes and applying your first theme

The README gives a three-step path. First clone the repository with a shallow clone, which keeps the download small since you only need the current files.

git clone --depth=1 https://github.com/spicetify/spicetify-themes.git

Second, copy the contents into the Spicetify Themes folder. On Linux and macOS the README uses the same destination path, and on Windows it derives the path from the Spicetify config command.

cd spicetify-themes
cp -r * ~/.config/spicetify/Themes

On Windows the README uses PowerShell instead:

cd spicetify-themes
cp * "$(spicetify -c | Split-Path)\Themes\" -Recurse

Third, select a theme by name. Replace THEME_NAME with a folder name from the repository, for example Matte.

spicetify config current_theme THEME_NAME

If the theme ships multiple color schemes, switch between them with the second key:

spicetify config color_scheme SCHEME_NAME

After the config commands, Spotify has to be restarted for the change to appear. The README's install section ends at the config step; it does not spell out the apply or restart commands, so check the Spicetify documentation for the exact sequence on your platform. Arch Linux users have a shorter route: the README notes the project is on the AUR as spicetify-themes-git.

Where this collection breaks down

The most concrete limitation is stated in the README itself: Dribbblish and Turntable do not follow the generic install steps. For those two you must read their own READMEs. A reader who copies everything and then runs the config command for Dribbblish may find the theme does not behave as the generic path implies, and the top-level README will not explain why.

The second constraint is the version requirement. The README asks for the latest Spotify and the latest Spicetify. That is not a soft preference: themes restyle Spotify's interface, and when Spotify changes its markup, CSS written against the old structure can stop matching. The repository has no published release history, so there is no changelog to check for compatibility notes. Your fallback is the theme folder's own files and, for Dribbblish and Turntable, their READMEs.

The third is the support model. The README asks people not to open issues for general support and directs them to the subreddit or the Discord server instead, reserving GitHub issues for bugs and feature requests. If you want a guaranteed answer channel, this is not it.

Finally, the ad-blocked Spotify build is unsupported. If that is your setup, the themes are outside the supported configuration regardless of how carefully you install them.

spicetify-themes against Marketplace and single-theme repositories

The real alternative is not another theme collection but a different delivery path: Spicetify Marketplace, which the related searches show people ask about alongside this repository. The difference is architectural. spicetify-themes gives you files in a git repository that you copy into the Themes directory yourself and select with spicetify config. Marketplace is an in-client route, so the install and update steps live inside Spotify rather than in your shell. If you want to browse and switch themes without touching the filesystem, Marketplace is the closer fit; if you want the theme files on disk, under version control, and reviewable before they are applied, this repository is.

The other alternative is a single-theme repository. DribbblishDynamic, linked from the README's useful resources section, is exactly that: one theme, maintained on its own, with its own install instructions. A dedicated repository can move faster on its one theme and can document its own edge cases in full. The trade-off is breadth. Here you get fourteen theme folders in one clone and one set of commands, at the cost of per-theme documentation that varies and, for two themes, diverges from the main path entirely.

The README also links SpotifyNoPremium, described as a Spicetify theme without free-version UI elements such as the Upgrade button. That is a different goal from restyling: it targets interface elements tied to the free tier, so it is not a like-for-like substitute for the themes in this collection.

Licence, maintenance and the cost of updating

The repository is MIT licensed, which is permissive and places few conditions on reuse of the theme files. The licence text is at the top level as LICENSE. This is a description of the repository's stated licence, not legal advice; if you redistribute theme files, read the licence yourself.

On maintenance, the last push to the default branch was on 2026-09-16, and the repository is not archived. That is recent activity, but there is no tagged version to pin to. Updating means pulling the repository again and re-copying the theme folders, which overwrites the copies in your Themes directory. Any local edits you made to a theme's CSS are lost in that overwrite unless you keep them somewhere else.

The version coupling is the ongoing cost. Because the README requires current Spotify and current Spicetify, a Spotify update can change the interface your chosen theme was written against. When that happens, the fix is either a change in the theme folder upstream or a local edit you maintain yourself. Budget for the second case, since the README directs support questions to Reddit and Discord rather than the issue tracker.

Editorial conclusion

Adopt it if you already run the Spicetify CLI and want a maintained set of CSS themes with documented install steps and per-theme color schemes. Do not adopt it as a first step: it is a theme collection, not the tool that patches Spotify, and the README points to the Spicetify docs for that. Before copying anything, confirm your Spotify and Spicetify versions are current, since the README requires the latest of both, and check the README of your chosen theme, because Dribbblish and Turntable do not follow the generic install path.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. README
4. spicetify/spicetify-themes on GitHub