> ## Documentation Index > Fetch the complete documentation index at: https://help.ammdistro.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a release, step by step > You build a release on one page with three sections: Release, Tracks and Review & submit. You build a release on one page with three sections: **Release**, **Tracks** and **Review & submit**. Everything saves as you type, so you can leave and come back at any time. When the checks pass, click **Submit for review**. ## Start a new release Click **+** at the top of the left menu and choose **New release**, click **New** on Home and choose **New release**, or click **New release** on the Releases page. ![The + menu with New release highlighted](https://ammdistro.com/helpdesk/distro-plus-menu-new-release.webp) A draft called "Untitled Release" is created and the builder opens. To come back to a draft later, open it from **Releases** and click **Edit release**. ## 1. Release Add what applies to the whole release. ![The Release section of the builder with the artwork, title, version line, artists, release date and record label fields numbered](https://ammdistro.com/helpdesk/distro-builder-release-section.webp) 1. **Artwork**: click or drop a square image of at least 1,000 × 1,000 pixels. See **Artwork requirements**. 2. **Title**: the release title. On a one-track single it has to match the track title. 3. **Version line**: only for things like "Remixes" or "Deluxe". Leave it empty otherwise. 4. **Artists**: everyone billed on the release, up to 4 primary artists. Type in **Search or add an artist…** to find an artist or create a new one. An artist who isn't on Spotify yet can be created without a profile. **Add featured artists** is below. 5. **Release date**: pick a date in the calendar, or click **Release as soon as possible** to have the date set to the day we approve the release. Dates more than 10 days out give the best chance at playlist pitching. 6. **Record label**: your label or artist name. It's used for both the © and ℗ lines, with the year taken from the release date. Also pick the **Genre** and the **Metadata language** (the language your titles are written in), and answer **Released before?**: choose **No, it's new**, or **Yes, it's been released** and add the **Original release date** and the **Previous distributor or platform**. ## 2. Tracks Upload your audio. Each WAV or FLAC file becomes a track, and the file name becomes the track title. Drag tracks to reorder them. Click a track to open it and fill in: * **Title** and **Version** (for example "Sped Up" or "Radio Edit"). * **Artists** and **Featured** artists. * **Vocals**: answer **Does this track have vocals?** with **Yes** or **No, it's instrumental**. With **Yes**, choose **Not explicit** or **Explicit**, pick the **Lyrics language**, and paste the **Lyrics** if you want to (optional). An instrumental is delivered with no lyrics, not explicit, and needs no lyricist. * **TikTok clip** (optional): choose where the 60-second TikTok sound starts. Drag the highlighted window on the waveform and click **Play clip** to hear it. * **Previously released**: choose **New recording**, or **Previously released** and enter the existing ISRC. * **Credits**: add each person once and pick their roles. Every track needs a songwriter, a producer or engineer, and a performer. A track with vocals and lyrics also needs a lyricist (Lyricist, Songwriter or Composer & Lyricist). The **Still needed** line under the credits says what's missing. The release type (single, EP or album) is set from the number of tracks. See **Single, EP or album?** ## 3. Review & submit Check everything and make your choices about where the release goes. ![The Review & submit section with Spotify profile protection, Preflight, stores, Content ID & social, territories and the Submit for review button](https://ammdistro.com/helpdesk/distro-builder-review-submit.webp) 1. **Spotify profile protection**: shown when we haven't delivered to an artist's Spotify profile before. Answer the question for each artist. 2. **Preflight**: the list of checks. Open it to see what's left to fix. 3. **Stores**: all stores by default. Open it to pick specific stores. 4. **Content ID & social**: you must choose whether the release goes to TikTok, Instagram, Facebook, YouTube Content ID and SoundCloud. 5. **Territories**: worldwide by default. Open it to block or limit countries. 6. **Submit for review**: available once every check passes and you've made the Content ID decision. It opens a final step where you confirm the release date and check a summary, then click **Confirm and submit**. After you submit, you'll see "Submitted for review" and we email you once it has been reviewed. ## Saving The top of the builder shows the save state: **Saving**, **Saved**, or **Unsaved**. If a change couldn't be saved you'll see "Change failed — reverted"; make the change again. If you try to leave while something is still saving, you'll be asked to stay on the page or leave anyway. Once a release is submitted, its details are locked in the builder. If we send it back for changes, you can edit it again. ## Common questions ### Can I work on a release with my team? Yes. Anyone on the account with the Admin or Member role can create and edit releases. ### Can I build a release on my phone? Not in the mobile apps. Creating and editing releases is done on the web. ### Can I delete a draft? Yes. Open the release and delete it. Only drafts and rejected releases can be deleted. **Related:** [Artwork requirements](https://help.ammdistro.com/creating-a-release/artwork-requirements.md) · [Audio requirements](https://help.ammdistro.com/creating-a-release/audio-requirements.md) · [Add songwriter, producer and performer credits](https://help.ammdistro.com/creating-a-release/add-songwriter-producer-and-performer-credits.md) · [Check and submit your release](https://help.ammdistro.com/creating-a-release/check-and-submit-your-release.md) · [Release statuses explained](https://help.ammdistro.com/release-status-and-review/release-statuses-explained.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.