What Is an ISRC Code, and Does Your Song Need One?
Published October 8, 2026
The short answer. An ISRC (International Standard Recording Code) is a 12-character ID for one specific recording. You almost certainly need one to release music, but you rarely have to make it yourself: a distributor usually assigns it. What matters is that a recording keeps the same code for life.
What an ISRC is
An ISRC is a code that names one recording. Not one song in the abstract, not one album: one recording of it, the specific take you finished in the studio. The International ISRC Registration Authority, which sits inside the trade body IFPI, publishes the rules in its ISRC Handbook (4th Edition, 2021). The handbook puts it plainly: the code identifies "the recording not the encoding of the recording."
That has a practical meaning. The same recording as an MP3, an AAC file, a high-resolution file, a streaming copy or a download carries the same ISRC. The handbook says so directly: the recording is the same "whether it is sold, licensed, streamed or broadcast." A CD or an MP3 file is not itself a recording, so it never gets an ISRC. The audio on it does.
What the 12 characters mean
The handbook's example is AA6Q72000047, written for people as ISRC AA-6Q7-20-00047. It breaks into three parts:
| Part | Length | What it is |
|---|---|---|
| Prefix | 5 characters | Two letters and three letters or digits. It identifies who is allowed to assign codes. Older prefixes carried a country code; newer ones are one block of five. |
| Year of reference | 2 digits | The year the code was assigned, such as 20 for 2020. Per the handbook it is not a reliable recording date. |
| Designation | 5 digits | A running number the prefix holder picks, padded with zeros, such as 00047. |
Do not read meaning into the digits. The code is a label, not a description. The year can differ from the year you recorded the song, and the handbook tells holders to keep the recording year in the metadata, not in the code.
Is an ISRC the same as an ISWC or a UPC?
No, and mixing them up is common. The Mechanical Licensing Collective, which collects US mechanical royalties, explains the split on its page about ISWC and ISRC codes. An ISWC identifies the underlying song, the composition, and stays the same across every recording of it. An ISRC identifies a recording, so a song recorded three ways has one ISWC and three ISRCs. An ISWC is 11 characters; an ISRC is 12.
The MLC's own example makes the point: it gives "Yesterday" by The Beatles one ISRC and Elvis Presley's 1969 recording of the same song a different one, while both share a single ISWC. A UPC or similar barcode identifies a product, such as an album release. The handbook itself notes that when you need to tell one release from another, you use product identifiers, which sit outside the ISRC system.
Who issues ISRCs, and do you need your own?
Codes are assigned by the owner of a recording or by someone authorised as an ISRC manager, under a prefix that a national agency has allocated to them. In the United States the agency is run by the Recording Industry Association of America. Its site, usisrc.org, describes a one-time fee of $95 for a rights owner prefix, with no further costs listed (checked October 2026; confirm before you pay, as fees change). Other countries have their own agencies and their own terms.
Most independent artists never pay that. The MLC says independent artists without a label typically get an ISRC from an authorised ISRC manager such as a music distributor. In practice you upload your track, and the code comes attached. If you plan to self-release, the question to put to your distributor is simple:
- Do you assign the ISRC for the track, and can the artist see it before the release goes live?
- Can an artist supply a code that already exists, for a track released before?
- If an artist leaves, will you hand over a list of every code you assigned to their tracks?
The answers differ by distributor and by plan, and they change. Read your distributor's current help pages before you decide. Owning your own prefix makes sense mainly if you run a label or release at volume, because it gives you one set of codes that stays with you whichever service you use. It does not change who owns the recording. The handbook is explicit that using a prefix "does not imply that the assigning party owns the recording, or that royalties are to be paid to them."
When does a recording need a new ISRC?
The governing idea in the handbook is creative input. If two recordings differ because someone made creative choices, they get different codes. If they differ only because of technical handling, they share one. The handbook states it as a rule: a recording "shall have exactly one ISRC," and a recording that has one "shall not have another ISRC assigned to it, even if ownership changes or it is licensed." IFPI's "when to assign" page adds the short version: any new or materially changed recording needs a new ISRC.
The handbook's Annex A sorts the common cases. This table follows it.
| What you do | New ISRC? | Handbook reasoning |
|---|---|---|
| Export the same master as MP3, AAC or high-resolution | No | Encoding is not the recording (A.8.1, A.8.2). |
| Put the track on a compilation, unchanged | No | Same code on every release it appears on (A.8.4). |
| Sell or license the unchanged recording to someone else | No | The code stays; the new owner is told what it is (4.6). |
| Release a live version of a studio song | Yes | A different recording (A.9.1). |
| Use a different studio take, even with the same players | Yes | Different takes are different recordings (A.9.3). |
| Make a clean edit that mutes or replaces profanity | Yes | An edited version (A.9.4). |
| Cut a verse or chorus, or add one | Yes | Length change that affects the content (A.10.2). |
| Change length by a speed shift or a longer fade | Only if the length differs by 10 seconds or more | Under 10 seconds, no; otherwise yes (A.10.2). |
| Record a cover of someone else's song | Yes, in your name as the new recording | A different recording of a work (A.9.5). |
| Release a music video | Yes, separate from the audio | A video is not the audio recording (A.9.6). |
Remasters are the case artists ask about most. The handbook says a remaster gets a new ISRC "if (and only if)" creative input is applied to the recording itself. It names processes that do not count as creative input: a simple level change, equalisation applied to the whole recording without variation, compression applied to the whole recording without variation, and digital clean-up such as de-noising or de-clicking where the settings stay fixed across the file, "even if the resulting recording is noticeably improved." A remaster where the settings change from one part of the recording to another is on the other side of that line. Where your case is borderline, the handbook says consistency between registrants matters and invites judgment; ask your distributor how they treat it, or write to IFPI's ISRC team.
What goes wrong when a song gets a second code
The handbook's rule is that one recording has exactly one code. Break that rule and you have two identifiers for the same audio. The handbook describes the code as the thing partners use to credit the right party for a use, and it expects partners to adjust their records when a recording changes hands under its unchanged code. Anything that counts or credits by code will see two recordings where there is one. That is our reading of the rule, not a figure from the handbook: the handbook does not discuss streaming totals.
The usual way it happens is a switch or a re-upload. You leave one distributor, upload the same master to another, and the new one issues a fresh code because you did not hand over the old one. The handbook does allow for fixing mistakes: it says a second code "may be permissible" where errors have been made and recovery needs it, and that two distinct recordings sharing one code should be split. But it treats a duplicate as an error to repair, not a normal step. Avoid creating one in the first place:
- Before you leave a distributor, export the list of ISRCs for every track you released.
- At the new distributor, look for the field that lets you enter an existing ISRC, and use it for every track that has already been out.
- Enter the codes before you submit the release, not after.
- Keep the list in a spreadsheet with the track title, version, release date and the code. It takes ten minutes and saves a long email thread later.
The same habit helps with the other direction: do not reuse a code for a different recording. The handbook says a code, once assigned, must never be assigned to another recording. If your remix shares the original's code because a form auto-filled it, change it.
Where the code gets used
Roughly, the ISRC rides along in the metadata of your release so that services, collecting societies and fingerprinting systems can name the exact recording. The handbook recommends that when recordings go to audio fingerprinting services, the ISRC should be part of the metadata supplied. It also says plainly that assigning a code is not the same as registering a copyright. A code does not protect you; it labels you.
Two further notes. First, the handbook says the ISRC system is voluntary unless a contract or a local rule requires it. Your distribution contract may require one, so check its terms. Second, the handbook says a code should be assigned if the owner intends to exploit the recording, and adds that exploitation need not mean money: it can involve reputation, promotion or exposure. A free release counts.
A quick checklist before you release
- One code per finished recording. A radio edit, an extended mix and a live take each get their own.
- Same master, new format: same code.
- Write the code down the moment you have it, next to the exact version it belongs to.
- Moving distributors: take your codes with you.
- Releasing a video: it needs a code of its own, and its metadata should point to the audio's code.
If you are still choosing a route to release, our guide to how independent artists get streams without a label covers the wider picture, and what happens when you submit a song here shows what a person checks at our end. Artists can submit at /for-artists/.
This is general information about how a metadata standard works, not legal or business advice. If a contract or a dispute turns on who owns a recording, ask a music lawyer, or a musicians' or songwriters' organisation in your country.
Send us your music
Submit a song to Life of Art and a person listens to it. If it runs, you see how many listeners it reached and what share of them liked it. See how submitting works.