Does your AI song need an ISRC code, and where do you get one?

ISRC AA-6Q7-20-00047

AA6Q7   prefix code        5 characters, allocated to whoever assigns the code
20      year of reference  the year the code was assigned, not the year you made the track
00047   designation code   5 digits, picked by the assigner from its own range

That is the made-up example the official ISRC Handbook uses to explain the format, and the handbook says plainly that nobody should ever use it on a real release. Twelve characters, no spaces. The word "ISRC" and the hyphens are only there for human eyes and are not part of the code.

The short answer to the title: if your AI song is going to a streaming service or a download store through a distributor, it needs an ISRC, and in most cases the distributor issues one for you during the upload. You can also get codes from the ISRC agency in your country or, as a self-releasing artist, through an online assignment service run by the international ISRC agency. How the track was made does not change the code or who can assign it. What AI changes is something quieter: how many different recordings you end up with, and that is where people get the code wrong.

What the code identifies, and what it does not

An ISRC (International Standard Recording Code, defined by the standard ISO 3901) identifies a recording. Not a song, not an album, not a file. The handbook is precise about this: the same recording as MP3 and as AAC carries one code, because the code belongs to what the listener hears, not to the container it arrives in. A CD or an MP3 file never gets an ISRC; the recording inside it does.

The song itself, meaning the words and the melody as a written work, sits in a separate system. Musical works are usually identified by an ISWC (International Standard Musical Work Code), and one work can have many recordings, each with its own ISRC. Your lyric belongs to the work side. The track you generated belongs to the recording side. The two numbers never replace each other, and royalty systems keep them apart for exactly that reason. Royalties for AI music walks through which money follows which number.

Two things an ISRC is not, both stated in the handbook itself:

• It is not a copyright registration. Assigning a code and passing it to a store "should not be confused with copyright registration", which exists in some countries as a separate process. If registration is what you are after, how to copyright a song covers what it buys and where it exists.
• It is not proof of ownership. The handbook says assigning an ISRC "does not affect ownership in any way", and a particular prefix in the code does not mean the assigner owns the recording or is owed royalties.

That second point matters more for AI tracks than for most. Whether anyone owns a machine-generated recording, and who, is a question that different countries answer differently and some have not answered at all. A code from a distributor settles none of it. Who owns AI-generated music lays out why licence and copyright are separate questions. This article describes how the identifier works; it is not legal advice, and for anything with money or a dispute attached, ask a lawyer in your country.

Where we fit, before you get to the code

An ISRC is the last small thing you fill in before a release. The first thing is a song, and a song starts with words. That part we make cheap.

The lyrics generator takes a short brief through a form (theme, point of view, language, structure, hook type, emotion, vocal) and returns a title and a full lyric, already marked up with [Verse] and [Chorus] tags so it pastes straight into Suno; another generator may want the tags adjusted to its own format. One run costs 20 credits, and at 100 credits to the dollar that is $0.20. It does not sing and it does not make audio; the recording happens in a separate tool you choose, usually Suno, which is a different company we do not resell or control.

There is no free trial and no way to pay for a single lyric on its own: $0.20 is what one lyric costs inside a plan, and two plans exist. $5 a month gives access to the catalogue and the prompt generator plus 500 credits every month, which is 25 lyrics. $19 once keeps the catalogue and the prompt generator open for good and comes with 1 500 credits a single time, which is 75 lyrics; those credits do not refill. For someone putting out a first EP, $19 is the sensible ask: the words for every track, with room to throw drafts away.

Why this belongs in an ISRC article: the words are the one part of the track you should finish before any code exists. More on that below, because it is the mistake the ISRC rules punish.

Do you need one? It depends on where the track is going

