Uploading a release seems simple: audio + cover + publish. Then you open a distribution form and find yourself facing a wall of fields. Title, version, artists, featuring, collaborators, lyrics, dates, territories, label, copyright… and suddenly you realize this isn't "bureaucracy": it's information that stores use to understand who you are, what you're publishing, and where it should end up.
In this article we'll look at:
- how many (and which) fields are actually inside a release
- which ones require the most attention (spoiler: artists, featuring, collaborators, lyrics, dates)
- how to reduce errors and stress with a well-designed flow (in LightSound: automatic drafts, step-by-step wizard, and smart suggestions)
Why a Release Is More Complex Than It Seems
A release isn't just an audio file: it's a "package" of data that must be compatible with dozens of stores (DSPs), each with often different rules. Every field you fill in is used to:
- associate the music with the correct artist profile
- correctly display titles and versions (radio edit, remix, explicit/clean)
- attribute credits (producer, songwriter, etc.)
- manage rights (copyright line, master)
- enable features like lyrics, pre-save, pitch, etc. (when available)
The complexity grows as soon as you have:
- features and co-main artists
- remixes
- multiple collaborators
- multiple tracks (EP/album)
- lyrics and alternate versions
The Typical Fields in a Release (the ones you'll almost always find)
Without turning this into an endless list, these are the blocks of fields that appear in most distribution systems:
1) General Release Information
- Release title
- Type (single / EP / album / compilation)
- Publication date
- Label and catalog number (if used)
- Language (often for metadata and lyrics)
2) Artwork (Cover)
- Cover file (format, dimensions, rules on text and logos)
- Consistency between cover and metadata (title/artist)
3) Tracks
- Track title
- Version / edit (radio edit, live, acoustic, remix, explicit/clean)
- ISRC (if present or auto-generated)
- Audio file (required format, quality, loudness/clipping)
4) Artists and Public Roles (those that appear publicly)
- Primary artist
- Featured artist
- Remix artist (if remix)
- Variants (co-main, duo, etc.)
5) Collaborators and Credits (behind the scenes)
- Producer
- Songwriter / Lyricist
- Composer
- Mixing / mastering engineer (when applicable)
- Other contributors
6) Lyrics and "Sensitive" Content
- Lyrics
- Explicit/clean flag
- Content with specific rules (e.g., titles and covers)
7) Copyright and Ownership (C-Line / P-Line)
- C-Line (©)
- P-Line (℗)
- Rights holder and year (usually the publication year)
If it seems like a lot, that's because it is. And the critical part isn't filling everything in: it's filling it in correctly.
The "High-Risk" Fields (the ones to treat carefully)
There are fields that, if wrong, cause more damage than others: incorrect profiles, confused credits, rejections, or slow corrections. Here are the most delicate ones.
Artists and featuring
This is the classic point where problems arise:
- a featuring listed as primary → the track ends up in the wrong place
- a co-main treated as a feat (or vice versa) → a "broken" discography
- inconsistent names → duplicate profiles or hard-to-fix issues
Practical rule: decide how you want the track to appear publicly and then translate that choice into the correct fields (primary/feat/remix).
Collaborators and roles (credits)
Credits aren't a "professional detail": they're the memory of the track. If you enter them incorrectly or forget them:
- you lose clarity with collaborators
- you create gaps in the catalog
- you end up chasing information later (when nobody remembers anymore)
Key roles that are often missing:
- songwriter/lyricist
- composer
- producer
Lyrics and explicit flag
Common errors here too:
- lyrics inconsistent with the version (clean vs explicit)
- incomplete lyrics or lyrics with major typos
- forgetting to set the explicit flag (or setting it randomly)
It's not just "form": it affects how the track is presented, filtered, and indexed.
Titles and versions
"Radio edit," "remix," "live," "acoustic"... if entered in the wrong field or inconsistently:
- you risk creating duplicates
- you confuse cataloging across stores
- you make it harder for listeners to understand what they're listening to
Dates: publication and pre-save
Dates are another sensitive point:
- date too close → insufficient time for review, pitch, or promotion
- date changed at the last minute → chaos with promo and links
- pre-save set without thought → missed opportunity
The Real Problem: It's Not Just Complex, It Gets Interrupted
Filling in a release rarely happens in one sitting. One of these things always comes up:
- a credit is missing and you need to write to someone
- you need to retrieve the final lyrics
- you need to fix the cover
- you need to export the right master
- you need to agree on a date with your team
That's why the most underrated feature in a distribution system is: not losing anything when you stop.
In LightSound: Automatic Draft Saving (Including Files)
LightSound has automatic draft saving: you go as far as you go and pick up where you left off whenever you want, without losing anything. And we're not just talking about text fields: you don't even lose audio files and cover art already uploaded.
This changes the workflow, because it lets you work the way you actually work:
- fill in what you know
- leave pending what you need to ask/retrieve
- come back later without re-uploading and re-checking 100 times
Step-by-Step Wizard: Less Chaos, More Control
When a form is a single endless page, errors multiply. The brain gets tired and you start "filling in to finish." A release, on the other hand, needs to be managed like a journey: a few fields at a time, clear feedback, and a sense of where you are.
In LightSound: Wizard Split into Clear Steps
To manage the complexity, LightSound's wizard is divided into clear steps, so you focus on one thing at a time:
- release info
- tracks
- artists and featuring
- collaborators and roles
- lyrics and content
- dates and publication
This reduces two problems:
- skipping important fields because you "didn't see them"
- confusing similar fields (e.g., public artists vs. contributors)
Features That Really Make a Difference (Especially When You Publish Often)
Complexity can't be eliminated: it's managed with tools that prevent repetitive errors.
Pre-filled Fields (e.g., roles)
Some fields shouldn't force you to reinvent the wheel every time. That's why LightSound offers pre-filled fields where it makes sense (for example, on roles), so:
- you choose more quickly
- you avoid inconsistent variations
- you maintain a standard across releases
Smart Suggestions (e.g., pre-save dates and timing)
Dates are a classic point where mistakes happen due to inexperience. That's why LightSound offers suggestions on choices like:
- release timing
- setting a sensible pre-save date
- warnings about windows that are too tight for promotion and delivery
It's not a rigid rule: it's practical help to avoid typical mistakes.
Consistency Checks and Useful Warnings
A good wizard isn't just a form: it's an assistant that helps you avoid oversights, for example:
- missing important fields
- inconsistencies between title/version
- mismatches between artists and featuring
- missing lyrics (when expected) or inconsistent explicit flag
How to Work Professionally Without Going Crazy (Recommended Workflow)
Here's a workflow that reduces stress and post-publication corrections.
- Upload audio and cover first (if you already have the final versions)
- Fill in artists and featuring carefully (it's the foundation of everything)
- Enter collaborators and roles while you still have the team "fresh" in mind
- Add lyrics and set explicit/clean
- Choose the dates (release + pre-save) with some margin
- Do a final consistency check and publish
Tip: when working step by step with automatic drafts, you can do everything across multiple sessions without wasting time re-uploading or re-entering fields.
Conclusion
A release is complex because it needs to speak the language of stores: many fields, many rules, many edge cases. The difference between a "smooth" publication and one full of problems lies in paying attention to the right fields: artists, featuring, collaborators, lyrics, and dates.
LightSound addresses this complexity with a flow built for real life: automatic draft saving (without losing even audio and cover files), a simple step-by-step wizard, and aids like pre-filled fields and smart suggestions (for example, on pre-save and timing). The result: less stress, fewer errors, and a cleaner release.
Related Articles
- Release Metadata: How to Fill It In Correctly
- Collaborators: Roles, Credits, and Common Mistakes
- The Most Common Mistakes in Music Distribution
- The Complete Checklist for Your First Release
Want to do it simply with LightSound? Check out Pricing or create an account.