Three quarters of verified AI releases go through one distributor, and that distributor is now being sued for up to $150 million. On 15 September 2026 Universal Music Group and its Capitol Records imprint filed a 52-page complaint in the US District Court in Delaware accusing DistroKid of presenting itself as a distributor of artist-created work while, UMG alleges, flooding Spotify, Apple Music and YouTube with AI-generated tracks that siphon revenue from legitimate rightsholders. The complaint cites a "Lofi Chill" account that released 4,562 tracks in twelve months. As of the filing date DistroKid had not responded publicly and no hearing had been set.
Short answer: UMG's own filing says the case is not about clearly disclosed AI music, and nothing has changed for a compliant catalogue today. The risk is concentration. SIQA's mid-year 2026 report puts DistroKid at 77.6% of verified AI releases with distributor data, up from 75.8% in Q1, while TuneCore fell from 4.7% to 1.7% after Believe began blocking tracks from unlicensed generators in April. If your entire catalogue, your identifiers and your publishing all live in one dashboard that is now in litigation, the question is not whether the case has merit. It is what you do the morning a policy changes. Here is the map and the plan.
What UMG actually alleges
Three things, in the complaint's own framing. First, copyright infringement: that DistroKid distributed AI-generated tracks that copy UMG works. Second, deceptive practice: that DistroKid marketed itself as serving artist-created music while knowingly passing generated volume. Third, harm: that the volume diverts listeners and royalties from human artists. UMG writes that "this lawsuit is not about the distribution of AI-generated music when clearly disclosed as such," and that the target is "DistroKid masquerading as something it is not."
For an independent musician the operative words are clearly disclosed. The industry response to the case, whatever the outcome, will be tighter declarations, more detection and stricter enforcement of the AI fields that already exist at upload. Catalogues that are honest today will feel that as paperwork. Catalogues that ticked the wrong box to avoid a review will feel it as takedowns.
The 2026 policy stack, store by store
| Layer | Rule in force | Date | Exposure for a human-fronted, disclosed catalogue |
|---|
| Believe / TuneCore | Block distribution of tracks from generators treated as unlicensed (Suno named); later opened to tracks from Suno's industry partner model, older-model tracks still blocked | April 2026 onward | Medium: depends on which model made each track |
| Spotify | AI Credits via DDEX from 16 April; spam filter removed 75M+ tracks; AI Persona badge from mid-September excludes synthetic identities from recommendations | April to September 2026 | Low if identity is human and uploads are not farm-shaped |
| TIDAL | No royalties on wholly AI-generated tracks; AI badge; policy may expand to "substantially" AI | 15 July 2026 | Low for hybrid work; total for fully generated tracks |
| Deezer | AI labelling; fraudulent streams excluded from royalties; AI tracks above 50% of daily uploads | Ongoing, peak June 2026 | Low unless streams are bought |
| DistroKid | Defendant in UMG v. DistroKid; AI declaration at upload; first DDEX AI-credit partner | Filed 15 September 2026 | Concentration: the platform, not your compliance |
Read across a row and the pattern is the same everywhere: platforms are separating identity fraud, stream fraud and undisclosed generation from tool use. Read down the last column and the only "medium" is the one that depends on model provenance, which is why every release file now records the model version.
Concentration risk, quantified for you
Do the arithmetic for your own catalogue in five minutes.
Percentage of tracks delivered through one distributor. For most independents this is 100.
Percentage of your ISRCs whose masters you hold locally, tagged, with artwork. If you would have to download them from the dashboard, the answer is lower than you think.
Percentage of works registered with a performing rights society independently of the distributor. If you used a distributor publishing add-on, have you seen the registrations?
Percentage of tracks made on a generator model that Believe and TuneCore currently block. You need the model version per track to answer.
Days it would take you to be live on a second distributor with the same catalogue. Honest answers range from two days to never.
If the answers are 100, 40, 0, unknown and never, your risk is not UMG. It is you.
The four-step contingency
1. Export everything this week
Masters at delivery quality, artwork, a metadata sheet with title, version, artists, writers and splits, ISRC, UPC, release date and language per track, and the AI declarations as submitted. Store it off-platform. This is the artefact that makes every other step possible, and the one people skip because the dashboard feels permanent.
2. Open, do not move to, a second distributor
Create the account, verify identity, upload one release to learn the form. Do not migrate a live catalogue: moving releases resets stream history and playlist placements, and re-uploading under new ISRCs is itself a farm signal. The second account is insurance, not a new home. Pick one with clear AI policies you can comply with, and read the generator rules, since Believe-owned services block older Suno models.
3. Detach rights from distribution
Publishing registration through your own society membership, with your own IPI number and ISWCs per work, so that composition income does not depend on a distributor add-on surviving the lawsuit. The full sequence is in the two royalty pipes.
4. Harden the identity layer
A real person on the profile, per-component AI disclosure, clean titles, sane cadence. Every store's 2026 rule rewards the same profile, and it is the one UMG's complaint explicitly excludes from its target. The 72-hour checklist is in the identity stack, and the pre-upload gate is in the metadata checklist.
What not to do
Do not delete and re-upload your catalogue elsewhere in a panic. You will lose history and look like the thing the filters hunt.
Do not change AI declarations retroactively to something less true. Metadata corrections should move toward accuracy, not away from it.
Do not spread one catalogue across five distributors to "diversify." Duplicate deliveries of the same ISRC create conflicts at the stores and can freeze both.
Do not assume a lawsuit resolves quickly. Complaints of this size take years; policy changes take days. Plan for the second.
The market you are actually in
The same SIQA report that shows DistroKid's share also shows fully AI-generated tracks falling to 13.9% of verified releases while assisted and hybrid work rose, and Suno present in 92.8% of workflows. The tool is universal; the method is what the stores and the courts are sorting. A human-fronted, disclosed, registered catalogue with a sane cadence is on the right side of every 2026 rule, including the one UMG just asked a court to enforce. The strategy behind that position is in Fully AI music just peaked. For catalogues in Indian genres the Bollywood Hit Song Factory and Regional Indian Music Pack include the metadata and provenance templates that make steps one and three a copy-paste, and our free Suno Prompt Builder records the model version with every style sheet it produces.
What to watch, and what each signal means for you
Court dockets move slowly; the signals that change your week arrive by email from your distributor. Watch these, in this order of importance.
Distributor terms updates. A new AI declaration question, a new generator field, or a new clause about "artist-created" content is the operational fallout of the case, whatever happens in Delaware. Read the diff, not the summary.
Store policy pages. Spotify, TIDAL and Deezer have each changed AI policy at least once in 2026. TIDAL described its rule as a living document and said it may expand from wholly to substantially AI-generated. If that expansion lands, hybrid work needs its human components documented, which is what the provenance folder is for.
DistroKid's response and any motion to dismiss. The first public filing will tell you how DistroKid characterises its AI users. If the defence leans on "clearly disclosed," honest declarations become more valuable, not less.
Believe and TuneCore model lists. Which generator versions are accepted is the single fact that decides whether a second distributor can carry your back catalogue.
Your own statements. A sudden drop in a store's payout for tracks that still show streams is a policy change you were not told about. The quarterly two-pipe audit catches it.
Set a monthly reminder to check the first two. The rest will find you.
Quick answers
Is UMG suing over all AI music on DistroKid?
No. UMG's complaint states it is not about clearly disclosed AI music. It alleges DistroKid misrepresented itself while distributing undisclosed generated volume, citing one act with 4,562 tracks in a year.
Should I leave DistroKid now?
Not on the filing alone. Export your catalogue, open a second distributor as insurance, register publishing independently, and keep your identity and disclosures clean.
Why does the model version matter for distribution?
Believe and TuneCore block tracks from generators they treat as unlicensed and have opened distribution to Suno's industry partner model while older-model tracks remain blocked. Provenance per track answers the question in one line.
What is the biggest risk for a compliant independent?
Concentration. One distributor holding your masters, identifiers and publishing means one policy change can freeze all three at once.
How long will the case take?
Complaints of this scale run for years. Distributor and store policy changes happen in days. Plan your contingency around the second timeline.
Disclaimer: This article summarises public filings and platform policies for informational purposes and is not legal advice. Consult a qualified professional about your own contracts and rights.
Export, insure, detach, harden. Every product mentioned is available at wowhow.cloud — pay once, ship forever.
Originally published at wowhow.cloud
