# Music Presence: Discord Rich Presence for Any Media Player

> Music Presence is a tray application that detects playback from over a hundred media players and publishes it to Discord. This review covers what it does, how to install it on Windows, macOS and Linux, and where it stops being the right tool.

**ungive/discord-music-presence** — The Discord music status that works with any media player

- Repository: https://github.com/ungive/discord-music-presence
- Website: https://musicpresence.app
- Stars: 3,504 · Forks: 138
- Language: C++
- License: NOASSERTION
- Published: 2026-09-23 · Updated: 2026-09-23 · Language: en
- Canonical page: https://hysenlabs.com/projects/ungive-discord-music-presence

## What Music Presence fixes for Discord users

Discord's own music status only covers a small set of services. If you play local files through foobar2000, or stream through TIDAL, Deezer or Apple Music, the official integration often shows nothing at all. Music Presence fills that gap: it runs as a tray application, watches the media players on your machine, and writes the currently playing track into your Discord status. The README describes the goal plainly: it "works with any media player, be that e.g. Apple Music, Spotify or even foobar2000."

The audience is desktop listeners who care what their profile card looks like. The README lists fine-grained control over which applications are shared, per-player setting overrides, and a tray icon that changes to show whether sharing is active. It also notes a specific behaviour the official Spotify integration lacks: podcasts can appear in your status as "Listening to a Podcast." If you only ever listen through Spotify on desktop, the official integration is simpler and you probably do not need this.

## How detection, artwork and the Rich Presence payload fit together

The repository is a C++ project with a tray front end. The mechanism, as the README describes it, is local: media players on your machine are detected, and the detected session appears in the tray menu. Nothing in the README suggests a cloud service in the middle, and the album cover claim is explicit about that: the artwork is correct "100% of the time" and is "achieved without the use of external image sources." That is the interesting design decision. Instead of querying a metadata API to find a cover, the application takes the image from the player itself, which is why the README says there are no missing covers. It also means the quality of the cover is bounded by what the player exposes.

Playback position is forwarded when the player supports it, and the README says the status can show the artist name, song title, player name or media type after the "Listening to" text, so "Listening to Spotify" and "Listening to Billie Eilish" are both valid configurations. Animated artwork exists for Apple Music and TIDAL, is converted on the fly, may take a few seconds to load, and is disabled by default. Paused media can be shown indefinitely, which the README frames as pinning a track to your profile.

## Installing Music Presence on Windows, macOS and Linux

The README's download section links installers per platform for release v2.3.6: a Windows x64 installer and zip, macOS arm64 and x86_64 disk images, and Linux x86_64 builds as AppImage, deb, rpm and tar.gz. There is no source build instruction in the README, so use the release artefacts unless you intend to work from the repository directly.

On macOS, Homebrew is the shortest path. The README gives this command:

```bash
brew install music-presence
```

On Arch, the README points at an AUR package and flags it as unofficial:

```bash
yay -S music-presence-bin
```

The AUR entry is maintained outside the project, so verify it before installing. On Linux distributions without a package manager entry, the AppImage is the portable option:

```bash
chmod +x musicpresence-2.3.6-linux-x86_64.AppImage
./musicpresence-2.3.6-linux-x86_64.AppImage
```

After launch, the README says playback is detected automatically and the player shows up in the tray menu. Start a track in your player, open the tray menu, and confirm the session is listed; then check your Discord profile to see the status. If nothing appears, the README points to a troubleshooting document with a section for players that are not detected.

## Where the any-player claim gets thin

The README says over 100 players are supported and that adding a missing one is "trivial." That second word deserves scrutiny. The linked troubleshooting section is titled "If your media player is still not detected," which tells you detection can fail in the first place. For a player with no existing integration, the fix is a contribution to a C++ codebase, not a settings toggle. A user of an obscure player should read that section before assuming support.

The animated artwork feature is narrower still: Apple Music and TIDAL only, off by default, with an on-the-fly conversion step the README admits may take a few seconds. And the mobile question is settled by absence. The download list contains desktop platforms only, and neither the README nor the repository layout mentions iOS or Android. Anyone who listens primarily on a phone is outside the project's scope. The README also does not document rollback or downgrade steps, so treat a version upgrade as one-way unless you keep the previous installer.

## Music Presence versus the official Spotify integration

The obvious alternative is Discord's built-in Spotify integration, and the difference is architectural. The official integration is service-specific: it works because Discord and Spotify have an arrangement, and it covers that one service. Music Presence sits on your machine and reads what your operating system reports about media sessions, which is why it can cover foobar2000, MusicBee and Apple Music with the same code path.

The trade-off runs the other way too. The official integration requires no local process and no additional software, and it is maintained by the two companies involved. Music Presence is a separate tray application that must be running for your status to update, and its Spotify support overlaps with something you already have. The README actually suggests combining them: use Music Presence for Spotify podcasts, which the official integration does not show, and leave music to the official integration. That is a reasonable split, and it is more honest than pretending the two cannot coexist.

## Licence, privacy and the cost of keeping it current

The repository carries a NOASSERTION licence label, which means GitHub could not map the LICENSE.md file to a known identifier. Read LICENSE.md yourself before shipping this in any commercial or redistributed context; a label that cannot be classified is not the same as a permissive licence. The README links a separate PRIVACY.md, which is the document to check if you care what the application does with playback data. The README does not summarise its contents.

Maintenance looks steady rather than dormant: the last push was on 2026-07-11, and the most recent release, v2.3.6, is dated 2026-07-09. The release history is not uniform, though. v2.3.5 landed on 2025-12-26, and before it a hotfix, v2.3.5-hotfix.1, on 2025-09-17. That pattern of a hotfix followed by months of quiet suggests fixes arrive when something breaks rather than on a schedule. Upgrading means re-downloading a platform artefact or re-running the Homebrew or AUR command; there is no documented auto-update path in the README.

## Conclusion

Adopt Music Presence if you listen through a desktop player that Discord does not see, or if you want per-player control over what appears in your status. Do not adopt it if you listen on a phone: the project ships Windows, macOS and Linux builds only, and the README does not promise a mobile version. Before installing, check the licence file and the privacy document, since the repository carries a NOASSERTION licence label and the README points to a separate PRIVACY.md for data handling.

## FAQ

### How do I use Music Presence on Discord?

Install the build for your platform from the releases page, launch it, and start playing music in a supported player. The README states that playback is detected automatically and appears in the tray menu, after which your Discord status updates.

### Is music presence safe?

The README states that album artwork is produced without external image sources, and it links a separate PRIVACY.md for data handling. The repository does not summarise that document, so read it and the NOASSERTION-licensed LICENSE.md before installing.

### Can people on Discord track you?

The README does not describe location tracking. What the application does is publish the media session it detects to your Discord status, and the README notes you can control which applications are shared and override settings per player.

### Are Discord music bots legal?

Music Presence is not a Discord bot. It is a desktop tray application that runs on your own machine and writes to your own status, so the README describes no server-side bot component at all.

## Sources

- [Issues](https://github.com/ungive/discord-music-presence/issues)
- [Project website](https://musicpresence.app)
- [README](https://github.com/ungive/discord-music-presence/blob/master/README.md)
- [Releases](https://github.com/ungive/discord-music-presence/releases)
- [ungive/discord-music-presence on GitHub](https://github.com/ungive/discord-music-presence)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/ungive-discord-music-presence