In 2004, the Ninth Circuit drew the line that still governs most DMCA misrepresentation disputes: under 17 U.S.C. § 512(f), the sender of a takedown notice is liable for damages only if it knowingly makes a material misrepresentation, only if it actually knows its infringement claim is false when the notice goes out. A sender who frankly believes content infringes, and turns out to be wrong, is not liable. Careless is not the same as lying, and the statute punishes only the lie.
That rule comes from Rossi v. MPAA. It gives rights holders room to enforce without being perfect, and it makes life harder for creators whose work was wrongly removed. If a notice just hit your content, read this alongside what to do when you receive a DMCA notice; in most disputes, the counter-notice clock matters more than a misrepresentation claim.
The Case Behind the Standard: What Happened in Rossi v. MPAA
Michael Rossi ran InternetMovies.com, a subscription website based in Hawaii that promoted movie downloads. The Motion Picture Association of America sent takedown notices to his hosting provider under 17 U.S.C. § 512(c), asserting a good-faith belief that the site was giving members unauthorized access to copyrighted films. The host pulled the site offline.
Rossi argued the notices were false in a way that mattered. At the time, he said, the download feature did not actually work; visitors saw promotion for a service that could not yet deliver films. He sued the MPAA under § 512(f), the misrepresentation provision, and the district court granted the MPAA summary judgment. Rossi appealed, and the Ninth Circuit reversed in 2004. Rossi v. MPAA, 391 F.3d 1000 (9th Cir. 2004), answered two questions that still frame these disputes.
The first was the meaning of "knowingly" in § 512(f). The court read it as actual knowledge of falsity, a subjective test. A sender is liable only if it knows its claim is untrue when it makes it. A sender who is sincere, even sincerely wrong, is not liable.
The second was what the good-faith statement requires before a notice goes out. The copyright holder must actually form the belief the notice declares. The evidence about what the MPAA's investigator had reviewed before the notices were sent left room to doubt that the MPAA had formed that belief, and that doubt belonged to a jury rather than a judge at summary judgment.
The case went back for trial, and no published damages ruling followed. Rossi's legacy is the standard itself: a plain mistake on a takedown notice is not actionable under § 512(f). Courts nationwide cite it for that proposition.
What Section 512(f) Actually Says About Misrepresentation
The provision is short enough to read in one sitting. It imposes liability on a person who knowingly and materially misrepresents that material or activity is infringing, and, in the current version, on a person who knowingly and materially misrepresents that material was removed by mistake. The injured party can recover any damages caused by the misrepresentation, including costs and attorneys' fees.
Two words do most of the work. "Knowingly" sets the state-of-mind requirement. "Materially" sets the significance bar: the false statement has to be one that mattered to the host's decision to remove content, not a stray typo in a URL.
The rule sits inside the DMCA's safe harbor structure, the framework that protects service providers from copyright liability when they respond properly to notices, how DMCA safe harbor works covers that framework in detail. Every compliant notice must also include, under § 512(c)(3)(A)(v), a statement that the complaining party has a good-faith belief that use of the material "is not authorized by the copyright owner, its agent, or the law." Section 512(f) is the teeth behind that statement. Sign it knowing it is false and the statute opens the door to damages. Sign it sincerely, even if the belief later proves wrong, and the door stays shut.
Actual Knowledge of Falsity, Not Should-Have-Known
The Ninth Circuit had to choose between two readings of "knowingly": that the sender actually knew the claim was false, or that something looser, negligence, recklessness, a failure to check, could suffice. It chose the strict reading. Actual knowledge of falsity is required. A copyright holder who sends a notice in the candid belief that the material infringes does not become liable under § 512(f) when the belief turns out wrong.
The reasoning was practical. Notice-and-takedown only works if rights holders use it, and a negligence rule would make every enforcement decision a bet on a lawsuit. Congress targeted lies, not errors.
Three situations cover most disputes.
The candid mistake: the sender checked the material, formed a genuine belief, and got it wrong. No § 512(f) liability. The recipient's remedy is the counter-notice process, not a damages claim.
The careless but sincere notice: thin investigation, real belief. Still no liability under Rossi, though the platform may reject the notice and the sender's credibility suffers.
The knowing falsehood: the material was licensed, the sender's own review showed no infringement, or the sender was told the facts and sent the notice anyway. That is what the statute punishes, with damages, costs, and fees.
Reasonableness still matters, but as evidence rather than as the test. What the sender did or failed to check before filing is how a factfinder infers what the sender actually knew.
One geographic caveat: Rossi binds federal courts in the Ninth Circuit. Courts elsewhere frequently follow it, but the Supreme Court has never settled the question, so the analysis can shift by jurisdiction.
What the Knowledge Threshold Means for Notice Senders
If you send takedowns, Rossi is mostly good news. The law does not demand perfection; it demands sincerity backed by a real look at the material before you sign the good-faith statement. Make that routine and your § 512(f) exposure stays near zero.
Verify the specific URL before every notice. Confirm the copy is unauthorized, not a licensed distributor, not the owner's own channel, not an authorized reseller, and confirm you are the proper party to send. Who can file a DMCA takedown is a threshold question, not a formality. A sound DMCA notice template gets the statutory elements right, but the good-faith statement is only true if you did the work. Boilerplate does not create good faith; verification does.
Keep records of what you reviewed: the URL capture, the comparison against the original work, who reviewed it, and when. A takedown evidence checklist is cheap insurance, because those records are how you later prove the sincere belief Rossi protects.
Watch the dangerous pattern: repetition after correction. A first notice built on a mistaken reading is a plain mistake. Resending the same claim after the recipient produced a license, or after the platform told you the use was authorized, is how a sender crosses from error into knowledge of falsity. If a platform refuses your notice, re-verify before resubmitting; what to do when a takedown is rejected is the right starting point.
Automation needs one caution. Fingerprinting and keyword tools send notices at scale, and they scale mistakes as efficiently as they scale enforcement. A human review step on borderline cases, commentary, reaction, criticism, remix, separates a defensible program from a liability magnet.
What the Knowledge Threshold Means If Your Content Was Taken Down
If your content came down on a notice you believe was wrong, Rossi explains why a misrepresentation claim is probably not your best first move. You would have to show the sender actually knew the claim was false when it was sent. Most bad notices are errors, and errors create no § 512(f) liability, no matter how much the downtime cost you.
The faster route is the counter-notice. Learn how to file a counter-notice, then read what happens after you file a counter-notice: a host that accepts the counter-notice generally restores the material within 10 to 14 business days, unless the sender files a court action first. That is days, not years. A counter-notice carries its own weight, though. You state under penalty of perjury that the material was removed by mistake, so assess the claim frankly before filing.
Preserve everything regardless: the notice text, URLs, timestamps, screenshots of your content before removal, and the full email thread. If facts later show the sender knew better, your license on file with them, notices resent after you explained the situation, a § 512(f) claim becomes realistic, and fighting back under 512(f) is worth a professional review.
Do not ignore the platform layer. Strikes, restrictions, and termination follow platform policy rather than the statute, so a sender with no § 512(f) exposure can still put your account at risk under the platform's DMCA strike rules. Fight those battles through the platform's appeals process, on the platform's timeline.
From Rossi to Lenz: The Fair Use Duty Before Filing
Rossi set the state-of-mind standard. Lenz v. Universal Music Corp. filled in what the belief has to cover.
Stephanie Lenz posted a 29-second home video of her toddler dancing while Prince's "Let's Go Crazy" played in the background. Universal's enforcement process flagged it, and a takedown followed. Lenz sued under § 512(f), and after years of litigation the Ninth Circuit added a duty to Rossi's framework: before sending a notice, a copyright holder must consider whether the use might be fair. Lenz v. Universal Music Corp., 815 F.3d 1145 (9th Cir. 2016).
The reasoning tracks the statute. The good-faith statement requires a belief that the use is not authorized by the copyright owner, its agent, or the law, and fair use is authorized by the law. The standard stays subjective; an unreasonable belief does not automatically create liability. But the court held that unreasonableness can be evidence the sender never held a good-faith belief at all.
For senders, the translation is a fair-use screen on anything resembling commentary, criticism, parody, review, or reaction. When fair use means you should not file at all, not filing is the compliant choice. The full saga is told in the dancing baby case.
For recipients, Lenz helps most when the fair use is obvious, a review or parody the sender's system flagged without a human ever asking the question. Where fair use is genuinely contestable, Rossi's protection for candid judgment usually still holds.
When Section 512(f) Claims Actually Succeed
Wins under § 512(f) are rare, and the successful cases show what the losing ones lack: proof of what the sender knew.
The best-known example is the Diebold email case. Diebold sent takedown notices over internal company emails about its electronic voting machines that critics had posted online. The district court granted summary judgment for the notice targets, finding Diebold had knowingly misrepresented that the posted emails infringed its copyright, and it awarded costs and fees. The Ninth Circuit affirmed.
The other frequently cited example is Automattic v. Steiner, where the company behind WordPress pursued a sender who used DMCA notices abusively to try to silence a user. The court awarded damages and attorneys' fees under § 512(f).
Notice what these cases share: proof, not mere wrongness. Internal records, admissions, a claim contradicted by the sender's own files. Rossi itself produced no damages award for anyone. Its contribution is the standard that filters out weak claims and filters out the weak ones.
Frequently Asked Questions About Rossi v. MPAA and Section 512(f)
Can I be liable under section 512(f) if my takedown notice was simply wrong?
No, not for the mistake alone. Rossi v. MPAA holds that section 512(f) requires actual knowledge of falsity. If you sincerely believed the material infringed when you sent the notice, being wrong is not enough for liability, even if your investigation was thin. Liability attaches only to knowing, material misrepresentations, so document what you checked before sending.
How do you prove a notice sender actually knew the claim was false?
Usually through circumstantial evidence: internal records showing the sender reviewed the material, prior correspondence where you explained the license or fair use, notices resent after corrections, or claims contradicted by the sender's own investigation files. Courts look at what the sender saw and did before sending. That is a demanding showing, which is why successful 512(f) cases remain rare.
Does Rossi v. MPAA apply outside the Ninth Circuit?
It is binding on federal courts in the Ninth Circuit, which covers nine western states and several territories. Elsewhere it is persuasive authority. Courts outside the Ninth Circuit frequently follow its actual-knowledge reading, though the Supreme Court has never resolved the question. Non-U.S. systems are different altogether; Canada's notice-and-notice regime, for example, involves no takedown obligation and no DMCA-style remedy against senders.
What damages can a section 512(f) claim recover?
The statute allows any damages caused by the misrepresentation, including costs and attorneys' fees. In practice that means actual losses, revenue lost while the content was down, for example, plus litigation costs and fees. There is no fixed statutory amount. Because proving knowing falsity is hard, fee awards are often the practical prize, and damages alone rarely justify the fight.
Do senders really have to consider fair use before sending a takedown notice?
Yes, at least for obvious fair uses. Lenz v. Universal extended Rossi by holding that a sender's good-faith belief must account for fair use, because fair use is use authorized by the law. You do not need a perfect legal analysis, but skipping an obvious fair-use question, criticism, parody, commentary, before filing creates real 512(f) exposure.
What to Do Next
Work through the list that matches your position.
- If your content was taken down, preserve everything first: the notice text, URLs, timestamps, screenshots, and the full correspondence. Do this before replying to anyone.
- Assess the claim frankly. Decide whether the use was infringing, licensed, or fair use. That answer determines whether a counter-notice is safe and whether any 512(f) theory exists.
- If the claim is wrong, file a counter-notice and track the 10-to-14-business-day restoration window rather than counting on a misrepresentation claim.
- If you send notices, verify each URL, screen for fair use, record what you reviewed, and never resend a disputed claim without new verification.
- Watch the platform layer separately. Strikes and account actions follow platform policy, not just the statute, so run the platform's appeal process on its timeline.
- When the stakes justify it, revenue on the line, a channel at risk, a repeat abusive sender, bring in professionals. Knowing when to hire a copyright lawyer protects your options, and managed protection programs handle verification and documentation so every notice stays defensible under Rossi.