How to file a DMCA counter-notice: a 2026 step-by-step guide

This guide is information, not legal advice. Counter-notices have real legal consequences — federal jurisdiction consent and identity disclosure to the original sender — and you should review your situation with a qualified attorney before filing. Counterspine generates drafts; you and your lawyer ship them.

A counter-notice is the formal mechanism for restoring content that was removed under a DMCA takedown. The mechanism is statutory: 17 U.S.C. §512(g)(3) lays out exactly what a valid counter-notice must contain, and platforms (Google, YouTube, Meta, GitHub, Reddit, AWS, Cloudflare, hosting companies) have a roughly aligned process.

Done correctly, a counter-notice forces the sender either to file a federal lawsuit within 10–14 business days or watch the platform restore the content. Done sloppily, it bounces, exposes you personally, and gives the original sender ammunition.

This post covers the §512(g)(3) statutory requirements, the consequences that surprise most first-time filers, the actual process at the major platforms, and a working template you can adapt.

The statutory requirements (§512(g)(3))

A valid counter-notice must contain, in writing:

1. A physical or electronic signature of the subscriber. Most platforms accept a typed name; some require image-uploaded signatures.
2. Identification of the material that has been removed or disabled. Include the URL(s) and a description sufficient to locate the content.
3. A statement under penalty of perjury that the subscriber has a good-faith belief the material was removed by mistake or misidentification. This is the substantive heart of the counter-notice. It is signed under penalty of perjury, so don't lie.
4. The subscriber's name, address, and telephone number. Real name. Real address. Real phone.
5. A statement consenting to jurisdiction of the federal court for the district where the subscriber lives (or, if the subscriber is outside the U.S., for any judicial district where the platform is located, typically Northern District of California).
6. A statement that the subscriber will accept service of process from the original notice sender or their agent.

That's it. Six elements. But each one carries a consequence most operators don't think through.

The consequences nobody warns you about

You are consenting to U.S. federal court jurisdiction

If you are based outside the U.S. and have no U.S. assets, this is mostly theoretical — service of process abroad via Hague Convention is slow and expensive, and a default judgment in U.S. court against a foreign individual with no U.S. assets is hard to enforce. But "mostly" is doing a lot of work. If the sender does file, you have to defend (or take a default), and that costs money even when you win.

If you are based in the U.S., you are agreeing to be sued. In a forum that may not be your home district. By a sender who, if they are a copyright troll, is well-resourced and litigation-comfortable.

Your real name and physical address get disclosed to the sender

Platforms forward your full counter-notice (including name, address, phone) to the original sender as part of the §512(g)(2)(B) process. If the original notice was filed by a copyright troll, a reputation-management firm, or a bad-faith competitor, you have just handed them your home address.

Wendy Seltzer's 2010 SSRN paper Free Speech Unmoored in Copyright's Safe Harbor and the UC Berkeley Efficient Process or "Chilling Effects"? report both document this as a measurable chilling effect. The original UC Berkeley Chilling Effects dataset contained only seven counter-notices total. Modern data is barely better.

If you live alone, this is mostly an annoyance. If you have a family, a stalker, or a bad-faith adversary, this is a serious consideration. Some operators use a registered agent or a P.O. box; the legality of substitution varies by jurisdiction.

"Penalty of perjury" is real

The good-faith-belief statement is signed under penalty of perjury. If you knowingly file a false counter-notice — for example, claiming you have a fair-use right to material you actually pirated — you have committed perjury under 18 U.S.C. §1621. Prosecutions are rare, but they are not zero, and a §512(f) civil action is even more common.

The platform may not actually restore the content

Platforms have wide discretion under their terms of service. A successful counter-notice obligates the platform to restore if it wants to retain safe harbor for that material. But the platform can also choose to remove the content under its own ToS — for example, YouTube can remove videos for "community guidelines" violations even after a successful counter-notice on the copyright claim.

How to file at the major platforms

The §512(g)(3) form is the same. The submission mechanism varies.

Google Search delisting

• Submit via the Google Counter Notification form. Email-only counter-notices are still accepted but slower.
• Google's review is largely automated; expect 7–14 days for action.
• After Google forwards the counter-notice, the original sender has 10–14 business days to file suit before reinstatement.

YouTube

