Does a remaster, edit, or remix need a new ISRC?
10 · · 11 min read · Español
A straight remaster keeps its ISRC; a remix or an edit always takes a new one. The line between them is creative input: change the recording itself and the version needs its own code, change everything around the recording and it does not. None of that is your distributor’s preference. It is written down — in the ISRC Handbook, with thresholds — and the advice everyone hands out instead, when in doubt get a new one, quietly walks people away from streams they already earned.
- A new ISRC is required when creative input changes the recording itself: remixes, edits, extended versions, live versions, re-recordings.
- A straight remaster keeps its code. Level changes, uniform EQ or compression, and de-noising are not creative input under the ISRC Handbook, even when the result sounds better.
- Length changes carry three rules: a verse or chorus edit always needs a new code; a speed or fade change needs one only at ten seconds or more; trimmed silence never does.
- One recording keeps one code across formats, resolutions, compilations, business models and changes of ownership.
- The song’s code is separate: a new recording of the same song is a new ISRC against the same ISWC.
What decides whether a version needs its own ISRC?
A version needs its own ISRC when it has undergone material change, and the ISRC Handbook measures material change by creative input.
The ISRC Handbook — the standard’s own rulebook, 4th Edition, 2021 — states the test once and then spends an annex applying it:
A key principle to be applied in determining whether there has been material change is whether one recording differs from another because of different creative input. If creative input is responsible for the difference then a new ISRC is required.
Recording, not file. The code identifies the performance that was fixed in the studio — not the container it ships in, the resolution it was bounced at or the store it streams from. Each distinct recording carries one and only one code, a code is never reused, and selling or licensing the recording changes nothing about it.
Hold that test. Every ruling below is the same sentence applied to a different version.
Does a remaster need a new ISRC?
Usually not: a straight remaster keeps the original recording’s ISRC, because a remaster is fundamentally the same recording.
The industry’s own ISRC FAQ answers the exact question — same ISRC for the remastered version? — with yes, generally. The Handbook then draws the boundary tighter than anyone quoting it from memory ever does:
A new ISRC shall be assigned if (and only if) the processes applied to a recording during re-mastering involve the application of creative input to the recording itself.
And it names what does not count as creative input, even when the result is audibly better:
- a simple level change;
- equalisation applied to the whole recording without variation;
- compression applied to the whole recording without variation;
- digital signal processing — de-noising, de-clicking, speed or pitch correction, sample-rate changes, dithering — where the settings stay the same across the whole recording.
The clause closes the loudness argument in six words: “even if the resulting recording is noticeably improved.” Better-sounding is not different. The 24-bit, 96 kHz reissue is the same recording as the CD master, and so is the same master on a compilation, in another territory, under a new owner.
A remaster where someone made creative choices about the recording itself crosses the line and takes a new code. That is the entire exception. Everything else keeping the anniversary edition warm is a transfer, and transfers keep the code.
Does a radio edit or a shortened version need one?
A radio edit needs its own ISRC: a version edited to remove or replace content is a new recording under the ISRC Handbook.
A version that is edited, for example to mute or replace profanities, shall be assigned a new ISRC.
The ten-second rule everyone half-remembers is real — and it is one rule of three:
- Removing or adding sections — a verse, a chorus — always requires a new code, at any difference in length.
- A change that leaves the creative content alone — a speed change, a different fade-out — requires a new code only when the playing time moves by ten seconds or more.
- Adding or removing nothing but silence, ambience or applause never requires a new code, whatever it does to the length.
Memorise the first rule, not the second. The edit that cuts the second verse for radio needs its own code even if it only moves the clock eight seconds. Content decides; the stopwatch only referees the cases where no content changed.
Does a remix need one?
Yes, always: a remixed version differs from the original by creative input, so a remix is a new recording with its own ISRC.
The same family of clauses covers the rest of the versions row. Overdubs are a new code. The extended mix is a new code. The instrumental and the a cappella are new codes the moment they are released on their own. A DJ mix that runs several recordings into one composite is a new recording too — one code for the mix, with the source ISRCs itemised in its metadata.
Who owns a remix is a different question, and the code will not answer it: the Handbook is explicit that assigning an ISRC does not affect ownership in any way. This page decides the code, and stops there.
Which versions need a new ISRC, and which keep the old one?
The table below rules on twenty-seven common versions, each with the Handbook clause that decides it.
| The version | New ISRC? | The rule |
|---|---|---|
| A different encoding or file format | No | Same recording, different container — A.8.1 |
| A high-resolution reissue | No | Same recording at a higher resolution — A.8.2 |
| Sold, streamed or broadcast — a new business model | No | The recording is the same however it is sold — A.8.3 |
| The same recording on a compilation | No | Reuse without change is reuse — A.8.4 |
| A recording licensed in with its code | No | The licensor’s code continues — A.8.5 |
| The catalogue is sold; ownership changes | No | The code outlives the owner — 4.6 |
| An automated up-mix or down-mix | No | No new recording was created — A.14.5 |
| Silence, ambience or applause trimmed or added | No | The length changed; the recording did not — A.10.2 |
| A straight remaster | No | Not creative input, even if it sounds better — A.10.1 |
| A speed or fade change, under ten seconds | No | Below the threshold — A.10.2 |
| A speed or fade change, ten seconds or more | Yes | Over the threshold — A.10.2 |
| A remaster with creative input | Yes | Creative input decides — A.10.1 |
| A verse or chorus edited in or out | Yes | Content changed; no threshold applies — A.10.2 |
| A radio edit or clean edit | Yes | An edited version is a new recording — A.9.4 |
| A remix | Yes | Differs by creative input — A.9.8 |
| A DJ composite mix | Yes | A new recording made of recordings — A.14.4 |
| A live version | Yes | A different performance entirely — A.9.1 |
| A different studio take | Yes | Different takes are different recordings — A.9.3 |
| A re-recording of your own song | Yes | A new take years later is still a new take — A.9.3 |
| A cover | Yes | A different recording by different artists — A.9.5 |
| Added vocals or instruments | Yes | A different version, hence a new code — A.9.9 |
| An extended version | Yes | A different recording — A.9.10 |
| A clip or ringtone | Yes | A different recording, even at fifteen seconds — A.9.11 |
| An instrumental, a cappella or released stem | Yes | A new code once it is released on its own — A.9.14 |
| A new spatial-audio mix | Yes | Each distinct mix carries its own code — A.14.5 |
| A music video | Yes | Never shares the audio recording’s code — A.9.6 |
| A promotional version that differs from the final | Yes | Different content, different code — A.9.2 |
Two rows surprise people, in opposite directions. The Dolby Atmos mix your engineer just delivered is a new recording — every distinct mix is — while the automated up-mix a platform renders from your stereo master is not, because nobody created anything. Creative input, again. It is always creative input.
What the version is called at the stores — where the parentheses go, which words Apple requires and Spotify strips — is formatting, not identity, and it has its own rulebook and its own page. The code answers what the recording is. The version field answers what to print on the shelf.
Does the song get a new code too?
No. The ISWC identifies the musical work, and a new recording of the same song is a new ISRC against the same ISWC.
CISAC, which runs the work identifier, draws the border in one sentence:
The ISWC will not identify recordings, sheet music or any other type of performance associated with the musical work.
So the remix: new ISRC, same ISWC. The cover: new ISRC under the coverer’s prefix, same ISWC. The re-recording: new ISRC, same ISWC. One code follows the recording and the other follows the song, and crossing the pair is how registrations end up pointing at the wrong thing. Which code is which, across the whole alphabet soup, is a piece of its own.
What does an unneeded new code cost you?
A new ISRC starts a new line in every service’s reporting, and the old code’s plays, playlist history and royalty records do not follow it.
No store publishes a policy for reuniting the two lines. The merge, where one happens at all, is a distributor-requested favour a service can decline — fixing an ISRC that is already wrong covers that repair and the order it has to happen in. When one recording ends up under two codes rather than one code under two recordings, the repair is a different one. Prevention is cheaper, and the prevention is the table above.
“When in doubt, assign a new one” is free advice that is only free for the person giving it — the streams that restart at zero are yours. You do not need the doubt. The rule fits in one fucking table, and you just read it.
What if your distributor assigns one automatically?
A distributor is required to use the ISRC the owner assigned: the standard reserves assignment to the recording’s owner or an authorised ISRC manager.
…a party receiving a recording for retailing, distribution, streaming, broadcast etc., shall not assign an ISRC but shall use the ISRC that was assigned by the owner.
Auto-assignment exists for the blank field. Leave the ISRC box empty at upload and the code comes back from the distributor’s own prefix — a code you cannot administer, in a register you cannot see, and one more era of your catalogue identified as somebody else’s paperwork. Getting a prefix of your own is one form and one fee, and it is the whole of what that takes.
So decide the version’s code before delivery, using the table; write it into your own register the day it is assigned; and supply it with the recording, every time. The decision this page exists for should happen once — at your desk, not in a distributor’s default.
FAQ
Does a sped-up or slowed version need its own ISRC?
Yes in practice. A speed change is exempt only while the playing time moves less than ten seconds, and speeding a three-minute track up by a quarter shortens it by 36 seconds.
Does re-recording a song need a new ISRC?
Yes. A re-recording is a different recording even with the same artist and the same arrangement — the Handbook is explicit that different takes are different recordings, whoever is in the room.
Does a clean version need its own code?
Yes. A version edited to mute or replace profanities is the ISRC Handbook’s own example of an edit that requires a new ISRC.
Can the same recording end up with two ISRCs?
Through error, yes — and the two codes split the recording’s streams and reporting between them. Which code survives, and what the standard requires you to do about it, is covered in two ISRCs on one recording.
Sources
- IFPI, ISRC Handbook, 4th Edition (2021) — the annex this piece keeps quoting: material change (A.7), remastering (A.10.1), playing time (A.10.2), the never-required list (A.8) and the always-required list (A.9). Every clause code in the decision table links to its page in the PDF.
- IFPI, ISRC FAQ — remasters keep their code; the changes that require a new one; a code is never reused and survives a change of ownership.
- CISAC, The ISWC — the work identifier defined, with recordings excluded in so many words.
The Handbook and the FAQ are the standard’s own documents, quoted verbatim above and current as of the date on this page. Distributor upload flows differ in how the ISRC field behaves; confirm yours before delivery. None of this is legal advice.
Keeping the register
Version, recording type, ISRC, ISWC — CatalogTracker keeps them as fields on the track itself, and search reads the identifiers directly: type a code and the result says which identifier matched. The decision this page walks through gets recorded where the next delivery will find it. In development for iPhone.