Essential Music Metadata Checklist for Distribution

Essential Music Metadata Checklist for Distribution

Last Updated: November 11, 2026

Quick Summary

Essential music metadata for distribution includes a release title and version, track titles, primary and featured artists, label, genre, release date, territory, copyright line, and a unique ISRC for each track plus a UPC for the release. Accurate music metadata lets stores credit the right artist and route royalties correctly, so verify every field before upload.

  • Standardize each artist name's spelling across every track and release-level field.
  • Assign a new ISRC to each distinct recording, including remixes and radio edits.
  • Keep one master spreadsheet and build every release from it.
  • Get split sheets signed by all contributors before any release goes live.
  • Re-export artwork at 3000 x 3000 pixels in RGB with no added text or borders.
Ready to get your releases onto Beatport?NexaTunes gives labels unlimited sublabels, monthly royalty payouts and detailed label-level reporting.
Start Your Label Release

Table of Contents

Getting music onto Beatport, Traxsource and the big streaming services depends less on the audio than on the data attached to it. Clean, complete metadata is what lets a platform's systems credit the right artist, match the right release to the right ISRC, and send royalties to the right place. This checklist from NexaTunes walks through each field a release needs before you hit upload, and explains what to fix when a submission gets bounced. For the exact Beatport metadata and formatting requirements, check the official specifications before you resubmit.

What Is Music Metadata and Why Accuracy Matters

Music metadata is the descriptive information attached to a recording, including the title, artist names, genre, release date, label, and identifier codes. Digital service providers read this data to catalog, search, and pay out your music, so errors in one field can ripple across every store your release reaches.

A mistyped artist name can split your streams across two profiles. A missing ISRC can stall a release for days. Inaccurate credits can misdirect royalties, and that is where the financial cost shows up. Accurate metadata is the cheapest protection you have for the income your music generates.

Core Metadata Fields Every Release Needs

Every release needs a consistent core set of fields. Fill these in before you start an upload, so you are not hunting for information mid-form:

  • Release title and version (for example, "Original Mix" or "Radio Edit")
  • Track titles, in running order
  • Primary artist and any featured artists
  • Label name and label copy
  • Genre and sub-genre
  • Release date and original release date
  • Territory availability
  • Copyright line (phonographic and composition)
  • ISRC for each track and a UPC for the release
  • Explicit content flag, where applicable

Keep a single master spreadsheet with these fields for every release. Copying from one shared source prevents the small inconsistencies that trigger rejections.

Format names exactly the same way on every release. If you use "DJ Nova" on one track, do not use "DJ NOVA" or "Nova" on the next. Platforms treat each variation as a separate artist profile.

Put remix and version information in the title field, not the artist field. Use "feat." or "ft." consistently for featured artists, and place the featured artist in the designated featured field instead of appending it to the title. Avoid putting artist names inside the track title itself, since many stores flag that as a formatting error.

Genre, Mood Tags and Release Date

Choose genres from the platform's own taxonomy rather than inventing labels. Beatport and Traxsource organize electronic music into specific sub-genres, and choosing the closest match improves discoverability within the right charts and playlists. Mood tags can help listeners find your track, but they should describe the music honestly.

For release dates, confirm the date you actually intend to go live. Submitting too close to the date can leave you without a pre-release window, and some stores require lead time before a release date can be locked.

ISRC and UPC for Music Distribution

An ISRC (International Standard Recording Code) identifies an individual recording. A UPC (Universal Product Code) identifies the release as a whole. Stores use both to track your music, so both need to be correct, and the mechanics of how each code is issued, structured, and verified matter more than most checklists admit.

An ISRC (International Standard Recording Code) is a standardized code that identifies an individual recording. It is issued through the national agencies that administer the international ISRC system, and it combines a country code, a registrant code, a year of reference, and a designation code (How It Works). The registrant code belongs to whoever registers the recording, and the designation code distinguishes recordings from one another.

A UPC is a product identification number, often issued through a distributor or a standards organization. For a side-by-side look at which code applies to your release, compare the two identifiers before you upload. Distributors commonly assign a UPC automatically when you create a release, which is convenient but means the code is tied to that distributor's catalog.

For a single, you typically need one UPC for the release and one ISRC for each track on it. For an EP or album, the same logic applies: one UPC at the release level, one ISRC per track. If you are unsure whether a single release needs its own code, the answer depends on whether it is a different product.

Verification is where most errors surface. Before upload, confirm three things: that every ISRC in your master spreadsheet matches the code your distributor has on file, that no ISRC appears twice across your catalog, and that the UPC on the release matches the one in your distributor dashboard.

Watch out: if you register your own ISRCs through the RIAA, keep the registrant code and designation log in a single document. Distributors cannot always see codes issued outside their system, and a code that exists in your records but not in theirs will read as missing at upload.

RIAA ISRC information

Song Metadata Template: Credits, Splits and Publishing

Credits and splits are where the most costly errors happen. Before submitting, document the following for every composition:

  • Songwriter names and their legal names as they appear on agreements
  • Each writer's percentage share of the composition
  • Publisher name and any co-publisher
  • Producer and mixing/mastering credits
  • Performance rights organization (PRO) affiliation for each writer, if applicable

A simple split sheet signed by every contributor before release protects everyone. Mechanical and performance royalties are paid based on these shares, and disputes over unsigned splits are common. If a contributor is not on the paperwork, they generally cannot be paid for work they did not have documented.

