Clean and explicit versions: organise audio and metadata correctly

Define the versions you actually have

Listen to each complete recording and record how they differ. A muted word, replacement vocal, shorter arrangement and unchanged master are not interchangeable descriptions. Keep an approved version sheet so the person uploading the release does not have to infer the content from a filename.

Use the actual content label

Spotify requires explicit recordings to be flagged in metadata and displays its own explicit indicator. Apple reserves the Clean flag for an edited counterpart of an existing explicit recording; a song that was never explicit is not automatically a Clean version. Apple also excludes explicit/clean labels from track and album titles. Do not place a decorative explicit symbol in the title to replace the required metadata flag, or label an unedited recording clean. Confirm destination-specific version wording and the available DistroBolt fields before submission.

Prepare a version-by-version checklist

• Approved final audio filename and duration.
• Exact title and any applicable version information.
• Correct content classification based on the whole recording.
• Lyric transcript that matches that version, where lyrics are submitted separately.
• Artwork and promotional material that do not misrepresent the edition.
• Identifier decision checked against the actual recording change and the relevant requirements.

Check identifiers instead of recycling blindly

A different audio edit can raise a new-recording identification question. Do not assume one ISRC fits every clean edit, radio edit or replacement vocal simply because the song is the same. Equally, do not invent a new code to disguise an unchanged recording during transfer. Use the ISRC guide and ask DistroBolt about the exact versions before delivery.

An original version-control example

An artist approves a clean vocal edit for daytime promotion while retaining an explicit edition for release. The team listens to both files, confirms the changed verse and stores separate lyric text. Before submission they review the identifiers and the correct metadata flags. The important check is that each row describes the actual audio; a neat filename alone is not sufficient.

If the wrong version is live

Record the release and track references, affected store link, current audio problem and intended correction. Ask whether the issue needs a flag update, audio review or a separate version delivery. Do not overwrite the record or submit duplicate releases without an agreed plan. Use the correction guide for a clear before-and-after request.

What clean does not mean

A clean edit does not establish rights clearance, guarantee all-age placement or promise availability in every territory. It also does not replace platform-specific content policies. Keep permissions for the recording, composition and borrowed material separately documented, and use the final-audio checks before uploading either version.