ISRC Codes Explained

An International Standard Recording Code (ISRC) is a persistent identifier for a particular sound recording or music-video recording. It helps services, distributors, rights-management systems, and reporting organizations distinguish one recording from another. It does not identify the underlying musical composition, lyrics, album or product, artwork, or every kind of audiovisual work. It also does not, by itself, prove who currently owns a recording or guarantee payment, chart eligibility, copyright registration, or a license.

The practical rule is simple: one distinct recording should have one ISRC, and an assigned code should never be reused for a different recording. If the recording is unchanged, its ISRC normally travels with it through new formats, releases, territories, licenses, compilations, and ownership changes. If the recording changes materially—such as through a remix, edited version, different performance, or separately exploited music video—it generally needs a new code.

This article explains the identifier’s structure, who can assign it, how to obtain one, and how to avoid common metadata mistakes. Procedures, fees, and platform requirements can change, so the current date and provider involved matter. The guidance here reflects the global ISRC standard and International ISRC Registration Authority guidance, with a United States agency example and provider-specific platform information checked on August 7, 2026.

What an ISRC identifies

An ISRC identifies a recording, not an abstract song. The distinction matters because a composition and a recording can have different owners, licensing histories, and versions. A songwriter may write one composition, while several artists record it, a producer creates a remix, and an artist later releases a live performance. Those recordings are not automatically the same asset merely because they contain the same musical work.

The ISRC system is intended for sound recordings and music-video recordings. The International Standard Recording Code Handbook describes the code as an identifier used to distinguish recordings and support information exchange across the music industry. The official International Standard Recording Code (ISRC) Handbook, 4th Edition also distinguishes recording identification from copyright registration. An ISRC is therefore metadata: it helps identify and track an asset, but it is not an application for copyright registration and does not replace one.

It is also not a product code. An album, single, EP, or physical product may have its own product or release identifier, while every individual recording inside that product can have its own ISRC. A track’s ISRC should not be confused with a UPC, EAN, catalog number, composition identifier, songwriter-rights record, or artwork reference. Those identifiers can work alongside an ISRC, but they answer different questions.

The same caution applies to money. An ISRC can support identification, reporting, and rights-management workflows, but possessing a code alone does not establish ownership, create a license, or guarantee royalties. The ISRC Standard describes ISRC as the ISO 3901:2019 recording-identification standard. Platform documentation such as YouTube’s Sound Recording assets shows how an ISRC can appear in asset metadata and support certain Content ID workflows. Those uses should not be expanded into a universal promise of payment or ownership.

The 12-character structure

An ISRC contains 12 alphanumeric characters arranged in three elements:

• A five-character Prefix Code
• A two-digit Year of Reference
• A five-digit Designation Code

In visual form, it is commonly displayed with the label “ISRC” and hyphens between the elements. The underlying identifier is still the 12-character code. The International Standard Recording Code (ISRC) Handbook, 4th Edition explains the structure and display conventions.

The Year of Reference is especially easy to misunderstand. It records the year in which that ISRC was assigned. It is not necessarily the year the recording was made, mastered, first released, or re-released. Recording dates and release dates belong in the associated metadata, not as assumptions derived from the code. The FAQ confirms this assignment-year distinction.

The Prefix Code also needs careful handling. It should not be treated as a live ownership label, a definitive statement of where the recording was made, or proof of the recording’s current territory. A recording can change hands, and an authorized third party can assign a code. Rights can also vary by territory. As a result, a prefix may provide useful information within the ISRC system, but it cannot answer the current ownership question by itself. The Handbook’s explanation of prefix use is the authoritative basis for this limitation.

The Designation Code is the five-digit portion assigned by the registrant within the relevant assignment process. It helps create a unique identifier for the recording. It is not a substitute for a title, artist name, version description, or catalog record. Good metadata should still state what the recording is, who performed it, which version it represents, and when it was created or released.

The central rule: one recording, one code

