Playlists

What it is

A playlist is an ordered collection of tracks you want to present together a set for a gig, a submission package, a genre showcase, or a public catalog page. Playlists can contain tracks already in your Aden library (internal) or tracks from Spotify, found via ISRC lookup (external), so you can curate across both.

Playlists can be private (team-only) or public. Public playlists appear on your team's profile page, and you can share a link directly with anyone. You can also connect a playlist to a Spotify playlist so that Aden pushes any changes there automatically.

Using it

Create a playlist. Go to Playlists in the sidebar and click New playlist. Give it a title, choose whether it's public or private, add tags and genres if you want, and save. The playlist starts empty.

Add a track from the track itself. Anywhere a track appears, you can file it without opening a playlist first: the track page's actions menu and its "In playlists" section both offer Add to a playlist, as does the right-click menu on a track row. The picker searches the playlists you can write to (your own, plus your teams'), and typing a name that isn't there offers New playlist "<name>" under the list, which creates it in your active team with the track already in it. The same entry sits in the actions menu of a public share panel, but only for a signed-in viewer who reaches the track outside the link: a collaborator, or a member of its team. Holding a share link is not enough, or an expired link would leave the track readable forever through someone's playlist.

Add tracks. Open the playlist and use the Add page to pick tracks from your Aden library or import them from an external source. To import from Spotify, either connect your Spotify account and pick one of your own playlists from the list (search by name), or paste a Spotify playlist, album, or track URL. Either way you preview the tracks before adding. Connecting the account also makes private and collaborative playlists importable. A pasted link to one of those cannot be read without it. You can also look up tracks by ISRC via Songstats. Confirmed tracks land at the bottom of the playlist.

The Add page's source tabs (From library, Spotify, Songstats / ISRC, Manual) are kept in the address (?source=spotify), so the tab survives a refresh, the back button and the Spotify sign-in round-trip, and can be linked to. A preview you already loaded stays on its tab while you look at another one. The three import tabs need a Pro plan on the playlist's team: without it they stay visible but disabled, and hovering one says why and where to upgrade.

Bring whole playlists over. Playlists → Import creates one Aden playlist per source playlist, tracks included, for when the playlists already exist somewhere else. Two ways in:

• Your Spotify. Connect the account and tick the playlists you want, with a search box for long lists. This is also the answer for a Spotify folder: Spotify's API has no folder endpoint and a folder share link resolves to nothing, so pick the folder's playlists from this list instead.
• Paste links. Paste any number of playlist links at once. One per line, or a whole block of text with links in it. Paste a page address instead (a SubmitHub curator page, a playlist directory, a blog post) and Aden reads the page and lists every Spotify playlist it links to.

Either way you see what was found, name, cover, track count, owner, and tick what to import, up to 25 playlists per run. Links Spotify won't open (private to someone else, deleted) are counted separately rather than silently dropped, and a playlist that fails mid-import is named in an error while the rest still land. Imported playlists are private unless you flip the public switch, and they are not wired to Spotify sync. Importing copies the tracks in, it never pushes Aden's version back over the source playlist.

Reorder. Drag and drop any row to rearrange the playlist. Each drag is a single-row write, no full list rewrites happen in the background.

Add DJ metadata. Each row in the playlist has optional BPM, key, mode, energy, and cue-point fields. You can edit these individually to annotate the set for mixing purposes.

Annotate with notes. The playlist has a freeform notes field. Any team member can edit it collaboratively to keep set notes or context alongside the track list.

Edit details from the sidebar. The playlist's right-hand info sidebar mirrors the track sidebar: edit the title, description, visibility (public/private), tags, and genres inline. Visibility is a dropdown that, when public, also exposes the public link with a copy button; tags and genres are type-to-search inputs. The Tracks section lists each track with its cover art on the left (falling back to a status-tinted gradient when a track has no artwork) and its status indicator on the right, so you can scan the playlist's completeness at a glance.

Give it a custom link. The sidebar's Link row sets the playlist's public slug, so it lives at /@yourteam/playlists/summer-2026 instead of a number. Slugs are lowercase letters, numbers and hyphens, unique within your team, and can't be only digits. The old numeric link keeps working after you set one.

Share publicly. Toggle the playlist to public and share the URL. Viewers outside the team can browse the track list via your profile page or a direct link. The public page shows the cover and the tracklist in one card. The same layout as a public track or album page, and each row opens that track's own page. Only tracks you've shared publicly appear there, and the count above the list reflects exactly what a fan can see. To share a private playlist with specific people, use the Shares tab (see Sharing).

Sync to Spotify and Tidal. Connect your Spotify or Tidal account from the playlist's Promotion section to create a mirrored playlist there. After the initial push, every subsequent edit (adding, removing, or reordering tracks) is pushed to every connected platform automatically. Tracks are matched by ISRC; tracks the platform doesn't carry are skipped and reported after each sync.