Music Metadata 101: Get Your Release Right the First Time

What metadata actually is, and why it decides whether you get paid

Metadata is just the structured information attached to your release and to each track on it: the titles, the artist and songwriter credits, the genres, the language, the two copyright lines, the barcode for the release, and a code for every recording. None of it is the music. All of it is what the stores read to decide what to do with the music.

Here’s why it’s worth getting right the first time. When you deliver to Spotify, Apple Music, and Amazon, a machine checks your fields before a human ever sees the release. Clean metadata gets accepted, your streams get tracked to the right recording, and your royalties get routed to the right owner. Broken metadata gets you one of four bad outcomes: a rejected upload, a delayed release while you fix it, split streaming numbers when a duplicate code shows up, or royalties that quietly go to the wrong place. The last one is the worst because nothing looks broken. The release goes live, the money just isn’t yours.

The good news is that the things that go wrong are a short, knowable list. Below is the producer’s version of that list, in the order that actually costs people. We start with the ℗ and © lines, because that’s the field most independent artists get wrong and the one with a direct money consequence.

℗ vs ©: the part most people get wrong

There are two copyrights in any release, and they cover two different things. ℗ (the circled P, for “phonogram”) covers the sound recording: the specific master you uploaded. © (the circled C) covers the underlying song, meaning the composition and the lyrics, and at the release level it also covers the artwork. Same release, two separate rights. The form fields ask for both because they answer two separate questions: who owns this recording, and who owns this song.

The format is the same every time: the symbol, then a 4-digit year, then the owner name. As a constructed example, a fully DIY artist would write ℗ 2026 Your Name and © 2026 Your Name. That order is what the copyright statute and the DDEX metadata standard expect, so distributors validate against it.

If you recorded and wrote everything yourself, your name (or your company) goes on both lines and they match. If a label owns the master, ℗ is the label and © is you or your publisher. That difference is correct, not an error, so a good checker treats a mismatch as a nudge to confirm, not a failure. The mistakes that genuinely get flagged are these:

• Leaving the field blank. The distributor fills it with its own name (you’ll see something like ℗ 2026 SomeDistributor.com). That’s the wrong owner on record, and since SoundExchange and PPL read the ℗ line to decide who collects the master’s performance royalties, it can send your money somewhere else.
• Typing (P) or (C) instead of ℗ and ©. The ASCII versions are fallbacks for when the real symbols can’t render. The statute and DDEX want the circled characters.
• Missing the year or the owner, doubling the symbol, or swapping ℗ and © between the recording and the song.
• Using the re-release year on a reissue instead of the original first-publication year.

ISRC: the code for each recording

An ISRC is the unique ID for a single recording. It’s exactly 12 characters: a 2-letter country or allocator code, a 3-character registrant code, a 2-digit year, and a 5-digit number. As a constructed example, USRC17607839 fits that shape. You’ll sometimes see it written with hyphens or with the word “ISRC” in front, but those are display only. The stored code is the 12 characters.

One thing that confuses people: the first two letters aren’t always a real country. QM, QZ, and QT are US pools, ZZ is the international agency, and CP and DG are overflow codes. They’re all valid, so if a code starts with one of those, it isn’t broken. A checker that rejects them as a bad country code is the thing that’s wrong.

The key idea is that an ISRC identifies the recording, not the song. Two different recordings of the same song get two different ISRCs. So a remix, an edit, a live take, or any version whose playing time changes by more than 10 seconds is a new recording and needs its own new ISRC. The flip side matters just as much: the identical master keeps its ISRC forever.

Last thing: never paste a UPC into the ISRC field. A UPC is all digits and a different length, so it can’t be a valid ISRC, and that mix-up is a common cause of a rejected delivery.

UPC / EAN: the code for the whole release

A UPC is the barcode for the release as a product. UPC-A is 12 digits, EAN-13 is 13 digits, and they’re the same family (GTIN). A 12-digit UPC is just a 13-digit EAN with a leading zero, which is why one validator handles both.

The rule to remember is one release, one UPC. A 10-track album has one UPC and ten ISRCs. And a single is a separate product from the album it later appears on, so it gets its own UPC. The single’s recording keeps its ISRC when it lands on the album, but the album as a product is a new UPC.

The last digit of a UPC is a check digit, and it’s computed with the GS1 modulo-10 algorithm, not the Luhn algorithm you might know from credit cards. A real validator recomputes that digit from the rest of the number. If it doesn’t match, the barcode is mistyped or fake, and the distributor will bounce it. (A useful detail: because the leading zero adds nothing to the math, a UPC-A and its leading-zero EAN-13 share the same check digit, so one routine checks both.)

Titles, artist names, and featured artists

The fastest way to get a title rejected is to put things in it that belong in their own fields. The featured artist is the big one. Put the feature in the artist credits with the Featuring or With role, not in the title. The store adds “(feat. X)” to the display automatically from that role. If you also type it in the title, you get the credit twice, like Song (feat. X) (feat. X).

If you do write it for some reason, the only accepted form is lowercase (feat. X) with the period, or (with X). Featuring, Feat, ft., FT, and w/ all get rejected.

Version words work the same way. Remix, Live, Acoustic, Instrumental, Radio Edit, Extended Version: those go in the Version or Subtitle field, not the base title, and you don’t type the parentheses because the platform adds them. Skip “Original Mix” entirely. The original is what you get when the version field is empty, so labelling it is redundant and gets flagged.

Language, explicit status, genres, and credits

Set the lyrics language on every track, and make it match what’s actually sung. An instrumental with no vocals isn’t a language at all; it uses ZXX, which means “no linguistic content.” If you mark a track instrumental, don’t also give it a lyricist credit, because a lyricist on a track with no lyrics is a contradiction that gets caught.

Explicit status is a flag, not something you type in the title. A track you tag Clean that actually has profanity in it is a rejection. A real clean version is a separately edited audio file, not a relabelled explicit one.

Keep genres tight: one primary, one optional secondary, and they can’t be the same value twice. Some categories need their matching primary genre to go through, soundtracks, karaoke, and classical among them.

Dates and pre-release lead time

Give yourself room. Set the release date at least about a week out so the stores and the editorial playlists have lead time to work with. For a brand-new release, the original release date and the consumer release date are the same. The one rule the system enforces is that the original release date can’t be after the consumer release date, and if you set a preorder date it has to fall before the release date.

The exception is the re-release. The new consumer release date is recent, but the ℗ line keeps the original first-publication year. Those two dates living apart is correct for a reissue, and it’s the single thing people most often get backwards.

Check it before you deliver

That’s the whole list. Two copyright lines in the right order with the first-publication year, one ISRC per recording and one UPC per release, features and version words and explicit status in their own fields, a language on every track, and a songwriter on every vocal track. None of it is hard. It just has to be right, because the part that goes wrong is usually the part you can’t see after the release is live.

So check it before you hit deliver. Paste your fields into the free metadata checker and it’ll flag the copyright format, the ISRC and UPC (including the check digit), the title issues, and the missing credits, so you fix them now instead of after a rejection.

run your release through the free metadata checker →