What Is Local Music and How Do You Play Your Own Collection?

Local music means audio files stored on hardware you control — your computer's drive, an external disk, a NAS, or a home server — rather than tracks streamed from a subscription catalog. You play it with a music player that scans folders, reads embedded tags, and builds a library from those files. The main trade-off: you supply and organize the files, but in return you get offline playback, no ads or tracking, and lossless formats like FLAC or WAV up to 192 kHz without resampling. This guide covers what counts as local music, how to pick a player, how to set up remote streaming, and where things commonly break.

What counts as "local music"

A file is local music when it lives on storage you own and the player reads it directly, with no streaming account in the loop. Common formats include FLAC, WAV, MP3, AAC, and OGG. Your player identifies each track by the metadata tags inside the file — artist, album, title, track number, cover art — not by the folder name, which is why clean tags matter more than a tidy folder tree.

Two things are worth separating:

• Playback — a desktop or mobile app opens the files on that device.
• Streaming your own library — a server process runs on one machine and sends your files to other devices over your network or the internet. The files are still yours; only the delivery changes.

What a local player actually does

A capable local player handles more than pressing play. Based on what Audion documents, the typical feature set looks like this:

Not every player offers all of these. When comparing options, check the rows you actually care about rather than the longest feature list.

Choosing a player: match it to your setup

The right choice depends on your operating system, how large your library is, and whether you want to reach your music from other devices.

• Desktop-only, single machine — any solid local player works. Prioritize fast search across large libraries and gapless playback if you listen to albums.
• Cross-platform consistency — Audion runs on Windows, macOS, and Linux from one codebase with the same features on each, plus an Android app. If you move between machines, that consistency saves reconfiguration.
• Remote access — you need a server component, not just a player. Audion Server runs on a home server, Raspberry Pi, or VPS and is reachable from any browser or the Audion app.
• Ecosystem fit — if you already run Plex, Jellyfin, or Navidrome, check whether the player integrates with them before switching. Audion lists integrations with Last.fm, MusicBrainz, Plex, Jellyfin, Spotify (playlist import), Discord, and Navidrome.

If privacy and offline use are your priorities, favor players that state plainly that no account or telemetry is involved. Audion describes itself as free and open source with no accounts, no ads, and offline operation.

Setting up remote streaming from your own library

If you want your collection available outside the house, the pattern is the same across server-based players: run a server on always-on hardware, point it at your music folders, then connect from a client.

With Audion Server, the documented flow is:

1. Run the server on a home server, Raspberry Pi, or VPS. The docs give a single Docker command:

   docker compose up -d
   

   Expected result: the server and frontend containers start, and the server reports ready on port 8080.
2. Confirm it's reachable by opening the server in a browser or connecting the Audion app.
3. Authenticate — the server uses JWT auth with multi-user support and isolated libraries per user, so each account sees only its own music.
4. Stream — the server handles multi-format streaming (FLAC, MP3, AAC, OGG and more) with on-demand transcoding, for example FLAC to MP3 via an ffmpeg cache when a client can't handle the original.
5. Connect other clients — the Subsonic API means apps like Symfonium, Feishin, and DSub can talk to the same server.

For access from outside your network, the docs mention tunnel support so you don't need to open ports. The backend is written in Rust and is light enough to run on a Raspberry Pi.

Common problems and how to check them

Files don't show up in the library. The player reads tags, not filenames. Check that the files carry proper metadata and that the folder is inside a scanned location. Unusual or corrupted tags are a frequent cause.

A track won't play or sounds wrong. Verify the format is supported. Lossless files like FLAC and WAV at high sample rates are handled by players that explicitly support them; a player that resamples will still play the file but not at full quality.

Remote streaming fails. Work through it in order: is the server process actually running, is the port reachable, are the credentials valid, and does the client support the file's format or need transcoding enabled? Transcoding settings and authentication configuration are the two most common culprits.

Lyrics don't appear. Synced lyrics are fetched automatically by players that support them, but the match depends on track metadata. Inconsistent artist or title tags break the lookup.

What you give up, and what you keep

Going local means you're responsible for acquiring files, backing them up, and keeping tags consistent. In exchange, playback works offline, there are no ads or tracking, lossless and high-resolution audio play without resampling, and the files remain yours regardless of what any service does with its catalog. If you also run a server, you get the convenience of streaming without handing your library to a third party.

Audion is free to download and use, with donations supporting development and unlocking account sync perks; the free tier includes full playback, synced lyrics, themes, plugins, and basic account sync. Check the current download page for your platform — Windows, macOS, Linux, and Android are listed — and confirm the feature set matches your priorities before committing your library to it.