Where the track goes                              ISRC?
------------------------------------------------  -----------------------------------
Spotify, Apple Music, other stores via a          yes, the distributor will ask for
distributor                                       one or issue one
A music video released as its own product         yes, a separate code from the audio
Plays you want tracked for recording royalties    yes, matching usually runs on ISRC
A birthday song sent to one person                no
A draft shared in a group chat                    no
A direct upload to a site that does not ask       the site will not ask; the handbook
                                                  still wants one for any public release

The practical rule: a code becomes necessary the moment the recording enters a system that counts plays or sales across many services. Stores and streaming platforms receive tracks from distributors with the ISRC in the delivery metadata, and that code is how a play of your track on one service gets tied back to the right recording in reports. Where recording-side royalties are collected (neighbouring rights, in countries that have them), matching typically leans on the ISRC as well. None of that applies to a song for your mum's birthday that lives in one chat, and assigning it a code achieves nothing.

The music video row surprises people. The handbook treats a music video as a different recording from the audio, even when the soundtrack is identical. If you cut a video for your track in a video generator and release it as a music video, it gets its own code, and the video's metadata should point back to the audio's ISRC.

Where to get one: three routes

1. Your distributor issues it. This is the usual route for an independent release. The international ISRC agency, or the national agency in a given country, authorises certain companies as "ISRC Managers", allowed to assign codes on behalf of the people whose recordings they deliver. You tick a box or leave a field empty, and the code appears. Before you upload, ask your distributor three things and get the answers from its own help pages:

1. Will you issue the ISRC, or do I need to bring one?
2. Can I enter a code I already have, for a track released before?
3. If I leave, does the code stay with the recording?

The third question has an answer in the standard itself: codes assigned by an ISRC Manager last for the lifetime of the recording and must not be changed if the rights move to someone else. A distributor that suggests otherwise is worth a second look. If you are still choosing, music distributors for AI songs covers what to check, including their AI-content rules, which differ and have changed more than once.

2. You get a prefix from your national ISRC agency. This is the label route. The agency in your country allocates you a prefix and a range of designation codes, and from then on you assign codes yourself, sequentially, and keep records. The handbook gives an example of an independent artist being allocated a range of a hundred codes rather than the full 00000 to 99999. The international agency's site, isrc.ifpi.org, lists the national agencies. Terms, fees and eligibility are set by each agency, so read your agency's current page rather than a guide like this one. It makes sense if you release often, run a small label, or want the codes to carry your own prefix instead of your distributor's.

3. You assign one through the international agency's online service. The international ISRC agency runs an online assignment service aimed at self-releasing artists. You create an account, enter the recording's details, and the service checks whether that recording already has a code before assigning a new one. It is a paid, credit-based service; check the current price and whether it serves your country on its own page.

For a first release with one distributor, route 1 is the plain choice. Routes 2 and 3 are for people who want the code to exist independently of any one distributor from the start.

The AI-specific part: count your recordings

A music generator produces takes the way a printer produces pages. Two runs of the same prompt give two different performances, and the handbook is blunt about takes: different takes are different recordings, even when everything else is the same, and each one gets its own code if released. Nobody needs codes for the forty drafts that stay on the hard drive. The trouble starts when the release version stops being one fixed thing.

The standard's answer is timing. A code "should be assigned when all creative processes are complete". Here is how the handbook's rules land on things people routinely do to generated tracks:

Change after the code exists                      Same code?
------------------------------------------------  ---------------------------------
Export the same audio as WAV instead of MP3       same
A higher-resolution copy, nothing else touched    same
Same recording placed on a compilation            same
Fade-out tweaked, length changes under 10 s       same
Regenerated with the same prompt (new take)       new code
A verse or chorus added, removed or extended      new code
A clean version with the swear word replaced      new code
A remix, or new vocals or instruments on top      new code
A music video of the track                        new code

Read the table from the point of view of someone who uses a generator. Nearly every AI-typical fix lands in the "new code" half. Regenerating the second chorus because one word came out mangled, extending the outro in the tool, swapping a line in the lyric and running it again: each of those makes a different recording. If the first version is already live, you now have two recordings, two codes, and two separate histories in every system that tracks plays.

