Website Review
What is Audion?
Audion is a free, open-source music player for your own local music files, not a streaming service. It runs natively on Windows, macOS and Linux (with an Android version mentioned on the site) and is built around the idea that you point it at folders you already own, it reads the tags, and it organizes the library for you — no account, no ads, no telemetry, and it works offline.
What it actually does
- Library scanning and organization — it scans your folders, reads tags and arranges things automatically.
- Synced lyrics — line-by-line lyrics that follow playback, fetched automatically.
- Themes — full CSS control, so you can use a community preset or write your own.
- Plugins — community-built extensions such as Last.fm scrobbling and Discord Rich Presence.
- Audio features — a 10-band equalizer, crossfade, gapless playback, multiple audio outputs, and lossless formats including FLAC and WAV up to 192 kHz with no resampling.
- Speed — the site emphasizes instant search across large libraries.
Who it suits
It fits someone with a real music collection on disk — ripped CDs, Bandcamp purchases, a NAS full of FLAC — who wants a fast desktop player without signing into anything. If your listening is mostly discovery through a subscription catalog, this is not that; Audion plays what you already have.
The server angle
There is also an Audion Server component you can run on a home server, Raspberry Pi or VPS, described as a single Docker command. It streams in multiple formats, can transcode on demand (for example FLAC to MP3 via an ffmpeg cache), supports the Subsonic API so clients like Symfonium, Feishin and DSub can connect, and handles multi-user setups with isolated libraries and JWT auth. That turns Audion from a desk-bound player into something you can reach from a browser or the app while away from home.
Trade-offs to weigh
The cost is setup effort and self-reliance: you manage your files, and features like lyrics or metadata quality depend on sources and community plugins rather than a single curated catalog. The payoff is control — your library stays local, formats are not resampled, and the interface is customizable down to the CSS.
A practical next step
Start with the desktop app on one machine and a single music folder to see whether the scanning and tag handling match how your files are organized. If that works and you want access from other devices, add Audion Server later — the Subsonic API support means you can keep using clients you may already have. The project's own pages are at Audion, and if you want to compare self-hosted library servers more broadly, Navidrome is a well-known alternative in the same space.
How do I set up Audion Server to stream my music library remotely?
Audion Server is the self-hosted companion to the Audion desktop player: you run it on a machine that holds your music, and then reach that library from a browser, the Audion app, or any Subsonic-compatible client. The site describes it as a lightweight Rust backend that can run on a home server, Raspberry Pi, or VPS, started with a single Docker Compose command.
What you need first
- A machine that stays on and can reach your music files — a home server, a Raspberry Pi, or a VPS.
- Docker and Docker Compose installed on that machine.
- Your music library organised in folders on that machine (Audion's scanner reads tags and organises automatically).
- A decision about access: same network only, or over the internet.
The basic setup path
- Put your music on the host machine and note the folder path.
- Create a
docker-compose.ymlthat mounts that folder into the server container and exposes a port (the site's example uses:8080). - Run
docker compose up -d. The site's sample output shows anaudion-serverandaudion-frontendcontainer starting, then "Audion Server ready on :8080". - Open the web interface at that address, create your account, and point the server at your music folder if it isn't already mounted.
- Add users if other people need their own libraries — the server supports JWT auth and multi-user setups with isolated libraries per user.
- Connect a client: the Audion app itself, a browser, or a Subsonic-compatible app such as Symfonium, Feishin, or DSub.
Reaching it from outside your home
The site mentions tunnel support specifically so you don't need port forwarding. That matters because opening a port to the internet exposes the service directly; a tunnel keeps the connection outbound from your server. If you'd rather not run a tunnel, a VPN into your home network is the other common route. Either way, treat the login as the only thing standing between the internet and your files, so use a real password and keep the server updated.
Practical trade-offs
| Choice | Good for | Cost |
|---|---|---|
| Raspberry Pi at home | Low power, cheap, always on | Limited CPU for on-demand transcoding |
| Home server / NAS | Large libraries, fast local access | You manage uptime and backups |
| VPS | Reliable remote access | Storage cost, and your music leaves your home |
| Tunnel vs. port forward | Simpler, safer remote access | Extra moving part to configure |
On-demand transcoding (the site gives FLAC → MP3 via ffmpeg with a cache) is the feature that decides your hardware. If you stream lossless to a phone on mobile data, transcoding saves bandwidth but costs CPU; a Pi can struggle with several simultaneous streams, while direct-playing FLAC avoids that entirely.
A concrete scenario
Say your library is 400 GB of FLAC on a NAS. Run Audion Server on a Pi 4 with the NAS folder mounted read-only, expose it through a tunnel, and use the Subsonic API from a phone app. At home, direct-play FLAC; on the road, let the server transcode to MP3. Your desktop Audion install keeps using the local files directly, so nothing changes there.
If you want the exact compose file and configuration options rather than this outline, the project's own documentation is the place to start: Audion.
What plugins are available for Audion and how do I install them?
Audion's plugin system is community-driven, and the site names Last.fm scrobbling and Discord Rich Presence as examples. It points to a plugin browser ("Browse all plugins") rather than a fixed list, so the exact catalog grows over time — check that page for the current set. Separately, the site lists built-in Integrations (Last.fm, MusicBrainz, Plex, Jellyfin, Spotify playlist import, Discord, Navidrome). Those are not the same as plugins: integrations appear to be supported connections handled by the app itself, while plugins are add-ons you install.
What the site confirms
- Plugins: community-built; Last.fm and Discord Rich Presence are the named examples.
- Integrations: the services listed above, described as working with tools you already use.
- Themes: full CSS control, with community presets or your own — a separate customization path from plugins.
- Server/streaming: Audion Server runs via Docker (one command shown), supports the Subsonic API, and works with clients like Symfonium, Feishin, and DSub.
How to install plugins
The page shows a "Loading plugins..." state and a "Browse all plugins" link but does not document installation steps in the supplied material. Practical route:
- Open the plugins section in the app (or the plugin browser on the site) and pick a plugin.
- Install or enable it from there, then configure it — for scrobbling or Discord presence you'll typically authorize your account once.
- Restart or reload if the plugin doesn't appear immediately.
If a plugin needs account credentials (Last.fm, Discord), expect a one-time sign-in flow; Audion itself requires no account for playback.
Choosing between a plugin and an integration
| Need | Likely path |
|---|---|
| Scrobble plays, show Discord status | Plugin |
| Connect Plex, Jellyfin, Navidrome, import Spotify playlists | Integration |
| Change look and feel | Theme (CSS) |
| Stream to other devices/apps | Audion Server + Subsonic API |
Next step
If you're setting up a home server, decide first whether you need plugins at all — the Subsonic API and Docker server cover most remote-listening needs. For desktop-only use, start with the plugin browser, enable Last.fm or Discord, and confirm playback and lyrics work before adding more. Compare against Navidrome if you mainly want a lightweight server, or Jellyfin if you already manage video and music in one library.
Can Audion sync lyrics and fetch metadata for my local music files?
Yes. Audion is built around local files, and the page lists both automatic synced lyrics and metadata lookups as core features. Lyrics are described as line-by-line and time-synced to playback and fetched automatically, while MusicBrainz integration is listed for retrieving metadata and high-resolution cover art. Your files stay on your machine; there is no sign-in requirement for playback.
H3 What this looks like in practice
- You point Audion at your music folders, and it scans them, reads existing tags, and organizes the library.
- For tracks with lyrics available, the player fetches timed lyrics and scrolls them with the song.
- For metadata, MusicBrainz integration fills in artist, album, and cover art where your tags are incomplete or inconsistent.
H3 Important trade-offs
- Synced lyrics depend on an external lyrics source, so obscure, self-released, or non-English tracks may come back without timing or without lyrics at all. Unsynchronized text is a common fallback.
- Metadata matching works best when your files have at least rough artist and title tags. Untagged files, compilations, and classical box sets are where automatic matching usually needs manual correction.
- Fetched lyrics and metadata are not the same as embedded tags. If you move the library to another player, corrections you make inside Audion may not travel unless you write them back to the files.
H3 A quick test before committing Copy 20–30 representative tracks into a separate folder, point Audion at it, and check three things: how many tracks get timed lyrics, how many get correct cover art, and how many need manual fixes. That ratio tells you more about your library than any feature list.
If you want a second opinion on how well your library matches, MusicBrainz's own database is the source Audion queries, so checking a few problem albums there first shows whether the data exists to be fetched: MusicBrainz. If you also keep a server-based library, the page notes Jellyfin, Plex, and Navidrome integrations, which let Audion act as a client alongside your existing setup.
Is Audion a good alternative to Spotify for playing my own music collection?
Yes, for a local library it is a strong alternative to Spotify — with one important caveat: it is not a streaming catalog. Audion plays files you already own, while Spotify gives you access to millions of tracks you do not. If your goal is to play, organize and stream your own collection without ads or accounts, Audion fits that job well. If you want discovery and new releases, it does not replace Spotify.
Where Audion fits
- Your own files: it scans folders, reads tags and organizes the library automatically, so you point it at a music drive rather than manage playlists by hand.
- Sound quality: FLAC, WAV and high-res up to 192 kHz are supported without resampling, which matters if you have lossless rips.
- Lyrics and look: synced line-by-line lyrics are fetched automatically, and themes are fully CSS-customizable — useful if you want a player that matches your setup.
- Offline and private: no accounts, no telemetry, works offline. Good for a laptop used on planes or a machine you would rather not tie to a cloud account.
- Extras: a 10-band EQ, gapless playback, crossfade, Last.fm scrobbling and Discord presence via plugins.
Audion vs. Spotify for a personal collection
| Need | Audion | Spotify |
|---|---|---|
| Play your own files | Yes, core purpose | Local files only, awkward |
| Lossless/high-res | FLAC, WAV, up to 192 kHz | Limited by plan and device |
| New music discovery | No catalog | Core strength |
| Accounts/tracking | None required | Required |
| Offline | Native | Downloaded tracks only |
| Remote access | Audion Server, Subsonic API | Spotify Connect |
The streaming question
Audion Server is the piece that makes it competitive with Spotify's convenience: run it on a home server, Raspberry Pi or VPS with one Docker command, then reach your library from any browser or the app. It supports on-demand transcoding (for example FLAC to MP3 via ffmpeg cache), the Subsonic API, JWT auth with multi-user libraries, and tunnel support so you avoid port forwarding. That is the difference between a desktop player and a genuine Spotify substitute for your own music.
A concrete scenario
You have 400 GB of FLAC on a NAS. Install Audion on your desktop for home listening, run Audion Server on the NAS, and use the Subsonic API to play the same library through Symfonium or Feishin on your phone. Last.fm scrobbling keeps your listening history intact, and nothing leaves your network unless you choose a tunnel.
How to decide
Choose Audion if your library is already large, you care about lossless playback and privacy, and you are willing to run a small server for mobile access. Stay with Spotify if discovery, shared playlists and a catalog you do not have to maintain are the point. Many people reasonably run both — Spotify for finding music, Audion for owning it.
How does Audion handle privacy and offline playback compared to other music players?
Audion's privacy and offline story is simple: it is a local-first player with no accounts, no telemetry and no sign-in, so your library stays on your machine and playback does not depend on a connection. That differs from streaming-first services such as Spotify, where offline listening means downloading licensed tracks inside a logged-in account, and from cloud locker products that require uploading your files before you can hear them anywhere.
Offline playback. Audion scans your folders, reads tags and plays local files directly, including lossless formats such as FLAC and WAV. Gapless playback, instant search and the 10-band EQ all work without a network. Lyrics are fetched automatically, so treat synced lyrics as the one feature that may need a connection the first time; cached lyrics should then display offline. For a commute or a flight, that means no "unavailable offline" gaps as long as the files are already on the device.
Privacy. No accounts, no telemetry and no tracking are stated product features. Your listening history lives locally unless you deliberately add a plugin such as Last.fm scrobbling or Discord presence, which shares data with those third parties. The optional Audion Server changes the picture: it is self-hosted on a home server, Raspberry Pi or VPS, with JWT auth and isolated libraries per user. Your music then leaves the house only through infrastructure you control, and tunnel support avoids opening router ports.
Where it fits against alternatives.
| Need | Audion | Streaming service | Cloud locker |
|---|---|---|---|
| Plays your own files offline | Yes, local-first | Only downloaded catalogue | Usually needs upload/sync |
| Account required | No | Yes | Yes |
| Data leaves your device | Only if you enable a plugin or self-host | Yes, by design | Yes, to the provider |
| Synced lyrics | Automatic | Varies by track/region | Often limited |
| Cross-platform | Windows, macOS, Linux, Android | Broad | Broad |
Decision criterion. Choose Audion if you already own a music collection and want playback, lyrics and theming without an account or an internet dependency. Choose a streaming service if discovery and a licensed catalogue matter more than file ownership. Choose a self-hosted setup only if you are comfortable running Docker and maintaining a server; otherwise the desktop or Android app alone covers most offline listening.
Next step. Install the desktop app, point it at one music folder, and confirm that tags, artwork and lyrics resolve correctly before moving your whole library. If you later want browser access from other devices, evaluate Audion Server separately, since it introduces the only real privacy trade-off: your files become reachable over the network you configure.
User reviews (0)