Do platforms have to ban repeat infringers?

You send a takedown notice, the upload disappears, and a week later the same account posts it again. Our internet law practice page describes how takedowns, counter-notices and escalation fit together. This page covers the narrower question of what the law actually requires a platform to do about an account that keeps coming back, and how to build the record that makes a platform, or a court, take the pattern seriously.

How the repeat infringer rule works, step by step

1. The platform claims a safe harbor. A service that stores material at a user's direction is shielded from money damages for that material if it meets the conditions in 17 U.S.C. 512(c), including removing material "expeditiously" after a proper notice. Search engines and link directories have a parallel harbor in 512(d).
2. It names an agent. The hosting harbor applies only if the platform designates an agent to receive notices, posts the agent's contact details on its service and gives them to the Copyright Office (512(c)(2)). You can look the agent up in the Copyright Office's DMCA Designated Agent Directory.
3. You send a valid notice for each upload. Each notice must contain the six elements in 512(c)(3)(A), from your signature to the statement made under penalty of perjury. Our page on what a DMCA takedown notice must include walks through them.
4. A threshold condition applies to every harbor. Under 512(i)(1)(A), the harbors apply only if the platform "has adopted and reasonably implemented, and informs subscribers and account holders" of a policy that provides for terminating repeat infringers "in appropriate circumstances."
5. A second condition covers technology. The platform must also accommodate and not interfere with "standard technical measures" (512(i)(1)(B)), a defined term in 512(i)(2).
6. The platform does not have to go looking. Section 512(m)(1) says the harbors are not conditioned on a platform monitoring its service or seeking out infringement, so your notices are what put the pattern in front of it.
7. If the user pushes back, a clock starts. A counter-notice leads the platform to restore the material 10 to 14 business days after receiving it unless you file suit first (512(g)(2)(C)), as our page on what happens after a counter-notice explains.

The statute does not set a number of days for "expeditiously." The Copyright Office's May 2020 report on section 512 says courts have read the word flexibly, case by case, and the Office largely agreed with that approach.

What counts as a repeat infringer, and how many strikes?

The statute does not say. The Copyright Office's report observes that section 512 does not define "adopted" or "reasonably implemented," gives no examples of when termination is warranted, and does not quantify "repeat," asking whether it means "two or twenty or somewhere in between." Courts have mostly left platforms discretion to define the term for their own service.

Two points are clearer. First, the Office reads "repeat infringer" to mean a repeat alleged infringer, not someone a court has found liable, which matches the Fourth Circuit's 2018 decision in BMG Rights Management v. Cox Communications as the report describes it. Second, the Office says the rule "certainly cannot mean" a platform must terminate a user after a single notice identifying a single instance of infringement. Between those points, the platform's own policy and the facts decide.

The Office was critical of how lenient the case law had become. It concluded that "the bar for demonstrating reasonable implementation and appropriate circumstances has been set so low for OSPs as to be largely impractical," and recommended that Congress monitor the issue. As of October 4, 2026, section 512(i) reads as it did when the report was issued.

How should you document repeat notices?

A platform applies its policy to the notices it can connect to one account. The Office's report describes the Second Circuit faulting a platform that "did not even try to connect" known infringing activity from takedown notices to the users who kept uploading, but you should not count on the platform to make the connection for you. Keep your own log from the first notice, and send each new notice so that it names the account and lists your earlier notices against it.

When the log shows a pattern, write to the designated agent separately from any single takedown. Ask the platform to apply its repeat infringer policy to the account, attach the log and quote the policy language from its terms of service. Keep the request factual and limited to valid notices, since knowingly misrepresenting that material is infringing creates liability for damages, costs and attorneys' fees under 512(f).

What can you do if the platform will not act?

A platform that ignores a documented pattern risks its safe harbor, but losing the harbor does not by itself make the platform liable. Section 512(l) says failing to qualify does not count against the platform's other defenses. In Cox Communications v. Sony Music Entertainment, decided March 25, 2026, the Supreme Court held that a service provider is contributorily liable only if it induced the infringement or provided a service tailored to it, and that the DMCA "merely creates new defenses" rather than imposing liability on providers who serve known infringers.

In practice, then, the strongest escalation is usually aimed at the uploader. If you do not know who that is, our page on finding out who is behind an anonymous infringing account covers the clerk-issued subpoena in 512(h).

Once the uploader is identified, a demand letter is often the first step; our post on cease and desist letters explains how they work. For a modest claim, compare the Copyright Claims Board with court. If the copying is commercial and continuing, our page on what happens in a copyright lawsuit in Atlanta federal court covers filing, service and the timeline in the Northern District of Georgia.

