navidrome.org No paid content found

What is Navidrome?

Navidrome is a self-hosted music server: you install it on a computer or server you control, point it at your existing music files, and it streams that collection to a web browser and to mobile apps. It is open source software distributed free of charge under the GNU GPL v3 license, so there is no subscription tied to the server itself.

Its main appeal is turning a local library into something you can reach from anywhere without handing your files to a streaming company. The project emphasizes being lightweight and self-contained, says it runs well on resource-limited hardware such as a Raspberry Pi, and reports having been tested with collections of roughly 900,000 songs. It also supports multiple libraries with user-specific access controls, which is useful if you want to keep, say, family music separate from personal audiobooks.

Two features matter for day-to-day use. On-the-fly transcoding converts or reduces files as they play, which helps if you are streaming over mobile data and want to avoid burning through a plan. And compatibility with the OpenSubsonic API means you are not locked into one official app: you can choose from a range of third-party clients on iOS and Android, or just use the built-in web player.

A practical next step: if you already have a music folder and a machine that stays on, try the web player first to confirm your library scans and tags look right, then pick a mobile client from the Subsonic-compatible ecosystem. If you have no always-on device or no interest in maintaining a server, a hosted service will likely be less effort.

Related options worth knowing: Jellyfin and Plex also stream personal media, but they are broader media servers rather than music-first tools; MusicBee and foobar2000 are desktop players for local listening rather than remote streaming.

How do I install and set up Navidrome on a Raspberry Pi?

Navidrome is a self-hosted music server, so "install and set up" means two things: getting the server running on the Pi, then pointing your phone or browser at it. The project explicitly targets resource-limited platforms like the Raspberry Pi, and it is open source under GPL v3, so there is no licence to buy.

Pick an installation route

For a first setup, Docker is usually the least painful. The official documentation at Navidrome lists the current image, ports and configuration options, and those details change between releases, so follow the version-specific instructions there rather than a blog post from an older release.

The setup sequence

1. Prepare storage. Put your music on a drive the Pi can read reliably. An external USB SSD or a network share is common; a large library on the SD card itself is fragile.
2. Create a config location. Navidrome keeps a database and settings in a data directory. On a Pi this should be on persistent storage, not a temporary path, so your playlists and scan history survive restarts.
3. Set the music folder. Point Navidrome at the folder containing your files. It scans and indexes them; it does not move or rewrite your files.
4. Start the service and open the web UI. On first run you create the admin account in the browser. The integrated web player is enough to confirm everything works.
5. Connect a mobile client. Navidrome speaks the OpenSubsonic API, so you can choose from a wide range of third-party iOS and Android apps instead of being locked to one vendor's player.
6. Decide on remote access. Either keep it LAN-only, or expose it through a reverse proxy or VPN. If you expose it to the internet, put HTTPS in front of it and use strong credentials.

Raspberry Pi-specific things worth thinking about

• CPU and transcoding. On-the-fly transcoding reduces bitrate so you do not burn through a mobile data plan, but it costs CPU. A Pi 4 or 5 handles a stream or two comfortably; an older Pi may struggle with multiple simultaneous transcodes. If your phone has storage to spare, syncing files and playing them directly avoids the problem.
• Library size. Navidrome is built to handle very large collections — the project cites testing with roughly 900,000 songs, mostly FLAC with some MP3 — but the initial scan on a Pi takes time. Run it once and let it finish rather than restarting mid-scan.
• Multi-library support. You can split music into separate libraries with per-user access, which is useful if you want to keep, say, family music separate from personal listening or audiobooks.
• Updates. The project releases regularly, so plan a simple update path (pull a new image, restart) and keep your data directory outside the container.

A concrete scenario

Suppose you have a Pi 4 with a USB SSD holding 40,000 FLAC files, and you want to listen on an iPhone while commuting. Install via Docker, point the music folder at the SSD, set the data directory to a path on the same SSD, and let the first scan run overnight. Create your admin account, then install an OpenSubsonic-compatible iOS client. Enable transcoding to a modest bitrate for mobile playback, and keep a direct-play option for home Wi-Fi. If you later want to listen away from home, add a VPN rather than opening a port directly.

Next step

Read the installation page on Navidrome for the exact Docker command, port and environment variables for the current release, then check its community links (Reddit and Discord, referenced on the site) if your Pi-specific hardware or storage setup throws an error.

Which mobile apps can I use to stream music from Navidrome?

Navidrome itself does not make a first-party iOS or Android app. Instead, it exposes your library through the Subsonic/OpenSubsonic API, which a broad ecosystem of third-party mobile clients already supports. That is the intended way to listen on a phone: run the server on your own hardware, then point a compatible client at it.

What this means in practice

• You install and run Navidrome on a computer, NAS or Raspberry Pi, and it serves your music collection over the network.
• On your phone, you install any OpenSubsonic-compatible client and enter your server address, username and password.
• The client handles browsing, playback, playlists and often offline caching; Navidrome handles the library, transcoding and user accounts.

Picking a client

The right choice depends mostly on your platform and how you listen:

Because the compatible-client list is long and changes over time, the most reliable starting point is Navidrome's own documentation and community channels, which maintain current recommendations. See Navidrome for the official client list and setup guidance, and the project's linked community spaces for user reports on which apps work well.

A sensible next step: decide whether you need offline playback, then shortlist two or three clients for your phone's platform, test each against your own library, and keep the one whose search and navigation feel fastest with your collection size.

How does Navidrome handle transcoding to save mobile data?

