Yes,
if you are on a paid tier and you declare it at delivery.
Most platforms don't reject generated music — they ask you to flag it, then decide how far it travels. The register below is who asks what.
Accepts AI, but you must own 100% of the rights and declare it via AI Credits at upload. Bulk raw uploads are flagged as spam. 1
AI-assisted is fine on a paid plan; fully AI tracks with no human input are refused. Requires DDEX disclosure and licensed training data. 2
More permissive — standard originality rules, no separate AI ban — but tightening. 3
Refuses all AI-generated content outright, even if commercially licensed — the strictest distributor policy. 4
Accepted; declare via the DDEX AI Credits field (set at distributor level). Disclosure is informational and does not down-rank on its own; spam and impersonation filters are separate. 5
Transparency Tags a delivery requirement since March 2026; declaration-based through your distributor, no public automated enforcement. 6
Accepted, but auto-detects fully-AI tracks, tags them, and excludes them from editorial and algorithmic recommendations regardless of what you declare. 7
Monetisable with disclosure — toggle Altered or synthetic content in Studio. Since May 2026 it also auto-detects. Disclosure does not cut reach or ad eligibility; Content ID claims are common. 8
Its January 2026 Keeping Bandcamp Human policy restricts music made wholly or substantially by AI — check the current wording before you rely on it. 9
Its 2026 anti-spam rule targets bulk AI uploads; the exact line on individual AI tracks is not clearly published. 10
NOT LEGAL ADVICE. RULES CHANGE WITHOUT NOTICE — THE NUMBERED SOURCES ABOVE ARE THE ONLY AUTHORITY HERE.
What your plan grants
A free tier and a paid tier differ in one way that matters here: the paid tiers grant commercial use of what you generate. That grant is what a distributor is really asking about when its upload form says you must hold the rights to the recording. It is a licence from the generator to you, and it covers tracks made while the subscription was active.
No distributor in the register verifies the plan. DistroKid and Amuse carry no AI-specific clause at all. TuneCore is stricter: generated tracks are fine on a paid plan, cloned vocals of real artists are refused.
Disclosure became the default
Through the first half of 2026 the stores converged on the same answer, and it was not a ban. Spotify made an AI-disclosure field required in delivery metadata in March. YouTube tightened its synthetic-content label in June. Deezer took a third route in February: accept, tag, and down-rank in algorithmic playlists.
Nobody in the register asks whether the music was generated in order to reject it — they ask so the flag travels with the file. Four of the ten platforms take a generated track with no conditions at all; one, Audius, removes bulk uploads under its 2026 anti-spam rule.
PROs and Content ID
A performing-rights organisation asks who the human authors are; where a work has no identifiable human authorship the registration has nowhere to go. In practice the writing credit has to describe a real contribution — arrangement, lyrics, performance, editing.
Content ID asks nothing. It matches audio against a reference set, and generated tracks that share a common texture or a stock loop attract claims that have nothing to do with your rights. Dispute, show what you generated and when, keep the run log.
Download limits and what you keep
A monthly download allowance is not a licence, and stems usually count against it separately. Export the files you care about while the plan is live.
Cancelling does not retroactively withdraw the commercial grant on tracks generated while you were paying, but it ends your ability to generate or download more. Anything already delivered keeps its own metadata, disclosure flag and date.
First pieces are being written. Check back soon.
