This edition looks at AI mastering in a release workflow 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.

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.

Where the money actually comes from

A muddy mix, a clipped take or a phase problem survives any amount of final processing. Mastering balances a finished record; it cannot finish an unfinished one.

What changed this year

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.

Common mistakes to avoid

  • Concealing AI involvement at delivery and meeting a takedown instead of a label.
  • Cloning a recognisable artist voice and describing it as a tribute.
  • Expecting AI mastering to rescue a clipped or muddy mix.

Do this next

  1. Declare the synthetic origin at delivery and tag it where the store allows.
  2. Check the master on a phone speaker before you export it.
  3. Use only tools with a paid commercial licence and clear training data terms.

What this means for your next release

Work through this before the next release rather than after it. A few hours of preparation protects the entire earning life of the record.