Someone filed a DMCA notice against your content, and the claim is bogus, the material is yours, or licensed, or obvious fair use, or the sender holds no rights in it at all. United States law gives you a counterweight. 17 U.S.C. § 512(f) makes anyone who knowingly and materially misrepresents that material is infringing liable for the damage they cause, expressly including your costs and attorney's fees. Federal courts have put real money behind that provision, against Diebold in 2004 and against a takedown sender sued by Automattic in 2015.

The candid caveat: § 512(f) claims are hard to win, because you must show the sender knew the claim was false, not merely that they were careless. Most bad-faith disputes never reach a courtroom. They end with a counter-notice, a documented retraction demand, and a paper trail strong enough that the sender withdraws rather than risk paying your lawyer. This guide covers the legal standard, the cases that gave it teeth, and the moves to make this week.

What § 512(f) Actually Says

The statute is short and pointed. Any person who knowingly materially misrepresents, in a takedown notice, that material is infringing, or in a counter-notice, that material was removed by mistake, must pay the damages the misrepresentation causes, expressly including costs and attorney's fees. Three groups can sue: the alleged infringer injured by a false notice, a copyright owner injured by a false counter-notice, and the service provider itself. That last category is why Automattic could sue over notices aimed at its users.

Two words do the work. "Knowing" means the sender either knew the claim was false or made it with no candid belief in it. "Material" means the false statement mattered to the takedown decision. A mistaken sender sits outside the statute's reach.

A few structural facts follow. The platform that removed your content is generally not liable to you: providers are sheltered when they act on a facially proper notice, which is exactly why they act fast, the safe harbor bargain rewards speed over certainty. No platform will enforce your § 512(f) rights for you; that claim belongs to you, in federal court or at the Copyright Claims Board. And the penalty-of-perjury language in the notice attaches to the sender's claim of authorization to act for the rights holder, not to the assertion that your content infringes. That clause gives you little by itself. § 512(f) is the remedy that does the work.

The Knowing-Misrepresentation Standard: Rossi v. MPAA

The standard comes from the Ninth Circuit's 2004 decision in Rossi v. Motion Picture Association of America. Michael Rossi ran a website that an MPAA agent concluded was selling pirated films. The site purported to do exactly that, but it never delivered any files, so nothing on it infringed. After the MPAA's notices got his internet service cut off, Rossi sued under § 512(f). The district court granted the MPAA summary judgment. The Ninth Circuit reversed and set the test courts have worked from since.

To be liable, a sender must have actually held a subjective good-faith belief that the material was infringing, and that belief must have been objectively reasonable, judged against what a reasonable copyright owner would have believed or done in the same circumstances. An agent who glanced at a homepage and fired off a notice, without confirming that the claimed files exist, can flunk the reasonableness half. Rossi also confirmed that statutory damages under § 504(c) of the Copyright Act flow through § 512(f), which matters when your dollar losses are hard to prove.

The limits matter just as much. In Lenz v. Universal, the dancing-baby case, the Ninth Circuit held in 2016 that senders must consider fair use before filing, because fair use is lawful use. Stephanie Lenz still lost her § 512(f) claim: a Universal employee had manually reviewed the 29-second video of her toddler before the notice went out, and the court accepted that brief look as a good-faith belief. Sloppy-but-honest senders survive. Knowing ones do not.

§ 512(f) Damages and Attorney's Fees: Diebold and Steiner

Two decisions show what winning looks like when the standard is actually met. Both produced damages and fee awards.

In Online Policy Group v. Diebold, decided in the Northern District of California in 2004, leaked internal Diebold emails about its electronic voting machines were posted online, including by two Swarthmore students and their internet service provider. Diebold answered with DMCA notices. The court found a knowing material misrepresentation: the postings were quintessential fair use of material with obvious public significance, and the court saw Diebold's purpose as suppressing embarrassing material rather than protecting any market for it. The court awarded $10,000 in statutory damages plus attorney's fees and costs.

In Automattic Inc. v. Steiner, the same district in 2015, Charles Steiner sent takedown notices targeting a WordPress.com article about a business dispute he was involved in. The fatal flaw was ownership: the court found he had knowingly misrepresented rights he did not hold. Automattic sued as the service provider and won statutory damages of $960 for each of the two notices at issue, plus attorney's fees.

