In this article
Music Assistant’s playlist interchange path has a specific boundary: only playlists in its library expose M3U8 export. The exported file can carry more than track references, including recording identifiers, provider mappings, artwork, and artist or album information (Music Assistant usage).
On import, Music Assistant creates a playlist. If a referenced track cannot be played directly, it can search user-selected, installed providers. It prefers exact identifiers, falls back to descriptive metadata, and retains the original reference for manual correction if no confident match is found (Music Assistant usage).
This is a documentation-based explanation. No export, import, matching, migration, or playback tests were performed.
The interchange path at a glance
Playlist in the Music Assistant library
|
Export
v
M3U8 file
+--------------------------------+
| Track references |
| ISRC and MusicBrainz ID |
| Artist and album information |
| Provider mappings |
| Artwork |
+--------------------------------+
|
Import
v
Created playlist
|
For each track reference
v
Play directly if possible
|
Otherwise search
selected, available providers
|
+------------+-------------+
| |
Exact ISRC or MusicBrainz ID IDs absent
| |
v v
Use match Try title, artist, duration
|
+--------+--------+
| |
Confident match No confident match
| |
v v
Use match Keep original
reference visible
This is an artifact-and-resolution path, not a promise that every track will match, remain playable, or resolve to an equivalent recording.
Which playlists can be exported?
Music Assistant documents M3U8 export only for playlists that live in its library. A provider-owned playlist found through Spotify, Tidal, or another provider’s search does not expose the export option merely because it is visible in Music Assistant (Music Assistant usage).
The important distinction is between:
- a playlist present in the Music Assistant library; and
- a playlist available only through a provider search.
Music Assistant also has a built-in provider for creating playlists containing tracks from multiple music sources. By contrast, a playlist stored on a particular music source can contain tracks only from that source (Music Assistant usage).
That establishes the general export boundary, but the documentation does not confirm export behavior for every specialized playlist subtype.
What the exported M3U8 can contain
Music Assistant adds extended tags to its M3U8 exports. The documented metadata categories are:
- ISRC, an identifier for a recording
- MusicBrainz ID
- Artist and album information
- Provider mappings
- Artwork
Music Assistant uses these extensions when importing the file. It also describes its exports as compatible with ordinary M3U players such as VLC and Kodi, which ignore the Music Assistant-specific tags (Music Assistant usage).
The exact identifiers are the export’s most useful portability inputs because Music Assistant gives them priority during matching. Provider mappings add context, but they do not guarantee that a provider will remain installed, available, or able to play the referenced item.
The documentation lists metadata categories without specifying the exact tag syntax or promising that every field will be present for every track. Its general compatibility statement is not a guarantee for every M3U implementation.
How import resolves unavailable tracks
When an import finishes, Music Assistant displays a “Playlist created” notification with an Open playlist shortcut (Music Assistant usage).
A track reference may be directly playable. If it is not, the import dialog provides a Search for tracks on list with a checkbox for each installed music provider. Music Assistant searches the selected providers that are currently available (Music Assistant usage).
Its documented resolution order is:
- Prefer an exact ISRC or MusicBrainz ID match.
- If those identifiers are absent, fall back to title, artist, and duration.
- If no confident match is found, retain the original reference for visibility and manual correction.
This is why the extended metadata matters: exact identifiers provide the importer with its preferred matching inputs, rather than leaving it only title, artist, and duration (Music Assistant usage).
The documentation does not define the confidence algorithm or guarantee that a result is the same release, edit, remaster, or recording. Retaining an unmatched reference preserves information about the original item; it does not establish that the item remains playable.
Library membership is not catalogue availability
YouTube Music offers a provider-specific example of the difference between library membership and searchable material. With an account connected, Music Assistant can show YouTube Music library content and playlists while separately searching its catalogue. By default, only liked music and the “episodes for later” playlists are added to the YouTube Music library. Other personal playlists must be added through the YouTube Music web app before they appear in the Music Assistant library (YouTube Music provider).
Catalogue availability, provider-account library membership, and presence in the Music Assistant library are therefore distinct states. Only the last places a playlist within the documented export boundary.
This example should not be generalized to other providers. Music Assistant describes its YouTube Music integration as best-effort because YouTube does not provide an official API for retrieving its data and streams (YouTube Music provider).
Smart Playlists are different
An imported M3U8 supplies track references and metadata for resolution. A Smart Playlist is instead a plugin-created, rule-based playlist whose tracks are reevaluated whenever it is played, using its saved rules and current library and provider state (Smart Playlists).
The Smart Playlists documentation makes no explicit export claim. It does not say whether these playlists can be exported or whether an export would contain their rules, currently resolved tracks, or another representation. An M3U8 export should therefore not be assumed to preserve Smart Playlist logic.
The documented boundary
Music Assistant documents a bounded interchange mechanism: an eligible in-library playlist becomes an M3U8 containing track references and potentially extended metadata. During import, directly playable references can be used as they are; unavailable ones can be searched across selected, available providers. Exact ISRC or MusicBrainz ID matches take priority over descriptive fallback fields, while unmatched original references remain visible for manual correction.
That mechanism does not guarantee complete metadata, universal player compatibility, successful matching, equivalent recordings, reliable playback, backup restoration, migration success, or Smart Playlist export.
No comments yet