What Is an ISRC Code? The Identifier Attached to a Recording

The short definition

An ISRC is an International Standard Recording Code. It is a unique identifier for a particular sound recording or music video recording. The official IFPI ISRC FAQ explains what the code identifies and how rights owners maintain the associated information.

The code identifies the recording asset, not the song in every form. A composition can exist as sheet music, a MIDI file, or several different recordings. Those are not all the same thing as the particular recording an ISRC identifies.

Recording, composition, and release are different assets

Three identifiers are easy to confuse. An ISRC identifies a sound recording or music video. An ISWC identifies a musical work or composition. A UPC or EAN identifies a product, such as a release package containing one or more tracks. The IFPI FAQ sets out these distinctions.

An ISRC does not tell a listener who owns the composition, who owns the master, or whether a recording has been licensed for a particular use. The code is useful for identification and administration, but it is not a rights agreement or proof of ownership.

That difference matters when a single song appears in a studio version, live take, remix, music video, or compilation. Keep the recording identifiers beside the asset details, and keep ownership, credits, and permission documents in their own records.

Who assigns an ISRC

The recording rights owner may assign an ISRC directly or authorize an ISRC Manager to do the work. IFPI says an independent artist does not need to belong to an industry association to use the system. A distributor may also handle assignment for the rights holder.

Before requesting a new code, check the recording's existing delivery information and ask the distributor or previous rights owner whether an ISRC has already been assigned. The IFPI FAQ says an assigned ISRC must not be reused for a different recording, and an ownership change alone does not call for a new code.

If the recording already carries a valid identifier, do not create a second one just because the artist changed distributor or the rights moved to a new owner. Confirm the record before delivery so the same asset is not represented by conflicting information.

What the code contains

The IFPI FAQ describes a 12-character structure with three parts: a five-character prefix, a two-digit year of reference, and a five-digit designation code. The code is an identifier, not a summary of the artist, genre, territory, or rights owner.

The year element refers to the year the ISRC is assigned, not necessarily the year the recording was made. If an artist is assigning codes directly, the applicable IFPI guidance explains how to maintain the prefix and designation sequence. Do not invent a code by copying one from another track.

Keep the identifier with accurate metadata

The IFPI guidance on using ISRCs calls for reference information such as the code, main artist, track title, version title when relevant, duration, content type, and publication date. Keep those details in a durable catalog record rather than in a delivery email alone.

Match the code to the correct track in the distributor's metadata, the recording file information, and any label or performance-rights records that ask for it. Version names matter: "radio edit," "live," "remix," and "extended mix" should not be allowed to drift between a file, a release form, and the catalog spreadsheet.

Re-recordings and remasters need a check

Do not assume that every change creates a new ISRC or that every version can keep the old one. IFPI's FAQ distinguishes ownership changes from changes to the recording and describes cases such as remixes, edits, and some creative changes that may require a new identifier. It also notes that a remaster generally may retain the same ISRC, while significant new creative input can change the analysis.

The right decision depends on what the recording actually is and the current applicable ISRC rules. Use the IFPI FAQ and handbook guidance and confirm with the distributor or ISRC agency when a release contains a new edit, remix, re-recording, or substantially changed master.

A practical pre-release check

Before delivery, match each ISRC to the exact recording, version, artist credit, duration, and asset type. Check the code against an existing release if the recording has been distributed before. Confirm who assigned it and make sure the distributor has not generated a different number.

Keep the ISRC next to the version metadata and the rights documentation, but do not use it as a replacement for either. A music distribution metadata checklist can help organize the remaining delivery fields.

An ISRC is small, but a stable identifier can keep the recording easier to distinguish as it moves between distributors, formats, and uses. The reliable habit is to assign it through an authorized process, preserve the record, and verify the match each time the recording is delivered.