Navidrome transcodes your music on the fly as you play it, converting or reducing files to a lower-bitrate stream before sending them to your device. The original files on your server stay untouched; only the streamed copy is altered, so you keep full-quality masters for home listening while mobile playback consumes less data.

The practical effect is that a large FLAC library doesn't have to be downloaded at full size over cellular. You can set a lower quality for mobile sessions and a higher one (or none) on Wi-Fi, which is the usual way people balance data usage against fidelity.

H3 How to think about the trade-off

• Data savings vs. quality: Transcoding to a lossy lower bitrate cuts bytes sharply, but you're hearing a re-encoded version, not the original. On decent headphones in a noisy environment the difference is often small; on a quiet system it can be audible.
• Server CPU vs. bandwidth: Transcoding costs processing power on the machine running Navidrome. The page notes it runs well on resource-limited hardware such as a Raspberry Pi, but heavy simultaneous transcoding is still the main thing that stresses a small server.
• Caching vs. streaming: If your mobile client caches tracks, transcoding mainly affects the first download; if it streams each time, the savings recur on every play.

H3 A concrete scenario

You keep 900K songs in mixed FLAC and MP3 on a home server, per the project's tested scale. On the train you stream at a reduced bitrate to stay inside a data cap; at home on Wi-Fi the same client plays the original files. The server does the conversion work, your phone does less downloading, and your library remains the single source of truth.

H3 Next step

Check whether your preferred mobile client exposes a per-network quality or transcoding setting, since Navidrome's OpenSubsonic API compatibility means third-party apps handle much of this. If you want a second opinion on client behavior, community channels such as Reddit discussions are where users compare real-world results.

Can Navidrome manage multiple music libraries with different user access?

Yes. Navidrome supports multiple libraries with user-specific access controls, so you can keep different collections separate and decide who sees what. The site gives music versus audiobooks and family versus personal as examples, which covers the two most common reasons people want this.

H3 How it works in practice

• You organize your music into separate libraries on the server side, then grant each Navidrome user access only to the libraries they should see. A household member logging in to the web UI or a mobile client sees their permitted libraries, not the whole collection.
• This is useful when content types differ (albums versus audiobooks, where browsing and playback habits differ), or when privacy matters (a personal library alongside a shared family one).
• Because Navidrome is compatible with the OpenSubsonic API, third-party iOS and Android clients inherit the same access rules — permissions are enforced by the server, not per app.

H3 Trade-offs to weigh

• Library separation is a server-side organizational task: you decide folder structure and access mapping up front, and adding a new user means assigning libraries rather than just creating an account.
• If you only ever have one listener and one collection, multi-library support adds little; the more relevant Navidrome strengths in that case are its lightweight footprint (it runs on resource-limited hardware such as a Raspberry Pi) and its handling of very large collections.
• Access control here is about visibility, not editorial curation — it won't merge or de-duplicate overlapping content across libraries.

H3 Next step

Sketch your intended split before installing: list the libraries you want (for example "Family Music," "Audiobooks," "Personal") and, for each household member, which ones they should reach. Then create users and map access accordingly, and verify from a mobile client as well as the web player, since both paths go through the same server permissions.

For background on the project and client options, see Navidrome.

How does Navidrome compare to other self-hosted music streaming servers like Plex or Subsonic?

Navidrome is best understood as a lightweight, open-source music server rather than a full media platform. It focuses on streaming your own collection through a web player and a wide range of compatible mobile apps, and it implements the OpenSubsonic API. That API compatibility is the key difference from Plex: because Navidrome speaks the same protocol as Subsonic, it can work with many existing Subsonic-compatible clients instead of locking you into one company's app ecosystem. Plex, by contrast, is a broader media server with its own first-party apps and a account-based ecosystem.

H3. Where the differences show up

• Scope: Navidrome is music-first. Plex covers music, video, photos and more, which is convenient if you want one server for everything, but heavier if you only care about audio. Subsonic and its forks are also music-focused, and Navidrome is compatible with that client ecosystem.
• Resource use: The page describes Navidrome as lightweight, fast and self-contained, and says it runs well on resource-limited platforms such as a Raspberry Pi. That makes it a practical choice for a small always-on box. Plex generally expects more capable hardware, especially if you use video transcoding.
• Library size: Navidrome states it handles very large collections, citing testing with roughly 900,000 songs. If your library is enormous, that is a concrete signal worth weighing against other servers.
• Clients: Navidrome's own web UI is the built-in player, and mobile listening comes through third-party compatible iOS and Android apps. Plex gives you polished first-party apps tied to a Plex account. Subsonic-compatible clients give you choice, but the experience varies by app.
• Access control: Navidrome supports multiple libraries with user-specific access, so you can separate music from audiobooks, or a family library from a personal one. That is useful in shared households.
• Transcoding: Navidrome transcodes on the fly, reducing file size as you stream so you do not burn through a mobile data plan. This matters most when you listen away from home.
• Licensing and cost: Navidrome is open source under GPL v3 and distributed free of charge. Plex has a free tier plus paid options, and its feature set is tied to those tiers.

H3. How to choose

If your goal is a small, efficient server for a large personal music collection, with freedom to pick Subsonic-compatible apps, Navidrome fits that job well. If you want one server for video, photos and music with tightly integrated first-party apps, Plex is the more natural fit. If you already use Subsonic clients and want a compatible server that is actively developed, Navidrome is a direct option.

A practical next step: list the devices you actually listen on, then check whether your preferred app is Subsonic-compatible. That single check usually decides between Navidrome and a first-party ecosystem like Plex. For broader context, see Plex and Subsonic.