contact us
The real state of the Suno and Udio copyright litigation, and what it means for anyone using AI music generation tools commercially.
Suno and Udio Are Being Sued for Billions. The Music They Make Hasn’t Stopped Getting Better.

Text-to-music generation is one of the more genuinely useful generative media categories for production work, and it's also at the center of one of the largest, most consequential AI copyright fights currently in court. Understanding both halves matters for anyone considering these tools for real commercial use.

Where the litigation actually stands

The RIAA filed landmark AI music copyright suits against Suno and Udio in June 2024 in Boston federal court, on behalf of Sony Music, Universal Music Group, and Warner Music Group, alleging both companies trained their models on copyrighted sound recordings without permission. The case has since fractured in a genuinely interesting way: Warner Music Group settled with Suno in November 2025 and entered a licensing partnership, and Universal Music Group settled with Udio in October 2025. Meaning two of the three major labels have moved from litigation to licensing with at least one of the two platforms.

The remaining fight just got much bigger

Universal Music Group and Sony Music remain in active litigation against Suno. In May 2026, they moved to expand the case from 560 recordings to 61,026 recordings, after discovery reportedly showed Suno had trained on millions of tracks from the labels' catalogs, a move that could push potential statutory damages past $9 billion. That's a scale of legal exposure that puts Suno's litigation risk in a genuinely different category from most other generative AI companies' copyright disputes.

What the settlements actually signal

The Warner-Suno and Universal-Udio settlements are worth reading carefully rather than as simple capitulation: both moved from adversarial litigation to licensing partnerships, which suggests the labels see a path to being paid for training data access rather than simply blocking these tools' existence. Suno has publicly emphasized that "transparency is important" as the recording industry has separately proposed an AI content labeling system. Signaling an industry-wide move toward disclosure and licensing infrastructure rather than an assumption that AI music generation itself will be litigated out of existence.

What this means for using these tools right now

For anyone using Suno, Udio, or similar tools for actual commercial production, the practical takeaway is that licensing status varies by platform and even by which label's catalog is in question, a genuinely more complicated picture than a blanket "is AI music legal" question can answer. This is the same unresolved-but-actively-evolving legal territory we cover in our status check on AI copyright lawsuits generally and in AI video generation's parallel legal exposure. Confirming a specific platform's current licensing and litigation status before commercial use isn't optional caution, it's a genuinely live business risk given the scale of damages being sought in the ongoing case.

Why the underlying technology keeps improving regardless

None of this litigation has slowed the pace of capability improvement. These tools continue to produce genuinely usable output for common production needs like background music and mood-setting tracks, the same "plausible and on-theme, not precisely structured" strength we found across AI image generation and AI video generation. The legal and technical stories here are running on separate tracks: capability keeps advancing, and the licensing question underneath it remains genuinely unresolved for at least one major platform.

The practical takeaway

Test these tools freely for what they're good at (background and mood music for lower-stakes creative work) but before using generated music in any commercial release, check the specific platform's current licensing status directly rather than assuming the legal picture is settled. Given the scale of the remaining Suno litigation specifically, that's not a hypothetical caution.

Share with