Re-Release, Remaster, or Re-Promote an Older Song?
Choose between promoting the existing recording, remastering it, or creating a distinct release by auditing the audience problem, audio change, rights, identifiers, and catalog risk.
The short answer
Re-promote the existing release when the recording is strong and the problem is awareness, context, links, profiles, or campaign execution. Remaster when the same fundamental recording has a documented technical or format problem that mastering can solve. Re-release only when a distinct product, version, audience event, rights change, or campaign reason justifies new delivery. Compare the audio change, original metadata, identifier treatment, platform linking, rights, distributor process, duplicate risk, fan confusion, cost, and evidence that a new product is more useful than a better campaign for the existing one.
Three things to know
- 01
Fix an awareness problem with re-promotion, an appropriate technical problem with remastering, and a genuinely distinct product or event with re-release architecture.
- 02
Do not assume a new upload preserves play counts or history; Spotify requires matching audio and metadata for track-linking, and every platform controls its own behavior.
- 03
Audit recording identity, ISRC guidance, original date, rights, files, distributor workflow, links, duplicates, and customer value before creating another catalog entry.
Which older-song strategy fits the problem?
Choose the smallest accurate intervention that creates real listener value and preserves a coherent catalog.
Re-promote existing release
Creates a fresh campaign, story, asset, audience path, or live context around the same product and approved recording.
- What must stay controlled
- Current identifiers, original date, links, saves, playlists, credits, availability, source baseline, truthful framing, and campaign evidence.
- Primary risk
- The new campaign repeats old creative without a meaningful reason, or misrepresents an existing song as newly released.
- Choose when
- The recording and product are healthy, while awareness, context, assets, targeting, or follow-up was weak.
Remaster same recording
Creates an appropriate technical master from the same fundamental recording for a documented sonic, restoration, or format need.
- What must stay controlled
- Archive lineage, approved mix, mastering notes, comparisons, rights, accurate label, identifiers, original date, distributor path, and platform checks.
- Primary risk
- A subjective louder version, hidden new mix, unnecessary duplicate, failed track link, or unsupported claim fragments the catalog.
- Choose when
- A real technical problem or edition requirement can be solved without changing the recording's creative identity.
Distinct re-release
Delivers a meaningfully different recording, version, language, edition, territory, package, track list, or audience event.
- What must stay controlled
- Version label, new and old roles, rights, identifiers, artwork, metadata, availability, linking, original dates, product value, and removal decision.
- Primary risk
- Near-identical products split listeners, search, links, reporting, editorial context, and fan understanding without adding value.
- Choose when
- The new product is genuinely distinguishable and its campaign reason cannot be served by promoting the existing release.
What problem is the older song actually facing?
Separate song quality, recording quality, awareness, discoverability, audience context, broken metadata, profile mapping, unavailable territories, rights restrictions, weak artwork, poor campaign assets, outdated links, or a genuine creative opportunity. Listen to the current platform file and compare it with the approved archive. Review audience source, saves, repeat behavior, search, Shazams, playlists, fan messages, live response, licensing interest, and past campaign activity without assuming low totals mean weak music. A recording with good fan response but little exposure usually needs a campaign. A damaged or inappropriate master may need technical work. A new performance, remix, language version, anniversary edition, or physical product may justify a distinct release. Write the problem before selecting the solution.
When is re-promotion the strongest option?
Choose re-promotion when the current recording, metadata, rights, availability, and listener experience are sound. Build a fresh reason to care: a new live moment, video, lyric story, creator format, sync use, press angle, catalog connection, tour date, seasonal context, fan milestone, or relationship to a new release. Update the artist profile, landing page, canvases or clips where supported, email, short-form assets, press materials, and links without pretending the song is newly released. Preserve the existing product, identifiers, saves, playlists, comments, and links. Measure new source activity and fan actions against a baseline. Re-promotion is not a lesser option; it is often the only choice that directly addresses an attention problem without fragmenting the catalog.
When does a remaster solve a real problem?
Remaster when the original mix is fundamentally retained but the delivered master has correctable translation, level, tonal, noise, sequencing, restoration, or format issues, or when a properly supervised archival or physical edition needs a new technical master. Compare the archive, mix, current file, proposed chain, references, platform normalization, mono behavior, artifacts, dynamics, start and end, and listener context. Use a qualified mastering engineer and approve blind or level-matched comparisons. Do not call a new mix, edit, restored performance with creative reconstruction, stem balance change, or rerecording a remaster merely to make it seem canonical. The benefit must remain audible and appropriate after platform processing, and the marketing claim should describe the actual work rather than declaring universal improvement.
When does a distinct re-release make sense?
Use a distinct release when the buyer or listener receives a genuinely different product or event: a new recording, remix, edit, language version, acoustic or live performance, expanded anniversary edition, newly cleared territory, restored catalog edition, physical package, soundtrack context, or a coordinated campaign that cannot be represented by updating the existing product. Define whether the old version remains available, how titles and version labels distinguish them, what the new artwork and track list communicate, and why fans should choose each. Avoid repeated submissions with near-identical audio and superficial title changes. Apple currently warns against duplicate versions of the same content with slightly changed metadata, and redundant products can split search, editorial context, links, reporting, and listener understanding.
How should ISRC and product identifiers be handled?
Identify whether the audio is the same recording, a fundamentally unchanged remaster, or a recording with creative or duration changes. IFPI's current ISRC FAQ says a remaster can generally retain the ISRC when it remains fundamentally the same recording, while creative restoration, changes exceeding its specified duration threshold, remixes, and edits require new treatment under its guidance. Do not copy an identifier simply to preserve numbers or assign a new one merely to create novelty. Confirm the exact audio and product architecture with the ISRC manager, distributor, label, rights owner, and current platform rules. A release product also needs appropriate product-level identifiers and original-release information. This is educational, not legal advice; ownership, contracts, registrations, and catalog representations need qualified review.
How can play counts, links, and catalog history be protected?
Spotify currently says re-uploaded tracks can use track-linking only when old and new audio and metadata are the same, including duration, title, and artist name; matching play counts in the desktop app verifies the link. That condition does not fit a materially different recording and does not promise equivalent behavior elsewhere. Preserve the current URLs, screenshots, identifiers, metadata, files, saves, playlists, credits, lyrics, claims, and reporting before any delivery change. Ask the distributor for its migration sequence and do not take down the old product until the new one is live, mapped, checked, and the plan calls for removal. Test every service independently. A failed link, split profile, lost territory, wrong date, or duplicate can be harder to repair after campaign launch.
How should the three options be compared and approved?
Build a one-page decision record with the problem, audience evidence, current product health, proposed audio change, rights, identifiers, original date, platform treatment, distributor steps, campaign story, assets, cost, timing, downside, reversibility, and expected learning. Score whether each option directly solves the problem. Re-promotion usually has the lowest catalog risk; remastering adds technical and delivery risk; a distinct release adds product, rights, metadata, and audience complexity. Obtain artist, master-owner, publisher, producer, featured-artist, archive, label, distributor, and legal approvals required by the agreements. Keep the old version available unless a documented rights, quality, strategy, or safety reason supports removal. No option assures renewed streams or editorial attention.
What supports this three-option decision?
Practical notes
- Spotify says track-linking depends on matching old and new audio and metadata, including duration, title, and artist name.
- IFPI distinguishes fundamentally unchanged remasters from significant creative changes, edits, remixes, and specified duration changes in its ISRC guidance.
Source notes
- Spotify for Artists Support: Re-uploading music, accessed July 18, 2026.
- IFPI International ISRC Agency: FAQ questions 7 and 8, accessed July 18, 2026.
Frequently asked questions
- Does an old song need a new release date to be promoted again?
- No. A truthful new campaign, video, live moment, story, or catalog connection can reintroduce the existing release without changing its date.
- Will a remaster keep the original Spotify play count?
- Do not assume so. Spotify's track-linking guidance requires the old and new audio and metadata to match, so verify the actual delivery and result.
- Does every remaster need a new ISRC?
- IFPI says a fundamentally unchanged remaster can generally retain the identifier, while significant creative changes can require different treatment; verify the case.
- Should the original version be removed after a re-release?
- Usually preserve it unless rights, quality, safety, or a documented catalog strategy supports removal and every dependency has been reviewed.
- Can an artist call a new mix a remaster?
- No. A new mix changes the balance or creative construction and should be labeled accurately rather than presented as mastering alone.