ISRC Codes Explained for Artists and Labels

What an ISRC code is

ISRC stands for International Standard Recording Code. It is a 12-character code that identifies one specific sound recording or music video recording.

The code identifies the recording itself, not the song, not the artist, and not the release. Two completely different recordings of the same song get two different ISRCs. The same recording keeps its ISRC everywhere it appears.

Think of it as a fingerprint for the audio file. Once assigned, it stays with that recording for life and should never be reused for anything else.

• Identifies a recording, not a composition or a release
• 12 characters, assigned once, permanent
• Travels with the recording across every store and streaming service

How the 12 characters break down

An ISRC looks like a block of letters and numbers. It is built from four parts that together describe who registered it and when.

The parts are read in order: a two-letter country code, a three-character registrant code identifying the issuer, a two-digit year of reference, and a five-digit designation number that is unique within that year for that registrant.

You usually see it written with hyphens for readability, but the hyphens are not part of the stored code. The 12 characters are what matter.

• Country code (2 letters) — the registrant's country, for example US
• Registrant code (3 characters) — identifies who issued the code
• Year of reference (2 digits) — the year the code was assigned
• Designation code (5 digits) — a unique number for that recording within the year

When you need a new ISRC

The rule is simple: every distinct recording needs its own ISRC. If the audio is different, it is a new recording.

A radio edit, a clean version, an extended mix, a remix, a live take, an acoustic re-record, and a remaster are all separate recordings. Each one needs its own code, even though they share a title.

You do not get a new ISRC just because a track lands on a different release. If the original master file is reused unchanged on a single, an album, and a playlist pitch, it keeps the same ISRC across all of them.

• New ISRC: radio edit, clean/explicit version, remix, live, acoustic, remaster, instrumental
• Same ISRC: the identical master reused on a single, an album, or a compilation
• Rule of thumb: different audio means a different code

ISRC vs UPC, and where each one lives

These two codes get confused constantly. An ISRC identifies a single recording. A UPC (the barcode) identifies a whole release, like an album or a single product.

One album release has one UPC and many ISRCs, one per track. A streaming service uses the ISRC to know exactly which recording is playing and the UPC to group those recordings into the right release.

Keeping the two straight matters at scale. If an ISRC is wrong or duplicated, streams and royalties can attach to the wrong recording.

• ISRC: per recording (track level)
• UPC: per release (product level)
• One release = one UPC + one ISRC for each track

How distributors assign ISRCs for free

You do not have to buy ISRCs to release music. Distributors such as DistroKid, CD Baby, and TuneCore assign an ISRC to each new recording you upload, at no extra cost.

If you already have your own ISRCs, from your label or from a national agency, most distributors let you enter them manually instead of generating new ones. That keeps a recording's identity consistent if it has already been registered.

Labels managing larger catalogs sometimes register as their own ISRC issuer to control the registrant code across every release. That is optional. For most artists, letting the distributor assign the code is enough.

• Let the distributor generate the code, or enter your existing ISRC
• Never paste the same ISRC onto two different recordings
• If you re-upload the identical master, reuse its original ISRC

Why ISRCs decide who gets paid

The ISRC is how plays get counted. Platforms and royalty systems use it to attribute streams and downloads to the correct recording, which feeds the reporting that determines your payouts.

Because the code is unique and permanent, it lets analytics and rights organizations match activity across services back to one recording. Sloppy or duplicated ISRCs scatter that data and make reconciliation painful.

ISRCs work alongside other catalog metadata, not in place of it. The recording still needs accurate titles, artist credits, version labels, and lyrics so the right recording is paired with the right information downstream.

• Streams and sales are attributed by ISRC
• Duplicate or missing codes fragment your royalty reporting
• Clean ISRCs plus clean metadata keep payouts traceable

Keep the rest of your metadata as clean as the code

An ISRC only points to a recording. The value of that pointer depends on the metadata attached to it, and version labeling is where catalogs get messy fast. A clean version and an explicit version are different recordings with different ISRCs, so labeling them correctly is part of getting the codes right.

This is where a transcription step helps. Musavox produces clean lyric sheets, timestamped LRC files, and catalog metadata from your audio, which gives you accurate, recording-level lyrics to file alongside each ISRC. Its dialect-aware modules cover Latin markets and handle Spanish, English, Portuguese, and Spanglish code-switching, which is where generic lyric tools tend to slip.

Musavox also separates ad-libs and producer tags from the main lyric and includes an assistive explicit-content flag to help your team review wording. The flag is a review aid only; your team and your distributor still make the final explicit determination, and Musavox does not handle rights clearance or ISRC registration itself.