Every distinct recording should have one and only one ISRC. Once an ISRC has been assigned to a recording, do not create another code for that same unchanged recording merely because it is being delivered to a new service or sold in a new format. Conversely, never take an existing ISRC and attach it to a different recording. The code is persistent, not disposable campaign metadata.

An unchanged master generally keeps its ISRC when it is:

• Delivered in a different file format or bitrate
• Included on a different release or compilation
• Licensed to another party
• Distributed in another country or territory
• Offered through a different business model
• Transferred to a new owner

The continuity rule is important during catalog sales, label changes, distributor changes, and re-delivery. If the same master moves from one distributor to another, the new distributor should receive the existing ISRC rather than treating the transfer as a new recording. The FAQ and International Standard Recording Code (ISRC) Handbook, 4th Edition explain that ownership changes do not normally break the recording’s identity.

That does not mean every new export or remaster automatically keeps the old code. The question is whether the recording remains materially the same. A conventional remaster generally retains the original ISRC when it does not introduce significant new creative input. If the result is materially different, a new code is appropriate. The authoritative guidance also notes that some duration changes, including changes over 10 seconds in relevant circumstances, can indicate that a new code is required. When the facts are borderline, preserve a clear version history and check the current guidance or assignment authority.

When a new ISRC is generally needed

A materially changed recording requires a new ISRC. Examples include a remix, an edited or censored version, a cover recording, a live version, a different take, an added performance, or an extended version. These are not merely new delivery containers; they are different recordings or materially changed versions of the recording.

A remix changes the creative content or arrangement. An edited version changes the duration or content. A live version captures a different performance. A cover is a new recording of the composition, even though the underlying composition is familiar. A different take is a separate performance. Adding vocals, instruments, or other performance elements can also produce a materially different asset. Each qualifying version should receive its own code and should be clearly described in the metadata.

Music videos require particular care. A music video is not simply the sound recording with pictures attached for identification purposes. It is a separately exploited music-video recording and should have a different ISRC from the underlying sound recording. YouTube’s Resource List requires valid ISRCs for delivered sound-recording and music-video resources and specifically requires the music-video ISRC to differ from the underlying sound-recording ISRC.

The result may be a pair of related identifiers: one for the audio master and another for the music-video recording. They should be connected through accurate metadata, but one should not be substituted for the other. This distinction matters when a distributor or platform delivers assets, matches usage, or reports activity.

Compilations are another source of confusion. Putting an unchanged recording onto a compilation does not ordinarily create a new recording, so the track keeps its existing ISRC. A newly edited, remixed, or otherwise materially changed version placed on that compilation can require a different code. The release context changes; the recording identity does not necessarily change.

Who may assign an ISRC

A valid assignment may be made by the recording owner, an exclusive licensee, or an authorized ISRC Manager. A distributor or retailer does not automatically gain authority merely because it distributes or sells the recording. Its authority depends on authorization or appointment under the ISRC system and the parties’ business arrangement. The Handbook describes the roles of recording owners, exclusive licensees, and authorized managers.

Applicants normally obtain assignment means, including a prefix where applicable, through the ISRC agency serving their territory. The official ISRC Agency Contacts list identifies appointed agencies. For the United States, the current list identifies the Recording Industry Association of America (RIAA) as the relevant agency. Applicants in territories without a listed agency can use the International ISRC Agency route. Agency appointments and contact procedures can change, so verify the live list before applying.

The standard is available to entities creating sound recordings regardless of membership in a trade association. The ISRC Standard explains the agency-application route and the availability of assignment means to recording creators. The precise process may depend on where the applicant operates and whether the applicant uses an agency, an authorized manager, or a distributor service.

Ways to obtain an ISRC

There is no single universal workflow or universal price. Assignment route and cost vary by agency, authorized manager, distributor, territory, and service. Do not assume that every song needs an ISRC, that every route is free, or that a code is universally required for every chart or platform. Those statements require separate, current documentation for the particular service or organization.

A practical route is:

