Playlist imports

Imported playlists are separate from flows.

• They do not regenerate on a schedule.
• They do not use source mix, focus filters, or deep dive.
• They keep the exact imported tracklist.
• They can reuse completed Aurral tracks or existing Lidarr files when worker settings allow.

Spotify import

The fastest path is in-app import on Playlists.

1. Open the create menu.
2. Select Import playlist.
3. Select Spotify.
4. Select Connect Spotify.
5. Approve access in the pop-up window.
6. Select a playlist.
7. Start the import.

You can set a display name and a synchronization schedule. Synchronization gets the Spotify tracklist again and queues new tracks.

Choose None for a fixed tracklist. You can change the schedule later from the playlist menu.

Aurral stores the connection for each user. Use Disconnect in the import modal to revoke access.

Allow the OAuth pop-up window if your browser blocks it. The Aurral origin must provide oauth.html.

Manual CSV import

When OAuth is not an option:

1. Export the playlist from Exportify.
2. Convert the file with the Spotify CSV converter.
3. Import the JSON file on the JSON file tab.

You can also use CSVJSON. Aurral accepts its output directly and understands Spotify-style keys like Track Name, Artist Name(s), and Album Name.

What the importer accepts

The importer accepts these JSON shapes:

1. An exported Aurral playlist file
2. A single playlist object with a tracks array
3. A raw array of tracks
4. A bundle object with a playlists array
5. A nested { "playlist": { ... } } wrapper

Required track fields

Each track must include:

• artistName
• trackName

Accepted aliases:

Field	Accepted keys
Artist	artistName, artist, artist_name, Artist Name(s)
Track	trackName, title, name, track, Track Name
Album (optional)	albumName, album, Album Name
Artist ID (optional)	artistMbid, artistId, mbid

Minimum shape:

{
  "artistName": "Burial",
  "trackName": "Archangel"
}

Accepted JSON examples

Exported Aurral playlist file

{
  "type": "aurral-static-tracklist",
  "version": 1,
  "exportedAt": "2026-03-25T12:00:00.000Z",
  "name": "Late Night Finds",
  "sourceName": "Friday Flow",
  "sourceFlowId": "abc123",
  "trackCount": 2,
  "tracks": [
    {
      "artistName": "Burial",
      "trackName": "Archangel",
      "albumName": "Untrue",
      "artistMbid": null
    },
    {
      "artistName": "Four Tet",
      "trackName": "Two Thousand and Seventeen",
      "albumName": null,
      "artistMbid": null
    }
  ]
}

Single playlist object

{
  "name": "My Playlist",
  "tracks": [
    { "artistName": "Massive Attack", "trackName": "Teardrop" },
    { "artistName": "Portishead", "trackName": "Roads" }
  ]
}

Raw array of tracks

Aurral treats a top-level array of track objects as one playlist.

[
  { "artistName": "Burial", "trackName": "Archangel" },
  { "artistName": "Air", "trackName": "La Femme d'Argent" }
]

Multi-playlist bundle

{
  "playlists": [
    {
      "name": "Warm",
      "tracks": [{ "artistName": "Bonobo", "trackName": "Kiara" }]
    },
    {
      "name": "Dark",
      "tracks": [{ "artistName": "Burial", "trackName": "Near Dark" }]
    }
  ]
}

Nested playlist wrapper

{
  "playlist": {
    "name": "Imported Set",
    "tracks": [{ "artistName": "Air", "trackName": "La Femme d'Argent" }]
  }
}

Import notes

• Aurral treats a top-level array of track objects as one playlist.
• Aurral treats a top-level array of playlist objects as multiple playlists.
• If an imported playlist name conflicts with an existing playlist, Aurral renames it automatically.
• Imported playlists queue their own downloads and do not affect any flow configuration.
• When existing file reuse succeeds, Aurral immediately marks the imported track as complete.

Download retries and failure behavior

Imported playlists behave differently from flows when downloads fail:

• Aurral queues each imported track as a separate worker job.
• The active download pipeline can try multiple candidates and configured sources.
• If all options fail, the track stays in the failed state after a restart.
• Choose Re-search missing from the playlist menu to explicitly queue failed tracks again.
• Only flows can generate replacement tracks.

Existing file reuse

Aurral can use one file in multiple playlists. This prevents a second download of the same file.

If you add a flow track to a static playlist, both playlists use the same file.

When the flow refreshes, Aurral keeps files that the static playlist uses. Aurral then builds the new flow.

Aurral prefers static playlists and Lidarr files. Multiple playlists can use one path.

Before Aurral removes a playlist, it moves the other file references. Navidrome does not show duplicate files.

Lidarr-aware reuse requires Aurral to read the files at the paths Lidarr reports. Match Lidarr’s media mount (for example /data:/data with root /data/music). See Match Lidarr.

If Lidarr runs on Windows and Aurral runs in Docker, run Test library access in Settings > Lidarr.

Use the reported path to add a mapping under Settings > Download Clients > Remote Path Mappings.

If Navidrome uses a different path for reused Lidarr files, enable Use Navidrome paths in M3U files.

Add a Navidrome path mapping so .m3u files use paths that Navidrome can open. See Navidrome.