Strawberry gates its macOS and Windows builds behind sponsorship
:strawberry: Strawberry Music Player
At a glance
- What is it?
- strawberrymusicplayer/strawberry is a Qt music player forked from Clementine in 2018, aimed at collectors rather than at a streaming subscription. The structural detail worth knowing before anything else: it is free software under the GPL, and the macOS and Windows releases are available to sponsors only.
- Who is it for?
- Strawberry suits a listener with a local collection who wants lossless formats, tag editing, gapless playlists and album art fetched from several sources at once, and who is on Linux where the packaged builds are open. It also suits anyone willing to sponsor, since that is the documented route to the macOS and Windows binaries.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly C++, 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
- strawberrymusicplayer/strawberry4,082 ★ · +102
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| strawberrymusicplayer/strawberry | 4k | 4.1k |
102 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The macOS and Windows binaries are available to sponsors only
The note under the tested-platforms line is short and unambiguous: macOS and Windows releases are currently available to sponsors only, and a monthly sponsorship through the platform's funding page grants direct access to new releases. Everything else in the repository says the opposite, that this is free software released under the GPL and that money is a donation rather than a licence. Both statements are true at once, and the difference is the distribution channel: the source is free and self-hostable, while the prebuilt binaries on two of the five platforms are gated. Linux is the platform where the packaged builds are simply available, with a stable and an unstable channel in two different package systems, plus a builds site and a distribution package tracker in the readme. OpenBSD, FreeBSD, macOS and Windows are also listed as tested; check the relevant platform's package sources for independently distributed builds.
Sixteen formats, and bit-perfect is claimed for Linux only
The format list is long enough that reading it aloud is the fastest way to understand the audience: WAV, FLAC, Ogg FLAC, WavPack, Ogg Vorbis, Opus, Ogg Speex, Musepack, TrueAudio, AIFF, MP4 with AAC, ALAC, MP3, ASF, Monkey's Audio, and DSD in both its stream and interchange flavours. Bit-perfect playback is claimed specifically on Linux, which tells you the bit-perfect path is tied to the audio stack rather than to the application. Two normalisation systems are supported side by side, one from scanned track metadata and one from a broadcast loudness standard, and the analyser set includes a spectrum analyzer, an equalizer, a moodbar and a waveform seek bar. Conversion output is a narrower list than the input list: MP3, AAC, FLAC, Ogg Vorbis, Opus, Speex, WavPack and ASF.
Tag fetching and cover art come from separate services, and some integrations are unofficial
Metadata work is the part of a collector's player that shows where a project draws its lines. Missing tags can be filled in by acoustic fingerprinting, which means hashing the audio and matching it against an open fingerprint database and a music encyclopedia rather than guessing from filenames. Cover art is fetched from eight separate sources, and lyrics from eight more, with the two lists overlapping in only one place. Scrobbling goes to three services, one of which is your own Subsonic-compatible server. Streaming from a Subsonic server is listed as a first-class feature, while integrations with three commercial streaming services are listed as unofficial, and that word is doing real work in a feature list. Remote control over the desktop session is Linux-specific, through a standard media-control interface, while global keyboard shortcuts are listed for all three desktop platforms.
The issue tracker refuses feature requests and sends them to a forum
The contributing guidance is unusual enough to read before filing anything. There are five ordered steps: read the frequently asked questions page, search existing issues and comment rather than duplicating, use the forum for technical problems and feature suggestions because it suits back-and-forth better, understand that feature requests are not accepted on the issue tracker and will be closed, and note that Flatpak problems go to the Flatpak support site because the project does not maintain that package. So the issue tracker is reserved for defects that have survived a documentation check and a duplicate search, and the forum carries the conversation that usually precedes a design change. Sponsorship is handled in a parallel section listing four payment routes and asking for support on the grounds that it keeps maintenance going.
Building needs fourteen libraries, and eight of them are optional per feature
The source build requirements are explicit about versions, which is unusual and useful. CMake 3.25 or higher, a C or C++ compiler from one of three named vendors, a package query tool, and then the libraries: a foundational utility library, an encryption library, Qt at 6.4 or higher with seven named modules, SQLite at 3.9 or higher, ALSA on Linux only, GStreamer, TagLib at 1.12 or higher, the Unicode library, a charset detector, and a single-instance application library at 1.1.0 or higher. Optional features each name their own dependency: fingerprinting, the fast spectrum moodbar, PulseAudio integration, audio CD support, MTP devices, iPod Classic support, loudness normalization, and secure password storage on Linux and BSD. GStreamer plugins base and good are needed, with three more sets optional for full codec coverage.
Four CMake commands and a recursive clone, with Windows on a different path
The build itself is four steps, and the clone is recursive rather than shallow, which matters because the tree has submodules. The commands are given as an indented block rather than a fenced one, so they read as a transcript:
cd strawberry
cmake -S . -B build
cmake --build build --parallel $(nproc)
sudo cmake --install buildNote that the parallelism is set from the processor count, which is a small portability assumption if you are cross-compiling. Windows is not covered by these commands at all. For Visual Studio 2022 and 2026 the readme points at a separate repository of build tools, which tells you that the Windows build is a distinct supported path rather than the same four commands on another platform. Translations are managed on a crowdsourcing platform, and the repository root carries a translation configuration file and a changelog, so the localisation pipeline is part of the source tree rather than something handled elsewhere.
The fork from Clementine explains both the feature set and the age of the code
The project states it was originally forked from Clementine in 2018, which is the single most useful fact for reading the rest of the feature list. A fork inherits a mature collection manager and then diverges, so the presence of audio CD playback, MTP and iPod device support, and a moodbar is not surprising: those are features of the thing it forked from. It also explains the licensing, since a GPL codebase forked in 2018 under the GPL is what you would expect, and it explains the plugin-oriented dependency list, which is characteristic of that lineage. What the fork added is best read by subtracting: the streaming-service integrations, the moodbar's fast spectrum mode, the Subsonic scrobbling target, and the modernised Qt requirement are all newer than 2018. The releases move in the 1.2 series with three published in the last month, so the divergence is still active.
Editorial conclusion
Strawberry suits a listener with a local collection who wants lossless formats, tag editing, gapless playlists and album art fetched from several sources at once, and who is on Linux where the packaged builds are open. It also suits anyone willing to sponsor, since that is the documented route to the macOS and Windows binaries. It does not suit someone who wants a player built around a streaming subscription, because the integrations with those services are described as unofficial. It does not suit a Flatpak user looking for maintainer support, because the project states it does not maintain that package. Before building it, note that the dependency list is long and that several optional features each add a separate library, and decide which platforms matter to you before you read the build instructions, since the Windows path points at a separate tools repository rather than at the documented commands.
Frequently asked questions
What audio formats does Strawberry support?
Sixteen are listed, including WAV, FLAC, Ogg FLAC, WavPack, Ogg Vorbis, Opus, Ogg Speex, Musepack, TrueAudio, AIFF, MP4 with AAC, ALAC, MP3, ASF, Monkey's Audio, and DSD in both stream and interchange flavours. Conversion output is a shorter list: MP3, AAC, FLAC, Ogg Vorbis, Opus, Speex, WavPack and ASF.
How do I get Strawberry for macOS or Windows?
The macOS and Windows releases are available to sponsors only, and a monthly sponsorship grants direct access to new releases. Linux packages are published openly through two package systems, each with a stable and an unstable channel, and a separate builds site is linked from the readme.
How do I build Strawberry from source?
Clone the repository recursively, then configure with cmake -S . -B build, build with cmake --build build --parallel $(nproc) and install with sudo cmake --install build. You need CMake 3.13 or higher, Qt 6.4 or higher with seven modules, SQLite 3.9 or higher, TagLib 1.12 or higher and several others. On Windows with Visual Studio the readme points at a separate build-tools repository instead.
Does Strawberry support bit-perfect playback?
Bit-perfect playback is claimed on Linux. The project also offers volume normalisation through two systems, one based on scanned track metadata and one on broadcast loudness analysis, plus an analyser, an equalizer, a moodbar and a waveform seek bar.
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/strawberrymusicplayer-strawberry)Star history chart for your README
[](https://hysenlabs.com/projects/strawberrymusicplayer-strawberry)Was this useful?