What changes the answer

• The kind of service. Section 512(i) applies to every harbor, including internet access providers under 512(a). The report records providers' argument that cutting off home internet access is more drastic than closing a social media account, and the Office noted that colleges and universities may need a different approach.
• Copyright or trademark. Section 512 covers copyright only. Counterfeit listings and fake accounts run through marketplace brand programs and trademark law, which our page on stopping counterfeit sellers on online marketplaces covers. Cloned stores and impostor profiles are the subject of our page on business impersonation online.
• Who sends the notice. A notice must be signed by a person authorized to act for the owner of an exclusive right (512(c)(3)(A)(i)). An exclusive licensee can qualify, as our page on whether a licensee can sue an infringer explains.
• Notice quality. A notice that fails to comply substantially with 512(c)(3)(A) is not considered in deciding whether the platform had knowledge (512(c)(3)(B)), so a defective notice may not count toward a strike.
• Counter-notices. Section 512(i) does not say whether an upload restored after a counter-notice counts as a strike. That is left to the platform's policy, so read it.
• Registration timing. A U.S. owner must register before suing (411(a)), and statutory damages and fees depend on registering in time (17 U.S.C. 412). Our page on copyright registration cost and processing time compares the options.
• Standard technical measures. The definition in 512(i)(2) requires a broad, open, multi-industry consensus. The Office's 2020 report noted that, to that date, no technologies had been designated as standard technical measures, so this condition has had little practical effect.

A worked example

Common mistakes

• Sending notices through the wrong channel. A complaint through a general contact form may not reach the designated agent, and the agent is who the statute names.
• Treating every notice as a fresh case. Notices that never mention the earlier ones make the pattern invisible.
• Padding the count. Notices for material you do not own, or that is clearly licensed, expose you to 512(f) liability and undercut the real ones.
• Assuming a ban is guaranteed. The statute leaves the number of strikes to the platform; read its policy before promising yourself a result.
• Suing the platform first. After the 2026 Cox decision, a claim against a provider for merely serving a known infringer faces a high bar; the uploader is usually the better target.
• Waiting to register. Unregistered U.S. works cannot be sued on, and late registration can cost statutory damages.

What to do this week

1. Start a log with every notice already sent: account, URL, work, date, reply and outcome.
2. Look up the platform's designated agent in the Copyright Office directory and confirm your notices went there.
3. Find and save the platform's repeat infringer policy from its terms of service, with the date.
4. Capture and save each new upload before you report it.
5. Register the works that keep being copied, starting with the most valuable.
6. Send the agent a separate written request to apply its policy, with the log attached.
7. Decide now whether you would pursue the uploader if identified, so a counter-notice does not catch you unprepared.

Frequently asked questions

Does a platform have to tell me what its repeat infringer policy says?

Not necessarily. The statute requires the platform to inform subscribers and account holders of the policy, and the Ninth Circuit held in Motherless that telling users a policy exists was enough. The Copyright Office disagreed and called a clear, publicly available policy the appropriate minimum, but that view is not binding.

Does a platform have to search for other copies after my notice?

No. Section 512(m)(1) says the harbors do not depend on a platform monitoring its service. The Office's report adds its view that a platform should not simply ignore information about repeated infringement once it has it.

Are filtering or fingerprinting tools required?

Not by section 512. A tool would matter under 512(i)(1)(B) only if it met the standard technical measure definition, and the Office's 2020 report noted none had been designated. The report notes that fingerprinting tools are nonetheless used by many platforms, outside that framework.

Does the rule apply to my internet provider as well as social platforms?

Yes. The 512(i) conditions apply to every safe harbor, including the one for providers that only transmit data. Whether ending a household's internet access is "appropriate" is a sharper question, which the report discusses.

Can a repeat uploader sue me for my notices?

Only for knowing, material misrepresentations. Section 512(f) makes a person who knowingly misrepresents that material is infringing liable for the damages, costs and attorneys' fees that result. Accurate notices about works you own are the protection.

How long do I have to sue a repeat uploader?

A copyright suit must be commenced within three years after the claim accrued (17 U.S.C. 507(b)), so keep your log dated from the first upload. What you can recover depends on registration timing and the facts, which our page on copyright infringement damages explains.

Zala IP Law helps creators and companies send takedown notices, track repeat uploads and decide when to escalate, and Shreepal J. Zala practices federal intellectual property law nationally. If the same account keeps coming back, request a consultation or call 404-313-1701 with your log in hand.