Are Pre-Saves Dead? What Spotify's New Token Expiration Rule Actually Means
On June 18, 2026, Spotify announced that refresh tokens issued to third-party apps now expire six months after a user's original authorization. The rule applied to newly registered apps right away and to existing apps, which includes established pre-save tools, from July 20, 2026. Refreshing a token doesn't reset the clock. Once the six months pass, the fan has to sign in to Spotify and authorize the app again.
That announcement set off a run of posts declaring pre-saves dead. For the way most artists run a pre-save campaign for a single release, very little changed. The rule does matter in two specific situations: a pre-save that opens more than six months before release day, and features that save every future release automatically. By the end of this post you'll know whether your own timeline crosses the six-month line and what to do before your next release if it does.
What Spotify changed, at a glance
Here's the change in one place, drawn from Spotify's announcement and its FAQ.
| What changed | When it applies | When it affects your campaign |
|---|---|---|
| A fan's Spotify authorization expires six months after they first grant it | New apps: June 18, 2026. Existing apps: July 20, 2026 | Release day falls more than six months after a fan pre-saved |
| Refreshing the token no longer extends the authorization | Same dates as above | Your tool relies on one authorization to keep saving releases over time |
| Authorizations already older than six months stop working on their next use | Existing apps, from July 20, 2026 | Fans who connected before January 20, 2026 through a feature that saves future releases |
| A fan who re-authorizes keeps the same permissions and starts a new six-month window | Ongoing | Any fan you ask to reconnect |
Who isn't affected: a fan who pre-saves a release that comes out less than six months after they connected. A pre-save opened weeks, or even a few months, before release day sits comfortably inside that window.
Why a standard pre-save keeps working
When a fan pre-saves, they connect their Spotify account and give permission for the release to be saved. On release day, the tool adds it to their library without the fan doing anything else. That's how pre-saves work in Sonikit, and most pre-save tools follow the same basic pattern. The permission only has to last from the moment the fan connects until release day.
Spotify measures its six-month limit from that first connection. So the question for any single release comes down to one comparison: is release day less than six months after your earliest pre-save? If it is, every fan's authorization is still valid when the save happens, and nothing about your campaign needs to change.
Worked example: check your own release timeline
The dates and fan counts below are an illustration to show the math, not Sonikit data or a typical result.
A single with a 10-week runway
Say you open a pre-save for a single on March 1, 2027, and set release day for May 14, 2027, about 10 weeks later. Over that stretch, 1,200 fans pre-save. Your earliest fan connected on March 1, so their authorization runs until September 1, 2027. Release day lands three and a half months before that. All 1,200 saves go through, and the six-month rule never comes into play.
An album announced seven months out
Now say you announce an album on October 9, 2026, open the pre-save that night, and set release day for May 14, 2027, roughly seven months away. Of the same 1,200 fans, suppose 300 pre-save in the first two weeks (October 9 to October 23). Their authorizations expire between April 9 and April 23, 2027, which is three to five weeks before the album comes out. Everyone who connected on or after November 14, 2026 is still covered on release day.
Those 300 fans can still get the album saved, but only if they sign in again before release day, and they'll only do that if you reach them first. That's the practical version of this rule for single-release campaigns: a runway longer than six months needs a second touchpoint for your earliest fans.
Where the rule really bites: saves that carry forward to future releases
Some tools offer a subscribe-once option: a fan opts in a single time, and every future release from that artist is saved to their library automatically. These features depend on one authorization lasting across many releases, which is exactly what Spotify has now capped. No single authorization can cover more than six months of releases. According to Spotify's FAQ, authorizations that were already older than six months stopped working the next time they were used after enforcement began.
In dates: for an established tool, any fan who subscribed before January 20, 2026 has to reconnect before the next automatic save can go through. Every subscriber after that needs to reauthorize at least once every six months to keep receiving saves.
Spotify's stated reason shows where this is heading. It wants apps to keep access only while that access still reflects what the user intends, which means authorizations get re-confirmed on a regular basis. Features built on a fan never being asked again work against that. Features that go back to the fan when a new release is ready fit it. For a closer look at this model, see why future-save style features are exposed to the six-month limit.
How Sonikit handles it
Standard pre-saves in Sonikit follow the same six-month math as any other tool, so the timeline check below applies to your single-release campaigns too. For saves that carry forward, NextSave keeps new releases reaching your subscribers and handles expired Spotify authorizations for you. You don't need to track when each subscriber connected or chase anyone to reconnect.
What to do before your next release
Work through these in order. If step 1 shows your campaign sits inside the six-month window, you can skip step 3.
- Count back six months from release day. Find the date exactly six months before your next release. If your pre-save opens after that date, every fan who pre-saves is covered.
- Collect a way to reach fans alongside the pre-save. Ask for an email address or phone number, with consent, as part of the same step. Without it, you have no way to contact early fans whose authorization lapses. Sonikit's guide to collecting and using fan data from pre-saves walks through the setup.
- Plan a reminder if your runway runs past six months. A few weeks before your earliest fans' authorizations expire, message the fans who pre-saved before your cutoff date and ask them to pre-save again, which re-authorizes them for a fresh six months. In the album example, that means messaging the 300 October fans in mid-March, ahead of their April 9 to April 23 expiry dates.
- Ask your pre-save tool how it handles a lapsed authorization. The answer you want is that it detects the expired authorization and prompts the fan to reconnect, rather than 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.
- Send a release-day message either way. A text or email on release day with a direct link to the release reaches fans whose authorization lapsed and reminds everyone else to listen. If fans have opted in to texts, you can send release-day texts from the same place you run the pre-save.
Start with step 1 today. It takes a minute with your release calendar and tells you whether the reminder step applies to you at all. If you'd rather reduce how much your campaign depends on a Spotify login in the first place, these pre-save alternatives that still capture fan data are the next thing to read.
