Limusic: seven builds, three that self-update, and no macOS Intel binary at all
Feature rich, native desktop, YouTube Music client. Tauri + Rust + SvelteKit, ad-free playback through libmpv, Last.fm scrobbling and Discord Rich Presence, no Electron.
At a glance
- What is it?
- Limusic is a native desktop client for YouTube Music written in Rust with a Tauri shell, playing audio through libmpv with no browser runtime and no server of its own. Its packaging is the part worth reading before you install: seven rows for three platforms, three self-updating builds, an unsigned macOS disk image, and no binary at all for Intel Macs.
- Who is it for?
- Limusic suits someone who wants gapless playback with loudness normalisation, local files alongside streamed ones, and no Electron process eating memory, and who is comfortable with a client that talks to a service's internal interface. Before you install, pick the artefact deliberately, because only three of the seven update themselves and the package-manager builds do not.
- 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 last received commits 1 day ago.
- What is it written in?
- Mainly Rust, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.
Star history
- SimoHypers/limusic2,173 ★ · +1,719
| Repository | 2026-09-17 | 2026-11-21 |
|---|---|---|
| SimoHypers/limusic | 454 | 2.2k |
1,719 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Seven download rows, and only three of them update themselves
The install table is the most information-dense part of the documentation, and it is organised by what each artefact will not do for you. Two Windows rows: an installer that self-updates and a plain package that does not. Three Linux rows: an AppImage that self-updates and bundles the media library, a Debian package that does not and relies on the package manager to pull that library and the web toolkit in for you, and an RPM that does not update at all, requires you to install the media library yourself first, and is redownloaded by hand at each release. One macOS row, self-updating. That is three self-updating artefacts out of seven, so the auto-update promise covers roughly half the matrix. The Linux AppImage also carries the highest system requirement of any row, naming a specific modern distribution floor for the C library it needs.
Intel Macs have no build, and the Apple Silicon one is unsigned
The macOS row covers Apple silicon only, and the table's note for the other architecture is three words long: build from source. There is no binary for Intel machines at all, so anyone on one is compiling a desktop application and its media backend themselves, following a document the project links for exactly that case. The disk image that does exist is unsigned, which has a concrete consequence on first launch: the quarantine attribute set by the browser makes the system report the application as damaged. The documented fix is a single attribute removal on that one application, and it is worth stating precisely rather than generally, because the difference between clearing the attribute on one file and disabling the check system-wide is the difference between a workaround and a weakened machine:
xattr -dr com.apple.quarantine /Applications/limusic.appThree community repositories, three maintainers, and a priority trick
The project publishes no packages for the Linux distributions that expect their own packaging, so three community repositories fill the gap and each is credited to a named person rather than to the project. One for Arch-family systems, installed through the usual helper and updated with the package manager. One for Fedora, enabled as an extra repository and then installed normally. One for a rolling SUSE variant, and this one has a wrinkle the documentation explains: that repository carries its maintainer's other packages too, so the repository is added at a priority below the distribution's own, which keeps the distribution's packages winning even though the repository is technically newer. That is a small piece of distribution engineering worth copying if you ever publish to a rolling release, and it is the kind of note that only appears in a project whose users actually maintain the packaging.
Six lyric sources in a fixed order, keyed on exact track length
Lyrics are the feature with the most engineering behind it, and the design decisions are specific. The panel opens from a button in the player bar next to the queue button, and it takes the same side of the window as the queue, so opening one closes the other. Sources are tried in a fixed order: one service first, then a community lyric database, then the music service's own timed lyrics, then three regional music services, and finally plain untimed text if nobody has a synced version. Matching is keyed on the track's exact length rather than on the title, because popular songs exist as several cuts and the wrong one drifts a few seconds out of sync within a verse. Results are cached locally so a replayed track is instant. The first source is also the only one with per-word timings, which is what enables word-by-word highlighting, and the trade-off is stated plainly: it goes first for that reason and is therefore asked about every track you play, and there is a setting to turn it off while the others still work.
Scrobbling needs a credentials file you have to create
Last.fm integration works from a browser approval flow with no key to copy, and clicking the mark again shows the connected account or disconnects it. The scrobble rule follows Last.fm's own: a track registers at the halfway point or at four minutes, whichever arrives first. Discord Rich Presence is a toggle in the same title bar, with a visible indicator that it is live, a card showing the track, artist, artwork and a progress bar, and a card that disappears when you pause. What differs between the two is the build story. Building from source needs your own API credentials, which are not in the repository, and they go in a file inside the desktop crate with two variables, a key and a secret. The documented behaviour when that file is missing is the good kind: everything else still builds and runs, and the scrobbling button reports that it is not configured rather than failing at startup.
A five-crate workspace whose release profile is tuned for download size
The Rust side is a workspace with four members and a desktop application crate. The four are the internal API client, the playback layer, a protocol crate for the shared listening rooms, and a synchronisation server, the last of which exists because the collaborative listening feature is described as running over a small relay you host yourself rather than a service someone else runs. That separation is the architectural statement: the client never needs a backend, and the only optional server is one you choose to run for other people to join you. The release profile is annotated with its reasoning, which is unusual and useful. It uses thin link-time optimisation and a single codegen unit for cross-crate optimisation, and it strips symbols, with the comment that this binary ships through a self-updating AppImage so its size is every user's download. It also deliberately keeps unwinding panics, because an abort inside the media event thread would kill playback for the whole application instead of degrading.
Editorial conclusion
Limusic suits someone who wants gapless playback with loudness normalisation, local files alongside streamed ones, and no Electron process eating memory, and who is comfortable with a client that talks to a service's internal interface. Before you install, pick the artefact deliberately, because only three of the seven update themselves and the package-manager builds do not. On macOS know that the disk image is unsigned, and on Intel there is nothing to download at all. If you build from source, plan for one missing secret, since the scrobbling credentials are not in the repository and everything else works without them.
Frequently asked questions
Which Limusic builds update themselves?
Three of the seven: the Windows setup executable, the Linux AppImage and the macOS disk image. The MSI, the Debian package and the RPM do not, and the RPM additionally requires you to install the media library and redownload the file at each release.
Can I install Limusic on an Intel Mac?
There is no build for that architecture; the download table lists it as build from source with a link to the platform build document. The Apple silicon disk image is unsigned, so the first launch needs the quarantine attribute removed on that application.
How does Limusic find lyrics?
Six sources in a fixed order, starting with the only one that has per-word timings, then a community database, the music service's own timed lyrics, three regional services, and finally untimed text. Matching is keyed on the track's exact length and results are cached locally.
Do I need Last.fm API credentials to build Limusic?
Only for scrobbling. The key and secret go in a file inside the desktop crate; without it everything else builds and runs, and the scrobbling button reports that it is not configured.
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/simohypers-limusic)Star history chart for your README
[](https://hysenlabs.com/projects/simohypers-limusic)Was this useful?