Skip to main content

How To Import Your Releases In CSV Format (Metadata)

This guide explains how to fill in the CSV file used to import releases into the platform.

Important

  • The CSV file must be sent to the support team so we can run the import.

  • You don't have to fill in every field.

  • The only fields currently required are upc and isrc.

  • If some data is missing, the release can still be imported and completed afterwards from the edit form on the platform.

  • The more information the CSV contains, the fewer manual adjustments will be needed after the import.

  • An import can fail if the file format is invalid or if the information is inconsistent. If that happens, the support team will get in touch to help you resolve it.


General rules

  • Each row represents one track.

  • All rows belonging to the same release must share the same upc.

  • Each track must have a unique isrc.

  • Audio files and cover art must be available at public URLs.

  • Do not rename or delete the column headers.


Release fields

These fields describe the general information for the release.

Column

Description

upc

UPC code of the release

catalog_number

Catalog number

title

Release title

release_remix_or_version

Version or remix of the release

label

Record label name

release_participants

Artists and participants on the release

release_primary_genre

Primary genre

release_secondary_genre

Secondary genre

release_language

Language code (for example: en, es)

release_explicit_lyrics

Whether the release contains explicit content (yes or no)

digital_release

Digital release date

original_release

Original release date

c_year

Copyright year

c_line

Copyright line

release_p_year

Phonogram year

release_p_line

Phonogram rights holder

cover_url

Public URL of the cover art


Track fields

These fields describe each track.

Column

Description

isrc

ISRC code of the track

track_title

Track title

track_remix_or_version

Version or remix of the track

track_participants

Artists and participants on the track

track_language

Language code

track_explicit_lyrics

Whether the track contains explicit content (yes or no)

track_p_year

Phonographic copyright year

track_p_line

Phonographic copyright line

audio_url

Public URL of the audio file


Participant format

Participants must follow this format:

role:name;role:name

Example:

primary:Juan Pérez;featured:María López;producer:Carlos Gómez

Currently supported roles:

  • primary

  • featured

  • composer

  • lyricist

  • producer

  • executive_producer

  • assistant_producer

  • vocal_producer

  • performer

  • vocalist

  • soloist

  • choir

  • orchestra

  • ensemble

  • arranger

  • adapter

  • songwriter

  • conductor

  • director

  • assistant_director

  • creative_director

  • art_director

  • remixer

  • mixer

  • sound_engineer

  • recording_engineer

  • mastering_engineer

  • assistant_engineer

  • assistant_mixing_engineer

  • assistant_recording_engineer

  • assistant_sound_engineer

  • assistant_mastering_engineer

  • engineer

  • sound_editor

  • post_producer

  • graphic_designer

  • cover_designer

  • photographer

  • production_assistant

  • publisher


Language codes

Example:

Code

Language

en

English

es

Spanish


Example

upc,title,isrc,track_title
123456789012,My Album,USRC17607839,My Song
123456789012,My Album,USRC17607840,Another Song

Both rows belong to the same release because they share the same UPC.


Sample file

A sample CSV file is available with all the headers and a complete example of how to load a release. You only need to fill in the rows with the information for your release and its tracks.

We recommend using it as your starting point.


Did this answer your question?