ISRC vs ISWC: Recording and Song Codes Explained

What is the difference between ISRC and ISWC?

An ISRC identifies a particular sound or music-video recording; an ISWC identifies the underlying musical work, such as a song's composition. They are not interchangeable, and neither settles who may release or use the music. Keep recording identifiers, work identifiers, contributor information, and agreements as separate records. For an actual release, confirm assignments with the relevant agency, rights administrator, or distributor and obtain qualified advice on permissions.

The distinction answers two different questions: which recording are we discussing, and which work does it contain? Pop conversation often calls both “the song.” A useful filing system needs to be less casual than that.

Which layer does each identifier describe?

ISRC stands for International Standard Recording Code. ISWC stands for International Standard Musical Work Code. IFPI's explanation distinguishes recordings from compositions and separately explains that music products generally use UPC/EAN identifiers. An album's product identifier does not replace identifiers for its individual recordings.

Use this editorial comparison when reading release paperwork:

The table is a map of different jobs, not a complete delivery specification. Follow the current requirements of the service receiving a real release. A field asking for one identifier should not be filled with another simply because both look like catalog numbers.

Our release-rollout guide covers the wider campaign. Here, the task is narrower: keep these layers distinguishable before they enter that campaign's records.

What can you learn from the characters?

IFPI's structure page describes an ISRC as 12 alphanumeric characters: a five-character prefix, a two-digit year of reference, and a five-digit designation code. The year refers to assignment, not necessarily when the recording was made.

An ISWC has a different structure: the letter T, nine digits identifying the work, and one numeric check digit, as described by the ISWC International Agency. Presentation may include dots and hyphens for readability.

Do not try to convert one structure into the other. Nor should a plausible-looking character string be treated as proof of a genuine assignment. In a working document, copy the confirmed identifier from the responsible source and retain that source's confirmation.

For learning exercises below, “Recording A” and “Work W” are deliberately plain labels. They are not codes to submit anywhere. This avoids putting an invented identifier into somebody's release spreadsheet.

Can one work have several recordings?

Yes. A musical work and a particular recorded performance are different things. The ISWC agency's description specifically excludes recordings and performances from what an ISWC identifies.

Consider an entirely fictional planning exercise. Work W is an unchanged composition. Recording A is its studio performance. Recording B is a separate live performance of that same composition. A later album uses Recording A without altering it.

There are three release appearances in this example, two distinct recordings, and one stipulated unchanged work. Those counts follow the assumptions written above; they are not a report of a real catalog.

The word “unchanged” matters. This exercise does not decide whether new lyrics, an adaptation, or other compositional changes should be treated as a different work. Send those questions to the responsible work-registration agency and qualified rights adviser. Similar titles alone do not resolve them.

When should a recording keep its existing ISRC?

IFPI's rules on when not to assign say an existing code should be retained for the same recording across releases, formats, and bit-rate differences. A licensing change or use in another country does not itself call for a replacement.

In the fictional example, moving unchanged Recording A onto an album does not create Recording C. The release container changed; the recording did not.

Record that distinction in two separate fields: “recording version” and “release appearance.” Otherwise, an album title can accidentally become the team's shorthand for a supposedly different master.

This is a documentation recommendation, not a promise about how a streaming service will display or combine releases. Confirm delivery handling with the actual distributor before replacing, migrating, or resubmitting anything.

When does a changed recording need a different ISRC?

IFPI's assignment guidance requires a new code for a new or materially changed recording. Its examples include different mixes or edits and a new surround mix made from recorded stems.

Do not use the filename alone as the decision. Write what changed in the audio and ask the responsible assigner to apply the current rules. “Final,” “final revised,” and “final absolutely this one” are project-management labels, not an identification standard.

A remaster needs particular care. The IFPI FAQ says retaining the code is generally appropriate when it remains fundamentally the same recording, while significant new creative input can justify a new one. Avoid a blanket rule that every remaster either keeps or changes its identifier.

Likewise, a new recording code does not independently decide the underlying work's identity. Keep the recording-version decision and the work-registration decision separate, and retain the reasoning supplied by the relevant administrator.

Does either code prove ownership or permission?

No. IFPI's ownership guidance says an ISRC remains with the recording when ownership changes and its elements should not be used to infer rights status. Current ownership information belongs in associated records, not in a guess based on the code.

The ISWC agency's guidance for collective management organisations likewise says identification does not confer copyright or another status. It also explains that assigning an ISWC to an arrangement or adaptation does not automatically mean right owners authorized it.

A code is therefore not a substitute for reviewing permissions, contributor terms, or the planned use. Ask a qualified music-rights adviser to assess a specific project before release. Do not infer that a searchable recording is available to sample, remix, or distribute.

Our featured-artist credit guide makes a related distinction: a public credit and the underlying agreement have different functions. Keep both, but do not ask either to stand in for the other.

Who should supply the identifiers?

For ISRC, first ask the recording's responsible rights holder or its authorized administrator what has already been assigned. IFPI's FAQ explains that a properly appointed ISRC Manager can assign at the rights holder's instruction. This is not a reason for an unrelated listener to invent codes for a catalog they find online.

For ISWC, the agency's allocation guidance states that creators and publishers do not allocate their own numbers. Authorized registration agencies process the work information; allocation requires the creators to be uniquely identified.

If a collaborator cannot find a work identifier, record the question for the appropriate society or administrator. Do not take “not found in our folder” to mean “no identifier exists,” and do not fill the gap with the recording's ISRC.

How can you audit a small release packet?

Here is Chorus Weather's editorial review method. It organizes questions; it does not assign codes, authenticate ownership, or replace a distributor's submission checklist.

Start a recording list with the working title, exact version label, approved audio-file reference, confirmed ISRC, and the person or organization that confirmed it. Keep a separate work list with the work title, relevant creator information, confirmed ISWC, and its source.

Then connect the records. For the fictional example:

1. Enter Recording A once in the recording list and connect it to Work W.
2. Enter Recording B separately and connect it to that same stipulated work.
3. In the release list, reference Recording A for both the studio release and later album.
4. Keep Recording B's live release as a separate appearance.
5. Attach the actual confirmations and flag anything still unresolved.

The review catches a concrete error: four spreadsheet rows do not necessarily mean four different recordings. Count unique confirmed recording identities, not file mentions or repeated appearances in several documents.

Have the collaborator responsible for delivery check the mapping against the approved audio. A correct-looking identifier attached to the wrong version is still a problem. Preserve corrections with a date and source rather than silently changing the shared record.

What should you do when two records conflict?

Pause the affected submission and preserve both records. Send the relevant agency, administrator, or distributor the exact identifiers, titles, version descriptions, and confirmation references. Ask which record applies and what correction route it requires.

Do not resolve an ownership disagreement by choosing whichever code appears first in search. Do not manufacture a replacement to make a validation warning disappear. These actions would hide the unresolved question rather than answer it.

Before handing the packet back, check three things: each identifier is in the correct field, each recording reference points to the intended version, and every outstanding rights or registration question has an identified person responsible for resolving it. That makes the paperwork useful without claiming it proves more than it does.

Sources

• IFPI: International Standard Recording Code.
• IFPI: ISRC FAQ.
• IFPI: ISRC structure.
• ISWC International Agency: The ISWC.
• IFPI: When not to assign an ISRC.
• IFPI: When to assign an ISRC.
• IFPI: Ownership.
• ISWC International Agency: Guidance for collective management organisations.
• ISWC International Agency: How to get an ISWC number.