ISRC vs UPC vs ISWC for Music Releases

November 11, 2026·by TrackTag team

The short answer: recording, release, composition

ISRC vs UPC vs ISWC comes down to three different things: a recording, a release, and the underlying musical work. The codes are related in catalog records, but they are not interchangeable.

  • ISRC identifies a particular sound recording or music video recording.
  • UPC, often represented as a UPC or EAN product code, identifies a release or product, such as a single, EP, or album.
  • ISWC identifies the musical work, meaning the composition created by its writers, rather than one performance or recording.

A useful shorthand is: ISRC = the recording you hear; UPC = the release it appears on; ISWC = the composition being performed. The International ISRC Registration Authority says an ISRC identifies recordings, not compositions or products. CISAC describes ISWC as a globally unique identifier for musical works, and GS1 describes UPC and EAN as barcode formats used to identify trade items. (isrc.ifpi.org)

This distinction matters when you deliver music, manage a label or library catalog, or match usage and rights records. If someone asks for a track’s ISRC, a release’s UPC, and a song’s ISWC, they are asking for three different identifiers.

What each code identifies

ISRC: one recording

The ISRC, or International Standard Recording Code, identifies a distinct sound recording or music video recording. It is a 12 character identifier. One studio master recording has its own ISRC, and a genuinely different recording, such as a live performance or a materially changed mix, may require a different one. (isrc.ifpi.org)

The same recording generally keeps its ISRC when it moves between distributors, countries, formats, or releases. For example, if you place the unchanged studio master on a later album or compilation, the recording does not become a new recording just because the release changed. IFPI says an ISRC remains with the recording even when ownership changes, and the same identifier can be used across releases and formats. (isrc.ifpi.org)

An ISRC does not identify the songwriter, publisher, album, or owner. The code is an identifier, not a readable summary of rights. Its associated database records may connect it to descriptive or rights information, but the code itself does not prove who owns the recording. (isrc.ifpi.org)

UPC or EAN: one release or product

A UPC is commonly used for a music release, while EAN is a related product code format used in many markets. You may see these labels used in distributor forms and catalog exports. In practice, check the field description in the delivery system: it is asking for the release identifier, not the identifier for each individual track recording.

A single release, an EP, and an album can each have their own product identifier. If the same recording appears on both a single and an album, each release can have a different UPC or EAN while the recording retains its ISRC. GS1 explains that UPC and EAN are barcode formats for product identification, and that a product number has no descriptive meaning that can be decoded on its own. (support.gs1.org)

ISWC: the underlying musical work

An ISWC, or International Standard Musical Work Code, identifies a musical work: the composition associated with its creators, such as its composers, authors, and arrangers. It does not identify a particular recording. One composition can be performed or recorded by different artists, and those recordings can have different ISRCs while being associated with the same underlying work. CISAC says the ISWC identifies musical works by reference to the title and creators. (cisac.org)

An ISWC is also not a songwriter or publisher identifier. If a form asks for an IPI number, that is a different identifier for a party in rights administration. If a form asks for a writer or publisher name, enter the party information requested rather than substituting an ISWC.

One song across a single and an album

Consider a producer who releases an original song called “Night Signal” as a single, then includes the same unchanged master on a ten track album.

  • The sound recording has one ISRC. If the identical recording appears on the single and the album, it keeps that ISRC.
  • The single has its own UPC or EAN, and the album has a different UPC or EAN because these are separate releases.
  • The composition has an ISWC record when registered and assigned through the relevant work registration process. That work identifier is not replaced just because the same composition appears on a second release.

Now suppose the producer makes a new remix with a different arrangement and a substantially different duration. That is a different recording, so it needs a distinct ISRC under the recording code rules. The release UPC depends on what product or release the remix appears on. The composition relationship depends on the work and its registration, not on the remix’s release barcode. IFPI’s guidance says materially changed recordings and different mixes or edits can require a new ISRC; its FAQ also notes that ordinary remastering may keep the existing code. (isrc.ifpi.org)

This is why a spreadsheet that stores only one “music ID” column becomes confusing. Keep separate columns for ISRC, UPC or EAN, and ISWC, and label what each value identifies. For a multi track release, the UPC belongs at release level, while each recording’s ISRC belongs at track level. Work identifiers belong with composition and writer information.

When an ISRC changes, and when it does not

Do not issue a fresh ISRC merely because you changed distributors, updated artist credits, moved a track to another album, or supplied a new file format for the same recording. Those changes do not automatically make the audio a different recording. Reusing the original ISRC helps keep references to that recording connected across services and releases. (isrc.ifpi.org)

