๐Ÿ’ฟ

Releases & submissions

7 articles Simon By Simon

Releases & submissions

How a release moves from draft to live

Every release follows the same path. You can watch it move through each stage on the release page. 1. Draft - you are still building it. Nothing is sent yet. 2. In review - you sent it to the label. We listen and check it. 3. Agreement - we accepted it. Your contract is being prepared, then sent for you to sign. 4. SACEM registration - for publishing, the works are declared and we wait for validation. 5. Distribution - your release is being delivered to stores and streaming platforms. 6. Live - it is out in the world. At each step a short banner tells you where things stand and whether anything is waiting on you (for example, "Your contract has been sent - please sign it to continue"). If we ask for changes Sometimes we send a release back with a reason ("Changes requested"). Fix the points listed and resend. It goes back into review. After it is live You can still request an edit to a live release. See "Editing a release that is already live".

Creating and sending a release

A release starts as a song and becomes a release when you send it to us. 1. Start it From Releases, choose New song, or start from a song you already have in your Studio tracker. A release can hold several songs, so you can add more later. 2. Fill in the release - Release title - Release date (at least 10 days out, see the release-date article) - Cover artwork (square, see the artwork article) - Label is set by our team when we accept it. 3. Complete each song For every song: title, DJ-store genre, genre, audio language, and the master audio file. Set the splits so credits total 100%. Add the ISRC only if the track was previously distributed. 4. Check the checklist A footer checklist lists exactly what is left before you can send, for example "Add a release title" or "Complete song #1". When it says Ready to send, you are good. 5. Send Click Send for review and confirm. It goes to the label. You can request changes afterwards, so sending is not final. If the Send button is locked, finish your profile setup first (name, one social link and a photo).

Audio and artwork requirements

Stores are strict about files. Meeting these upfront avoids rejections and delays. Audio master - Upload a lossless file: WAV, FLAC or AIFF. - Use the best-quality master you have. No MP3s or other lossy files. - After upload the file is stored, then processed. You will see Ready when it passes, or Rejected if something is wrong (upload a new master in that case). Cover artwork - Must be a perfect square. - Minimum 1500 x 1500 px. We recommend 3000 x 3000 px for best quality. - JPG, PNG or WEBP, up to 30 MB. - No blurry images, and no store logos (Spotify, Apple, and so on) on the cover. If your image is not square or too small, the uploader tells you the exact size it detected so you can fix it.

Choosing a release date

The release date is when your music goes live in stores. Two things guide your choice. At least 10 days ahead We need about 10 days of lead time to deliver your release to every store before the date. The date picker will not let you choose anything sooner. We suggest a Friday Most music comes out on Fridays, and it helps your release stand alone that day. When you open the date field we suggest the next open Friday, but you are free to pick another date. One release per label per day Two releases from the same label cannot share the same day. If the day you want is already taken by another release on that label, we will point you to the next open date so your release gets its own spotlight. You can change the date any time while the release is still a draft or in review.

Splits, credits and co-artists

Splits decide who is credited and paid for a song. They must total 100%. Adding people to a song In the song's Artist splits, add everyone who should be credited, each with their real legal name and email. Choose their roles (composer, author, songwriter, remixer). Set each share so the total is 100%. Legal names and emails are used only for agreements and payment. We keep them on file so you do not retype them next time. Inviting co-artists If a co-artist should have their own account to review the release and confirm their share: 1. Add their email in the credits. 2. Open Invite co-artists, review, and Send invite. The invite goes to the email on file. They can create an account, check the release and confirm their split. You can still send the release before they confirm - their confirmation is not a blocker. On the other side If someone invites you, the release appears under Collaborations, where you confirm your own legal name, email and split. Once the release is sent, your details become read-only.

ISRC and UPC codes

These are the standard IDs that identify your music. You rarely have to think about them. ISRC (per track) An ISRC identifies one recording. There are two cases: - Brand-new track: leave it blank. Fatstep assigns an ISRC when your release is processed. It is read-only for you. - Previously distributed track: tick Previously distributed and enter the recording's existing ISRC (from its earlier release). This is required so streams stay attached to the same recording. UPC (per release) A UPC identifies the whole release (the "barcode"). We assign it for you. It is shown read-only. Back-catalogue titles For older titles already in your catalogue, some code fields are editable so we can line up historical data correctly. For new releases, treat ISRC and UPC as handled for you unless the track was distributed before.

Editing a release that is already live

Made a typo, want to swap the master or update artwork after sending? You can request a change at almost any stage. Reopen to edit On the release, choose Reopen to edit. This unlocks the release so you can make your changes. A short note explains that your edits are reviewed by the team, and once validated the release continues from where it was. What happens next 1. You make your changes and resubmit. 2. Our team reviews each changed field one by one. 3. Approved changes are applied (and synced to the catalogue where they map). Rejected changes restore the previous value. Recall vs reopen - Recall to edit pulls a release in review back to a draft. You then send it again. - Reopen to edit is for releases further along, including live ones, without losing their stage. Changed your mind? While reopened, you can Cancel to discard your edits and return the release to exactly where it was.