Answers · music
How do I dispute a YouTube Content ID claim on royalty-free music I licensed?
Last updated
TL;DR: If you really hold a license that covers the video, you can dispute the claim in YouTube Studio (Content, then the video's Claims, then See details, then Take action, Dispute) and choose the reason that you have a license or permission. Before disputing, check two things: that your license covers this use (a monetized YouTube video, on this channel, licensed before you published), and whether the music library has its own claim-clearing route, because many royalty-free libraries register their tracks with Content ID and release claims for licensed customers faster than a dispute does. A claim is not a copyright strike, but a dispute is reviewed by the claimant, not by YouTube, and a claimant who rejects it can file a copyright removal request, which can lead to a strike. So dispute only with proof in hand: the license or receipt naming the track, the date, and your channel or project.
What should I check, step by step?
1. Read the claim first: in YouTube Studio open Content, filter by Claims, then See details. Note the claimant, the matched track, the matched timestamps and the action (block, monetize or track).
- Match the claim to your license: same track title and artist, licensed before the video went live, and terms that allow YouTube use and monetization on this channel. A subscription license often covers only videos published while the subscription was active, and on the channels you registered with the library.
- Try the library's route first: most subscription and stock music libraries publish a process to clear a claim for licensed customers, such as allowlisting your channel or a claim-release form. Send them the video URL and your license ID.
- If that fails or the claimant is someone else, dispute in YouTube Studio with the license reason, and paste a short factual statement: the track, where you licensed it, the license ID or order number, the license date, and that the license covers this channel and use.
- Dispute within 5 days of the claim if you want the video's revenue held while the dispute is pending, instead of being paid to the claimant from the start.
- If the claimant reinstates the claim, you may be able to appeal; for a claim that blocks the video, Escalate to Appeal skips the 30-day dispute step. Only appeal when you are confident, because a rejected appeal can be followed by a removal request and a strike.
- If the license does not cover the use, don't dispute: trim, mute or replace the song with YouTube Studio's editor, or let the claim stand.
What evidence matters?
The license itself: a license certificate, receipt or written permission that names the track, the licensee and the date. A general "royalty-free" label on a website is weaker than a document naming you and the track.
- Coverage of the use: the license terms in force when you licensed the track (a saved copy or archived page), showing that YouTube publication and monetization are allowed.
- Timing: the order or download date, and the subscription period if it is a subscription library, set against the video's publish date.
- Identity: the channel name or URL you registered with the library, if the license is tied to channels.
- For Creative Commons music: the source page URL, the exact license and version (CC BY 4.0 is not CC BY-NC 4.0), and the credit line in your video description. Under CC BY you must credit the artist; under any NC license, a monetized video is commercial use the license does not grant.
- Things that are not evidence: giving credit, owning a copy of the song, or turning monetization off. YouTube's help pages list these as reasons that do not justify a dispute.
What happens after you dispute?
The claimant has 30 days to respond. It can release the claim, let it expire (released automatically after 30 days), reinstate it, or submit a copyright removal request.
- A valid removal request takes the video down and gives the channel a copyright strike; you can then answer with a counter notification if you are confident it is wrong.
- Content ID is limited to copyright owners YouTube has approved, who must own exclusive rights in the material, and YouTube says claimants who repeatedly make erroneous claims can lose Content ID access. If a royalty-free track you licensed is claimed by a party with no connection to the library or artist, tell the library: it is their catalog being claimed.
- Repeated or malicious abuse of the dispute process can lead to penalties against the video or channel, which is why every dispute should rest on a document.
What do the license checks say?
Yes means the license grants the use, on the duties listed. Duties such as source_disclosure, share_alike and network_source_offer are the ones that conflict with keeping a product closed-source.
| Use | Answer | Why |
|---|---|---|
| CC BY 4.0 track in a monetized YouTube video, with credit (CC-BY-4.0) | Yes | Every use you described is granted by CC BY 4.0, and nothing you described is prohibited. Duties: attribution, license_notice, state_changes, no_additional_restrictions. |
| CC BY-NC 4.0 track in a monetized YouTube video, with credit (CC-BY-NC-4.0) | No | CC BY-NC 4.0 prohibits commercial_use. Duties: attribution, license_notice, state_changes, no_additional_restrictions. |
How do I ask a2ally about this (free, no key)?
Add the MCP server https://www.a2ally.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code, then ask: “I used a CC BY 4.0 track in a monetized YouTube video and got a Content ID claim. Does the license cover this use, and what credit do I owe?”
{
"tool": "check_license",
"arguments": {
"license": "CC-BY-4.0",
"intended_use": {
"commercial_use": true,
"redistribution": true,
"attribution_planned": true
}
}
}- Pass the track's page as source_url when it is on a source a2ally reads, and it checks the license that page declares.
- attribution_string writes the credit line a CC BY track asks for, to paste in the video description.
- issue_rights_receipt (needs an API key) records a signed Rights Receipt binding the audio file's SHA-256 to its license and intended use on the ledger, dated when you cleared it; verify_rights_receipt checks one for free. Keep it with the project as proof of when and on what terms you cleared the track.
a2ally reads licenses and terms you point it at. It is not a party to YouTube disputes, cannot release or file Content ID claims, and does not decide who owns a recording.
What are the sources?
- YouTube Help: Dispute a copyright claim
- YouTube Help: Monetization during copyright claim disputes
- YouTube Help: How Content ID works
- YouTube Help: Common copyright myths
- Creative Commons Attribution 4.0 legal code
Related
- Is CC BY-NC OK for YouTube?
- Does "no copyright infringement intended" protect you?
- Who can file a DMCA takedown?
- Rights Receipt standard
Not legal advice. JSON · Markdown · All answers
Get a free API key in one call
No card and no email needed. 100 free credits; the license and policy checks stay free without a key.
curl -s -X POST https://www.a2ally.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export A2ALLY_API_KEY=rs_... # the api_key from the reply (shown once)
curl -s https://www.a2ally.com/v1/licenses/check -H "Authorization: Bearer $A2ALLY_API_KEY" \
-H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'