In this article
A Music Assistant provider table is best read as a set of independent capability declarations, not as a single compatibility score. One field identifies supported media types; others describe recommendations, subscription requirements, authentication, or maximum stream format.
These fields can help you rule providers in or out before configuration. They do not measure playback reliability, search relevance, network performance, or overall quality. This guide is based only on Music Assistant’s documentation; no providers or playback devices were tested.
Start with the source model
Music Assistant does not supply media. A music source is where media lives: a streaming service, local storage, a media server, or a directory of radio stations, podcasts, or audiobooks. Music Assistant reads configured sources and combines their items into one library (Music Assistant: Music Sources).
That combined library can contain artists, albums, tracks, playlists, radio stations, podcasts, and audiobooks. However, each provider exposes only its documented categories and capabilities.
The provider table therefore answers several narrow questions rather than one broad question: What can this source expose? Where does it search? How does it authenticate? Which discovery features are available? What stream format can it provide?
Subscription and source location are separate fields
Subscription FREE indicates whether the documented integration supports free access. Self-Hosted Local Media indicates whether it connects to media hosted through infrastructure you operate.
Emby and YouTube Music show why these fields should be considered separately:
| Provider | Subscription FREE | Self-Hosted Local Media |
|---|---|---|
| Emby | Yes | Yes |
| YouTube Music | No | No |
Emby is a media server you run yourself. Its provider connects Music Assistant to music libraries already indexed by that server (Music Assistant: Emby).
YouTube Music is a hosted streaming service, and its Music Assistant provider does not support free accounts (Music Assistant: YouTube Music).
These fields are eligibility checks, not wider assessments. Self-hosted status does not establish privacy, security, uptime, or network performance. Likewise, the subscription field does not establish whether a particular account or plan suits your needs.
Media types define what can appear
Media Types Supported lists the categories a provider can expose to Music Assistant.
Emby lists:
- Artists
- Albums
- Tracks
- Playlists
YouTube Music lists the same four categories plus podcasts (Emby; YouTube Music).
Read this field literally. If you require podcasts, the documented difference matters. Do not assume support for unlisted categories: neither page lists audiobooks or radio stations.
A listed category also does not guarantee parity with another provider. “Tracks” does not promise identical metadata or availability, while “playlists” does not establish equivalent editing or synchronization behavior.
Library controls are another layer
Music Assistant provides general controls for:
- Synchronizing supported media categories into its library
- Importing tracks associated with an album
- Importing tracks from selected playlists
- Synchronizing library additions and removals back to the originating source
- Scheduling synchronization through background tasks
These controls are described in the general source documentation, but their presence does not prove that every provider supports every media type or form of write-back. Sync-back applies only to the originating source; adding an item from one provider does not add it to every configured provider (Music Sources).
When the same album exists in multiple sources, Music Assistant attempts to link the copies and play the best-quality available version. This linking requires sufficient metadata and is not guaranteed (Music Sources).
Ask three separate questions:
- Can the provider expose the required media type?
- Can Music Assistant import it in the desired way?
- Can changes be synchronized back to that source?
Search support needs a boundary
A search capability matters only when you know what it searches.
For Emby, Music Assistant can search the “Music” libraries on the connected Emby server. Its search scope is therefore the music available through those libraries (Emby).
For YouTube Music, the connected account’s library and playlists can appear in Music Assistant, and the service catalogue can be searched (YouTube Music).
These claims define scope, not performance. The documentation does not compare search completeness, ranking, latency, or relevance.
Discovery features are independent flags
Provider tables separate several discovery capabilities:
- Recommendations Supported
- Endless Mix
- Artist Top Tracks Support
- Similar Artists Support
- Similar Tracks Support
Emby marks recommendations and Endless Mix as unavailable but supports artist top tracks and similar tracks. YouTube Music supports recommendations, Endless Mix, artist top tracks, and similar tracks. Neither provider lists similar-artist support, and both mark lyrics as unsupported (Emby; YouTube Music).
Each flag stands alone. Recommendation support does not imply Endless Mix, and similar-track support does not imply similar-artist support. A “Yes” documents availability, not the quality, consistency, or personalization of the results.
Authentication indicates operational work
Login Method describes how Music Assistant accesses the source.
Emby uses password authentication and requires a server address, username, and password (Emby).
YouTube Music uses token-and-cookie authentication and requires a Proof of Origin token service. Its cookies expire and may require authentication to be repeated. Because the supported token-server version can change, check the current provider page during configuration (YouTube Music).
These fields reveal setup and maintenance requirements. They do not establish credential security, predict session lifetime, or confirm account suitability.
Maximum stream quality is a ceiling
The provider pages list these maximum formats:
| Provider | Documented maximum stream quality |
|---|---|
| Emby | FLAC, 192 kHz/24-bit |
| YouTube Music | AAC, 256 kbps |
Treat these values as documented ceilings, not measured results. They do not prove that every item is available at the maximum, that the output device receives the format unchanged, or that one provider sounds better (Emby; YouTube Music).
Always read the provider notes
The summary table can omit important operating constraints.
Emby’s server must be reachable from the Music Assistant instance for scanning and playback. That establishes a connectivity requirement, not a guarantee of throughput, latency, or uptime (Emby).
YouTube Music is documented as a best-effort integration because YouTube provides no official API for retrieving its data and streams. The page also states that cookies expire and that the provider cannot run more than three concurrent streams (YouTube Music).
Preconfiguration checklist
Before adding a provider, ask:
- Does it expose every required media type?
- Is it self-hosted or a hosted service?
- Is the required account type supported?
- What library or catalogue can it search?
- Which discovery features are explicitly supported?
- What import and write-back behavior is available?
- What authentication and maintenance does it require?
- What is its documented stream-format ceiling?
- Do its notes identify connectivity, concurrency, metadata, or API constraints?
The answers establish structural fit. They do not determine real-world reliability, performance, security, subjective audio quality, or which provider you should choose.
No comments yet