Automattic v. Steiner began with a takedown notice, not a lawsuit. In 2025, Automattic, the San Francisco company behind WordPress.com, sued the operator of a firm called Steiner Litigation in California federal court, invoking 17 U.S.C. § 512(f), the DMCA's penalty clause for people who knowingly send false removal demands. The takedown had targeted a WordPress.com blogger who had criticized Steiner, and the core question was authorship: whose words were they?

That pattern is why the case matters beyond two litigants. Most hosts remove content on a notice and never look back. Automattic removed, investigated, restored the material after a counter-notice, and then spent its own legal budget going after the notice sender, a step almost no platform takes. This page covers what happened, what the statute actually requires, and what to do if a bogus takedown lands on your content, or if you are the one sending notices.

What the Automattic v. Steiner case is actually about

First, the machinery, because everything turns on it. A DMCA takedown is a private statutory demand that a host remove material the sender claims is infringing. If you are new to the process, start with what a DMCA takedown notice actually is; this case is best understood as a fight over how that machinery gets used against critics.

As alleged in Automattic's complaint and public reporting on it, the sequence was this. A WordPress.com user ran a blog critical of Steiner's operation. Takedown notices arrived claiming copyright in the blog's material. The blogger's answer was simple: the writing was mine, not yours. Automattic, which fields takedown demands on WordPress.com every day, see how DMCA notices work on WordPress.com, reviewed the evidence and concluded the blogger, not the notice sender, was the author. The dispute then left the platform's support queue and landed on a federal docket.

Two cautions before you go further. A complaint is one side's story, written to persuade; Steiner's response, any rulings, and any settlement live on the public docket, so check the current status there rather than trusting any single article, including this one. And the statute at issue applies to every notice sent to every US-based host, including notices aimed at your content.

The authorship dispute at the heart of the takedown

Strip the names away and this is a who-wrote-it fight. The notices claimed, in substance, that the disputed material belonged to Steiner's side, that the blogger had taken it. The blogger said the opposite: the words were original. That matters legally because only a copyright owner, or someone the owner authorizes, may send a valid notice in the first place. A claim over work the sender knows was never theirs is a textbook § 512(f) misrepresentation, not a close judgment call about copying.

Platforms cannot hold trials, so a responsible host resolves an authorship dispute the way a careful reviewer would: by weighing evidence. Drafts. Publication history. Metadata. Older archived copies. Registrations. A blogger who can prove content ownership with dated material and timestamp evidence usually earns the host's confidence, and per the complaint, that is the side Automattic's review landed on.

Keep the burden of proof in view. Section 512(f) requires knowing falsity, and a sender who credibly claims to have believed the material was copied can survive the claim. But a fabricated authorship claim over a critic's original writing is exactly the fact pattern that can clear that bar, if the plaintiff can prove what the sender actually knew. That is the load-bearing question in this case, and in every case like it.

How the takedown and counter-notice played out on WordPress.com

Under the DMCA's safe harbor rules, a host that receives a facially proper notice must take the material down quickly to keep its legal immunity. That is why content disappears fast even when the claim is weak; the statute pushes hosts to remove first. The balancing mechanism is the counter-notice. The user signs a statement, under penalty of perjury, that the material came down by mistake or misidentification, provides contact details, and consents to federal-court jurisdiction.

Once a proper counter-notice arrives, the host must restore the material within 10 to 14 business days unless the notice sender files an actual copyright action seeking a court order. After that window, the only thing that keeps lawful content offline is a court order, not a second notice, not a sharper letter. The gap between a DMCA notice and a court order is the pivot this whole dispute turns on, and what happens after a counter-notice is worth knowing cold if you ever face this situation.

As alleged, that is the road this case traveled: removal, counter-notice, restoration, and no follow-through infringement suit from the notice sender, the step the statute requires for keeping disputed material down. Automattic treated that mismatch as the abuse § 512(f) was written to punish.

Section 512(f) fees: what the statute promises, why it rarely delivers

Section 512(f) is short. Anyone who knowingly materially misrepresents, in a takedown notice or a counter-notice, that material is infringing, or was removed by mistake, is liable for the resulting damages, including costs and attorneys' fees. The statute names three parties who can collect: the alleged infringer, any copyright owner or licensor injured by the misrepresentation, and the service provider. Read that third one again. The host has its own claim, staff hours, legal review, correspondence, and that standing is what let Automattic sue over abuse aimed at a single user.

Few plaintiffs succeed, and the reason is the Ninth Circuit's reading of "knowingly." In Rossi v. MPAA (2004), the court held the standard is subjective: the sender must have actually known the material was not infringing. Sloppy searches and lazy guesses are not enough by themselves. Wins do exist. In Online Policy Group v. Diebold (2004), a California federal court found Diebold's takedown threats over leaked internal emails to be knowing misrepresentations and awarded damages and fees. In Lenz v. Universal, the dancing-baby case, the Ninth Circuit added a duty to consider fair use before sending a notice, though that claim still failed years later at summary judgment, because proving what a sender actually believed is notoriously difficult.

The takeaway: § 512(f) is real but narrow. A platform with subpoena power, legal staff, and money changes the odds, and that is the quiet significance of this case.

Community defense: what Automattic's model changes for users

