01 / The case in plain language
What is the UMG–DistroKid lawsuit actually about?
A distributor can deliver a recording to a streaming service without owning the song, the recording or every sound inside it. That distinction sits at the heart of a practical problem for independent artists: when somebody challenges a release, can the person who uploaded it show the authority to distribute it?
On September 15, 2026, UMG Recordings, Capitol Records and Capitol CMG sued DistroKid and two related companies in the US District Court for the District of Delaware. The complaint alleges misleading representations about distributed content and infringement involving unauthorized recordings, including altered recordings and samples. These are the plaintiffs’ allegations. [1]
The five counts comprise a Delaware deceptive-trade-practices claim, direct and alternative vicarious copyright-infringement claims, and corresponding claims concerning pre-1972 recordings. Vicarious liability concerns responsibility for others’ infringement under specific legal conditions. The plaintiffs seek injunctions, damages and other relief; those requests are not court awards. [1]
The complaint expressly excludes artists’ legitimate use of AI tools and says it is not challenging clearly disclosed AI-generated music. It is therefore misleading to describe the filing as a court-imposed ban on AI music, or simply as an AI-training case. [1] Reuters reported that DistroKid strongly disputes the allegations and intends to defend its practices. [2]
A practical evidence pack that helps an artist answer questions accurately. It does not guarantee acceptance, royalties or immunity from a claim. This is general educational guidance; a disputed contract or clearance needs advice for the relevant territory.
This is a US case, not a new Jamaican statute. For Jamaican creators, the immediate opportunity is to strengthen the connection between music, permission and payment. A singer should be able to explain who wrote a song. A producer should be able to show what a riddim licence allows. An uploader should know whether a vocal was recorded by a consenting performer, licensed from a library or generated using a tool. None of that requires surrendering independent ownership.
02 / Dated case status
What has happened, and what remains unresolved?
The case is UMG Recordings, Inc. et al. v. DistroKid, LLC et al., 1:26-cv-01156. The public docket mirror records filing and service on September 15 and lists October 6, 2026, as the defendants’ response deadline. Its own retrieval date is September 15. We reviewed that snapshot on September 22; later PACER activity has not been independently confirmed for this article. [3]
| Stage | What the reviewed record shows | What to check next |
|---|---|---|
| Complaint | Filed September 15, 2026. | An amended complaint or additional exhibits. |
| Service and response | Service recorded; response due October 6 in the snapshot. | An answer, motion or extension. This is not a hearing date. |
| Court decision | No merits decision appears in the reviewed snapshot. | An actual order and its precise scope. |
| Practical outcome | No settlement or damages award established by these sources. | Confirmed terms, judgments or published policy changes. |
A continuing tracker should record the filing date, document number, source and a short explanation of each material development. Keep allegations, company statements and judicial findings in separate entries. A scheduled deadline can move; an amended complaint can change the issues. This page is a dated explainer, not an automatically refreshed docket feed.
03 / Know which right you are documenting
The song, the master and the permission are different things
The US Copyright Office distinguishes a musical composition from a sound recording. The composition is the underlying music and lyrics; the recording is a particular recorded performance. Control of one does not automatically establish control of the other. [4]
| Layer | Question to answer | Evidence to gather |
|---|---|---|
| Composition / publishing | Who controls the music and lyrics being used? | Writer identities, agreed splits, publishing or administration agreements and relevant permissions. |
| Master / sound recording | Who controls this particular recorded audio? | Recording and production agreements, master-ownership records and distribution authority. |
| Sample | Was existing audio copied, and what rights does that use engage? | Source identification and applicable recording and composition clearances. |
| Interpolation / replay | Was music recreated without copying the original recording? | Identification of the borrowed composition and any required permission; records of the new recording. |
| Licensed beat or riddim | What uses does the actual agreement authorize? | The licence, purchase record and limits on territory, term, exclusivity, monetization and claims. |
| AI-assisted contribution | What was generated, what was human-created and what may be used? | Tool terms, input permissions, output records, relevant consent and human-contribution notes. |
Treat this table as a filing system, not a substitute for interpreting an agreement. The practical sample-clearance question includes both the audio being copied and the music embodied in it. Replaying a phrase removes the act of copying that original audio, but does not necessarily resolve the composition issue. DistroKid’s cover-licensing workflow expressly excludes sampling and remixes. [5][6]
In a shared-riddim project, make a separate evidence entry for the instrumental, each vocal recording and the writing contributions. “The producer sent the beat” is a useful account of how a session began. The release pack should go further: identify the producer, preserve the permission and describe which uses were agreed.
04 / Ownership folder
Build a chain of permission that another person can follow
Start with a one-page release sheet. Give the project a stable name, identify the final version and name the person responsible for delivery. List contributors by legal name and professional name, with their roles and contact details stored privately. A public credit and the person authorized to sign an agreement may use different names; your records should connect them.
Put the actual agreements next to the release sheet. Include the relevant producer agreement, beat or riddim licence, recording arrangement, publishing arrangement and collaborator permissions. Preserve attachments and later changes. A screenshot of a payment can help establish that a transaction occurred, but your reviewer still needs the terms describing what was purchased.
Use a split sheet to record the writers’ agreed shares and the basis on which the figures were entered. Do not treat an unsigned draft as a resolved agreement. Keep a separate master-ownership entry so that a composition percentage is not accidentally repeated as a recording percentage. If the collaborators disagree, record the issue and the person responsible for resolving it before delivery.
Read restrictions while there is still time to negotiate. Does the licence cover the intended countries and services? Does it expire? Is it exclusive? Does it permit audiovisual use, remixes or sublicensing? Does a play or sales threshold trigger another payment? These are questions for the actual document, not assumptions that follow from the word “premium.”
Also separate ownership from collection. JIPO describes copyright protection as not dependent on registration or deposit. Its collective-management guidance distinguishes organizations serving musical works and sound recordings, including JACAP and JAMMS. An artist should check each organization’s mandate, repertoire and territorial coverage rather than assuming one registration collects every income stream. [7][8]
A useful evidence index gives every document a short reference, such as OWN-01, and a secure location. Keep an accessible backup. The goal is a clear trail from the person granting permission to the release being delivered, with unresolved points visible rather than buried in a messaging history.
05 / Samples and riddims folder
Inventory borrowed sounds before they disappear into the mix
Open the session and identify every element that came from outside the project. Include a vocal phrase, drum break, instrumental stem, sound-library loop, field recording or downloaded beat. Record the source, where it appears in the track and the document that supports its use. A filename such as “final_loop_03” is not enough to reconstruct that history six months later.
DistroKid says it cannot approve samples from other songs on an artist’s behalf. Its guidance requires permission for relevant third-party recordings and permits appropriately licensed royalty-free samples for distribution. “Royalty-free” should therefore lead you to the licence conditions, not to the conclusion that there are no conditions. [5]
For a Jamaican producer licensing the same riddim to several vocalists, the paperwork should make the shared arrangement understandable. Identify the instrumental and version, explain what the vocalist can release and keep the agreed credit and payment terms together. Where the licence leaves a question unanswered, request written clarification instead of guessing how a platform will interpret it.
Fingerprinting needs a separate decision. DistroKid’s YouTube Content ID option applies stricter eligibility rules than ordinary distribution, including restrictions on third-party beats, loops and library audio. A track may be licensed for release while failing that particular claiming service’s eligibility test. Do not enroll shared material merely because a distribution upload succeeded. [9]
Imagine two singers who both legitimately license one instrumental. A claim against the second singer’s upload could still interrupt a valid release if the first uploader improperly treats the shared backing as exclusively claimable. Clear restrictions and coordinated release records help collaborators avoid turning a shared musical resource into a dispute.
Finish this folder by recording one decision for each borrowed element: cleared for the planned use, awaiting clarification, replaced or removed. Keep the source record even when an element is removed, so that the final audio can be distinguished from an earlier mix.
06 / Metadata folder
Make the release data match the music and the agreements
Metadata is the description that travels with a release: artist names, titles, versions, credits, identifiers and other delivery information. Build one approved sheet that everyone uses. Compare it with the final audio, artwork and signed documents before copying it into a distributor’s form.
Check the primary artist, featured performers and producer roles separately. Confirm the correct artist-profile links so that a new single does not land on an unrelated performer’s page. Preserve Jamaican spelling and language while applying the platform’s formatting rules accurately. Explain a title in editorial copy when helpful; do not silently replace the artist’s chosen identity.
Record the title, version description, language, explicit-content setting, release date, available songwriter and publisher identifiers, and the recording and packaging identifiers when assigned. Distinguish a clean edit, instrumental, dub or remix from the version already approved. Verify the copyright and phonographic-copyright notices against the rights documents rather than copying last year’s artwork.
The International Standard Recording Code identifies a recording. IFPI explicitly says an ISRC does not establish who owns it. Treat the code as a reliable reference for matching records, not as a certificate of ownership or clearance. [10]
Save the final delivery sheet, audio filename, artwork filename and distributor submission confirmation together. A file checksum can help a technically equipped team distinguish versions, but a careful dated index is already valuable. If a collaborator changes a credit or replaces a mix, update the shared record and obtain a fresh check before delivery.
Keep public metadata and private verification evidence separate. A store needs accurate credits; it does not need your passport or an entire confidential contract in a track description. Send sensitive supporting documents only through the distributor’s verified process and share the relevant pages or information that the request actually requires.
07 / AI provenance folder
Document what the tool did and what the artist did
Begin with a factual description: no AI used, assistive AI used, generative material used, or a combination. Name the tool and version where available, date the session and describe the task. Noise cleanup, lyric suggestions, a generated backing track and a cloned singing voice are different activities; a single unexplained “AI” label hides the distinctions a reviewer may need.
DistroKid currently accepts music made with AI tools subject to rights and service requirements. Its policy prohibits unauthorized impersonation, infringement and mass-generated spam or algorithm manipulation. This is a distributor policy, not a universal legal declaration that every AI-assisted recording is prohibited. [11]
Save the tool terms that applied to your account and intended commercial use. Preserve relevant input files and the permissions supporting those inputs. If a recognizable person’s voice or identity is involved, keep the relevant authorization and its scope; a tool subscription alone should not be treated as that person’s consent.
Keep meaningful creative records as well: original lyrics, session edits, arrangements, performances and decisions about the final work. In its January 2025 copyrightability report, the US Copyright Office explains that human authorship remains central; using AI assistance does not automatically defeat protection, while purely AI-generated material is not protected on that basis. Human selection, arrangement or modification may be assessed separately. That is US guidance, not a statement that every jurisdiction applies an identical test. [12]
For Jamaican writers, there is also a concrete registration task. JACAP’s current Notification of Works form asks whether AI was involved, whether a work is wholly AI-generated and how AI contributed. The form states that wholly AI-created work may be recorded in its database but is not eligible for royalty distribution under its declaration. This is JACAP’s published registration position, not a court ruling on all AI music. [13]
Answer the form you are actually completing. A distributor’s questions, a collecting society’s declaration and a copyright application serve different purposes. Keep consistent underlying facts and ask for clarification when an ambiguous percentage or category cannot accurately describe the work. Do not invent a human contribution or conceal a generated element to fit a preferred answer.
08 / The wider distribution environment
Verification is becoming part of the release workflow
On September 14, 2026, IFPI announced the Streaming Integrity Initiative. Its baseline commitments cover customer and rights verification, content and metadata checks, action against fraud, lawful sharing of high-confidence information and measurement of enforcement. These are industry commitments, not new legislation or a judgment in the DistroKid case. They do not establish identical procedures at every distributor. [14]
The practical response is to ask a distributor clear questions before a deadline becomes urgent. What evidence is accepted? How are disputed rights reviewed? Where is an appeal sent? How does a shared-riddim release interact with optional claiming products? Record the answers and the date instead of assuming a promotional description resolves every detail.
Apply the same care to promotion. Ask a campaign provider where listeners come from and what activity is being purchased. Keep invoices, campaign descriptions and reports. Avoid arrangements built around artificial plays or concealed traffic. Good documentation should explain the release’s audience-building activity as well as the permission to release its audio.
09 / If a release is challenged
Respond to the actual issue with focused evidence
Preserve the notice, submission number, track identifiers, dates and affected services. Work out whether the issue concerns a recording, composition, sample, identity, artwork, metadata, artificial activity or a specific AI-policy requirement. Ask for clarification when the notice does not identify the problem clearly enough to answer.
Build a short response that connects each issue to an indexed document. Identify the relevant grant of permission and the exact release version it covers. Avoid sending an unorganized archive that forces a reviewer to reconstruct the project. Keep a copy of what you submitted and the support reference.
If the evidence exposes a genuine gap, resolve that gap with the contributor or rights holder before making another assertion. Do not alter identifiers or open another account to disguise the same unresolved release. A legal counter-notice or disputed ownership claim can have consequences beyond customer support; obtain appropriate advice before making formal legal declarations.
10 / Download and use the toolkit
One release, four evidence folders, one final review
The accompanying five-page checklist is fillable and printable. It covers ownership, samples and riddims, metadata, AI provenance and a final evidence index. Tick an item when it has actually been checked. Record “not applicable” or an unresolved question explicitly, with a document location and a person responsible for the next step.
Jamaican Artist Release Checklist
Five pages · Fillable PDF · Ownership, samples, metadata and AI provenance
Download the checklist ↓Open in a PDF reader to fill and save, or print a copy. Entries remain in your own file; this page does not collect them.
Use the review before scheduling delivery, and repeat it when the audio, contributors, licence, artwork or intended use changes. Preserve the completed checklist alongside the release pack so that the next reviewer can understand what was checked and what remained open.
The purpose is to give Jamaican artists a stronger account of their own work: who created it, who authorized it, how it was assembled and where its income should be directed. A clear record helps a small team defend legitimate collaboration without mistaking a distributor’s approval for ownership of the culture itself.