Quick answer: a claim is automated revenue capture — the rights holder monetizes or restricts the content, your channel survives. A strike is a formal DMCA takedown — content removed, a mark on your channel, and a few of them ends it. Same underlying cause (unlicensed material), wildly different stakes.
The severity ladder, bottom to top
- 1. Auto-muted VOD (Twitch): matched audio silenced after the fact. Not a strike — but a flare showing what a sweep would find.
- 2. Content ID claim (YouTube): automated match → rights holder takes the ad revenue, sometimes blocks regions. No strike, but your monetization on that content is gone and the material is now on the record.
- 3. DMCA takedown / copyright strike: a human filed a legal notice. Content comes down, the strike counts toward repeat-infringer termination, and on YouTube three active strikes ends the channel.
Why the distinction changes your response
Claims: business decision. If the music was genuinely unlicensed, accept the revenue loss or remove/replace the audio — disputing a valid claim invites escalation to a manual strike. Strikes:emergency. Read the notice, remove matching content everywhere (the same song probably exists in other VODs), and only counter-notify if you truly held rights — it's a sworn legal statement, not an undo button. Full incident playbook: got a DMCA strike? do these 5 things.
Living below the ladder entirely
Every rung starts the same way: copyrighted audio reached your broadcast. Choose music that's actually licensed for streams, and let StreamHushhandle the audio you didn't choose — it recognizes copyrighted songs live and mutes them off your stream in ~2 seconds, before they exist in any VOD for a claim, a mute, or a strike to find. Your voice never drops.