A DMCA strike is the black mark a platform attaches to your account after it grants a copyright takedown request. The takedown is the legal document that removes the content, the video, the listing, the file. The strike is what happens to the account behind that content: a recorded offense, counted toward termination.
The two words get used interchangeably, but they are different halves of one event, and the distinction decides outcomes. A takedown is survivable. A strike is cumulative. Enough strikes and the account goes, channel, followers, revenue, usually with no appeal.
Takedown vs. strike: the two halves of one event
A takedown notice is a formal demand under 17 U.S.C. § 512(c). The rights holder, or an agent acting for one, identifies infringing material on the platform, and the platform must remove it expeditiously to keep the safe harbor that shields it from liability for user uploads. Platforms almost always comply, and the content disappears. That completes the takedown half.
The strike half is the platform's bookkeeping. Granting a valid takedown creates a record: this account hosted infringing material and was formally notified. That record is the strike. It outlives the removal, attaches to the account rather than any single upload, and counts toward the platform's termination threshold. If the front half of the event is what you're facing, the anatomy of a takedown notice and what it must contain is covered separately.
Why platforms hand out strikes: the repeat-infringer requirement
Strike systems are not platform cruelty. They are a statutory condition turned into software.
The DMCA's safe harbor, the immunity that lets platforms host user uploads without being sued for them, comes with strings. One of them, 17 U.S.C. § 512(i)(1)(A), requires a service provider to adopt and reasonably implement a policy terminating, in appropriate circumstances, the accounts of repeat infringers. Skip that condition and the safe harbor is gone.
The statute never defines "repeat infringer." No number, no threshold, no procedure. Platforms had to invent all of it, strike counters, warning emails, termination triggers. Getting this wrong is expensive. In BMG Rights Management v. Cox, a federal appeals court held that Cox Communications forfeited safe-harbor protection because it wrote a repeat-infringer policy and then quietly stopped enforcing it. After that case, no platform treats strikes as optional.
So when a platform terminates on a third strike, it is performing its statutory duty, not being harsh. How safe harbor works and what goes into a repeat-infringer policy are covered separately.
How a copyright strike lands on your account
The mechanics are consistent even when the numbers differ. A valid takedown arrives. The platform removes the content and notifies the uploader of what was removed and who claimed it. Then the platform logs the strike. From that moment it counts, even though the content is already gone.
The numbers matter. YouTube is the famous case: three copyright strikes on the account at the same time and the channel is terminated. Strikes there expire after roughly 90 days, Copyright School required, so the real rule is three live strikes simultaneously, not three in a lifetime. Filing a takedown against a YouTube video is its own topic because YouTube runs two enforcement systems at once.
That layering is the most misunderstood part. YouTube also runs Content ID, an automated fingerprinting system that flags matched content and redirects monetization. A Content ID claim is not a copyright strike: no statutory counter-notice, no strike counter, no termination math, only its own dispute process. A claim becomes a strike only when the rights holder files an actual DMCA removal request. Reading how Content ID claims work prevents plenty of false alarms.
Other platforms count differently. Twitch's notice process and the systems behind Instagram and TikTok takedowns set their own thresholds; some publish a number, most simply state that repeat infringers are terminated. Policies shift, so verify current terms.
How strikes clear: retraction, counter-notice, and expiry
Strikes are not permanent, and there are exactly three ways one disappears.
Retraction, the claimant withdraws the takedown. Platforms restore the content and remove the strike. This happens more often than people expect when the strike came from a plain mistake: a label's automated system hitting licensed use, an agency hitting its own paying customer. A short, professional, evidence-backed message to the claimant's designated agent works. Rage does not.
Counter-notice, the route with legal teeth, for when the removal was a misidentification: you licensed the material, the use was defensible, or the claimant never owned it. You file under 17 U.S.C. § 512(g). Once a valid counter-notice is on file, the platform restores the content in roughly 10 to 14 business days unless the claimant files an actual lawsuit to restrain you. The claimant must choose between suing a real person in a real court and dropping the matter. On YouTube, if no suit arrives, the strike comes off. The mechanics and risks are in the counter-notice guide; read what happens after you file before signing anything.
Expiry, where the platform allows it, you wait the strike out. On YouTube that means roughly 90 days plus Copyright School. Expiry resets the visible count. What it does not do is erase history: nothing in the statute requires a platform to forget a takedown, and nothing stops it from weighing that record later when judging whether an account belongs to a repeat infringer.
You received a strike: what to do first
One rule has no exceptions: do not re-upload the same content. A second strike from the same claimant is far worse than the first. The notice established your knowledge, and continuing after notice is what willfulness arguments are built on, the pattern that raises damages exposure. You would also burn a second strike toward termination and gain nothing.
Next, read the notice like evidence, because it is. Identify the claimant, the exact content removed, and whether the claimant plausibly owns what it claimed. Some strikes trace to mistake or overreach, agencies claiming works they do not control, claimants whose ownership is shaky. Save the notice and every platform message about it.
Then pick your path. If you owned or licensed the content, say so with proof, proving content ownership is its own discipline, and ask for a retraction while you weigh a counter-notice. If the use was defensible, counter-noticing is the designed remedy. If the claim was right, the plain answer is expiry: take the strike, keep the account, stop the behavior. The full decision tree is in what to do when a DMCA notice arrives, and copyright infringement penalties covers what follows if a dispute escalates.
What you cannot do is nothing. An uncontested strike sits on the account, counts, and never expires faster for being ignored.
What a DMCA strike is not
A strike is not a lawsuit. No court is involved, no money changes hands, nothing is adjudicated. The platform checks the notice for formal validity, not who truly owns the copyright, and acts.
A strike is not a fine and not a criminal matter. Nobody owes money because a strike was issued, and platform enforcement by itself never creates criminal exposure.
What a strike is, though, is evidence. The notice shows you were told about a specific claim, and your response, or silence, is recorded. If a dispute later becomes a lawsuit, that paper trail is what the claimant's counsel will use: notified once, did it again. That is why the difference between a DMCA notice and a court order matters: a strike feels like a ruling but carries none of one.
Strikes also do not cross platforms. A YouTube termination does not automatically reach Twitch or Instagram; each platform keeps its own count. The underlying acts are yours, though, and in litigation they are cumulative evidence everywhere.
When platform policy, not US law, drives the strike
The DMCA is American law, but platforms enforce their strike rules worldwide because running one global policy is simpler than running dozens of local ones. A strike received in Germany, Brazil, or Japan from a US platform: the DMCA authorized the removal; the count toward termination is platform policy.
Elsewhere the law itself differs. The EU's Digital Services Act notice-and-action regime imposes its own obligations on platforms, and Canada's notice-and-notice system forwards notices without forced takedowns, strikes there are almost pure platform policy. Whether the DMCA applies abroad changes your legal hooks, even when the platform's strike counter does not.
You're issuing strikes: leverage with liability attached
For a rights holder, the strike system is a leverage multiplier. One valid takedown removes the content and moves the uploader toward losing the account, for serial re-uploaders, the only consequence they feel. Deleting a video is an inconvenience. Ending a channel changes behavior.
That power cuts both ways. Filing a takedown triggers account-level punishment for another person on the strength of your say-so. File on gray-area content, material that might be defensible, might be licensed, or that you have not verified you control, and you hand the uploader grounds for a misrepresentation claim under 17 U.S.C. § 512(f). Courts read a knowing-falsity requirement into that statute, and Rossi v. MPAA is the classic illustration; fighting back under § 512(f) covers the uploader's side. The judgment framework for when not to file exists for exactly this reason, and if you are sending notices yourself, the DIY takedown path documents the mechanics step by step.
The discipline for issuers: verify ownership, verify the copy, check for licenses, then file. Volume without verification is how enforcement programs turn into § 512(f) defendants.
Strikes also stop working against a determined operator. Accounts terminated for repeat infringement reappear under new names quickly, and a fresh account starts at zero. Individual strikes treat symptoms. Tracking the operator across accounts is what pattern monitoring is built for, and a managed takedown documents the repeat history so a platform or registrar can act against the operator, not the account of the week.
Frequently asked questions about DMCA strikes
How many DMCA strikes until my account is terminated?
Three is the best-known threshold because YouTube terminates channels with three live strikes at once, each expiring after roughly 90 days. The number is platform policy, not law, the DMCA requires terminating repeat infringers without defining "repeat." Other platforms set their own thresholds or simply reserve termination rights.
Does a DMCA strike go away on its own?
Often, yes. On YouTube a strike expires after roughly 90 days if you complete Copyright School; other platforms set their own expiries or remove strikes on retraction. Expiry resets the visible count, but the platform keeps its record of the removal, and may lawfully weigh that history later.
Is a DMCA strike the same as being sued?
No. A strike is platform enforcement: no court, no damages, no judgment on who owns the copyright. It is not harmless, though. If you counter-notice, the claimant must sue within days to keep the content down, and the strike's paper trail, the notice, your response, any re-uploads, becomes the evidentiary backbone of any later lawsuit.
Can I get a strike removed if the claim was mistaken?
Yes, two ways. The claimant can retract, which removes the strike and usually restores the content, worth requesting directly with proof of a license. Or you file a counter-notice under 17 U.S.C. § 512(g), forcing the claimant to either sue or accept restoration in roughly 10 to 14 business days. Read the mechanics before acting.
Will a DMCA strike affect me on other platforms or show up in records?
No. Strikes are internal platform records; they do not transfer between platforms, and a YouTube termination does not reach Twitch or Instagram. Nor are they court records. What travels is the conduct: if a dispute becomes litigation, takedowns across platforms become evidence of one pattern.
What to do next
- Read the strike notice and record three facts: the claimant, the removed content, and the response deadline.
- Do not re-upload the same material anywhere until the dispute is resolved.
- Choose one path, retraction request, counter-notice, or expiry, and commit to it; re-uploading while disputing is the worst combination.
- If you issued the strike and were wrong, retract quickly. Speed limits both the uploader's harm and your § 512(f) exposure.
- If the same content keeps reappearing on new accounts, stop filing one-off strikes and shift to tracking the operator behind them.
- Keep every document, the notice, your response, all platform messages, in one place. If this ever becomes a lawsuit, that file is your defense.