Hosts respond to takedown notices on a spectrum. At one end, platforms remove content, discourage counter-notices, and terminate accounts readily, partly because the safe harbor requires a repeat-infringer policy, partly because removal is cheap and defense is expensive. Users on those platforms carry all the risk of a false claim.

Automattic sits toward the other end: process the notice as the statute requires, honor the counter-notice, restore on the statutory clock, investigate, and, where the evidence says the notice was knowingly false, make the sender answer in court. Call it community defense. The platform spends resources a solo blogger could never spend, and the user gets a defense they could never fund alone. The deterrence is the point; § 512(f) recoveries are usually modest, and no one builds a business model on them.

Two candid caveats. Nothing in the DMCA obligates a host to sue bad-faith senders; this is company policy, not law, and it can change with management. And it matters where you publish. WordPress.com sites run on Automattic's own infrastructure, so its willingness to defend is decisive there. A self-hosted WordPress site lives on a third-party host whose stance, cautious, aggressive, indifferent, is your real protection. Outside the US, hosts operate under different regimes entirely, such as the EU's notice-and-action rules, and the calculus differs.

What a bogus takedown means for you as a blogger

If a false notice hits your content, the sequence in this case is your template. Start by reading the notice precisely: which work is claimed, who supposedly owns it, what exactly is accused. If the format confuses you, begin with the basics of what to do when you receive a DMCA notice.

Then do what Automattic did, scaled to one person. Test the authorship claim: pull your drafts, dated files, archives, and registration if you have one. Test fair use frankly: if the material is quoted for criticism, the notice may have been improper even if the sender owns a copyright, because senders are supposed to weigh fair use before filing, not after. If the claim fails both tests, your statutory lever is the counter-notice. Follow a proper guide to filing a counter-notice, because defects give the host an excuse to keep your material down. Understand the trade before you sign: you are accepting federal jurisdiction and inviting the sender to sue for real. Most never do. Some do.

Document everything from day one, the notice, your costs, your hours. That record is what a later § 512(f) claim feeds on, whether you pursue it yourself or hand it to someone who does. And if the host stalls past the restoration window, that is a different problem; see what to do when a DMCA takedown is rejected and what comes next for the escalation path. For the fuller strategy, our walkthrough of fighting back against a DMCA notice under § 512(f) connects the pieces.

What this case signals if you send DMCA notices

Flip the chair. If you send takedowns, read this case as a warning shot, whatever its final outcome. Owning a copyright does not entitle you to a removal; the difference between copyright and the DMCA is exactly where careless senders stumble. Before your next notice, confirm you own the work or are authorized to enforce it, the rules on who can file a DMCA takedown are not optional, and check whether the use is fair. Practitioners keep a list of situations where you should not file a DMCA notice at all for a reason: a claim over a critic's own words, sent anyway, is the profile that invites fee-shifting, a public docket, and press coverage. The dollar exposure is usually modest. The reputational exposure is not.

Automattic v. Steiner: frequently asked questions

Can a hosting platform sue the sender of a false DMCA notice?

Yes. Section 512(f) lets three parties recover: the alleged infringer, the copyright owner or licensor, and the service provider. Automattic sued in the provider's slot, seeking its own costs and fees from notices it claims were knowingly false. Platforms almost never exercise this right, which is why the case drew attention.

What can you recover under Section 512(f)?

Damages, plus costs and attorneys' fees, caused by the misrepresentation. Reported recoveries tend to be modest, staff time, legal fees, correspondence, because the injury is mostly the cost of handling the notice. The practical value is deterrence and leverage: fee-shifting makes abusive senders recalculate even when the dollars at stake are small.

Does filing a counter-notice expose me to a lawsuit?

It can. A counter-notice states, under penalty of perjury, that you hold a good-faith belief the material was removed by mistake, and it consents to federal-court jurisdiction. The sender then has roughly 10 to 14 business days to file a real infringement action; otherwise the host restores the material. Most senders never sue, but make sure your position holds up before you sign.

Does fair use automatically stop a DMCA takedown?

No. Hosts generally remove first and ask questions later, and nothing in the statute requires them to weigh fair use on your behalf. Fair use matters later: courts consider it in any infringement suit, and after Lenz v. Universal, senders must form a good-faith view on fair use before filing. Skipping that duty can support a § 512(f) claim.

Who decides authorship when a takedown is disputed?

No judge decides unless the sender files suit after a counter-notice. Until then, the platform makes a risk call based on the evidence, drafts, timestamps, archives, registrations, and either restores the material or leaves it down. Build your authorship documentation before a notice ever arrives, not after.

Your next steps

  1. If your content was taken down, preserve the original notice, screenshot the removal, and log every cost from day one. That record is the foundation of any § 512(f) claim.
  2. Test the claim before reacting. Authorship evidence and a fair-use check determine whether a counter-notice is safe to file.
  3. If the facts support you, file a proper counter-notice and let the 10-to-14-business-day restoration clock run.
  4. If the sender escalates or the host stalls, get professional help, our guide on when to hire a copyright lawyer separates the questions a lawyer must answer from the ones a takedown service can handle.
  5. If you would rather hand the whole process off, WebDMCA handles takedowns, counter-notices, and escalation for creators and site owners. We are a professional service, not a law firm, and our pricing is published up front.