Album Metadata Examples and Artwork Specifications

Album metadata follows the same logic as single metadata, applied across the full tracklist. Track numbering should run sequentially, disc numbers should be set for multi-disc releases, and each track should carry its own ISRC alongside the album's UPC.

Music producer reviewing album artwork and track list music metadata on a laptop in a home studio
Music producer reviewing album artwork and track list music metadata on a laptop in a home studio

Artwork requirements vary by store, but a common specification is a square image at a minimum of 3000 x 3000 pixels in RGB color, saved as JPG or PNG, with no added borders and no text beyond the title and artist name. Confirm the current specification with your distributor, since platforms update these requirements.

For example, a four-track EP might list the release title and UPC once at the album level, then four separate track entries, each with its own title, ISRC, featured artists where applicable, and the same primary artist spelling. Reviewing the album as a whole, then each track individually, catches errors that a single pass misses.

Music Metadata Best Practices and Troubleshooting Rejections

Most rejections come down to a handful of repeatable problems, and each one maps to a specific field you can fix. To go beyond fixing rejections and raise metadata accuracy going forward, build the habits below into your routine. The table below is the fix-it guide most checklists skip: match the rejection reason in your distributor notice to the likely cause, correct the source in your master spreadsheet, then update every affected track before resubmitting.

Rejection reason Likely cause Fix
"Artist name mismatch" Primary artist spelled differently across tracks or versus the release-level field Standardize to one spelling in the master file; update every track and the release-level artist field
"Duplicate ISRC" Same code assigned to two recordings, often from a copy-paste in the spreadsheet Assign a new ISRC to the second recording; never reuse a code across mixes
"Missing ISRC" Code not yet issued by the distributor, or issued outside the distributor's system Request the code through the distributor dashboard before upload; log it in the master file
"Artwork resolution too low" Image below 3000 x 3000 pixels or saved in a non-RGB color space Re-export at 3000 x 3000 RGB, JPG or PNG, no borders
"Artwork contains prohibited content" Store logos, URLs, social handles, or pricing on the image Remove all text beyond artist name and title; re-export
"Title contains artist name" Artist name appended to the track title instead of the artist field Move the name to the primary or featured artist field; keep the title clean
"Explicit flag missing" Track contains explicit lyrics but the flag is set to clean Set the explicit flag per track; do not rely on a release-level default
"Release date too close" Date submitted inside the store's lead-time window Push the date out to meet the longest lead time among your target stores

When a submission is rejected, read the specific reason in the notice rather than resubmitting unchanged. Distributor notices usually name the field and the track, so the fix is narrow, but the same error often exists on other tracks in the same release, which is why you correct the master file first and then rebuild the release from it.

Several habits prevent most problems:

  • Maintain one master file and build each release from it
  • Verify ISRCs against your records before upload, checking for duplicates across the catalog
  • Confirm split sheets are signed before any release goes live
  • Check artwork dimensions, color space, and text content before exporting
  • Do a final read-through of every name and title against the master
  • Keep a rejection log so repeat causes become visible over time

A common pattern is that labels hit the same two or three rejection reasons across releases because the error lives in the template, not the release. Fixing the template once, the artist-name field, the artwork export preset, the ISRC log, eliminates the category rather than the instance.

If you want a clearer view of how your releases are performing and where your royalties come from, NexaTunes provides detailed label-level royalty reports.

Booking Your Next Release Through NexaTunes

Clean metadata helps releases move smoothly through distribution, and it supports accurate label-level reporting across your sublabels and artists. NexaTunes gives labels unlimited sublabels and artists, monthly royalty payouts, and detailed label-level reports. Pricing depends on your catalog and needs, so visit the NexaTunes website or request a quote for current details.


Frequently Asked Questions

What metadata do I need to distribute a song?

At minimum, a release needs a track title, primary artist name, any featured artists, songwriter and producer credits, genre, release date, label name, copyright line (the (P) and (C) information), and an ISRC for each recording. Services like NexaTunes will ask for these fields during upload, and missing or inconsistent entries can delay delivery. Gather them in a spreadsheet before you start the upload so every track and album uses identical spelling for artist and label names.

Do I need an ISRC and UPC before distributing music?

You need a UPC for the album or single as a whole and an ISRC for each individual track. Some distributors assign these codes for you, but if you already own codes, you can supply them yourself to avoid duplicates. Reusing an ISRC on a different recording can cause conflicts on streaming platforms, so check any code you enter before submitting the release.

How do I prepare music metadata for a release?

Start with a single source document that lists every track, its version (original, remix, radio edit), each contributor and their role, and the release date. Confirm the spelling of artist names against your existing profiles on streaming services, and make sure artwork meets the required resolution, which is commonly 3000 x 3000 pixels in RGB. Review the full document once more before uploading, since corrections after delivery often take longer to process.

How can incorrect music metadata affect royalties and release delivery?

Incorrect credits can send royalties to the wrong party or leave earnings unclaimed, because collection societies and performance rights organizations match payments to the songwriter and publisher data you supply. Mismatched titles or artist names can also cause a release to be flagged or taken down during review. Fixing these problems after the fact usually requires a correction request and can delay payouts, so accuracy at upload saves time later.

If you’re looking for a reliable way to distribute your music to major platforms, NexaTunes offers direct distribution with transparent terms.

Learn more
“Running a label? Get fair Beatport & Traxsource access without flat fees. Our Features Contact Sales