# Spicetify Marketplace for Spotify Extensions and Themes > Spicetify Marketplace is a TypeScript custom app for browsing and installing extensions, themes, and CSS snippets from within Spicetify. It is a convenient option for Spotify customization, but custom apps still require manual installation. **spicetify/marketplace** — Download extensions and themes directly from Spicetify - Repository: https://github.com/spicetify/marketplace - Stars: 1,589 · Forks: 332 - Language: TypeScript - License: MIT - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/spicetify-marketplace ## Why Spicetify Marketplace Exists Spicetify Marketplace addresses the gap between having Spicetify available and finding a visual way to manage Spotify client customization. Its stated purpose is to let users "browse, download, and install" extensions, themes, and CSS snippets directly from within Spicetify. The target audience is therefore not general Spotify listeners, but users who have adopted Spicetify and want access to client modifications through an interface rather than a separate catalog workflow. The scope is narrower than the word Marketplace might imply. Extensions, themes, and CSS snippets are the directly supported categories in the README. Custom apps can also be browsed, but the project explicitly says that making them work requires some manual installation. That distinction matters because an installed item is not necessarily a finished configuration in every category. The project is a custom application built with Spicetify Creator. Its primary language is TypeScript, and the repository includes a standard source tree under `src/`, TypeScript configuration, a workspace lockfile, linting configuration, and build scripts. This makes it a development repository as well as an application with an end-user interface. ## Marketplace and Spicetify Data Flow The repository information supports a straightforward integration model: Marketplace runs inside Spicetify and presents a catalog for user-selected customizations. The README identifies browsing, downloading, and installation as the core operations. It does not expose catalog source code, update behavior, conflict handling, or the exact filesystem destinations, so those parts of the installation pipeline cannot be confirmed from the available documentation. The TypeScript project adds clues about the implementation surface. `package.json` includes `react-i18next` and `i18next`, indicating that the interface includes localization support. `semver` is present, which is consistent with version handling somewhere in the application, although the available files do not show how a selected release is matched to the local Spicetify environment. `dexie` is also listed, but the repository data does not document whether it stores catalog data, preferences, or another kind of local state. For drag-and-drop or list interaction, the project includes `@hello-pangea/dnd`. That dependency does not prove a particular workflow without source-level details, but it shows that interaction libraries are part of the application. The safe conclusion is limited: Marketplace provides an in-client discovery and installation interface for selected Spotify customizations, while custom apps cross a boundary that requires additional user action. ## Installing Marketplace and Completing a First Use The README does not contain direct installation commands. Instead, it directs users to the project's wiki and specifically links the `Installation` page under `https://github.com/spicetify/marketplace/wiki`. That wiki is the documented starting point for obtaining and installing the application, so no unsupported command, package invocation, port, or configuration flag is reproduced here. After installation, the first real use described by the README is to open Marketplace within Spicetify and browse its entries. From there, a user can select an extension, theme, or CSS snippet and use the interface to download and install it. The expected result is that the chosen customization is added to the Spotify client through Spicetify. Custom apps need separate treatment. The README says they can be browsed, but manual installation is required to get them working. It does not define which files must be copied, where they belong, or when Spicetify must be reapplied. Those details must come from the linked wiki or the custom app's own documentation. This is the main tutorial boundary: Marketplace can start the normal extension, theme, and snippet workflow, but it does not promise a fully automatic custom-app setup. ## Package Requirements for Contributors The repository does not publish a complete contributor setup in the README, but `package.json` gives concrete requirements for working on the source. It declares Node.js `>=24`, pnpm `>=11`, and package manager `pnpm@11.9.0`. It also states `npm` as `please-use-pnpm` and `yarn` as `please-use-pnpm`, which means the package metadata directs developers to pnpm rather than presenting npm or yarn as supported alternatives. The package declares itself private, with version `1.0.11`. That setting describes package publication status, not the project's release history. The repository does list version `v1.0.11` as a recent release, but it does not imply that this private package is intended for direct public installation through a package registry. Contributor commands are present and can be run from the repository. These examples are source-development operations, not end-user installation steps. ## Building and Checking the Marketplace Source For contributors, the repository defines a production build as a local minified build followed by copying documentation into `dist/`. The local build uses `spicetify-creator` with the output directory set to `dist` and minification enabled. The general `build` script delegates to `spicetify-creator`, while the watch script starts the same creator tool in watch mode. The following commands are copied from the package scripts. They build the project or check its TypeScript and lint configuration. ## TypeScript, Biome, and Release Checks The repository separates compilation checking from formatting and linting. `type-check` runs TypeScript without emitting output. `lint:ci` runs Biome in check mode across the repository, while the `lint` script uses Biome's write mode on `./src`. That distinction is useful for contributors: the check command is suitable for validation, whereas the write command is intended to modify source files. The source project also includes Husky through a `prepare` script, indicating that package preparation is connected to repository hooks. The available package metadata does not explain which hooks are installed or what behavior they enforce. For contributors who need to refresh Spicetify's type definitions, the repository defines an `update-types` script. It downloads `globals.d.ts` from the Spicetify CLI repository into `src/types/spicetify.d.ts`. The command is explicit about the source and destination, but it also means contributors should review how that file changes before committing it. ## Maintenance, Licensing, and Upgrade Boundaries The repository is not archived. Its last push was on 2026-10-04, and recent releases include `v1.0.11` on 2026-09-02, `v1.0.10` on 2026-08-29, and `v1.0.9` on 2026-07-04. That history supports a recent release cadence, but the README does not document a compatibility policy for Spotify client versions, Spicetify CLI versions, or individual Marketplace items. The project is licensed under MIT. The repository includes `LICENSE`, while `package.json` also marks the package private. The MIT label indicates the repository's stated licensing model, but it does not by itself establish the license of every extension, theme, CSS snippet, or custom app browsed through Marketplace. Users would need to inspect each item's own license before redistribution or other reuse. Maintenance cost is therefore partly an integration question. Upgrading Marketplace may interact with a separately installed Spicetify CLI and a locally customized Spotify client. The repository documents no rollback procedure, migration notes, or automated compatibility check for installed marketplace items. The source-level commands above address building and validation, not recovery from a failed installation. ## When Marketplace Is the Wrong Choice The clearest wrong-fit case is a user whose main goal is installing a custom app with no further work. Marketplace can display custom apps, but the README explicitly says that manual installation is needed to get them working. A graphical catalog entry therefore does not guarantee a finished app. It is also a poor fit for users who do not already use Spicetify or do not want to customize the Spotify desktop client. The project's premise is integration with Spicetify, not a general extension installer for every Spotify installation. The available documentation does not describe browser, mobile, or web-client support. Compared with manual installation, Marketplace changes the approach from finding and configuring each customization yourself to browsing and selecting it through an in-client interface. That is useful for extensions, themes, and CSS snippets, but the project does not claim that it removes setup for every package type. The alternative is appropriate when automatic discovery is less important than exact control over each installation step. ## Conclusion Spicetify Marketplace fits users who already use Spicetify and want a graphical route to Spotify extensions, themes, and CSS snippets. It is less suitable for users who need custom apps to work after a single Marketplace action or who cannot meet the repository's Node.js 24 and pnpm 11 development requirements. Before adopting it, verify the documented Spicetify installation path, the effect of an item on the local Spotify installation, and whether any custom app requires the manual setup described by the README. ## FAQ ### How do I install Spicetify Marketplace? The README does not provide direct installation commands. It directs users to the project's `Installation` wiki page under `https://github.com/spicetify/marketplace/wiki/Installation`. ### Can Spicetify Marketplace install custom apps automatically? No automatic custom-app setup is documented. The README says that users can browse custom apps but must do some manual installation to get them working. ### What can I install with Spicetify Marketplace? Marketplace supports browsing, downloading, and installing extensions, themes, and CSS snippets. Custom apps are browseable but require additional manual installation. ## Sources - [Issues](https://github.com/spicetify/marketplace/issues) - [License: MIT](https://github.com/spicetify/marketplace/blob/main/LICENSE) - [README](https://github.com/spicetify/marketplace/blob/main/README.md) - [Releases](https://github.com/spicetify/marketplace/releases) - [spicetify/marketplace on GitHub](https://github.com/spicetify/marketplace) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/spicetify-marketplace