Without an ISRC code, your track cannot be reliably identified by any platform or collection society. Here is how they work, why they matter, and how to make sure yours are correctly issued.
What is an ISRC code?
An ISRC (International Standard Recording Code) is a unique 12-character identifier assigned to a specific sound recording. Think of it as a barcode for your track. Every commercially released recording should have one, and it follows that recording permanently, regardless of which platform it appears on, which distributor delivered it, or which label releases it.
How an ISRC is structured
An ISRC takes the format: CC-XXX-YY-NNNNN
- CC: two-letter country code for the registrant's country
- XXX: three-character alphanumeric registrant code (assigned to the label or distributor)
- YY: two-digit year of registration
- NNNNN: five-digit unique designation for the specific recording
An example
GB-A1B-26-00001 identifies a recording registered by a UK-based registrant in 2026. The same ISRC appears in Spotify's database, Apple Music's catalogue, and PRS for Music's registry, allowing all three to unambiguously identify and report on the same recording.
Why ISRCs matter for royalty collection
When a streaming platform reports plays to a collection society, it uses ISRCs to identify which recordings generated which royalties. If your track has no ISRC, or has an incorrect one, the platform cannot attribute the play to you. The royalty exists, but it cannot find you. It goes into an unmatched pool and, after a holding period, is redistributed to other rights holders.
Common ISRC problems that cost artists money
ISRC errors are more common than most artists realise:
- Missing ISRCs: track was distributed without one, usually by a budget distributor
- Duplicate ISRCs: different recordings sharing the same code, causing royalty misattribution
- Incorrect ISRCs: typos or formatting errors preventing correct matching
- Re-released recordings without new ISRCs: a re-release or remaster should carry a new ISRC, not inherit the original's
- ISRCs not submitted to collection societies: the code exists but was never registered with PRS, PPL, or relevant societies
ISRC vs ISWC: understanding the difference
These two codes are often confused. An ISRC identifies a sound recording: the specific performance you recorded. An ISWC (International Standard Musical Work Code) identifies the underlying musical composition: the song itself, independent of any specific recording. A song can have dozens of recordings, each with its own ISRC, all linked back to a single ISWC. Both are required for complete royalty attribution.
How to check if your ISRCs are correct
You can look up ISRCs through your distributor's back-end, through IFPI's ISRC search tool, or through your PRO's catalogue portal. What is harder to verify is whether those ISRCs have been correctly submitted to all relevant collection societies and whether they are matching correctly in streaming reports. That is where metadata administration becomes essential.
ISRC for cover songs and remixes
A cover song or remix is a new recording of an existing composition. It is a distinct sound recording and therefore requires its own new ISRC - it must not reuse the ISRC of the original recording. The underlying composition (the words and music) uses the same ISWC as the original, but the recording has its own ISRC because it is a different performance. Remixes deserve particular attention: a remix that is substantially different from the original (different arrangement, added elements, new structure) is a new recording. A version that is a minor edit (slightly shorter, fade-out earlier) may or may not qualify as a new recording depending on the platform's standards. When in doubt, issue a new ISRC for each distinct audio file that will be commercially released.
ISRC reuse when switching distributors
One of the most commercially damaging ISRC errors occurs during a distributor switch. If an artist leaves DistroKid for a new distributor and re-uploads the same recordings without using the same ISRCs, the new distributor issues new codes. The DSPs now have two records for what is effectively the same recording: the original (with streaming history, playlist inclusions, and algorithmic data) and the new upload (starting from zero). Streaming history does not automatically transfer to the new ISRC. Preserving ISRCs during a distributor switch requires explicit co-ordination between both distributors. Always audit your ISRC ownership and confirm portability before initiating any distributor move.
ISRC prefix exhaustion: the QM, QZ, and QT codes
When ISRC registrant codes were first assigned, the country prefix codes were tied to the two-letter ISO country code for the registrant's nation. As the music industry globalised and online distribution platforms began issuing ISRCs to artists globally, some platforms exhausted their assigned national prefix blocks. The IFPI introduced special prefixes to handle this: QM (initially allocated to streaming platforms for international use), QZ (allocated for digitally-native independent release platforms), and QT (reserved for additional overflow capacity). An ISRC starting with QM, QZ, or QT is not inherently problematic, but it identifies that the code was issued by a platform rather than a traditional national registrant. Artists who want ISRCs in their own national code (GB for UK artists) can register as an ISRC registrant through PPL in the UK.
How to get your own UK ISRC registrant code
UK-based labels and artists can register as ISRC registrants through PPL, which is the designated ISRC registration authority for the UK. The registration is free and straightforward via ppluk.com. Once you have a UK registrant code, you issue all future ISRCs in the format GB-[your code]-[year]-[five digit sequence]. Owning your own registrant code means your ISRCs are portable - they belong to you, not to any distributor - and you maintain control over your ISRC registry regardless of which distributor or platform you use.
Embedding ISRC in the audio file
Beyond registering ISRCs in external databases, ISRCs can be embedded directly in the audio file itself using the BWF (Broadcast Wave Format) axml chunk for WAV files or ID3 tags for MP3s. Embedding the ISRC in the file means the code travels with the audio regardless of which system handles it - a sync agent receiving a WAV file will find the ISRC embedded in the file, a broadcaster receiving your track will have the code in the metadata layer. The professional audio tool BWF MetaEdit (free, from mediaarea.net) is the simplest way to embed and verify ISRCs in WAV files. This is best practice for mastering deliveries and archival masters.
If you have a catalog of more than a handful of releases and have never audited your ISRC registrations, meaningful royalties are likely unattributed. Our Catalog Assessment covers ISRC verification, registrant code ownership, and cross-system matching. Start at codegroupmusic.co.uk/#catalog-assessment.
Frequently Asked Questions
What happens if two recordings share the same ISRC?
If two different recordings share an ISRC (a duplicate), streaming platforms and PROs attribute all usage for that code to a single record - which may be the wrong one. Royalties are misattributed, streaming histories merge incorrectly, and resolving the conflict requires intervention with both the platform and the ISRC registration authority. Duplicate ISRCs are difficult to fully resolve retrospectively and are best prevented by maintaining a careful ISRC registry.
Can I look up who owns an ISRC?
Yes. The IFPI maintains an ISRC search tool at isrc.ifpi.org where you can look up an ISRC and see the registrant country code and registrant identifier. This tells you which organisation issued the ISRC, though not necessarily the current rights holder of the recording.
Do I need a new ISRC for every format of a release?
You need a new ISRC for every distinct recording: the album version, the radio edit, the acoustic version, the remix, the remaster all need separate ISRCs. You do not need different ISRCs for different file formats of the same recording (WAV vs MP3 vs FLAC of the same audio).
Do pre-releases and demos need ISRCs?
ISRCs are required for recordings that are commercially distributed. A private demo that is never commercially released does not need an ISRC. However, if a demo recording is later commercially released on a streaming platform or used in a sync placement, it needs an ISRC at that point.
What is the difference between ISRC and UPC?
ISRC identifies a specific sound recording (a track). UPC (Universal Product Code) identifies a release - an album, EP, or single as a product. A 12-track album has one UPC (for the release as a whole) and 12 ISRCs (one per track). Both are required for full distribution and royalty attribution.
Published · Updated