ISRC CODES EXPLAINED: EVERY UK INDIE MUSICIAN’S GUIDE

Somewhere in the release process, a distributor asks you for your ISRC codes, and if you’re like most artists I talk to, your stomach drops a little. What are they? Do you already have them? Have you done something wrong by not knowing? Relax. You haven’t.

This is ISRC codes explained properly, for the independent artist doing it all themselves. By the end you’ll know exactly what an ISRC is, why you need one, and how to get an ISRC code without paying a penny you don’t have to.

From where I sit at CD Unity, I see hundreds of masters come through every year, and the ones with their metadata sorted always have a smoother ride to release. The ISRC is a small, unglamorous thing that quietly makes sure you get paid. Let me break it down so it stops feeling like a mystery.

An ISRC, or International Standard Recording Code, is a unique identifier assigned to one specific sound recording. Think of it as a digital fingerprint. No two recordings share the same ISRC, and that unique ISRC follows your track everywhere it goes, across every platform, every country, for the life of the recording. It’s defined by an international standard called ISO 3901, which is just the official rulebook that keeps every code consistent worldwide.

Here’s the key thing to understand: an ISRC identifies the recording, not the song. If you record the same song twice, those are two different recordings, and each needs its own ISRC. The code is a piece of metadata that travels with the audio file, so when your track gets played on Spotify or Apple Music, the system knows exactly which recording was used and who to pay.

The whole system exists so that recordings and music can be tracked accurately across a global industry. It was set up by the IFPI, the international body that oversees the recording industry, and in the US the RIAA administers it. Whenever your music is played, streamed or broadcast, the ISRC is the thing that says “this exact recording, made by this artist” so the royalty lands in the right account.

An ISRC is a 12-character code, and it’s not random. It’s built from four parts, each carrying a piece of information. Once you see the structure, it stops looking like gibberish.

The four parts

• Country code (2 characters): where the code was issued, for example GB for the United Kingdom.
• Registrant code (3 characters): identifies who assigned the code, the registrant, usually your distributor or agency.
• Year of reference (2 digits): the year the ISRC was assigned to the recording.
• Designation code (5 digits): a unique number for that specific recording within the registrant’s catalog for that year.

So a code like GB-ABC-25-00001 tells you it’s a UK-issued code, from registrant ABC, assigned in 2025, and it’s their first recording of the year. You’ll usually see it written without the hyphens once it’s embedded in a file, but the structure is always the same. The registrant code is the part that ties a whole body of work back to one issuing source.

This is where a lot of independent artists get tangled up, so let’s clear it up. The ISRC vs UPC question comes down to one simple distinction: an ISRC identifies a single recording, while a UPC identifies a whole release as a product.

UPC stands for Universal Product Code, and it’s the same family of barcode you’d find on a tin of beans. In music it’s sometimes called an EAN, the European Article Number, or a barcode. Where an ISRC uniquely identifies one track, the UPC identifies the album, EP or single as a saleable package. So a ten-track album has one UPC for the release and ten ISRCs, one for each recording.

A quick word on one more code you might bump into: the ISWC. That one identifies the underlying musical composition, the song as written, rather than a specific recording. It’s tied to the songwriter side and handled by a performance rights organization like PRS for Music, whereas the ISRC is about the master recording. Different codes, different jobs.

Here’s the part that matters for your wallet. The ISRC is how money finds its way back to you. When your track is streamed, downloaded, or gets radio play, the ISRC is what identifies your recording in the enormous sea of tracks out there, so the right royalty gets attributed to the right person.

Try to release without an ISRC code and you hit walls fast. Most distributors and DSPs simply require an ISRC before they’ll accept your track. Beyond that, it’s essential for accurate royalty collection: streaming services log plays against the code, and organisations that handle performance royalties use it to work out who earned what. Without an ISRC, your performance royalties can end up unclaimed or misattributed.

It also matters for a music video, which needs its own ISRC (there’s a specific format for audiovisual recordings). And as your catalog grows, having every recording properly coded means you can actually keep track of what you’ve released and how each track is performing. It’s the backbone of a tidy, professional catalogue rather than a pile of untracked files.

Good news: for most indie artists, you don’t have to do anything special to obtain ISRC codes. When you upload through a distributor, they’ll assign them automatically. DistroKid, TuneCore and CD Baby all generate ISRCs for free as part of the upload, and the ISRC registration happens behind the scenes. For a lot of you, that’s the whole answer, your distributor sorts it.

If you’d rather control your own codes, you can register directly with your national ISRC agency to become a registrant yourself and assign codes from your own registrant code. In the UK that’s PPL. This is worth it if you release a lot and want consistent codes that aren’t tied to one distributor, so if you ever switch, your ISRCs stay yours. For most people starting out, though, letting the distributor handle it is perfectly fine.

Getting the codes embedded in your files

Once you have your ISRCs, they should be embedded into the actual audio. This usually happens during the mastering process. A mastering engineer can encode the ISRC directly into the master, whether that’s a WAV file or a DDP for physical manufacturing, so the code travels inside the audio itself. Embedding ISRC data at this stage means the code is baked into the master before it ever reaches a distributor. Our mastering service handles this as standard, and if you want the full picture on setup, our ISRC page walks through it.

A few traps catch people out, and they’re all easy to sidestep once you know them. Here’s what I’d watch for.

Reusing a code across different versions. This is the big one. Every different version of a recording needs its own ISRC. A remix needs a new ISRC. A remaster or remaster of an old track needs one. Even a radio edit that’s just a shorter cut of the same song counts as a separate recording and needs its own code. The rule is simple: if the audio is different, it needs its own ISRC.

Assigning the same code twice. Once an ISRC was assigned to a recording, it belongs to that recording forever. You never reuse it, even if you delete the track. Assign a new one every time.

Leaving it to the last minute. Sort your codes before you send anything to a distributor. Trying to add or fix codes after a release is live is fiddly and can delay you. Getting the metadata right up front is part of a smooth release day, and it pairs neatly with choosing a good distributor, which I covered in my guide to picking a digital music distributor.

Josh McKenzie

Hello, I’m Josh, and I’ve been honing my graphic design skills for almost 15 years now, catering to the needs of bands and businesses alike. What really fascinates me is the business aspect of the music industry. In addition to my design work, I also happen to play the Hammond organ, and I strive to share my knowledge through helpful articles that I write exclusively for you all!