mStream

Last reviewed Sep 13, 2026 · 872 words

mStream will have your music library streaming to your phone in under 10 minutes, with offline downloads, and that is genuinely its best feature and its ceiling. It scans a folder, serves a web player and its own mobile apps, and asks nothing else of you. Navidrome does more, integrates with more, and gets updated more often, and for most people it is the better server. mStream stays on the list because it is easier, lighter, and has a first-party mobile app with offline sync that just works, which the Subsonic-compatible world only gets through third-party clients. It has 2,384 stars, a GPL-3.0 licence, and a 2016 start date, with a release cadence the catalogue politely calls slower.

Setup is a folder and a port

The Node.js server reads a JSON config that points at one or more music directories and defines users. The LinuxServer image is the least fiddly way to run it:

services:
  mstream:
    image: lscr.io/linuxserver/mstream:latest
    environment:
      PUID: 1000
      PGID: 1000
      TZ: Europe/London
    volumes:
      - ./config:/config
      - /mnt/music:/music:ro
    ports:
      - "3000:3000"
    restart: unless-stopped

Open port 3000, add the /music folder as a library in the admin panel, create a user, and the scan starts. On a 20,000-track library the first scan takes a few minutes and the server settles at around 150 MB of RAM, under the catalogue's 256 MB. Metadata comes from the file tags and nothing else; there is no last.fm or MusicBrainz lookup, so a badly tagged library looks badly tagged. Tag your files first with Picard and mStream is happy.

The mobile app is the reason to pick it

The mStream mobile app for Android and iOS connects to your server, plays your library, and downloads albums or playlists for offline use with a tap. Playlists you build on the phone sync back to the server and appear in the web player. That is the loop people want from a personal Spotify, and mStream delivers it with no configuration and no third-party client to evaluate.

There is also a jukebox mode, where the web player on a laptop or a Raspberry Pi connected to speakers is controlled from your phone, which is a nice trick for a party or a kitchen. Shared links let you hand someone a playlist without an account. Multi-user is supported with per-user library access, so different folders for different household members is a matter of config.

What it lacks next to Navidrome

The Subsonic row is the one that matters. Navidrome speaks the Subsonic API, and that means Symfonium, DSub, play:Sub, Tempo and a long list of others work out of the box, several of which have offline modes that match or beat mStream's app. It also means Navidrome slots into anything else that speaks Subsonic, from car head units to Home Assistant. mStream has its own protocol, so its own app is the only mobile client, and if that app stalls, so does your phone experience. The personal Spotify with Navidrome walkthrough is the setup I point most people to.

Transcoding is the other gap. Navidrome will downsample a FLAC library to 128 kbps Opus for a mobile connection per client; mStream largely sends files as they are, which on a FLAC library is 1,000 kbps and a fast way through a mobile data cap. If your library is already MP3 or AAC this does not matter.

Who it suits

A household with a tagged MP3 library, a couple of phones, and no interest in scrobbling, smart playlists or a fleet of clients. Someone who wants offline sync without evaluating third-party apps. A low-power box where 150 MB and a Node process are fine. The catalogue's "basic web UI" and "slower release cadence" are real, and neither has stopped it working. Just be aware that a quiet project with a proprietary app protocol is a single point of dependency you cannot route around, whereas a Subsonic server can be swapped for another without touching the phones.

If your needs are bigger, the media server category has the full set, and Jellyfin already streams music adequately if you run it for video and would rather not add another service.

What I'd do

Try mStream first if you want the shortest path from a music folder to offline playback on your phone, and stay on it if the app satisfies you. Move to Navidrome the moment you want scrobbling, transcoding for mobile data, or a choice of clients, which in my experience is about 3 months in. Either way, tag the library properly first with MusicBrainz Picard, mount it read-only into the container, and keep the config folder in your backups; the music itself should already be there.