1. Check whether the recording already has an ISRC. Search your catalog, prior distributor delivery records, label metadata, and platform reports before requesting a new code.
2. Confirm that the recording is actually distinct. If it is an unchanged master, preserve the existing code. If it is a remix, edit, live take, cover, extended version, or materially changed master, document the version and assess whether a new code is required.
3. Identify the appropriate agency or authorized manager. Start with the current ISRC Agency Contacts. In the United States, the listed agency is RIAA; an unlisted territory can use the International ISRC Agency route.
4. Prepare complete metadata. The online assignment service’s Assign ISRC Online instructions require recording information and provide a database lookup intended to reduce duplicate assignments.
5. Record the assigned code in your master catalog. Store it with the exact version title, artist, duration, recording date, release information, ownership or license records, and delivery history.
6. Send the same code with the recording whenever the master is delivered again. If a platform or distributor shows a different code, investigate before accepting the change.

The International ISRC Agency offers an online assignment service. As of August 7, 2026, its cited instructions describe a current fee of £15 plus applicable UK VAT for 30 credits, with three credits used for a new assignment. That price applies to the cited IFPI service only and may change; it is not evidence that every assignment route charges a fee.

Distributors may also provide assignment as an authorized service. For example, DistroKid states in its Uploading – DistroKid Help Center that it accepts existing external ISRCs and automatically generates codes for eligible uploads. Its plan eligibility, timing, and post-upload workflow are DistroKid-specific and may change. Do not apply that procedure automatically to TuneCore, CD Baby, or another distributor without checking that provider’s current documentation.

ISRCs in distribution and platform metadata

ISRCs make recording metadata more interoperable. Online services, distributors, and collective-management organizations can use the identifier to distinguish a particular recording from other versions. The code is especially useful when the same master appears in several releases, territories, formats, or licensed catalogs.

For platform delivery, treat the ISRC as one field in a larger metadata record. The code should match the exact audio or video asset being delivered. Version labels, artist credits, duration, release context, and ownership information still need to be accurate. A correct code cannot repair an incorrectly described master, and a new release does not justify changing the code for an unchanged recording.

YouTube’s documentation illustrates the distinction between asset types. Its Resource List addresses sound-recording and music-video resources, while Sound Recording assets describes ISRC as sound-recording asset metadata used in Content ID workflows. These are platform-specific examples of identification and reporting use, not proof that an ISRC alone creates a right to payment or a successful claim.

A worked example

Suppose an artist records an original studio master in 2026 and obtains an ISRC in 2026. The two-digit Year of Reference reflects the assignment year, not necessarily the recording date. The artist uploads the unchanged master to a distributor, later includes the same master on an EP and a compilation, licenses it in another country, and changes distributors. Those events do not ordinarily require new ISRCs. The same recording keeps its code.

The artist then releases a radio edit that removes part of the performance. That edited version is materially different and should be assessed for a new ISRC. A producer creates a remix, which also needs its own code. The band performs the song live and records that performance; the live recording is a different recording. Finally, the artist produces a music video using the studio audio. The music-video recording receives a code different from the audio master’s code.

The artist’s catalog should therefore preserve the original code for the unchanged studio master and maintain separate records for the edit, remix, live recording, and music video. The composition may remain the same across several of these assets, but composition identity and recording identity are separate.

Final checklist

Before delivering a release, ask:

• Am I identifying a recording, rather than a composition or product?
• Does this recording already have an ISRC?
• Is the master unchanged, or has it been materially edited, remixed, extended, re-performed, or otherwise altered?
• If it is a music video, does it have a code separate from the underlying sound recording?
• Am I using an authorized agency, manager, or distributor route?
• Have I verified the current agency, provider workflow, eligibility, and fee information?
• Have I stored the code with exact version metadata and delivery history?
• Am I avoiding claims that the code alone proves ownership, guarantees royalties, registers copyright, or qualifies a release for every platform or chart?

ISRCs work best when treated as durable recording identifiers. Find an existing code before assigning another, preserve it when the master is unchanged, create a new one when the recording materially changes, and keep the code tied to precise version metadata. Open Music Business provides educational information, not individualized legal, financial, tax, contract, or royalty advice.