Museeks: a Tauri v2 and React music player that the 'electron' topic tag no longer describes

Museeks runs on Tauri v2 and Rust, but the repository still carries an 'electron' topic tag

Museeks is a cross-platform music player for Linux, macOS and Windows. Its stated goal is simplicity: the README says outright that the aim is not to compete with more complete and more famous music players, and the feature set reflects that choice.

The backend is Tauri v2 with Rust. The UI layer is React. This is worth stating because the repository topics include 'electron', a label that predates the current architecture. Anyone searching for Electron-based music players will find Museeks in those results, but the current codebase does not use Electron at all. The Tauri framework handles native window management, file system access and OS integrations through the @tauri-apps family of packages in package.json, while Rust handles application logic in src-tauri/.

For a user who specifically wants an Electron-based cross-platform player, Museeks is no longer a match. The migration away from Electron is not explained in the README, only visible in the tech stack description and the outdated topic tag.

Community-maintained package manager builds may not match the 0.23.4 binary at museeks.io

Museeks ships platform-specific installers and binaries for Linux, macOS and Windows. These are linked from the project page at museeks.io, where the 0.23.4 build is the current version.

Package managers are a second path. Homebrew for macOS and AUR for Arch Linux are mentioned as examples. However, the README explicitly notes that Museeks packages in community-maintained managers may not be the latest version. Verifying that a package manager's build matches 0.23.4 before installation is the check the README implicitly calls for.

For developers wanting to build from source, Tauri does not support cross-platform compilation: the build command produces binaries for the current platform only. Separate macOS, Linux and Windows builds each require a native machine.

Seven audio formats and .m3u import/export define what the library can read

Museeks handles seven audio formats: mp3, mp4, m4a/aac, flac, wav, ogg and 3gpp. Files in other formats do not appear in the library. No transcoding layer or converter is documented.

Playlist handling goes through .m3u files, which Museeks can both import and export. This covers the most common playlist interchange format and keeps a library portable across players that support the same standard.

The library auto-refresh feature updates the library when files are added to a watched folder, without requiring a manual rescan. How watched folders are configured, and whether changes in subdirectory depth affect detection, is not documented in the README.

Sleep mode blocking and playback speed control sit beyond the minimal player baseline

Two features push Museeks past the minimum playback tier. A sleep mode blocker keeps the machine awake during playback, useful for longer sessions or background music during work. Playback speed control lets you adjust a track's tempo, absent from most stripped-down players.

Beyond those two, the feature set is close to the essentials: playlists, queue management, shuffle, loop, cover art display and a dark theme. These are presented as deliberate choices.

Queue management and shuffle are the features where implementations diverge most. Museeks does not document the shuffle algorithm or whether the queue persists across restarts, so checking those behaviors against your actual use case is the verification step before committing to it.

Freezes and crashes are resolved by deleting the platform-specific config directory

The troubleshooting path for Museeks freezes or crashes is a full reset: delete everything in the storage directory and restart. Settings -> Open Storage Directory is the in-app route. The platform paths are:

- Windows: `%AppData%\museeks` - macOS: `~/Library/Application Support/museeks` - Linux: `~/.config/museeks/` or `$XDG_CONFIG_HOME/museeks`

This deletes all Museeks configuration and library data. The README does not list what is stored in the directory, so selective deletion is not possible without inspecting the directory contents first.

The README notes that since version 0.20, backwards compatibility is a goal but edge cases may be missed. A crash that follows an upgrade from before 0.20 points toward a storage format mismatch, and a reset is the documented fix.

Building from source requires Tauri prerequisites, Rust and the vp frontend tool

Development setup uses vp, which the README identifies as Vite+ from viteplus.dev/guide/. This tool manages Node.js, dependencies and build tools as a single step rather than requiring a separate Node.js installation beforehand.

The steps for a local development environment are:

git clone [email protected]:<username>/museeks.git
cd museeks
vp env use
vp install
vp run tauri dev

This starts Museeks in development mode. Hot reload applies to .js files automatically; editing a .rs file triggers a Rust rebuild.

To package binaries:

vp run tauri build

Tauri does not support cross-platform compilation, so this command produces binaries for the current platform only. The Tauri prerequisites page at v2.tauri.app/start/prerequisites/ covers the Rust toolchain and system dependencies needed before any of these commands succeed.

Translations use .po files with lingui, and right-to-left support is explicitly not ready

Museeks has an internationalization layer based on lingui, with translations stored as .po files. Adding a language means editing src/translations/languages.ts to register it, running vp run gen:translations to generate the template file, filling in the translations and opening a pull request.

The README qualifies this with a direct statement: translations are in an early stage. Right-to-left languages, locale-specific variants and other special cases are flagged as possibly unsupported, and contributors with those requirements are directed to open an issue before starting.

The last push was on 2026-07-03 and the project is distributed under the MIT licence; the full text is at LICENSE in the repository root.

Editorial conclusion

Museeks suits users who want a cross-platform player that handles common audio formats without configuration overhead. The sleep mode blocker and playback speed control add real utility beyond basic playback. Those who need library features beyond playlists and queue management, or formats outside the seven Museeks handles, will find the limits the README acknowledges directly. For installation, museeks.io is the reliable path; community-maintained package manager builds may not carry the 0.23.4 build.

Frequently asked questions

Official sources

1. License: MIT
2. martpie/museeks on GitHub
3. Project website
4. README
5. Releases