This edition looks at AI catalogue management as it stands in November 2026, written for independent artists and small labels who run their own releases rather than handing them to a team.
A properly labelled AI record gets distributed; a hidden one eventually gets removed.
What to verify before release day
AI generated music should be declared when the release is delivered and tagged as synthetic where the platform allows it. An honestly labelled release is distributed normally.
How the numbers really behave
The central argument in music is whether a model was trained on material without permission, not whether a track was made with AI. Tools with licensed data are the safe choice.
Where independents win
Cloning a recognisable artist voice carries a different legal risk from copying a composition. Original synthetic voices are fine; digital copies of a living identity are not.
What the stores reward now
More AI submissions are rejected for missing contributor credits and thin documentation than for their synthetic origin.
The detail that decides the outcome
Stores normalise to roughly -14 LUFS on Spotify and YouTube and -16 LUFS on Apple Music, with true peak under -1.0 dBTP. AI mastering does not change that target.
Common mistakes to avoid
- Expecting AI mastering to rescue a clipped or muddy mix.
- Keeping no record of the tool, licence and prompt used for a track.
- Concealing AI involvement at delivery and meeting a takedown instead of a label.
Do this next
- Use only tools with a paid commercial licence and clear training data terms.
- Keep a provenance note per track: tool, licence, prompt, date and files.
- Declare the synthetic origin at delivery and tag it where the store allows.
What this means for your next release
None of this is theory. Every point above maps to a decision you can make on your next release, and the cost of getting it wrong is paid months later in a statement nobody can correct.