Quick answer: Twitch scans VOD audio against a copyrighted-music database. On a match, it mutes the surrounding segment — and the muting is blunt, historically silencing large blocks where everythinggoes quiet: the song, your jokes, the clutch call. Live audio isn't affected; the recording pays the price.
Is it a strike? (No — it's a warning shot)
Muting is Twitch protecting itself beforerights holders act, so it doesn't count against you. But read it as intelligence: the scanner just publicly marked exactly where claimable music sits in your archive. A manual sweep reads the same signal — muted VODs are how channels discover, too late, what their archive was carrying.
Can you un-mute it?
Only two honest paths: dispute the match if you genuinely licensed that music (the dispute is per-segment, and false disputes invite escalation), or edit around it — export, cut the segment, re-upload as a highlight. If the song was really there without a license, the mute stands. Which is why everything useful happens before the VOD exists:
Keeping VODs clean (the real fix)
- Enable the Twitch VOD track in OBS — your live stream can carry music while the recorded VOD gets a clean mix without it. Setup in the OBS DMCA guide.
- Use stream-licensed music for everything intentional — the safe-music map.
- Silence the accidents live: StreamHush recognizes copyrighted songs in your audio and mutes them in ~2 seconds — the song never reaches the broadcast, so the VOD scanner finds nothing and your commentary survives intact. It mutes only the music source; your voice keeps rolling.
The difference in outcomes is stark: Twitch's mute silences a half-hour of you; StreamHush's mute silences three minutes of a song. Same trigger, opposite collateral.