Music metadata is the invisible infrastructure of the modern music industry. It's what tells streaming platforms who made a song, who owns it, who the co-writers are, what the BPM is, and hundreds of other data points that determine how music is categorized, recommended, and — most critically — how royalties get matched to rights holders. Incorrect or missing metadata is the single most common reason royalties go uncollected. Understanding it isn't optional for serious artists and producers.
Music metadata is the descriptive information embedded in or associated with a music file — artist name, title, release date, songwriter credits, ISRC code, and dozens of other fields. Every major streaming platform, PRO, and royalty collection organization uses metadata to match streams and uses to registered rights holders and distribute payments. Missing, incorrect, or inconsistent metadata is the primary reason royalties end up uncollected in the music industry's hundreds-of-millions in "unmatched" funds.
Core Metadata Fields — Every One Matters Beginner
These are the fields that every artist and producer must get right for every release. Getting them wrong doesn't produce an error message — it produces unmatched royalties that may never reach you.
| Field | What It Is | Why It Matters | Common Error |
|---|---|---|---|
| Track Title | Official name of the recording | Search and display; must match PRO registration exactly | Inconsistent capitalization or punctuation between platforms |
| Artist Name | Performing artist(s) | Links to artist profile; affects search | Spelling variations creating duplicate artist profiles |
| ISRC Code | International Standard Recording Code — unique ID for each recording | Used by every platform to track streams; links master to royalty payments | Generating a new ISRC for each upload of the same recording |
| ISWC Code | International Standard Musical Work Code — unique ID for each composition | Used by PROs and publishing organizations to match compositions to registrations | Not registering for ISWC codes at all |
| Songwriter Credits | Full legal names of all composition co-writers | PROs use this to distribute performance royalties; MLC uses for mechanical | Using stage names instead of legal names; omitting co-writers |
| Publisher Information | Name of music publisher or self-publishing entity | PROs split publisher share based on this registration | Not registering publisher entity; leaving publisher field blank |
| Release Date | Official public release date | Affects editorial pitching windows; chart eligibility | Inconsistent dates between distributor and streaming platforms |
| Genre | Primary and secondary genre classification | Affects algorithmic recommendation and editorial categorization | Selecting incorrect genre for marketing reasons vs. honest categorization |
| Language | Language of lyrics | Affects regional recommendation and PRO reporting | Not updating for non-English tracks; marking instrumental as English |
ISRC Codes — The Recording's Identity Beginner
The ISRC (International Standard Recording Code) is a 12-character alphanumeric code that uniquely identifies a specific sound recording. Think of it as the barcode for your track — every streaming platform uses it to track how many times that specific recording has been played, and it's the primary key that connects streams to master royalty payments.
Most music distributors generate ISRC codes automatically when you upload a track. The critical rule: one ISRC per recording. If you upload the same recording multiple times (for different releases, different regions, or after correcting a metadata error), each upload gets a new ISRC unless you specify the existing one. Multiple ISRCs for the same recording fragment your stream data and can cause royalty calculation problems. Keep a spreadsheet of every ISRC you've been assigned, with the corresponding track title, release, and distributor. This record becomes important when registering with PROs, the MLC, and SoundExchange.
ISWC Codes — The Composition's Identity Intermediate
The ISWC (International Standard Musical Work Code) is the composition-level equivalent of the ISRC — a unique identifier for a specific composition (song) rather than a recording. Where the ISRC identifies the master recording, the ISWC identifies the underlying composition that could be recorded by multiple artists.
ISWC codes are assigned by your PRO when you register a composition. Unlike ISRCs, they're not automatically generated by distributors — you need to actively register your compositions with your PRO and request ISWC codes. Once assigned, the ISWC travels with the composition globally and is used by collection societies worldwide to match performances and mechanical uses to the correct rights holders. Many independent songwriters never register for ISWC codes and lose international royalty matches as a result.
Embedded vs Delivery Metadata Intermediate
Metadata exists in two forms: embedded metadata (written into the audio file itself using ID3 tags for MP3, or Vorbis comments for FLAC) and delivery metadata (submitted separately to distributors and PROs through their registration systems).
For streaming purposes, delivery metadata submitted to distributors takes precedence over embedded file metadata — Spotify reads the information you entered in DistroKid, not the ID3 tags in the file. But embedded metadata matters for: files distributed directly to collaborators, sync pitches, files uploaded to SoundCloud or Bandcamp, and any context where your file is shared independently of your streaming release. A professional practice: always embed correct metadata in every audio file you distribute, even if the delivery platform has its own separate metadata system.
The Direct Connection Between Metadata and Royalties Advanced
Here's the specific mechanism by which metadata errors cost you money. The MLC (Mechanical Licensing Collective) receives streaming usage reports from Spotify and other platforms that contain ISRC codes. It attempts to match those ISRCs to compositions registered in its database. If your ISRC doesn't match a registered composition (because you registered the composition with a different title, because the ISRC on the stream report is different from the ISRC you registered with, or because you never registered with the MLC at all), the mechanical royalties generated by those streams go into the "unmatched works" pool. The MLC holds these funds and attempts to match them, but unmatched funds that can't be resolved within a certain period are distributed among registered rights holders — meaning other songwriters effectively receive the money that should have been yours.
The same logic applies to performance royalties through PROs. Your PRO needs to match the song title and songwriter names on performance reports from platforms to your registered compositions. If your composition is registered as "Take It Easy (featuring Maria)" but the streaming report lists it as "Take It Easy," the match may fail. Consistency between how you register compositions and how they appear in streaming metadata is not a bureaucratic nicety — it's a financial necessity.
Before every release, verify: (1) track title matches exactly across distributor, PRO registration, and MLC registration; (2) songwriter names are legal names, not stage names; (3) ISRC is consistent and not regenerated; (4) publisher entity is registered and credited; (5) co-writer splits are documented in writing and registered with PRO. Five checks, five minutes, prevents years of royalty problems.
Metadata connects to royalties through the MLC, PROs, and SoundExchange — understanding how those systems work clarifies why metadata accuracy matters.
Spotify-specific metadata requirements and how to set up your artist profile correctly from the first release.
The technical standards organization for music metadata and digital supply chain communications. Their documentation defines the metadata standards that every major platform and distributor follows.