Music data · rights literacy · 10 minute read

ISRC vs ISWC:
the identity map behind a song.

A listener sees one title. Music systems may need to distinguish the underlying musical work, a particular recording of it, the release that contains that recording, and the people connected to each layer.

By Jamil Maiss · Published September 4, 2026 · Independent educational commentary

Scope note: This is a plain-language guide to identifier concepts. It does not determine ownership, royalty shares, or confidential contract terms.

Start with the object, not the title

Music fans often use one phrase—“the song”—for several different things. Copyright and metadata systems need more precision. The U.S. Copyright Office distinguishes a musical composition from a sound recording: the composition is the underlying musical work, while a sound recording is a particular fixed series of sounds. A new performance can therefore create a different sound recording while still relating to the same underlying composition.

That difference becomes especially useful when versions multiply. A studio recording, a later re-recording, an acoustic performance, and a live performance may all feel recognizably connected to one composition while remaining distinct recordings. Human-readable titles can describe those relationships, but identifiers help computer systems avoid guessing which object is being discussed.

ISRC: an identifier for a recording

IFPI describes the International Standard Recording Code, or ISRC, as the international identification system for sound recordings and music video recordings. Its purpose is to give a particular recording a persistent reference as that recording moves between services, territories, products, and licensing contexts.

The important word is recording. IFPI explicitly says ISRC is not used to identify musical compositions, performers, or music products. That means an ISRC should not be interpreted as a universal “song number,” a proof of who owns a master, or the identifier for an album package. It points to the recording resource.

ISWC: an identifier for the musical work

CISAC describes the International Standard Musical Work Code, or ISWC, as a globally unique identifier for musical works. The associated information connects a work to its title and creators, including composers, authors, and arrangers. CISAC also makes the boundary clear: ISWC identifies the musical work, not a particular recording, publication, or broadcast of that work.

This gives us a useful two-layer model. The musical work can have an ISWC. A particular sound recording of that work can have an ISRC. Those identifiers answer different questions, so neither replaces the other.

Why one familiar song can have several ISRCs

Imagine a fictional composition called Glass Constellation. The original studio performance is recorded and released. Years later, the artist records the composition again with new vocals and production. Later still, a concert performance is fixed and commercially released as a live recording. The composition can remain the same musical work while the three fixed performances are distinct sound recordings.

From an archive perspective, treating those recordings as interchangeable would erase useful information. Production credits may differ. Performers may differ. Duration, mix, arrangement details, release date, and rights metadata may differ. Distinct recording identifiers help preserve those distinctions.

But the same recording does not need a new identity every time it appears

The opposite mistake is assigning a new conceptual identity every time the exact same recording appears in a different package. IFPI's guidance emphasizes that ISRC identifies the recording rather than the product in which it appears. A recording can therefore move onto a compilation, a later edition, or another delivery format while retaining its recording identity when the underlying recorded resource is unchanged.

DDEX similarly separates resource identifiers from release identifiers in its metadata standards. Its identifier guidance lists ISRC for sound recordings while release-level objects may use product-oriented identifiers such as UPC, EAN, or GRid. DDEX specifically cautions against using an ISRC as the release identifier merely because a release contains a single primary resource.

Identifier does not mean ownership

This distinction matters in fan discussions about catalog ownership. An identifier tells a system which object it is talking about. It does not, by itself, prove who currently owns the copyright, who controls a territory, how royalties are divided, or what a contract says.

CISAC makes a similar point for ISWC: the code identifies a musical work, but it does not itself state the ownership shares of the work. Those shares can involve multiple parties and can vary over time or territory. Rights information therefore needs its own associated data and authoritative records.

Why the release is another layer

A commercial release is a package or offer containing one or more resources. It can have its own title, release date, territory, label, product identifiers, track sequence, parental-warning metadata, and availability information. DDEX's Release Delivery standards model releases and their component resources separately because a release is not the same thing as a recording.

That creates a four-part mental model useful even outside professional metadata work: work → recording → release → availability. The work is the composition. The recording is one fixed performance. The release packages one or more resources. Availability describes where and when the release can be offered. Mixing those layers is the source of many fan-archive errors.

A practical fan-archive workflow

When documenting a version, start with the narrowest verifiable statement. Is this the same recording appearing on a new package, or a newly recorded performance? Are the displayed credits recording credits, composition credits, or release-level metadata? Is the identifier attached to the track resource or to the product? If a service differs from another service, is the difference evidence of a new recording—or simply a metadata discrepancy?

Good archives preserve uncertainty. If you cannot verify whether two files represent distinct recordings, say that. Do not invent an identifier, infer ownership from a code, or treat a storefront title as a complete rights record.

Why this is useful to listeners

Identifiers may sound bureaucratic, but they protect interesting distinctions. They help explain why a re-recording is a new recorded object, why a live version can be tracked separately from a studio version, why the same recording can appear across multiple releases, and why credits need more structure than a single artist-name field.

For TayTV, that makes identifiers a storytelling tool as much as a data topic. They let an archive describe relationships precisely without reproducing copyrighted material. The more accurately the object is named, the less the archive needs to rely on vague claims.