Guide
Do pre-saves actually work?
Short answer
Pre-saves do something real — they can concentrate streams into the first day of release, which is a signal streaming algorithms respond to — but they convert poorly and cost more than most artists realise. The problem is friction and trust: a pre-save asks a listener to grant a third-party tool permission to modify their music library, before they have heard the song. Many people abandon at the permission screen, and the mechanic depends on platform APIs that change without notice. The deeper issue is what you're left with afterwards: a pre-save gives you a stream on release day and no way to contact that person again. If you are going to ask a listener for something before they've heard the track, asking for an email you keep is usually a better trade than a save you don't.
What a pre-save genuinely does
It front-loads streams into release day. Streaming platforms respond to early velocity, so a cluster of day-one activity can improve how a track is treated algorithmically. That effect is real and it's the honest case for running one.
Where they fall down
The ask is heavy relative to the moment. You're requesting account-level permission from someone who hasn't heard the song yet, and the permission screen itself is where a large share of people quit. Multi-step flows lose people at every step, and any step that depends on a third-party API can degrade when the platform changes its terms.
The part nobody counts
Once the release lands, the pre-save has done its job and left you with nothing durable. You got a save. You cannot message that person about the next release, the tour, or the merch. Everything you gained expires on release day.
A better trade for the same ask
You are asking a listener to do something before they've heard the track. That's a moment of goodwill and it's worth spending on something that persists. Offering an unreleased version, a demo, or early access in exchange for an email gets you a contact you keep and gives them something immediately, rather than a promise that pays off later.
When to run one anyway
If you have an existing audience large enough that day-one velocity meaningfully affects algorithmic placement, and you're already capturing contacts elsewhere, a pre-save is a reasonable addition. The mistake is treating it as the whole campaign when you have no audience to concentrate.
When this isn't the right advice
Plenty of successful campaigns use pre-saves, and dismissing them entirely is as wrong as treating them as mandatory. If you have a real audience and a release worth concentrating, they help. The argument here is narrower: for an artist with a small audience and one thing to ask for, a pre-save is usually the weaker use of that ask.
Find out what you actually own
Paste your Spotify link and get a Fan-Ownership Score: how many of your listeners you could still reach if every platform you use disappeared tomorrow. Free, ten seconds, no account needed.
get your scoreRelated questions
- Do pre-saves help with the Spotify algorithm?
- They can, indirectly, by concentrating streams into release day — early velocity is a signal streaming platforms respond to. The effect depends on having enough people pre-saving to make the concentration meaningful.
- Why do pre-saves have low conversion?
- They ask for account permissions before the listener has heard the song, and the permission screen is a common drop-off point. Multi-step flows compound that at every stage.
- What's better than a pre-save?
- Trading something immediate — an unreleased version, demo, or early access — for an email address. The listener gets value now instead of later, and you get a contact that outlives release day.