How to Run Navidrome Music Streaming for VPS
Run Navidrome for your own music library on any phone. See storage sizing, Subsonic clients, offline sync, TLS, and safe backup advice before you start.
Wetin self-hosted music streaming for VPS dey give you
Self-hosted music streaming for VPS mean say na you dey run the player and provide the music. The server dey hold files wey you already own, and any phone fit reach am through internet with normal login. Make you understand the trade-off before you start: this one replace streaming service player, e no replace the service catalogue. Nothing new go appear for your library until you buy am or rip am, then copy the file go server.
Audio dey easier for server than video. The files small, phones fit decode common formats without help, and one listener dey use less bandwidth than video call. CPU no be the main wahala here. Disk space na the real limit. The other two things wey determine whether this setup go work na the quality of your tags and whether your phone app fit download music for offline use.
Which music server: Navidrome, Jellyfin, or Funkwhale?
Navidrome na the default choice when na audio you care about. Na one Go binary for one container, and e dey keep im state for one SQLite database. E answer the Subsonic API, na why plenty third party phone apps dey exist at all. Version 0.64.2, wey release on 24 September 2026, still be the current release on 2026-10-27. No run anything wey old pass 0.64.1, wey fix five security advisories, including password guessing against the Subsonic login wey no get throttling. The project talk say e dey run well for hardware wey get small resources, like Raspberry Pi, so server software no be the part wey go cost you.
Jellyfin make sense if you already dey run Jellyfin as media server for VPS for video. The music library dey work, and Finamp na free Jellyfin music app for Android and iOS wey fit download tracks for offline listening. Jellyfin itself still no get built in Subsonic endpoint, but community plugin dey add one. Subfin-NG, wey be fork of the Subfin plugin, "dey allow Subsonic-compatible music apps play your Jellyfin music library" by adding OpenSubsonic API to Jellyfin. E need Jellyfin 12.0 or later, and release v12.1.13.0 set this minimum on 16 October 2026 when e add Jellyfin 12.0 support. E also dey change quickly: at least seven releases land between 24 and 28 September 2026. So Subsonic apps fit reach Jellyfin too, through third party plugin instead of core feature, and you suppose test your chosen client against am before you depend on am. The bridge fit work the other way too: Navidrome 0.64.0 add experimental Jellyfin API, wey dey off by default and you fit switch on with ND_JELLYFIN_ENABLED, and im documentation talk say dem test am with Finamp, Jellify and Feishin.
Funkwhale na the federated option, and version 2.0 release for March 2026. Dem dey call Funkwhale server a pod, pods federate over ActivityPub (the protocol behind Mastodon), and users dey follow each other's playlists across pods. Version 2.0 replace the old libraries with playlists, so library follows turn playlist follows, and 2.0 pod no dey federate with pods wey still dey run 1.x. E answer part of the Subsonic API too, with one difference wey you need know: each user set separate Subsonic password for im own settings, because Subsonic protocol expect password wey server fit read back. Funkwhale installation heavy pass, because e need PostgreSQL and task queue beside the web app.
Pick Navidrome unless you want federation, or unless Jellyfin already dey run. The rest of this guide go set up Navidrome with Docker.
Why Subsonic API dey decide which phone app you go use
Subsonic na music server wey im HTTP API become common language for self-hosted audio, while OpenSubsonic na community project wey dey continue to extend am. Na this history make your phone get different options. Navidrome no ship with im own mobile app and e no need one, because any Subsonic client fit log in with server address and your account details.
This matter dey important pass for offline sync, wey na the feature wey decide whether the setup go work for everyday use. Phone wey dey inside tunnel no fit reach your server, so the client must don copy the files enter local storage before then. Every client fit stream. Na only some fit download. The client directory for navidrome.org/apps dey show which ones fit do am, and the choice wide for both platforms: Substreamer and Ultrasonic for Android, Amperfy and play:Sub for iOS. Several of the strongest clients na paid apps, and people dey mention Symfonium for Android pass others. Install two before you decide, because na this part of the system you go dey touch every day.
How much storage music library need?
Di data wey dey behind dis chart
[
{
"label": "Opus 128k",
"kbps": 128,
"gb_per_1000_albums": 43
},
{
"label": "MP3 320k",
"kbps": 320,
"gb_per_1000_albums": 108
},
{
"label": "FLAC 16/44.1",
"kbps": 900,
"gb_per_1000_albums": 304
},
{
"label": "FLAC 24/96",
"kbps": "3,000",
"gb_per_1000_albums": "1,013"
}
]Those figures na rough estimates based on bitrate, no be measurement of real collection, and the calculation simple enough make you check am against your own files. Treat album as 45 minutes, which be 2,700 seconds. Multiply bitrate for kilobits per second by 2,700, then divide by 8,000 to get megabytes. For 320 kbps, that one album go use 108 MB, so one thousand albums go use about 108 GB.
Lossless go change the answer. CD quality FLAC dey average near 900 kbps for ordinary material, so that same one thousand albums go need about 304 GB. 24 bit, 96 kHz library go reach roughly 1,013 GB, which be full terabyte for collection wey you fit list for paper. Phone-friendly Opus copy for 128 kbps fit put that same one thousand albums inside 43 GB. Run du -sh /path/to/music for the library wey you already get, because na your own average bitrate be the only number wey matter when you dey choose plan.
Bandwidth na the smaller part of the bill. Stream wey be 320 kbps dey use 40 kilobytes per second, so one hour listening go move about 144 MB. One hundred hours for one month na around 14 GB, and VPS transfer allowance no go even notice am. The exception na the first offline sync for phone, wey fit push tens of gigabytes for one evening.
Storage tier or compute tier?
Music server na large pile of cold data wey almost no computation dey run on top am. Reading one file at 40 kilobytes per second leaves any disk idle, and CPU only get serious work during library scan, during transcoding, wey you mostly no go do, and when e dey extract and cache cover artwork during scan or the first time person opens one item. So, fast NVMe for compute plan no go give you any benefit here, while the price per gigabyte na wetin dey stop you from uploading the FLAC copies. Na for this kind case storage VPS dey beat regular VPS, because dem price those plans per terabyte instead of per core.
Memory need no too much. Navidrome fit serve personal library with few hundred megabytes, and scan na the peak usage, not playback. Give the box 1 GB or 2 GB of RAM, then use the remaining budget for disk.
Install Navidrome with Docker Compose
First create the directories, then make the user ID wey the container go run as own dem. If Compose new to you, Docker Compose for VPS explain wetin this file dey assume.
sudo install -d -m 755 -o 1000 -g 1000 /srv/navidrome /srv/musicWrite docker-compose.yml by itself for im own directory:
services:
navidrome:
image: deluan/navidrome:0.64.2
user: "1000:1000"
ports:
- "127.0.0.1:4533:4533"
restart: unless-stopped
environment:
ND_LOGLEVEL: "info"
ND_SESSIONTIMEOUT: "24h"
ND_SCANNER_SCHEDULE: "@every 24h"
ND_BACKUP_PATH: "/data/backup"
ND_BACKUP_SCHEDULE: "0 4 * * *"
ND_BACKUP_COUNT: "7"
volumes:
- /srv/navidrome:/data
- /srv/music:/music:rodocker compose up -d
docker compose psdocker compose ps suppose show say the service dey run, instead make e dey restart. Container wey dey restart continuously almost always get permission problem for /srv/navidrome, and docker compose logs navidrome show the name of the file wey e no fit write.
Four details for that file worth explain. The port dey published only on 127.0.0.1, so na through the reverse proxy server go reach am, and e no go dey available on port 4533 from open internet: Docker dey write im own firewall rules, so plain 4533:4533 still dey exposed, even for machine wey ufw report say everything dey denied. The music volume dey read only, meaning scanner bug no fit delete your only copy. ND_SCANNER_SCHEDULE dey disabled by default, and guides wey dem write before Navidrome 0.55 dey call am ND_SCANSCHEDULE, the old name wey 0.55 change. The three backup settings turn on the built in database backup wey the backup section below depend on.
Put your music for the server
Use rsync copy the library go the server. E go continue from where e stop instead of starting again if connection drop.
rsync -av --info=progress2 ~/Music/ user@music.example.com:/srv/music/The trailing slash for the source dey important. If you no put am, you go get /srv/music/Music. When the copy finish, correct the ownership:
sudo chown -R 1000:1000 /srv/music
id -uThe container dey run as user id 1000, and the mount dey read only. So that id need read access to every file and traversal access to every directory. If another account own the copied files and the permissions block everybody else, the scan go find zero tracks while the web interface remain cheerfully empty, and the log go show open /music: permission denied. The chown above na one way to fix am. If other programs dey use the folder too, Navidrome Docker documentation suggest say make you allow reading instead, without changing the owner: sudo chmod -R a+rX /srv/music. id -u go print your real id, and how PUID and PGID dey work for Docker containers explain the mapping fully.
Reverse proxy and TLS so the phone fit work from anywhere
Point DNS A record to the VPS, then give Caddy three lines:
music.example.com {
reverse_proxy 127.0.0.1:4533
}sudo systemctl reload caddyCaddy request the certificate in the background as soon as e load the site, without waiting for visitor. Port 443 must dey open. Caddy enable two ACME (automatic certificate management environment) challenges by default, the HTTP challenge for port 80 and the TLS-ALPN challenge for port 443, and e pick one at random instead of always starting with HTTP. After failure, e retry once and then switch to the other challenge, so closed port 80 no stop the certificate. Leave port 80 open anyway, because Caddy's automatic redirect from HTTP to HTTPS dey served there. For nginx, add proxy_buffering off; to the location block: Navidrome dey push progress events to the web interface over one long lived connection, and when buffering dey on, the interface go wait while nginx still dey hold the response. If you serve am under path like /music instead of im own subdomain, set ND_BASEURL to the same path or the interface go load as blank page. The three common proxies dey compared for Nginx, Caddy and Traefik for VPS.
Open the site and create the first account. Default password no dey, and the first visitor go get prompt to create the admin user, so do this before you tell anybody the address. Then test the exact path wey phone client dey use:
SALT=$(openssl rand -hex 6)
TOKEN=$(printf '%s%s' 'YOUR_PASSWORD' "$SALT" | md5sum | cut -d' ' -f1)
curl -s "https://music.example.com/rest/ping.view?u=YOUR_USER&t=$TOKEN&s=$SALT&v=1.16.1&c=curl&f=json"Healthy answer dey start with {"subsonic-response":{"status":"ok" and name navidrome as the server type. Body wey contain "status":"failed" and error code 40 mean say proxy dey fine and the credentials wrong. Certificate error for this step na the first one to fix, because most phone clients reject bad certificate with message wey no tell the user anything.
Why your library dey look wrong after the first scan
Navidrome dey browse by tags instead of folders, so na the tags decide wetin you go see. If track no get album artist tag, e go file am under the track artist. Na why one compilation wey get different artist for every track fit turn to twenty albums with one track each. Fix this for the files, no be for Navidrome: MusicBrainz Picard and beets both dey look up album for MusicBrainz database, then write standard tags back.
Navidrome still dey split multi artist tag into separate artists. So if band name get separator, e fit split am by mistake. AC/DC na the example wey everybody dey meet. ND_SCANNER_ARTISTSPLITEXCEPTIONS hold the names wey dem must never split.
New files dey get picked up by file watcher few seconds after dem land. The watcher depend on kernel change notifications. Those notifications no dey arrive for files wey another machine write to network share wey dem mount. So for that kind setup, na the periodic ND_SCANNER_SCHEDULE dey keep the library current. Full rescan dey read tags for every file. This slow down for big library, and na one reason why database below worth protecting.
Users, playlists, and sharing
Admin go create the other accounts for the web interface, and users no get self signup. Each user get separate play counts, playlists, favourites, and ratings, so household no go end up dey share one taste profile.
Playlists dey come from two directions. Playlist wey user make for client dey live inside database. When person drop .m3u file inside library folder, system go import am during scan. This na the easy way to carry playlist from desktop player. Smart playlists na .nsp files. Dem be small JSON rule files wey system import the same way, and dem dey update by themselves as library dey change.
Sharing dey enabled by default from version 0.63.0, wey release for July 2026. E let user create public link for album wey anybody fit open without logging in. For server wey dey hold your complete library, this fit no be wetin you want. Set ND_ENABLESHARING to false to turn am off.
Back up database separately from music files
Navidrome backup wey e own dey cover database only. Documentation talk am direct: backup process dey back up database, meaning users, play counts, and the rest, but e no dey back up music or config. This separation na the correct way to reason about am, because the two parts dey fail differently. You fit copy music files again from the disk wey you rip dem from. Play counts, ratings, favourites, and playlists no dey anywhere else, and rescan no go bring dem back.
The compose file already dey write one copy every night into /data/backup and e dey keep seven of dem. Take one manually before upgrade:
sudo docker compose run --rm navidrome backup createThe move from 0.63 to 0.64 na the upgrade wey need this pass. Version 0.64.0 dey re-encode every internal id for migration wey touches every table, and clients wey keep offline downloads fit need to sync again afterwards.
Restore dey wipe the current database and copy the backup enter its place, and e must run while Navidrome stop. Restore no safe for live server.
Those files still dey for the same VPS, so dem no go survive if VPS fail. Push /srv/navidrome go another machine or object storage on schedule. Na the work restic and BorgBackup dey built for. The whole directory small, usually far below one gigabyte, so daily encrypted copy off the box cost almost nothing and e go restore everything wey rescan no fit bring back.
FAQ
I need transcode music for a VPS?
Almost never. Phones fit decode MP3, AAC, Opus and FLAC by demself, and current browsers for most systems fit do am too. So, server go send the file as e be and use almost no CPU. Na browsers you suppose check: Firefox only plays AAC when operating system or external library provide the decoder. So, AAC library for web player fit need transcoded stream. The main case wey make sense to enable am na when you dey stream FLAC library through mobile data. Converting from about 900 kbps down to Opus at 128 kbps fit reduce data usage by about seven times. Navidrome get managed transcoding for server since version 0.61. E dey detect the codecs wey client support, apply format-aware bitrate defaults, and let you cap bitrate for each player.
Why my phone app no fit download music for offline listening?
Because offline storage na client feature, no be server feature. Subsonic API allow any client fetch complete file, but na the app dey decide whether to keep copy for phone. Check client directory for navidrome.org/apps and choose one wey description mention offline downloads or caching. Some clients only cache wetin you don already play. That one no be the same as syncing album before journey.
Why one album split into several albums after the scan?
The album artist tag dey missing or e no consistent across the tracks. Navidrome dey group by tags, no be by folder. So, twelve tracks wey get twelve different artist values and no shared album artist value go look like twelve albums. Set album artist tag for every track inside the album, usually to Various Artists for compilation, then make am rescan. MusicBrainz Picard or beets fit do this for complete folder at once.
Self-hosted music streaming replace Spotify?
E replace the player and the library, no be the catalogue. You get your own collection for every device, with playlists and play counts wey no licensing change fit take away from you. You no go get new releases, and you no go get recommendations based on other people listening habits. Most people wey run this dey buy their music and keep cheap streaming account for discovery.