Music Distributor Metadata Requirements: What Counts

November 9, 2026·by TrackTag team

Music distributor metadata requirements start with the delivery record

Music distributor metadata requirements are the information a distributor needs to identify your recording and release, deliver them to stores, and display the right details to listeners. The exact upload form varies by distributor and destination, so there is no single universal set of required boxes. But the important distinction is consistent: delivery metadata is not the same thing as every detail a label, library, or rights team may want to keep in its catalog.

Think of a release as two connected records. The release record describes the product, such as a single or album. The track record describes each recording on it. A release might have one UPC, while each distinct track has its own ISRC. Apple says its delivered products need a unique UPC, EAN, or JAN, and each song or music video needs an ISRC. (itunespartner.apple.com)

If you are preparing one single, you may enter everything in a distributor dashboard. If you are delivering a label catalog, those same facts may live in spreadsheets, a delivery system, or a metadata feed. Either way, separate the fields needed to get a release accepted from the richer information you need to find, license, report on, or reuse your music later.

What the upload form usually needs

Exact requirements vary by distributor and platform. Use this as a preparation list, then check the current instructions in your distributor account before delivery.

Release information commonly includes the release title, primary artist, release date, release type, cover artwork, and the countries or territories where the release can be sold or streamed. A product identifier, usually a UPC or an equivalent, identifies the release. For a multi track release, provide the track order and each track title. Apple’s delivery guidance, for example, treats product identifiers as unique and non reusable. (itunespartner.apple.com)

Recording information usually includes a track title, artist credits, the audio asset, and an ISRC if you already have one. Some distributors assign identifiers during upload, so an empty ISRC field does not always mean you need to stop and obtain a code yourself. Ask who will assign it and save the final code in your catalog. The IFPI explains that ISRCs identify recordings, and that a recording owner or an ISRC manager may assign them. (isrc.ifpi.org)

Display and safety fields may include an explicit content flag, language, genre, and version information such as instrumental, remix, or live. Artist roles and credits can also matter for how a release is presented. Spotify says the label or distributor supplies the metadata it displays, including artist names and roles, and that it uses the delivered information to show a release. (support.spotify.com)

Treat fields as conditional if the form asks only when relevant. A cover song, sample, or restricted territory may trigger extra declarations or documentation. Do not mark a field as optional just because one distributor did not ask for it. Another distributor, store, or delivery route may require it.

What a distributor often ignores, or does not deliver

“Ignored” does not necessarily mean a field has no value. It means it may not be part of the distributor’s store delivery, may not be supported by the service, or may not be shown to listeners. Keep these categories separate.

Deep descriptive tags: subgenre detail, mood, emotion, theme, occasion, instrumentation, vocal style, song structure, and production notes can be useful to a sync team or a music library. They are not a universal prerequisite for putting a release on streaming services. A distributor may accept one broad genre and never offer fields for the rest.

Internal library fields: cue sheet status, internal catalog number, delivery notes, rights contact, target brief, alternate mix relationship, and searchable keywords are useful operational data. A distributor may not have a box for them, and the DSP may not receive them. Keep them in your own catalog rather than squeezing several meanings into the title field.

Detailed ownership and publishing records: some upload forms collect songwriter or contributor credits, but do not assume that uploading a track completes registrations, confirms splits, or records every rights relationship. Spotify says it displays credits delivered by labels or distributors, while noting that some distributors do not support credits. (support.spotify.com) Record ownership, composition ownership, contributor roles, and royalty splits should be managed in the relevant systems and agreements, not inferred from an ISRC or UPC.

Audio measurements and creative analysis: BPM, key, energy, detailed mood tags, and descriptive notes can help you search your own catalog, but they are not generally required fields for a basic release submission. Do not mistake a useful internal catalog field for a distributor validation requirement.

A practical rule: if a field affects identification, display, delivery, rights declarations, or platform policy, treat it as submission critical. If it helps your team search and reuse a track, preserve it in your catalog even if the distributor never asks for it.

Genre: delivery choice, not a universal song truth

A distributor may ask you to select a primary genre and sometimes a secondary genre. Choose the closest available category in that distributor’s menu. These menus are controlled vocabularies, not a full description of everything a recording sounds like. A track can be leftfield electronic with jazz harmony and ambient textures, yet the upload form may allow only one broad category.

This is why “get song genre” can mean two different jobs. For delivery, you need a sensible selection from the distributor’s options. For catalog search, you may want several descriptive tags that reflect the actual audio. Keep the required selection concise, then keep richer descriptors in your own records.

