Skip to content

The Share Page

When you share a playlist or selection of tracks from The Library, visitors land on a dedicated, token-gated share page. The page can preview the selected content and expose downloads only when you have allowed them; visitors do not need a Library account.


The share endpoint returns only the token-gated selected content and configured metadata for that delivery. For playlist links, this includes the stored track order and only the files permitted by the stored selection and download configuration.


When the share renders playable content, playback is limited to the selected content returned for that token. The public endpoint does not expose the owner’s Dropbox access token.


Depending on the permissions you set when creating the share link, visitors may be able to download selected individual files or allowed project folders. The share page shows only the available download options:

  • Per-file downloads — visitors can download specific formats like WAV, stems, or project files for each track
  • Folder downloads — for larger packages like full stem collections, visitors can download everything as a ZIP file
  • No downloads — if downloads are disabled, visitors can only use the remaining allowed share features

When downloads are enabled, the share page displays download buttons only for allowed files and types. Unselected files must not be exposed through the public share page.


Direct links record access and per-format download counters. Playlist links record access/download totals and per-track download metadata. These are endpoint data contracts, not a promise of a universal dashboard report.


When visitors view your share page, they can see the collaborators listed on each track. This builds transparency — anyone checking out your work knows who contributed to it.

Collaborator avatars and names appear alongside the track information, making it easy for listeners to discover other artists or producers involved in a project. This is especially useful for co-production credits or vocal feature arrangements.


Share links can have an expiration. When a link expires, the share endpoint returns an unavailable response rather than share data. A link may also be created without an expiration.

  • Temporary shares — useful for time-sensitive feedback like sending a mix to a client before a deadline
  • Never-expiring shares — useful when you need a durable delivery link and intend to manage revocation yourself

If a temporary share expires, create a new delivery link when you still need to share the tracks.


The Library uses Dropbox to store and serve your shared files. When you create a share link, the system generates temporary download URLs through your connected Dropbox account. This means:

  • Files stay in your Dropbox — nothing gets uploaded to separate servers
  • Temporary delivery URLs — Dropbox URLs are generated for allowed content rather than exposing your stored Dropbox token
  • Direct transfers — visitors download straight from Dropbox, so file quality remains intact

If your Dropbox connection is interrupted or its token expires, affected temporary delivery URLs cannot be generated until the connection is repaired.


  • Send shares before final deadlines — set expiration dates that give collaborators enough time to review without leaving permanent links active
  • Review the stored selection — selected files and configured permissions, not folder naming, determine what a recipient can download.
  • Use shares for A&R submissions — compile your best five to ten tracks and share them as a curated playlist rather than individual links
  • Keep Dropbox connected — an expired Dropbox token breaks all your share download links until you reconnect