Three lessons. Fee shifting is the real teeth, the sender pays your lawyer, which changes the math on fighting back. The strongest claims involve rights the sender knew they lacked, or fair use so plain that a plain look would have stopped the notice. And both winning plaintiffs were organized and represented. Individual recipients win the same way: with documents, not indignation.

Building the Evidence Record While It's Fresh

Your § 512(f) leverage lives or dies on the record. Build it while timestamps are intact, before reinstatement makes the whole thing feel over.

  • The notice itself. Full text, email headers, delivery times, the exact URLs targeted, the sender's identity. Check it against the required elements of § 512(c)(3), a compliant notice has a fixed shape, and formal defects matter both to the platform's obligations and to how a court later frames the dispute.
  • Your proof of rights. Dated drafts, source files, registrations, purchase or license records, whatever establishes that the content is yours.
  • The platform's paper trail. Takedown confirmations, restore dates, the counter-notice receipt, and any strike applied to your account.
  • Knowledge and motive. Emails admitting a competitive grievance, prior disputes with the sender, notices aimed at criticism rather than copying.
  • Impact. Lost sales, lost traffic, money spent responding. § 512(f) compensates damages incurred, you will need to show what they were.

Dating matters more than people expect; a takedown evidence checklist is good discipline while you assemble all of this. Creation dates, publish history, and registration records can establish that no reasonable sender could have believed you stole the work. That is the reasonableness half of Rossi, proven with files instead of assertions.

Demanding a Retraction Before Anyone Sees a Courtroom

Most knowingly false notices collapse when the sender realizes the recipient is documenting. A retraction demand turns your record into leverage. Send it in writing, keep it businesslike, and cover five points:

  • the notice you are answering, date, URLs, sender;
  • the facts that defeat the claim, with evidence attached: ownership, license, or fair use;
  • the legal position: § 512(f) liability, the Rossi standard, and the Diebold and Steiner awards;
  • a deadline, five business days is customary, for a written withdrawal sent to the platform;
  • a closing statement that all claims and remedies are preserved.

Retraction has mechanical effects, too. If the notice went to Google for search delisting, a withdrawal filed by the sender restores your results, Google's DMCA removal process has a retraction path. Most platforms treat a notice of withdrawal as the end of the matter, and strikes or account flags can be cleared with it.

Some notices die earlier: platform review rejects them outright because formalities are missing, and the content never comes down. When that happens, the dispute shifts fully to the sender's next move, what to do when a takedown is rejected is its own scenario.

Watch the response, whatever it is. A sender who refuses to withdraw a facially false claim after a documented, courteous demand is helping you show knowledge. Keep the exchange.

The Counter-Notice: Starting the 10–14 Business Day Clock

The counter-notice is the statutory lever that forces a decision. Under § 512(g), it states under penalty of perjury that you have a good-faith belief the material was removed by mistake or misidentification, gives your contact information, and consents to federal jurisdiction. What a DMCA counter-notice is and isn't is worth knowing cold before you send one. Once the platform passes it along, the sender has a short window: file a court action, or the platform restores the material in 10 to 14 business days.

Two cautions. First, the counter-notice puts the sender to a choice, and a genuinely bad-faith actor may file suit, it is the only way to keep your content down, and your jurisdictional consent means the case lands in federal court. Second, § 512(f) cuts both ways. A counter-notice asserting mistake you know to be false creates the same liability the notice did. Send it when it is true, never as a bluff; the mechanics of filing one are simple, but the statement is sworn.

For how the restoration window plays out in practice, including the sender-sues branch, walk through what happens after you file. Platforms also differ in how they treat account history after restoration; platform policy, not the statute, governs that part. Pair the two tools: the counter-notice starts the statutory clock, and the retraction demand gives the sender a dignified exit before it runs.

Bad-Faith Patterns Courts and Platforms Recognize

Abusive notices cluster into recognizable patterns. Naming yours helps you frame the record, and sometimes helps the platform's reviewer see what they are looking at.

Competitive sabotage. A rival targets your listings, reviews, or product pages to disrupt sales at a critical moment. Motive evidence does the work here: market overlap, prior disputes, timing.

Silencing criticism. Commentary and reviews sit near the core of fair use, and courts have not been polite about notices aimed at them, Diebold is the archetype. A sender who targets criticism rather than copying is advertising purpose, and senders have clear obligations not to file over obvious fair use.

