How to Re-Release Old Music Without Losing Spotify Plays
Re-release music after deciding whether you are moving the same recording or issuing a changed version. For the same audio, preserve its ISRC and align the title, artist name, and duration so Spotify can track-link play counts. Verify before removing the old delivery. Re-releases already on Spotify are not eligible for Release Radar simply because they are delivered again.
Lead visual
Catalog value starts with an audit
metadata
review before you spend on the next move
rights
review before you spend on the next move
performance
review before you spend on the next move
opportunities
review before you spend on the next move
Catalog · Strategy
Catalog asset map
Decision
Treat old releases as assets with data, rights, and revenue paths that can be improved.
Evidence
Metadata, registrations, ownership, performance history, licensing readiness, and missing money.
Risk
Catalog value stays hidden when the underlying records are incomplete or outdated.
Good outcome
A better-maintained catalog that can earn, license, and explain itself.
Key takeaways
- Decide whether the asset is the same recording before assigning identifiers.
- Reuse the existing ISRC for the same recording and align Spotify's documented matching metadata.
- A remaster does not automatically require a new ISRC; significant new creative input can change the answer.
- Verify track-linking and every required store before removing the old delivery.
- Spotify excludes re-releases already on the service from Release Radar.
When should an old recording keep its ISRC?
| Usually keep the existing ISRC | Review whether a new ISRC is required | |
|---|---|---|
| New product | The unchanged recording appears on a compilation, album, licence, stream, download, or later issue | The recording itself was edited, remixed, re-recorded, or materially changed |
| Resolution | A high-resolution and standard-resolution version represent the same recording | The change includes significant new creative input beyond a technical format difference |
| Remaster | The remaster remains fundamentally the same recording under IFPI guidance | Creative changes make the resulting remaster a materially distinct recording |
| Live or remix | Not applicable when the performance or mix is genuinely different | A live version, remix, edit, or other distinct recording normally needs its own code |
ISRC identifies the recording, not the release package
A single, album, compilation, and distributor delivery can have different product identifiers while an unchanged recording keeps the same ISRC.
How do you preserve Spotify play counts during a re-upload?
Same-recording migration
Five checks before the old takedown
- 01
Check 1
Authority
Confirm the master owner, current delivery control, contract exit, takedown rights, and target distributor.
- 02
Check 2
Identity
Preserve the ISRC and align the audio, duration, title, artist name, credits, and release lineage.
- 03
Check 3
Delivery
Submit through the new distributor and retain identifiers, timestamps, destination selections, and support receipts.
- 04
Check 4
Link
Use Spotify's desktop play-count check and verify the intended artist, release, audio, and metadata at other stores.
- 05
Check 5
Takedown
Remove the old delivery only after required links and destinations are verified and the rollback path is recorded.
What does Spotify track-linking preserve?
Spotify says track-linking can keep the play count when re-uploaded music has the same audio and matching metadata, including duration, title, and artist name. It tells artists to confirm the link by checking that the play counts match in the desktop app. That is a verification step, not a guarantee that unrelated store objects or every user context will migrate.
Keep a destination checklist for play counts, artist mapping, audio, credits, product pages, playlists, saves, links, territories, availability, and statement reporting. Separate what the platform documents from what the migration actually preserves for this release.
Can an old song become new to Release Radar again?
Spotify explicitly excludes re-releases of songs already on Spotify from Release Radar. The service can include a song for up to four weeks when an eligible listener has not heard it, but redelivery does not restart that clock. Plan a re-release around catalogue access, corrected delivery, packaging, or a genuinely distinct version, not a promised second first-week placement.
build the identifier and metadata comparison before submitting or removing a delivery
Which primary sources define re-release and ISRC rules?
Frequently asked questions
Should I reuse the ISRC when re-releasing a song?+
Reuse the existing ISRC when it is the same recording. IFPI says an ISRC should not be assigned again to a recording that already has one, and unchanged uses on later products keep the code. A remix, edit, live recording, or other materially changed recording may need a new ISRC. Confirm edge cases against the current ISRC Handbook and the responsible registration agency.
Does a remaster always need a new ISRC?+
No. IFPI says a remaster can generally keep the original ISRC because it remains fundamentally the same recording. A new code becomes appropriate when the remaster includes significant new creative input, and the Handbook gives more detailed cases. Do not assign a new ISRC merely because resolution changed. Document the audio change and ask the registration agency when the boundary is unclear.
Will Spotify preserve streams after a re-upload?+
Spotify says track-linking can preserve the play count when the old and new audio and metadata match, including duration, title, and artist name. Verify the result in the desktop app by checking that play counts match. Spotify does not promise that every playlist, save, recommendation, URL, or store outside Spotify will transfer, so keep both deliveries live until each required destination is checked.
Can a re-release enter Spotify Release Radar again?+
Spotify says it does not include re-releases of songs already on Spotify in Release Radar. Delivering the same recording again or changing its product packaging does not create a new eligibility promise. Some genuinely different versions have separate rules, and Spotify lists exclusions for certain acoustic, karaoke, and live versions while saying remixes can be included. Check the current Release Radar page before scheduling.
Should I delete the old release before uploading the replacement?+
Usually verify the replacement first. Ask the current and new distributors for their migration sequence, deliver the same recording with its existing identifiers and matching metadata, wait for the stores to process it, confirm Spotify track-linking and other destination behaviour, and only then schedule the old takedown. Overlap, timing, edits, and takedown control vary by distributor and store, so preserve every receipt.
Get better release strategy in your inbox
Release planning checklists, royalty explainers, and artist strategy notes from Velveteen. No daily noise.
Was this useful? Send a signal or flag a correction.
Keep reading
Pillar guide
Catalog strategy guide
A transparent catalog-control and valuation workflow covering rights scope, revenue evidence, risk, comparables, and decision-ready assumptions.
Related guide
PRO registration
How to register back-catalog tracks with SOCAN, ASCAP, or BMI, including what happens to performance royalties already earned before you registered.
Related guide
Copyright registration
What copyright registration actually requires from musicians in Canada versus the US, including the US deposit rule, the lawsuit prerequisite, and what both systems protect.
Related guide
Switch without losing streams
Keep your original ISRCs and audio file, upload through the new distributor, then leave the old release live for 48 to 72 hours so Spotify's track-linking can merge the two.
Related guide
What is an ISRC
What an ISRC code is: the 12-character ID for one recording, why a remix needs a new one, and how to carry it across distributors so you don't split your streams.
Check your metadata before your distributor does
Run your titles, credits, copyright lines, and ISRC and UPC codes through the free checker and catch the rejection-bait errors before you upload. It all runs in your browser.