A pre-save is a fan action that automatically adds your release to their streaming library the moment it goes live.
The fan clicks a link before release day, authorises a one-time permission, and on the release date the track or album appears in their library, often triggering an Apple “New Music” notification or a Spotify Release Radar inclusion. It is the streaming equivalent of pre-ordering a CD.
This guide is for artists and managers who keep reading that pre-saves matter but want to know what they actually move.
What is a pre-save?
A pre-save is a permissioned action where a fan authorises a third-party app to add a specific release to their DSP library on its release date. The mechanism is built on top of each DSP’s API.
The current setup as of 2026:
- Spotify — supports pre-saves through both first-party Spotify Marquee campaigns and third-party pre-save tools that use the Spotify Web API. The fan authorises once and the track is added on release date.
- Apple Music — uses a “pre-add” mechanic via MusicKit. The fan adds the upcoming release to their library while it is still in the pre-release window.
- Deezer, YouTube Music, Amazon Music — variable third-party tool support.
The actual user flow is short: click link, log in to DSP, authorise, done. The artist or distributor receives a count of pre-saves accumulated. On release day, every authorised library updates simultaneously.
Why does pre-save exist?
Two reasons, one for the artist and one for the DSP.
For the artist, a pre-save concentrates first-day streams into a single window. A track that accumulates 10,000 pre-saves goes live with 10,000 listeners hitting play in the first hour. That spike is a signal to the DSP’s algorithm. Release Radar inclusion, New Music Friday pitching strength, Discover Weekly seeding all weigh first-day velocity.
For the DSP, pre-save is a retention and engagement mechanic. A fan who pre-saved a release is statistically more likely to actually listen on release day than a fan who simply intended to. The DSP cares about active library growth, and pre-save delivers it predictably.
There is no per-pre-save royalty payment. A pre-save in itself earns nothing. The economic value is downstream: the play that follows the pre-save.
How does a pre-save work in practice?
The standard campaign workflow:
- Two to four weeks before release, generate a pre-save link via a smart-link tool, your distributor’s pre-save service, or a dedicated pre-save platform (Hyppe, Show.co, Feature.fm, Toneden, paid Spotify-Marquee adjacent tools).
- Push the link in artist bio, Instagram link tree, TikTok bio, email newsletter, paid social ads.
- Monitor count as it accumulates. A healthy emerging artist might collect a few hundred to a few thousand pre-saves. A mid-tier artist with active fanbase collects tens of thousands.
- Release day fires automatically. The third-party app calls the DSP API, the track lands in fans’ libraries, the spike happens.
- Pitch editorial with the pre-save count as a “fan demand” data point on Spotify for Artists pitching.
The math of why this matters. A track with a strong first-week velocity is dramatically more likely to land in Release Radar. Release Radar in turn drives organic Discover Weekly seeding. A concentrated pre-save burst is the cheapest way to engineer that velocity.
What pre-save means for indie artists
Three working rules.
Pre-save only works if you actually have a fanbase to pre-save. A pre-save link with 8 signups is a vanity metric. The campaign concept assumes you have an existing email list, social following, or paid-ad budget to drive volume. Without that, a pre-save link is a cosmetic.
Time the campaign launch to your largest reach window. A pre-save link launched the same week as a TikTok trend, a podcast appearance, or a tour announcement converts higher than one launched cold.
Pre-add on Apple Music is undervalued by most indie artists. Spotify pre-save gets all the marketing attention because Spotify is bigger. Apple’s pre-add converts at a higher rate per click because Apple subscribers are higher-intent, and Apple Music editorial weighs first-week velocity heavily for “New Music” feature placement. Run both, link from one shared page.
Common pre-save mistakes and gotchas
- Posting the link too late. A pre-save launched three days before release with no warm-up gets a fraction of the volume of one launched two weeks out.
- Using a pre-save tool with poor DSP support. Some tools claim multi-DSP support but only really function for Spotify, dropping Apple and others. Test the flow end-to-end before promoting.
- Forgetting Apple Music pre-add entirely. A meaningful audience on Apple Music is left out.
- Not switching the link to a post-release smart link automatically. On release day, the same URL should serve a live listening page, not a broken pre-save form. Use a tool that flips automatically. See smart link.
- Treating pre-save count as the success metric. The metric that matters is first-week streams, Release Radar inclusion, and editorial pitch acceptance. Pre-save count is the input, not the output.
- Misrepresenting the auth flow. Some pre-save tools harvest fan email addresses by adding extra opt-ins. That can violate DSP terms and is a sketchy fan experience. Use clean tools.
- Stacking pre-saves with bot-like fan-grow services. DSPs detect inauthentic library activity. The whole release gets demoted.
How InterSpace Distribution handles this
InterSpace Distribution offers a built-in pre-save campaign tool that generates a single link covering Spotify, Apple Music, Deezer, and Boomplay, flips automatically to a live listening page on release day, and surfaces the pre-save count in your release dashboard so you can pitch editorial with the number in hand. Get started at cms.interspacemusic.com/signup.