Ownership confusion over AI-generated material. Who holds rights in AI output is genuinely contested. Senders claiming infringement in AI-generated images or text often cannot show the exclusive rights the statute requires, which makes their good-faith story hard to sustain, see our coverage of AI-generated content and copyright.

The wrong legal tool. Some senders use copyright notices to fight impersonation, such as a fake profile pretending to be them. Impersonation follows its own removal path, and a sender who confused the two regimes has a hard time claiming a reasonable copyright belief.

Serial targeting. Repeated notices from the same sender, against you or others, establish pattern and knowledge. Keep them all.

When to Hand a § 512(f) Dispute to Counsel

Escalate to a lawyer when the sender files suit after your counter-notice, when the notices keep coming, when revenue or your channel is at stake, or when you are weighing an affirmative § 512(f) claim and the sender has assets worth pursuing. Venue comes in two flavors. One is federal court. The other is the Copyright Claims Board, the CASE Act small-claims forum, which has jurisdiction over § 512(f) claims, caps recovery at $30,000, and is built for self-represented parties. A respondent can opt out and push the case to federal court, so the Board is a cheaper first move, not a guaranteed one.

The economics favor well-documented claims: fee shifting plus statutory damages mean a proven knowing misrepresentation can largely pay for its own enforcement. That is why the record-building steps above matter so much. On timing, see our walkthrough of when hiring a copyright lawyer makes sense. One boundary, stated plainly: we are a professional takedown service, not a law firm. We handle the notice and counter-notice workflow; litigation belongs with counsel. And if you or the sender sit outside the United States, leverage depends on the platform's US footprint, whether the DMCA works internationally is its own question, with different notice systems and remedies abroad.

Frequently asked questions

Can I recover under § 512(f) without proving dollar losses?

Yes. The statute covers any damages you incur, expressly including costs and attorney's fees, and the Ninth Circuit in Rossi read § 512(f) to include statutory damages under § 504(c). Diebold produced $10,000 in statutory damages plus fees; Automattic recovered $960 per notice against Steiner. Costs and fees often exceed the statutory award, which is the real exposure for a bad-faith sender.

What separates a plain mistake from a knowing misrepresentation?

Rossi requires proof that the sender lacked a subjective good-faith belief that the material infringed, or that whatever belief they held was objectively unreasonable. A sender who reviewed the content and misjudged fair use usually wins, as Universal did against Lenz. A sender who knew they held no rights, or targeted criticism or a competitor, fits the statute. Carelessness alone is not enough.

Does § 512(f) apply to counter-notices too?

Yes, and the exposure runs both directions. The statute covers knowingly misrepresenting, in a counter-notice, that material was removed by mistake or misidentification, and it protects the copyright owner injured by that misrepresentation. File a counter-notice only when you genuinely believe the removal was a mistake; the penalty-of-perjury clause and § 512(f) liability both attach to your filing.

What if the sender neither retracts nor sues after my counter-notice?

The platform must restore your material within 10 to 14 business days if the sender files no court action, so silence usually ends the takedown. It does not erase a § 512(f) claim. If you suffered documented losses while the content was down, the claim remains available, and your record is already assembled if you decide to use it.

Can I pursue a foreign sender under § 512(f)?

Sometimes, with difficulty. The DMCA is United States law, and jurisdiction over a foreign sender depends on that sender's contacts with the US platform and forum. Serving process and collecting a judgment abroad are slow and uncertain. Many platforms apply DMCA-style procedures worldwide, but other countries run separate notice systems with their own remedies and standards.

Your Next Steps

  1. Save the full paper trail today, the notice, headers, platform emails, your own copies of the content. If you have not yet worked through the basics of responding to a DMCA notice, start there.
  2. Assemble your rights documentation: ownership, license, or fair use, dated and organized.
  3. File the counter-notice to start the 10–14 business day restoration clock.
  4. Send the retraction demand: your evidence, § 512(f), the Rossi and Diebold authority, and a deadline.
  5. Track the window. If the sender sues, get counsel immediately; if they do not, confirm restoration and ask the platform to clear any strike.
  6. If the targeting is repeated or business-critical, hand the file to professionals. We run both sides of the notice process, filings and responses, through our managed takedown work, and we will say plainly when it is a lawyer's job instead.