That is not a disaster. It is simply two releases where you meant to have one, with plays and playlist adds split between them.

Lock the words before you make the take

The cheapest way to stay on one recording is to change nothing that forces a new one after the code is assigned. Of all the things in that table, the words are the part you can finish completely before any audio exists. A lyric is text: you can read it aloud, cut a line, fix the rhyme, check the name is spelled right, all for free and without making a single new recording.

A working order that keeps one code per song:

1. Brief       theme, point of view, emotion, structure, hook
2. Lyric       generate, then edit until you would sing every line as is
3. Freeze      no more word changes from this step on
4. Takes       generate the audio as many times as you like
5. Pick        one take, trimmed, faded, mastered
6. Metadata    title, version, main artist, duration, type, year
7. Code        distributor issues it, or you assign your own

Step 2 is where the lyrics generator sits, and it is also why the $0.20 matters: you can run a brief several times, keep the strongest lyric and still have used under 100 of the 500 credits a monthly plan gives before step 3. Step 3 is the one people skip, and then they are back at step 4 after release, making a new recording to fix a word.

Step 6 is not decoration either. The handbook lists the reference metadata that must be held alongside every code: title, version title, main artist, duration, type (sound recording or music video) and year of first publication. If two of your recordings differ, at least one of those fields should differ too. That is why a clean edit gets "Clean" in its version title, and why an extended mix says "Extended" instead of sharing the exact title of the original.

A metadata sheet for a single generated track might look like this before upload:

Title            Paper Lanterns
Version title    (empty for the main version)
Main artist      Lina Morrow
Duration         3:12
Type             sound recording
Lyrics           final text, section tags removed
ISRC             leave empty if the distributor issues one;
                 once issued, copy it here and never change it

The lyric line is there because lyrics reach streaming services through their own pipeline, separate from the audio. If you want the words to show on screen, why Spotify shows lyrics for every song except yours explains the separate route they take.

The mistakes the code does not forgive

Two codes for one recording. If you upload the same audio through two distributors at once and each issues its own ISRC, the same recording now has two identifiers, which is exactly what the standard exists to prevent. If you move distributors, carry the existing code over by typing it into the new upload form, which is what question 2 above was for.

One code for two recordings. Reusing the ISRC of the original on a clean edit, a regenerated take or an extended version breaks the rule from the other side. The handbook says a code assigned to a recording must never be moved to a different one.

Editing after release and keeping the old code. A changed chorus is a material change. The honest move is a new version with its own code and a version title that says what changed.

Treating the code as a certificate. A string of twelve characters from your distributor proves the recording has an identifier. It says nothing about who owns the words or the audio, whether the output can be protected where you live, or whether a platform will keep the track up. Our own disclaimer states our position on the lyrics: commercial use is allowed, we claim no rights in them, the rights are non-exclusive, and similar briefs can produce overlapping text for different users. An ISRC changes none of that.

Mistyping the code. The handbook specifically warns about confusing the digit zero with the letter O, and the digit 1 with a lowercase l or a capital I. When you copy a code into another form, paste it; do not retype it.

Not legal advice, again: rules on ownership of AI output, and on what distributors accept, depend on the country and the company, and they keep changing. Check the current terms of your distributor and your generator before release.

What to do next

If the track is already finished and mastered, you do not need anything from us: pick a distributor, let it issue the code, write the code down and never change it. The release checklist for a first single covers the rest of the upload, and the Spotify release guide covers what that platform checks.

If the track is not finished because the words are not, fix that first, since every word you change after release costs you a new recording. Open the lyrics generator, write a brief for the song you are about to release, and get a first draft for 20 credits, $0.20 of a plan. The cheapest way in is $5 a month for 25 lyrics. If you are planning an EP, the $19 lifetime plan covers the catalogue and the prompt generator for good and comes with 75 lyrics once, enough to write every track and throw out the drafts that do not earn their code.