Spotube 6: a plugin-driven music player rebuilt on Compose Multiplatform, with a heavy native build
GitHub describes it as 🎧 Open source music streaming app! Available for both desktop & mobile!. The repository metadata lists Dart as its primary language. The metadata lists the NOASSERTION license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- Spotube is an AGPL-3.0 music streaming app whose catalog, playlists and audio all come from plugins. Version 6 moves it to Compose Multiplatform and GraalVM native builds, which changes what it takes to run it from source, especially on Linux.
- Who is it for?
- Spotube fits listeners who want an open-source, telemetry-free player and are comfortable choosing plugins as their music source. It is not a self-contained service: without a plugin for the platform you want, there is nothing to play.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly Dart, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- KRTirtho/spotube50,791 ★ · +2,460
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| KRTirtho/spotube | 48.3k | 50.8k |
2,460 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Plugins supply the metadata, the playlists and the audio
Spotube calls itself a cross-platform, extensible music streaming platform, and the extensible part carries most of the weight. The app does not ship a catalog of its own. Music metadata, playlists and the audio source are all brought in through plugins, either community plugins for popular platforms or ones you write yourself. The repository includes a plugin_interfaces directory and a js_plugin_example directory for that purpose.
The consequence is that what Spotube can actually play depends on which plugins exist and keep working. If the service you care about has no plugin, or its plugin breaks, the player has nothing to stream from it. The project frames this as a step toward decentralized music streaming; in practice it means the app is the shell and the plugins decide the experience. Time synced lyrics are the one feature promised regardless of plugin support.
No telemetry, and playback controlled on the device
The feature list makes several specific privacy claims: no telemetry, diagnostics or user data collection, and playback control handled locally rather than on a server. A PRIVACY_POLICY.md file sits at the root of the repository alongside the AGPL-3.0 LICENSE. Tracks can be downloaded with tagged metadata, and the project lists small size, lower data usage and native performance as goals.
Those claims cover the app. They do not cover the plugins you install, which talk to whatever service they were written for. Anyone weighing whether Spotube is safe to use should read the privacy policy for the app and then look separately at each plugin's source and the service behind it, since that is where your account and listening data actually go.
Version 6 is a beta rewrite on Compose Multiplatform
GitHub still labels Spotube's primary language as Dart, but the build instructions on the master branch describe a Compose Multiplatform app driven by Gradle, with a composeApp module, an iosApp directory, a buildSrc of Kotlin build logic, and a Rust library built through Gobley. The latest release, v6.0.0-beta.0, was published on October 30, 2026. The newest non-beta release is v5.1.2 from June 5, 2026.
This matters for which build you install. Building master gets you the version 6 beta, not the 5.x app most existing guides describe. The last push to the repository landed on November 2, 2026, so work is ongoing, but a beta label means you should expect changes between builds. The GitHub release named nightly also carries a creation date of February 5, 2023 while its title reads Nightly 2026-10-26-526, so judge nightly freshness by its title, not the date GitHub shows.
Downloads and nightly builds come from spotube.cc
For regular use, the project sends people to its official website at spotube.cc to download the app. Nightly builds are published separately at spotube.cc/downloads/nightly. Nightly builds are a distinct channel: when built from source, the -Pnightly=true Gradle property produces them with separate icons and a separate name, so a nightly can sit next to a stable install rather than replacing it. The Android debug build has matching tasks for both channels.
The project is funded through Patreon, Buy Me a Coffee and Open Collective, and support questions go to its Discord server. Mobile and desktop are both targets, but installation steps for iOS are not part of the build instructions on the repository front page, so check spotube.cc for what is offered on your platform before planning around it.
Building needs JDK 21, Rust, and a webview you publish yourself
A source build has four prerequisites. JDK 21 runs Gradle, and the Gradle daemon JDK and GraalVM are provisioned automatically. Rust, through rustup and cargo, builds the composeApp library via Gobley. The Android SDK is needed only for Android builds. The fourth is the awkward one: ComposeNativeWebview is not on Maven Central yet, so you must clone it at the commit pinned as COMPOSE_WEBVIEW_COMMIT in .github/workflows/spotube-release-binary.yml and run ./gradlew publishToMavenLocal inside that clone before Spotube will build. Skipping that step leaves the dependency unresolved.
Once that is in place, the fastest edit and run loop is the desktop JVM target:
./gradlew :composeApp:runAn Android debug APK uses:
./gradlew :composeApp:assembleStableDebugDevelopment builds skip the release-only optimizations, which keeps them quick compared with the native build below.
On Linux the app will not start without VLC and WebKitGTK
Linux needs runtime libraries even for ./gradlew :composeApp:run, including VLC for audio and WebKitGTK 4.1 for the webview. On Debian and Ubuntu:
sudo apt-get install libvlc5 vlc-plugin-base libwebkit2gtk-4.1-0 libgtk-3-0 libasound2 libgl1 libxtst6 libxi6 libxrender1On Arch, CachyOS and Manjaro:
sudo pacman -S vlc webkit2gtk-4.1 gtk3 alsa-lib libglvnd libxtst libxi libxrenderFedora uses dnf with vlc-libs, webkit2gtk4.1, gtk3 and related packages, and vlc-libs requires the RPM Fusion repository to be enabled first. openSUSE uses zypper with libvlc5 and libwebkit2gtk-4_1-0. On Ubuntu 24.04 and newer and Debian 13, libgtk-3-0 and libasound2 are renamed libgtk-3-0t64 and libasound2t64, and apt resolves that on its own. The AppImage build avoids most of this by bundling Ubuntu 24.04 packages, including an audio-only VLC built through vlcj-bundler, GTK 3, WebKitGTK 4.1 and glib-networking.
A native desktop build takes ten minutes and about 15 GB of RAM
Release builds compile to a GraalVM native image, and that is expensive: about 10 minutes, every CPU core, and a peak around 15 GB of RAM. A laptop with less memory will struggle, so plan to use the JVM run target for development. The cost only applies to the packaging tasks, never to run. Nucleus downloads GraalVM CE on the first build, or you can point GRAALVM_HOME at your own. Linux also needs gcc, zlib headers and patchelf, plus rpm for .rpm and fuse with zstd for AppImage; macOS needs the Xcode Command Line Tools; Windows needs Visual Studio Build Tools with Desktop development with C++.
./gradlew :composeApp:createGraalvmNativeDistributableOutput lands in composeApp/build/compose/binaries/main/graalvm-app/, and the spotube binary must stay next to the libraries it was built with because it loads them from its own folder. Installers build only for the host OS, for example:
./gradlew :composeApp:packageGraalvmDmgEditorial conclusion
Spotube fits listeners who want an open-source, telemetry-free player and are comfortable choosing plugins as their music source. It is not a self-contained service: without a plugin for the platform you want, there is nothing to play. Before switching, decide between the stable v5.1.2 line and the v6.0.0-beta.0 rewrite, and if you plan to build from source, confirm you have JDK 21, Rust and around 15 GB of free RAM for a native desktop build.
Frequently asked questions
What is Spotube for?
Spotube is an open-source music streaming app for desktop and mobile. It plays music from metadata, playlist and audio-source plugins, made by the community or by you, and offers time synced lyrics and downloadable tracks with tagged metadata.
Does Spotube work anymore?
The repository is not archived, its last push was on November 2, 2026, and v6.0.0-beta.0 was released on October 30, 2026. What you can play still depends on the plugins available for your music service.
Is Spotube safe to use?
Spotube is AGPL-3.0 open-source software and states it collects no telemetry, diagnostics or user data, with playback controlled locally. Plugins connect to outside services, so review each plugin you install separately.
How much does Spotube cost?
Spotube is open-source, libre software under the AGPL-3.0 license, downloaded from spotube.cc. The project is supported by donations through Patreon, Buy Me a Coffee and Open Collective.
How to use Spotube nightly?
Download nightly builds from spotube.cc/downloads/nightly. When building from source, adding -Pnightly=true produces the nightly channel with its own icons and name.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/krtirtho-spotube)Star history chart for your README
[](https://hysenlabs.com/projects/krtirtho-spotube)Was this useful?