How to Self-Host Navidrome: Music Streaming Server 2026

TL;DR

Navidrome (GPL 3.0, ~12K GitHub stars, Go) is a modern, lightweight self-hosted music streaming server. Point it at your music folder and stream to any device via the web UI or hundreds of Subsonic-compatible apps. Spotify charges $9.99/month for music you don't own. Navidrome streams your own purchased collection — every FLAC, MP3, and ALAC file — to every device for free.

Key Takeaways

Navidrome: GPL 3.0, ~12K stars, Go — music server compatible with Subsonic API
Subsonic API: Works with 50+ existing client apps (DSub, Symfonium, Sonixd, Feishin)
Transcoding: Serve FLAC to web browser as MP3/AAC on-the-fly for bandwidth efficiency
Playlists: M3U playlists in your music folder, plus server-side playlists
Last.fm scrobbling: Track listening history and discover similar music
Multi-user: Each user has their own playback history, playlists, and favorites

Part 1: Docker Setup

# docker-compose.yml
services:
  navidrome:
    image: deluan/navidrome:latest
    container_name: navidrome
    restart: unless-stopped
    ports:
      - "4533:4533"
    volumes:
      - navidrome_data:/data
      - /path/to/music:/music:ro    # Your music library (read-only)
    environment:
      ND_SCANSCHEDULE: "1h"          # Scan library every hour
      ND_LOGLEVEL: info
      ND_SESSIONTIMEOUT: 24h
      ND_BASEURL: ""
      ND_MUSICFOLDER: /music
      ND_TRANSCODINGCACHESIZE: 100MB
      TZ: America/Los_Angeles

volumes:
  navidrome_data:

docker compose up -d

Visit http://your-server:4533 → create admin account on first visit.

Part 2: HTTPS with Caddy

music.yourdomain.com {
    reverse_proxy localhost:4533
}

Part 3: Music Library Structure

Navidrome reads standard music folder structure:

/music/
├── Artist Name/
│   ├── Album Name (Year)/
│   │   ├── 01 - Track One.flac
│   │   ├── 02 - Track Two.flac
│   │   └── cover.jpg            ← Album art
│   └── Another Album (Year)/
│       ├── 01 - Song.mp3
│       └── cover.jpg
├── The Beatles/
│   ├── Abbey Road (1969)/
│   │   ├── 01 - Come Together.flac
│   │   └── 02 - Something.flac
│   └── cover.jpg

Supported formats

Format	Description
FLAC	Lossless — best quality
MP3	Lossy — most compatible
AAC/M4A	Lossy — good quality/size
OGG Vorbis	Lossy — open source
ALAC	Apple lossless
WMA	Windows Media
AIFF	Uncompressed

Part 4: Transcoding

Serve high-quality FLAC files as compressed audio for bandwidth savings:

# Enable transcoding in docker-compose.yml:
# Requires ffmpeg in the container (included by default):
environment:
  ND_TRANSCODINGCACHESIZE: 500MB   # Cache transcoded files

Transcoding profiles (configured in web UI):

mp3 320k: FLAC → MP3 320kbps
mp3 192k: FLAC → MP3 192kbps (default for web browser)
aac 256k: FLAC → AAC 256kbps (for mobile)

In the web UI:

Admin → Users → [user] → Max bit rate: limit per user

Part 5: Client Apps (Subsonic API)

Navidrome implements the Subsonic API — any of these apps work:

Web browser

Built-in at https://music.yourdomain.com — modern Vue.js interface with:

Queue management
Shuffle / repeat
Keyboard shortcuts
Album art display

Mobile apps

App	Platform	Notes
Symfonium	Android	Best Android Subsonic client
DSub	Android	Classic, reliable
substreamer	iOS	Good iOS client
Ultrasonic	Android	Open source
Sonic	iOS/macOS	Native macOS support

Desktop apps

App	Platform	Notes
Feishin	All	Modern Electron client
Sonixd	All	Open source, actively maintained
Strawberry	Linux/Windows	Music player with Subsonic support

Setup (same for all apps)

Server URL: https://music.yourdomain.com
Username: your-navidrome-username
Password: your-navidrome-password

Part 6: Last.fm Scrobbling

Track your listening history on Last.fm:

Profile → Last.fm → Connect
Authorize Navidrome on Last.fm
Every played track scrobbles automatically

This enables:

Listening history and statistics
Similar artist/album recommendations
"Now Playing" display on your Last.fm profile
Weekly/annual listening reports

Part 7: Playlists

M3U playlists in your music folder

# Create a playlist file in your music folder:
cat > /path/to/music/playlists/Morning Workout.m3u << 'EOF'
/music/Artist A/Album/01 - Energetic Song.mp3
/music/Artist B/Album/03 - Pump Up.flac
/music/Artist C/Album/07 - Fast Track.mp3
EOF

Navidrome imports M3U files from a configured playlist folder.

Server-side playlists

In the web UI:

Browse albums/tracks
Click + → Add to playlist
Create new playlist or add to existing

Playlists sync to all connected apps via Subsonic API.

Part 8: Multi-User

# Create users in Navidrome admin UI:
# Admin → Users → + Add User

# User types:
# Admin: full access, can create users
# Regular: play music, manage own playlists
# Read-only: play only, no playlist management

Each user has separate:

Playback history
Playlists (private or shared)
Star/favorites
Recently played
Last.fm connection

Maintenance

# Update:
docker compose pull
docker compose up -d

# Force library rescan:
# Admin → Library → Rescan Full

# Backup (Navidrome DB + config — your music files are separate):
tar -czf navidrome-backup-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect navidrome_navidrome_data --format '{{.Mountpoint}}')

# Logs:
docker compose logs -f navidrome

# Check library statistics:
# Admin → About → Library stats

Why Self-Host Navidrome?

The case for self-hosting Navidrome comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Navidrome means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Navidrome, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Navidrome headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Navidrome data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Navidrome without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Navidrome's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Navidrome backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Navidrome's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Navidrome's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Navidrome's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Navidrome's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f navidrome

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Navidrome's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats navidrome. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Navidrome Updated

Navidrome follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Navidrome is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See also: Jellyfin — if you also want to stream video

See all open source music tools at OSSAlt.com/categories/media.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)