Spicetify themes: fourteen CSS folders and the two keys that switch them

Fourteen theme folders at the top level

The repository root is the catalogue. Fourteen directories hold a theme each: Blossom, BurntSienna, Default, Dreary, Dribbblish, Flow, Matte, Nightlight, Onepunch, SharkBlue, Sleek, StarryNight, Turntable and Ziro. Beside them sit _Extra/, a text/ folder, manifest.json, THEMES.md, CONTRIBUTING.md and CODE_OF_CONDUCT.md. The primary language here is CSS, so a theme is a stylesheet tree rather than a plugin and nothing has to be compiled before Spicetify reads it. THEMES.md is where previews of all the themes live, which means the visual comparison happens in one separate file instead of in the folders themselves. The directory name is the identifier: whatever Spicetify later holds as current_theme is one of those fourteen names.

Install is a shallow clone and a copy into Themes

Installation is two steps, both written out in full. The clone is shallow on purpose, since a set of stylesheets does not need history:

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

Then the tree is copied into the Themes folder that Spicetify reads. Linux and macOS share the same destination path:

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

The copy is recursive and it takes everything, including manifest.json, THEMES.md and the documentation files, so the destination ends up holding files no player will read. There is no apply or refresh command afterwards. Switching is a separate action, and that is the next thing to look at.

Windows asks Spicetify for the config directory

Windows cannot use a fixed path, so the documented command asks the tool where its configuration lives and appends Themes to the answer. This is the only platform specific line in the whole install:

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

Arch Linux is the exception to the whole sequence: the project is packaged on the AUR as spicetify-themes-git, which removes the clone but not the requirement to have Spicetify installed already.

Two config keys pick the folder and the palette

Selecting a theme is a config write, not a file move. The value has to match a folder name:

spicetify config current_theme THEME_NAME

Themes that ship more than one palette add a second key:

spicetify config color_scheme SCHEME_NAME

That second command only means something for themes with two or more color schemes, and the scheme names live inside each theme folder rather than in any list here. Moving between them is the same config call again, so changing look costs no reinstall.

Dribbblish and Turntable need steps this repo will not print

Two themes are explicitly outside the clone and copy sequence. Installing Dribbblish and Turntable means following the READMEs inside those two theme folders instead of the generic recipe here. That split is a real gap for anyone who wants a scripted setup: the generic command covers the other twelve themes and stops working for these two, and the extra steps are in those themes' own READMEs. A separate DribbblishDynamic theme built for version 2 is linked as an alternative, and it lives in a different repository entirely. So the fast path has a known, named exception rather than a documented condition.

The ad-blocked Spotify build is refused, not warned about

The stated floor is the latest version of both Spotify and Spicetify, and there is one flat exclusion: the Spotify ad-blocked version is not supported. The other linked project addresses a different gap, a theme that removes free version UI elements such as the Upgrade button. Taken together the two links mark the boundary of the collection. It restyles an unmodified current client. Anything about accounts, unlock buttons or modified builds is handled outside this repository.

Support goes to Reddit and Discord, issues stay for bugs

There are rules about where to ask. GitHub issues are to be reserved for bug reports and feature requests, and general support questions are asked on the r/spicetify subreddit or on the project Discord server. If you cannot tell which channel fits, the guidance is to go for Reddit or Discord. The effect on a reader is real: a broken install leaves no written fix anywhere, because the answer lives in a conversation rather than in the tracker. Contributions follow the same split, going through a separate contribution guidelines document rather than through the issue queue.

No releases, a moving master branch, and an undocumented _Extra

What this repository does not do is worth stating plainly. It publishes no releases, so there is no version to pin and no upgrade path. The default branch is master, and the last push to it landed on 5 October 2026, which means the tree you copy today can change under you on the next clone. There is no rollback command, no description of what manifest.json holds, and no documentation for the text/ folder. The extra resources for tweaking the look of Spotify live in _Extra, and that folder points at a README of its own. Previews sit in THEMES.md, so choosing a theme means opening a second file, and no theme is described in prose anywhere here.

Editorial conclusion

Use this if you run the desktop client and want to change its colors from a terminal without writing CSS yourself. Skip it if you need a versioned release, an upgrade path, or an install that works on the ad-blocked client, because none of those exist here. Before copying, confirm your Spicetify is current and that the theme name you pass matches a folder exactly.

Frequently asked questions

Official sources

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