A new ISRC may be needed when the recording itself is materially different. Examples from IFPI guidance include a different mix or edit, a live version of a studio recording, or a change to the musical content. A remaster can be a judgment call: ordinary mastering changes may retain the original ISRC, while significant new creative input may support a new one. Do not decide from the filename alone. Check the recording history and the applicable ISRC guidance, especially if you inherited a catalog or are preparing a reissue. (isrc.ifpi.org)

Once assigned, an ISRC must not be recycled for a different recording. If an old code is missing from a file or delivery sheet, look for the code already assigned to the recording before creating another one. (isrc.ifpi.org)

How to check a code before delivery

1. Identify the entity the form is asking about. Track recording means ISRC. Release or product means UPC or EAN. Composition or song work means ISWC.

2. Search the records you already control. Check distributor dashboards, label delivery reports, catalog spreadsheets, and prior release paperwork. If you are changing distributors, ask the previous provider for the original recording codes rather than assuming new ones are required.

3. Look up the recording or its code. TrackTag’s ISRC lookup tool helps check an ISRC against associated recording information. If you know the title and artist but not the code, try the reverse ISRC lookup tool. Database coverage can vary, so treat a missing result as a reason to check another source, not proof that the recording has never had a code.

4. Confirm who delivered the release. If a code record or delivery sheet names an unfamiliar provider, a music distributor lookup can help identify distributor information. Confirm the result against your own contracts or release account before relying on it.

5. Keep the identifiers beside the matching records. Store release codes on release records, recording codes on track records, and work codes with composition data. Keep the title, artist, version, duration, and source for each lookup so a near match is not mistaken for the right recording.

A code lookup is not a substitute for audio and catalog organization. If you manage a large library, keep the identifiers with the corresponding file and version records. TrackTag Studio batch audio analyzer can help enrich analyzed files with fields such as genres, moods, instruments, vocals, and song structure, but it does not assign or replace ISRC, UPC, or ISWC codes. TrackTag Studio analyzes audio; the identifiers still need to come from the appropriate release and rights records.

If a label asks for a publisher, remember that a music publisher lookup is a separate task from checking an ISWC. The ISWC identifies the work, while publisher information is associated rights data in a repertoire or registration record. Verify the publisher and writer details with the relevant society, administrator, or rights database rather than treating the code as proof of ownership.

Common code mix ups in catalogs

  • Putting a release UPC in every track’s ISRC field: the UPC identifies a release, not each recording on it.
  • Assuming an ISRC identifies the composition: it points to the recording. A separate work record and identifier handle the composition.
  • Creating a new ISRC for a new distributor: the recording’s identifier normally stays with it through a transfer.
  • Assuming the characters reveal ownership or genre: identifiers are keys for looking up records, not self explaining descriptions. Confirm linked metadata from reliable records.
  • Using a title match as final proof: multiple recordings can share a title, and the same recording can appear with variations in title formatting. Check artist, version, duration, and source as well.

For music libraries, sync teams, and platform catalog managers, consistent fields make downstream matching more dependable. Keep each code in its own column, preserve the code’s source, and flag missing values separately from confirmed absence. If you later need to get song genre for sorting or pitching, use a genre lookup or audio analysis field for that purpose. Genre is descriptive metadata, not something encoded in ISRC, UPC, or ISWC.

FAQ

Is an ISRC the same as a UPC?

No. An ISRC identifies a sound recording, while a UPC or EAN identifies a release or product. The same recording can keep its ISRC when it appears on more than one release, while those releases have different product codes.

Does an ISWC identify a recording or a song?

An ISWC identifies the musical work, meaning the underlying composition and its creators, rather than a particular performance or master recording. The recording has an ISRC. Different recordings of the same composition can therefore have distinct ISRCs.

Can one song have multiple ISRCs?

Yes, when there are distinct recordings, such as a studio version and a separate live performance or materially different remix. The unchanged master should generally retain its original ISRC across releases, formats, and distributor transfers. Check official guidance for borderline remastering or edit cases.

How do I get song genre from an ISRC or UPC?

These codes identify records, but they do not encode genre. Use a catalog or audio analysis source for genre information, then keep that descriptive field separate from the identifiers. TrackTag’s genre lookup tool is one option for checking genre information.

Tag your whole catalog with AI

BPM, key, genre, moods, instruments and keywords: 30+ fields per track, exported ready for libraries.

Open TrackTag Studio →

← All posts·In-depth guides