An ISRC code is a 12-character identifier that uniquely tags a single sound recording — one specific master of one specific track. Think of it as a digital fingerprint that stays with that recording everywhere it goes: streaming platforms, download stores, radio, and royalty systems. If you are releasing music, every track you put out needs one.
The good news: you almost never have to chase one down yourself. Read on for what an ISRC code actually is, where it comes from, and the small but important rules for using it correctly.
What an ISRC code is (and isn’t)
ISRC stands for International Standard Recording Code. It identifies a recording, not a song. That distinction matters: if you record an acoustic version and a full-band version of the same song, those are two recordings and they get two different ISRCs. A remix gets its own. A remaster usually gets its own too.
An ISRC does not identify the composition (the underlying song and lyrics) — that side is handled by publishing and PROs. For how the songwriting side works, see our explainer on music publishing and what a PRO is.
What an ISRC code looks like
An ISRC is 12 characters, usually written with hyphens for readability, in four parts:
- Country code — two letters (e.g. the issuing country).
- Registrant code — three characters identifying the issuer.
- Year of reference — two digits.
- Designation code — five digits, unique to that recording.
Once assigned, an ISRC stays with that recording permanently. You do not reissue it if the track moves to a different distributor or store. The hyphens you often see written between the parts are purely for human readability — when the code is embedded in a file or sent to a platform, it travels as a single unbroken 12-character string. The “year of reference” is the year the ISRC was assigned, not necessarily the year the track is released, so do not read too much into it.
How to get an ISRC code
For most independent artists, the simplest route is your distributor. When you upload a release through one of the best music distribution services such as DistroKid, TuneCore, CD Baby, or Amuse, they assign a free ISRC to each track automatically. This is the path covered in our guide to releasing a song independently, and it is the right choice for the vast majority of people.
If you want to own and manage your own ISRCs across releases — useful if you run a label or switch distributors often — you can apply to your national ISRC agency for a registrant code and issue your own. That is more administrative work, so only bother if you have a reason to.
Distributor-assigned vs. your own registrant code
Choosing between the two routes comes down to scale and control. Letting your distributor assign codes is free, instant, and requires zero paperwork, which is exactly why it suits a solo artist putting out a handful of singles a year. The trade-off is that the codes carry the distributor’s registrant prefix rather than your own, and you are relying on them to log the assignment correctly.
Applying for your own registrant code makes more sense once you are releasing high volumes, running a label with several artists, or moving catalogue between distributors regularly. Owning the prefix means every recording you issue is tied to your organisation, your numbering stays consistent across services, and you keep a single authoritative log. The cost is the upfront registration plus the ongoing discipline of assigning codes by hand and never duplicating one. For most people reading this, the distributor route wins; only step up to your own registrant code when the admin clearly pays for itself.
Why the ISRC code matters
The ISRC is how plays get counted and money gets routed. When your track is streamed or sold, platforms log activity against the ISRC, which feeds the reporting that pays out your music royalties. It also powers chart reporting and helps services recognise the same recording wherever it appears. Get it wrong — reuse one ISRC for two different recordings, or assign new ones to a track that already has one — and your data can get split or misattributed.
ISRC vs UPC
People mix these up constantly. The ISRC tags an individual recording (the track). The UPC code tags the release as a whole (the single, EP, or album). A 10-track album has one UPC and ten ISRCs. Both are handled for you when you distribute.
Common ISRC mistakes to avoid
Most ISRC problems are not technical — they come from misunderstanding what the code is meant to identify. A few patterns cause the bulk of the trouble:
- Reusing one ISRC across versions. A radio edit, an extended mix, and the album cut are three recordings, not one. Sharing a code between them merges their data and muddies your royalty reporting.
- Minting a fresh code for an unchanged re-upload. If you take down a track and put the identical master back up, it should keep its original ISRC. A new code splits the play history into two and can wipe out the streaming numbers that help with playlisting and chart eligibility.
- Letting a new distributor auto-assign over an existing code. When migrating a catalogue, supply the existing ISRCs during upload so the distributor reuses them instead of generating new ones. If you are weighing a move, our comparison of DistroKid vs CD Baby walks through how each handles existing codes.
- Confusing the ISRC with the UPC. Putting a release-level UPC where a track-level ISRC belongs (or vice versa) breaks the way platforms match your metadata.
- Not keeping a log. Once you have more than a handful of releases, an undocumented ISRC is easy to accidentally duplicate. A simple spreadsheet prevents it.
Practical tips for using ISRCs
- Let your distributor assign them unless you have a clear reason to own your own.
- Never reuse an ISRC for a different recording, even a slightly different version.
- Keep a record of which ISRC maps to which track — handy for sync deals and audits. Our music release checklist includes this step.
- Don’t generate a new one just because you re-upload an unchanged track.
Before you get to codes, make sure the actual audio is ready. A clean, properly finished master is what you are tagging — see what mastering is if you are unsure your track is release-ready.
Frequently asked questions
Do I have to pay for an ISRC code?
No. Distributors assign ISRCs for free as part of uploading your release. You only pay if you choose to register as your own ISRC issuer through a national agency, which is optional.
Can two songs share the same ISRC code?
No. Every distinct recording needs its own ISRC. Even different versions of the same song — radio edit, acoustic, remix — each get a separate code.
What happens to my ISRC if I switch distributors?
The ISRC stays attached to the recording. If you move a release to a new distributor, you should keep the existing ISRC rather than letting a new one be assigned, so your streaming history and royalty data stay intact.
Do cover songs and live recordings need their own ISRCs?
Yes. An ISRC identifies a specific recording, so a cover you record is a new recording and gets its own code, even though the underlying composition belongs to someone else. A live performance of a track you have already released studio is likewise a separate recording and needs its own ISRC.
This article is general information, not legal advice. For decisions about rights and royalties, consider speaking to a qualified professional.