• For Content ID disputes: use the dispute flow inside YouTube Studio. Do not skip directly to a counter-notice; YouTube's own dispute process is faster for genuine fair-use cases.
• For copyright takedown counter-notices: YouTube's counter-notification form.
• 65% of disputes resolved in the uploader's favor in 2024 (per YouTube's Copyright Transparency Report), but only because most uploaders never dispute in the first place.

Meta (Facebook, Instagram, WhatsApp)

• Use the IP Reporting Center counter-notification form.
• Meta is slower than Google; expect 14–30 days.

GitHub

• File via GitHub DMCA Takedown counter-notice form.
• GitHub publishes counter-notices to its dmca repository — your name and address become public record on github.com/github/dmca. Plan accordingly.

Reddit

• Email [email protected] with the §512(g)(3) elements. Reddit forwards to Lumen, so the counter-notice becomes public there too.

AWS / Cloudflare / hosting providers

• Each host has its own form. AWS uses DMCA Counter-Notification. Cloudflare publishes the process at cloudflare.com/abuse.

Template (edit this; do not file as-is)

The following is a §512(g)(3)-compliant template. It is not legal advice. Replace every bracketed field. Have a lawyer review before submitting.

To: [Designated Agent of Recipient Platform]
From: [Your Full Legal Name]
Re: Counter-Notification under DMCA §512(g)(3)
Date: [YYYY-MM-DD]

I am the subscriber whose content was removed or disabled by your service in
response to the DMCA notice referenced below.

Original notice reference: [Notice ID, takedown URL, or sender name + date]

Affected material:
- URL: [https://example.com/your-page]
- Description: [brief description of the removed content]

I have a good-faith belief that the material identified above was removed
or disabled as a result of mistake or misidentification of the material to
be removed or disabled. Specifically: [one paragraph explaining why — fair
use, no copyright infringement, licensee, original author, etc.]

I consent to the jurisdiction of the United States Federal District Court
for the [judicial district where you live, or Northern District of California
if outside the U.S.], and I will accept service of process from the person
who provided the original notification under §512(c)(1)(C), or an agent of
such person.

Under penalty of perjury, I declare that the foregoing is true and correct.

Signed,
[Your Full Legal Name]
[Street Address]
[City, State, ZIP, Country]
[Phone Number]
[Signature: typed name or image]

That is the bare minimum. A strong counter-notice goes further: it cites specific §512(f) precedent (Automattic v. Steiner, Lenz v. Universal Music, MFB Fertility v. Action Care), attaches a side-by-side showing the original sender's lack of copyright registration in the work, includes archive.org timestamps proving precedence, and — if applicable — flags evidence of an abuse pattern (back-dated articles, mass fake accounts, reputation-firm involvement).

The §512(f) citations matter. They put the sender on notice that knowingly false notices carry liability. Senders who are running an abuse playbook tend to back off when their playbook gets named in writing.

What Counterspine does

We generate the §512(g)(3) draft from your evidence package — the notice, the takedown action, sender's full filing history, abuse-pattern detections, archive.org snapshots, WHOIS data on suspicious domains. You edit the draft inside the dashboard, your lawyer reviews, and you submit through the platform's form yourself. We never auto-file.

Drafts are quota'd by plan: 5/mo on Starter, 25/mo on Pro, 100/mo on Agency, 500/mo on Scale.

When to call a lawyer

Always when:
- The original notice came from a known law firm rather than a self-filer.
- You operate from the U.S. and the content is high-stakes (revenue-generating, brand-critical).
- The original sender has filed against you before.
- The §512(f) facts are strong and you want to consider counter-litigation.

Sometimes when:
- You are filing a counter-notice for the first time and want a sanity check.
- Your address would be exposed and you want to discuss alternatives.

Rarely necessary when:
- You operate outside the U.S., have no U.S. assets, the content is low-stakes, and the §512(g)(3) facts are clean.

TL;DR

A DMCA counter-notice is six statutory elements, two real consequences (federal jurisdiction consent + identity disclosure), and a single click that starts a 10–14 business-day litigation window. Done well, it works. Done sloppy, it bites. Use a template, document your evidence, and have a lawyer in the loop for anything that matters.

If you want help producing the draft from your evidence package, start your free trial.