Releases
Building a release: metadata, audio, artwork, credits, splits, AI disclosure and stores.
11 articles
All guides
11 articles- Creating a release, step by step Every section of the Run release wizard, what each one needs, what blocks submit, and what happens once you send it.
- Importing your catalog from Spotify How Import from Spotify turns a discography into pre-filled drafts, what comes across, and what you finish before submitting.
- Metadata rules that stop rejections The title, credit, genre, language, date and code rules Run's checks enforce, including the wording that fails outright and the wording a reviewer looks at.
- Audio file requirements The exact audio specs Run accepts, the warnings that do not stop a release, and how to export a master that clears the checks first time.
- AI Mastering (Upcoming) AI Mastering by master.audio is Upcoming, with a launch date of 9 November 2026, and is not available in the workspace yet.
- Artwork requirements The cover art specs Run enforces at submit, the store content rules a reviewer applies, and what to do when your artwork is too small.
- Credits, contributors and publishing splits How display artists, song credits and publishing splits differ, the rules Run enforces on each, and what stops a release submitting.
- AI disclosure, explained The three AI disclosures Run collects, what the four levels mean, the separate question on each credited person, and why disclosure is never a penalty.
- Choosing stores and Content ID Stores are all on by default and Content ID is not. What each category does, the ownership confirmation, and which tracks are never eligible.
- The sound recording and copyright lines What the two rights lines on a release mean, what Run fills in when you leave them blank, and how one track can override them.
- Editing, reopening and resubmitting A release can only be edited while it is a draft. How to reopen one that failed checks or was refused, and what is fixed once it has been delivered.