What the Music Industry is Getting Wrong About the End of Pre-Saves

When Spotify announced in June that authorizations for third-party apps would start expiring, a wave of commentary across the music industry reached the same verdict: pre-saves are finished. Some of it came from industry leaders, and much of it sounded less like alarm than relief. Pre-saves never converted anyway, the sentiment went, and the token change simply made it official. A technical policy change about how long a login stays valid produced that reaction instead of a shrug and a changelog entry, and that's worth looking at closely.

The change has no effect on nearly every pre-save campaign artists actually run, and the "pre-saves are dead" reaction says more about the platforms voicing it than about the feature. You'll be able to check in about a minute whether your next pre-save campaign is affected at all, and you'll see why a well-built pre-save matters more now than it did before the change.

Six months is longer than almost any pre-save campaign needs

What the six-month clock actually measures

Start with what Spotify changed. Since July 20, 2026 for established apps, a fan's Spotify authorization expires six months after they first grant it, and refreshing it in the background doesn't reset the clock. Once the six months are up, the fan has to sign in again.

Now look at what a pre-save needs that authorization for. A fan connects their Spotify account when they pre-save, and the save happens on release day. The authorization only has to last between those two moments. Singles typically open a pre-save a few weeks out. Album campaigns commonly open at announcement, three to four months before release day. Both fit inside six months with room to spare, and the math holds for every fan, because each fan's six months starts when that fan connects. The earliest fan to pre-save is the only one whose window could run short, and on a four-month album campaign, even that fan still has two months left when the album comes out.

Three campaigns, one release day

Say you're planning a release for Friday, May 14, 2027. Here's how three different runways would line up against the rule:

Suppose the four-month album campaign collects 2,000 pre-saves. The first fan connects on January 14 and stays authorized until July 14, two months after release. Every fan who follows has even more room. All 2,000 saves go through on May 14, and nothing about the campaign had to change. Only the seven-month campaign crosses the line, and only for the fans who pre-saved in its first month; they'd need a reminder to pre-save again before their authorizations lapse in mid-April. The full breakdown of Spotify's token expiration rule walks through that case date by date.

So any claim that pre-saves are dead because of the six-month expiration rests on campaigns that open more than half a year before release day. That's a timeline problem with a simple fix: open the pre-save later, or plan a second touchpoint for your earliest fans. A single-release pre-save that needs to stay authorized for longer than six months is being used in a way the feature was never designed for.

The one setup the rule does affect

There is one pattern the change genuinely touches: features that ask a fan to authorize once and then save every future release, relying on that single authorization to last indefinitely. Spotify says it wants app access to stay relevant and intentional, which means authorizations get re-confirmed on a regular schedule. A design that never goes back to the fan needs an answer for what happens when the authorization expires. Sonikit's system handles expired authorizations for NextSave, so artists using it don't have to track who connected when. For the wider picture, here's why future-save style features are exposed to the six-month limit. That's a design question for one category of feature. It says nothing about whether a pre-save for next month's single still works.

Why the timing of the reaction is the tell

A feature doesn't get declared dead the week its underlying mechanism gets slightly harder to maintain unless it was already on shaky ground. If pre-saves genuinely drove no value, that would have been true in 2023, in 2024, and in 2025, not only in the week Spotify tightened a token policy. The value of a pre-save to an artist didn't change that week. The cost of keeping the feature working did, and that cost landed on teams that had already deprioritized it.

What "pre-saves don't convert" usually means

When the complaint is that pre-saves don't convert, the honest follow-up is: convert into what, and measured how? If the only thing being tracked is stream count on release day, a pre-save was never going to look impressive, because that was never its whole job. A pre-save's value shows up in a different column: fan contact details collected before the release exists, and an audience of pre-savers you can retarget with ads once it's out. A platform that never built the tooling to capture or use that data would see a pre-save that looks like it did nothing. The feature didn't fail there; half of it was never built. That's the core of the case that a pre-save's real value is the data, not the stream.

The strongest case for walking away, and why it falls short

The case against pre-saves deserves a fair hearing. As a category, they're overhyped. Too much of the industry treats a pre-save button as the whole release strategy instead of one input into a bigger fan relationship. A big pre-save count can still say little about who will actually listen, and for a platform, keeping Spotify integrations working through every policy change is real, ongoing engineering work. If your pre-save feature was never much more than a button, stepping back from it is a defensible call.

All of that is fair. None of it adds up to "pre-saves are dead," though. It points toward building pre-saves better: capturing a way to reach the fan alongside the save, supporting more than one streaming service, and giving artists something to do with the data afterward.

You also need to consider the fact that there's nothing "magical" about a pre-save that collects data. You can collect data with an artist follow button, an album or track save button, even an Instagram automation. The point is capturing data when fans are engaged. Not a tool that magically does something profound.

What's more likely happening is that some platforms with weak pre-save implementations (ones that never captured fan data well and leaned heavily on a single service) are using the announcement as cover to deprioritize a feature they were already struggling to support. That's a legitimate business decision for them. It isn't a fact about the feature.

Why the pullback is an opening for artists who keep pre-saves

Every platform that steps back from pre-saves cedes ground on a feature that, done well, still does what it always did: identify high-intent fans before a release and hand you the data to act on it. The token change doesn't touch that value on a normal release timeline. It only exposes one design pattern, silent indefinite authorization, that was always going to need a better answer eventually. Treating that as a reason to give up on the feature is a business conclusion dressed up as a technical one.

This holds if you run single or album campaigns with a runway under six months, which covers the way most artists release music. It holds with one extra step if you announce albums more than six months out: your earliest fans will need a reminder to pre-save again. The setup worth questioning is a tool that saves every future release from a single sign-in and has no plan for what happens when that sign-in expires.

What to check before your next release

1. Count back six months from release day. If your pre-save opens after that date, every fan who pre-saves is covered and nothing about your campaign needs to change.
2. Collect a way to reach fans alongside the pre-save. An email address or phone number, gathered with consent, lets you remind early fans if your runway runs long and reach everyone on release day. Here's how to collect emails and phone numbers with your streaming pre-save.
3. Ask how your tool handles an expired authorization. The answer you want is that it catches the expiry instead of letting the save fail silently. These questions to ask any pre-save tool after Spotify's API change cover the rest of what to check.

Start with step 1 today. It takes a minute with your release calendar, and for most campaigns it's the only step you'll need.