Metadata

Music Metadata: The Distribution Guide That Protects Your Royalties

May 16, 2026 · 9 min read

What music metadata actually is

Metadata is everything that describes a recording except the audio itself: track and artist names, writers and producers, the ISRC and UPC, language, release date, genre, the explicit flag, and the lyrics.

Distributors and DSPs do not listen to your catalog to decide who gets paid. They read the metadata. If a field is wrong, blank, or inconsistent across releases, the money follows the wrong path or sits unmatched.

Think of it as the shipping label on every track. The song can be perfect and still get lost because the label was sloppy.

Why correct metadata pays artists

Royalties are matched, not assigned by goodwill. A streaming service reports usage against an ISRC; a publishing collection society matches a composition against writer and work data. When those identifiers and credits line up cleanly, payments route to the right parties.

When they do not, the play still happens but the payment falls into an unmatched pool. Recovering that money later means claims, disputes, and time. Clean metadata at upload is cheaper than a correction six months after release.

  • Recording royalties follow the ISRC and the rights-holder data attached to it.
  • Publishing royalties follow songwriter splits, the work, and accurate writer names.
  • Featured artists and producers only get credited if you list them, spelled consistently.
  • A wrong release date can reset playlist eligibility and skew chart reporting.

ISRC and UPC: the two codes that route everything

An ISRC (International Standard Recording Code) is a 12-character identifier for a single recording. A specific recording keeps one ISRC for life. If you remaster or release a new version, that new recording gets its own ISRC.

A UPC (or EAN) identifies the release product: a single, EP, or album as a package. One album has one UPC and many ISRCs inside it.

Most distributors assign ISRCs and UPCs for free at upload. DistroKid, CD Baby, and TuneCore all do this. The trap is generating duplicates: never re-upload the same recording through a second distributor that mints a fresh ISRC, or you split the same track's streams across two identifiers and two royalty trails.

  • ISRC = one recording. Reuse it everywhere that exact master appears.
  • UPC = one release product. New release, new UPC.
  • Never let two distributors assign two ISRCs to the same master.
  • Keep a master spreadsheet of every ISRC you own so you stop re-minting them.

Lyrics, language, and the explicit flag

Lyrics are metadata too, and they increasingly drive discovery. Synced lyrics on a DSP come from partners like Musixmatch and LyricFind, who deliver lyric data to streaming services. Musixmatch's human review of submitted lyrics typically takes around two days, so accurate, well-formatted lyrics submitted early save you a launch-week scramble.

Language tags matter for search, recommendations, and lyric matching. Latin catalogs break the simple cases: a track can be Spanish with English hooks, or Spanglish line by line. Tagging a code-switching song as a single language misroutes lyric matching and search.

The explicit tag is a yes/no field that affects playlist placement, radio edits, and family filtering. A clean version mislabeled as explicit can be excluded from placements it qualified for; an explicit version marked clean can get pulled. The call is yours to make per recording, and it has to match the audio.

Common mistakes that quietly lose royalties

Most lost royalties are not theft. They are formatting and consistency failures that nobody catches until a statement comes in light.

Audit against this list before every release, and across your back catalog when you have a quiet week.

  • Inconsistent artist names: "DJ", "Dj", and "D.J." read as three different artists and split your profile and pay.
  • Stuffing features or producers into the track title instead of the proper credit fields.
  • Duplicate ISRCs from re-uploading the same master through multiple distributors.
  • Missing or wrong songwriter splits, so publishing royalties never match.
  • Promo text, version notes, or emojis jammed into title fields, which some DSPs reject or strip.
  • Wrong language tag on bilingual or Spanglish tracks, breaking lyric sync and search.
  • Ad-libs and producer tags mixed into the lyric sheet, which confuses lyric review and timing.
  • A release date that does not match across stores, costing you playlist pitch windows.

Where transcription fits the workflow

Lyrics are the field most teams treat as an afterthought, then rush at deadline. For Latin catalogs that is harder than it sounds: regional slang, dialect, and code-switching trip up generic tools.

Musavox is built for that case. It isolates the vocal from the beat, runs speech recognition, then cleans the result with a language model, using dialect-aware modules for regions like Puerto Rico, Mexico, Colombia, the Dominican Republic, Argentina, and US-Latin, plus Brazilian and European Portuguese.

It separates ad-libs and producer tags from the main lyric, labels song sections, and gives a per-line confidence score so a reviewer knows where to look. You can export a clean lyric sheet, a timestamped LRC for synced lyrics, and catalog metadata, and batch whole catalogs on Pro and Label plans. Its explicit-content flag is an assistive review aid, not a compliance ruling; your team makes the final call. Musavox transcribes and organizes the workflow; it does not clear rights or guarantee legal compliance.

The pre-distribution metadata checklist

Run this before you hit submit. Every "no" is a royalty risk you are choosing to ship.

  • Artist, featured artist, and producer names spelled identically to your past releases.
  • Every recording has exactly one ISRC, and reused masters carry their original ISRC.
  • One UPC per release product, with the right track order inside it.
  • Songwriter splits add to 100% with correct legal names.
  • Language tag reflects the actual sung language, including bilingual and Spanglish cases.
  • Explicit flag matches the audio for each recording.
  • Final lyric sheet proofed, with ad-libs and producer tags separated from the main lyric.
  • Synced lyrics submitted early enough for partner review before release day.
  • Title fields free of promo text, version clutter, and stray characters.
  • Release date identical across every store and pitch deadline.

FAQ

What is the difference between an ISRC and a UPC?

An ISRC is a 12-character code that identifies one specific recording and stays with it for life. A UPC identifies the release product, like a single, EP, or album. One album has a single UPC and a separate ISRC for each track inside it.

Do I have to pay for ISRC and UPC codes?

Usually not. Most distributors, including DistroKid, CD Baby, and TuneCore, assign ISRCs and UPCs for free at upload. The risk to avoid is duplicating ISRCs by re-uploading the same master through more than one distributor.

How do lyrics get onto streaming services?

Synced and static lyrics typically reach DSPs through partners like Musixmatch and LyricFind. Submitted lyrics can go through human review (Musixmatch's review usually takes around two days), so accurate, well-formatted lyrics submitted early help them appear by release.

Why am I not getting paid for plays I can see?

Plays you can see but not get paid for usually trace to metadata mismatches: duplicate or wrong ISRCs, inconsistent artist names, or missing songwriter splits. The usage is reported, but it cannot match your rights data, so the money sits unmatched until corrected.

Related

For distribution teamsFor record labels

Transcribe your catalog with the dialect intact

Vocal isolation, dialect-aware Spanish & Portuguese, ad-lib separation and release-ready exports — start free.