Questions people ask.

A music player for the music you host yourself. It connects to your own Jellyfin, Emby or Navidrome server and plays your library on your phone, computer and car.

macOS, iPhone and iPad, Android, Windows and Linux. iOS needs 17.4 or later and macOS needs 12 or later. Linux builds come for x86_64 and ARM64, including the Raspberry Pi 4 and 5 with a 64-bit OS based on Debian 13 or Ubuntu 24.04. Linux needs glibc 2.38 or newer, so Ubuntu 24.04, Debian 13, Fedora 39 or later.

Get it from the App Store, Google Play or the download section on the front page. The Mac also has a DMG, and Android has an APK and an Obtainium link for installing outside Google Play.

There are two common reasons.

The library is not a Music library. Depending on when you created it, its content type may be empty or set to "General", and JellyBox only works with Music libraries. The easiest fix is to open the Jellyfin admin dashboard and change the library type to Music.

The library was migrated from Jellyfin 10.x to 12 and the migration did not fully finish. This is a known Jellyfin issue. Try rescanning the library first, and if that does not help, remove the library and create it again.

Lyrics come from two places: your server's library, and LRCLIB if you turned it on in Settings. If neither has lyrics for the song, there is nothing to show.

More lyrics providers are planned.

Maybe. Check Settings: many features can be set up the way you like.

Jellyfin, Emby and Navidrome. You pick the server type when you sign in. Navidrome connects through the OpenSubsonic API.

Other OpenSubsonic servers may work too, but Navidrome is the only one we test against.

Not at the moment.

Yes. You can stay signed in to several servers or accounts at once and switch between them without signing out.

Yes. FLAC and ALAC play at full quality. If a device cannot play a format, such as ALAC on Android, the server converts it to FLAC, so it stays lossless.

The player bar shows the codec, bitrate and sample rate of what is playing.

Yes. Download albums and playlists to the device and they play with no network at all. Downloaded playlists update themselves when they change on the server.

For patchy signal there is forward caching: the app downloads the next tracks in your queue ahead of time, so playback carries on through a gap in coverage.

Yes. You can set a separate streaming quality for Wi-Fi and for mobile data in Settings. Lower quality is converted on your server before it is sent.

Yes, to ListenBrainz. Connect your account in Settings. Last.fm is not supported yet.

Yes. JellyBox can send audio to AirPlay devices, to a Chromecast from your phone, and to DLNA/UPnP speakers and TVs on your network. You keep control of playback in the app.

Some DLNA devices handle this better than others. This article explains why.

Yes, both. You can browse your library, play mixes and play downloads from the car screen. See the CarPlay and Android Auto pages for details.

Android Auto hides apps that were not installed from Google Play. You can turn on "Unknown sources" in Android Auto's developer settings. The Android Auto page has the steps.

If you already reach your server through Tailscale, a VPN or a reverse proxy, add that address under Settings → Server. JellyBox uses your home address when it can and switches to the other one when it cannot.

If you run Jellyfin and have nothing set up, the remote access plugin connects your server with no port forwarding. It is Jellyfin only for now.

Yes, with Continuity. Sign in to Jellybox Link on each device and you can move what is playing to another device mid-song, or control one device from another.

Your music, library and server login never reach us. The app sends one anonymous "app opened" event with your operating system name, and crash reports when something breaks. Both can be turned off in Settings. The privacy page has the full details.

Continuity shares the song IDs in your current queue, the ID of the song that is playing, and whether it is playing or paused. Song IDs are random IDs unique to your server, with no way to match them to song names or artists. It also shares a device ID that the app generates the first time it runs, the device type (mobile or desktop) and the operating system (Windows, Linux, Android and so on).

Remote access shares only a server ID, so that when you have more than one server in the app, the relay knows which one to send your requests to. Nothing else.

Remote access traffic is end-to-end encrypted. The app and your server set up encryption while both are on your home network, so the keys never leave your devices. After that, every request and all audio is encrypted, and the relay cannot read any of it.

See the comparison table. It covers the features we lack as well as the ones we have.

Open an issue on GitHub or ask on Discord.