Searching “get song genre Spotify” can also lead to confusion. Spotify’s public help describes metadata as information delivered by a label or distributor, while its playlist pitch form asks artists to submit details such as genre and mood for editorial context. Those are different workflows. A genre answer or mood tag used for pitching is not proof that the distributor requires the same field for release ingestion. (support.spotify.com)

If you need to check an existing track rather than choose a submission category, try TrackTag’s free genre lookup tool. It can help you investigate a recording, but use your distributor’s own genre menu for the actual delivery selection.

A release preparation workflow for artists and catalog teams

1. Create one release record and one record per recording. Store release title, release artist, release date, release type, and UPC at the release level. Store track title, version, artist roles, audio file reference, and ISRC with each recording. Do not use one release code as a substitute for the recording codes.

2. Confirm identifiers before delivery. If you already have an ISRC or UPC, copy it from a reliable catalog or distributor record, not from a guess based on a code format. If the distributor will assign one, capture it after assignment. For an existing release moved to a new distributor, ask the new provider how to submit it as an existing recording, and preserve the identifiers and core metadata when appropriate.

3. Standardize names and credits. Match artist spelling, punctuation, featuring credits, track order, and version labels across your release sheet, audio files, and upload form. Spotify says artists should be entered consistently and roles should be provided as distinct credits, rather than folded into titles. (support.spotify.com)

4. Complete required declarations honestly. Check explicit content, language, genre, territories, and any rights or sample questions that apply. If a field is unclear, consult the distributor’s help center before submitting. Do not put extra keywords into a title to compensate for a missing descriptive field.

5. Keep the useful fields the form omits. Preserve detailed genre and subgenre, mood, themes, instruments, vocals, BPM, key, structure, and production notes in your own searchable catalog. If you are handling a backlog, TrackTag Studio batch audio analyzer returns up to 35 fields per track, including those descriptors, plus measured BPM and key. You can export whole batches or selected files in formats such as CSV, XML, JSON, and PDF. That is an enrichment workflow for your catalog, not a substitute for distributor submission requirements.

For a larger library or label, a single source of truth prevents the release sheet, distributor form, and internal catalog from drifting apart. See the catalog preparation guide for a way to organize information before delivery.

Labels and distributors are separate metadata fields

A label name identifies the imprint associated with a release. The distributor is the service delivering the release to stores. An independent artist can use a distributor without having a separate record label, and a label can use different distributors for different catalogs or territories. Do not enter the distributor’s name in the label field unless the release is genuinely presented under that label name.

This distinction matters beyond the upload. Spotify says its label catalog views are based on distributor and label names in release metadata. It also recommends checking label name spelling when a release is missing from a label catalog. (support.spotify.com) If you are reconciling an unfamiliar company name, TrackTag’s distributor lookup and label lookup can help with those identification questions. A lookup is a research aid, not a replacement for the label or distributor field your delivery account requires.

The phrase “record labels numbers” may refer to several different things: a label’s catalog number, a label code, a UPC, or an ISRC. These identifiers do not mean the same thing. Keep the label’s own catalog number as an internal reference unless the distributor specifically asks for it, and do not use it in place of a standard release or recording identifier.

FAQ

What metadata does a music distributor require?

Usually, a distributor needs enough information to identify the release and recordings, deliver the audio and artwork, credit artists, and apply relevant release settings. Common fields include titles, artists, release date, genre, explicit status, territories, UPC, and ISRC, but requirements vary. Check the current form and guidance for your specific distributor.

Does a distributor require me to provide an ISRC?

Not always. Some distributors let you provide an existing code, while others can assign one during submission. Ask which applies, and save the assigned code with the recording so you can identify it consistently later.

Do I need to enter a song’s genre for Spotify?

Your distributor may require a genre selection as part of its delivery form, but that does not mean Spotify requires every artist to supply a detailed genre profile for each track. Spotify displays delivered metadata and also has a separate editorial pitching workflow that asks for genre and mood details. Use the correct form for the task. (support.spotify.com)

What information should I keep if the distributor does not ask for it?

Keep the fields your team will need to search, license, report on, or deliver the recording again. That can include detailed genre tags, mood, instrumentation, BPM, key, version relationships, rights notes, and internal catalog references. Store them in your own catalog rather than assuming the distributor or streaming service will retain them.

Tag your whole catalog with AI

BPM, key, genre, moods, instruments and keywords: 30+ fields per track, exported ready for libraries.

Open TrackTag Studio →

← All posts·In-depth guides