DMCA Counter-Notice Defense Built on the 512(g) Restoration Window
We draft statutory counter-notices under 17 U.S.C. § 512(g), assess whether a takedown against you was filed in bad faith, and track the 10 to 14 business day restoration clock so nothing slips. Quoted case by case, per strike.
Last updated
What a counter-notice actually does
A DMCA counter-notice is the statutory reply defined in 17 U.S.C. § 512(g)(3) to a takedown you believe was sent by mistake or misidentification. Filing one does not get a human at the platform to re-review the claim on the merits. It starts a fixed procedural clock: the host forwards your counter-notice to the original complainant, who then has 10 to 14 business days to file a federal lawsuit. If no suit is filed in that window, the host must restore the material. If a suit is filed, the material stays down pending that case.
The trade you make when you file is jurisdiction. A valid counter-notice requires your name, address and phone number, and your written consent to the jurisdiction of a US federal district court plus agreement to accept service of process. That is the mechanism that flushes out anonymous bad-faith claimants, since they now have to either sue you under their real identity or let the content come back.
On the other side of the same coin, if you filed a takedown and the target sent back a valid counter-notice, you are the one facing that 10 to 14 business day deadline. Doing nothing means the content returns automatically. If your original claim was accurate, that is the point where you either file suit or accept that the removal was temporary. If your claim turns out to have been mistaken, pursuing it further risks § 512(f) liability for knowing misrepresentation.
Deciding whether to file a counter-notice at all
Filing is usually right when you clearly own or are licensed to use the material, when the claim rests on a fair-use argument you can document against the four statutory factors, or when the claimant is a repeat filer with no plausible ownership claim. It is usually wrong when the underlying dispute is not really about copyright at all: a competitor trying to suppress a product listing, or someone using a copyright claim as a proxy for a defamation or harassment complaint. In those cases, disclosing your address and consenting to federal jurisdiction buys you nothing, and the faster route is often a platform trust and safety appeal or, where the real issue is reputational, our defamatory content removal or general content removal services.
If you are the original rights holder and someone has filed a counter-notice against your takedown, the decision tree runs the other way: is the claimed fair use or ownership plausible enough that a court would take it seriously? If yes, and the stakes justify it, you file suit within the window. If the counter-notice is weak but you do not want federal litigation, you let the restoration happen and pursue removal through a different theory, such as a fresh notice against a materially different re-upload, or, where the content is defamatory rather than merely infringing, a news article takedown addressed at the underlying falsehood. For the original filing itself, see our DMCA takedown notice service.
How we handle a counter-notice, step by step
- 1
Intake and strike documentation (day 0-1)
We collect the original takedown notice or strike email in full, including headers and case IDs, screenshots of the removal banner, and your proof of ownership or license: original files with metadata, purchase receipts, license terms, or a first-publication date. This is also the point where we check whether the claim is copyright at all or a defamation dispute mislabelled as one.
- 2
Validity and bad-faith assessment (day 1-2)
We review the underlying claim against the four fair-use factors where relevant, check whether the claimant plausibly owns the work, and flag indicators of bad faith: competitor relationships, a pattern of takedowns against the same target, or claims over material that is clearly your own. This assessment decides whether a § 512(g) counter-notice, a platform trust and safety appeal, or a separate removal route is the correct tool.
- 3
Draft the statutory counter-notice
We draft every required element under § 512(g)(3): signature, identification of the material and its pre-removal location, the penalty-of-perjury good-faith statement, your contact details, and consent to federal jurisdiction. We explain in plain terms what that jurisdiction consent means before you sign anything, because it is the one irreversible step in the process.
- 4
File through the correct channel
Each platform has its own intake: YouTube's Copyright Notice webform, Meta's IP appeal tied to the case ID, GitHub's DMCA repository, or a designated agent's email address for a standalone host. Filing to the wrong address restarts the clock or gets the notice ignored entirely, so we confirm the recipient from the U.S. Copyright Office's Designated Agent Directory or the platform's published policy before submission.
- 5
Track the 10-14 business day restoration window
Once the host forwards your counter-notice to the original complainant, the clock starts under § 512(g)(2)(C). We track the exact business-day count for your platform, confirm the host received it, and follow up at day 10 if restoration has not happened, since some platforms are slow to act even after the window closes.
- 6
Evidence preservation for the litigation scenario
In parallel we build a preservation file: dated screenshots, wayback machine captures, the full notice chain, and a written timeline. If the original complainant files suit within the window, or if you later pursue a § 512(f) claim, this is the record a court or your litigator will need. We do not file suit ourselves, but we hand off a file that is ready for one.
- 7
Decision point and referral
If the complainant files suit within the window, we flag it immediately and refer you to a copyright litigator; your content stays down pending that case. If no suit is filed, the host restores within 10-14 business days and we confirm the URL is live again and re-indexed.
Platform-specific handling
YouTube requires the counter-notification through its Copyright Notice webform inside the channel's copyright strikes page, not by email. A successful counter-notice removes the strike but the video stays down for the full 10 to 14 business day window regardless. Three strikes still terminate the channel even mid-dispute.
Meta (Facebook and Instagram) ties the appeal to the case ID issued in the original removal notice, filed through the IP form in Business Help Center. Meta's timeline runs slower than YouTube's in practice, we typically see 12 to 18 business days even on unopposed counter-notices.
GitHub processes both takedowns and counter-notices publicly through its own DMCA repository on GitHub. Repositories taken down for code claims are commonly restored within 10 business days if the claimant does not respond, and GitHub publishes the notice text itself, so evidence quality matters even more here.
Cloudflare is a CDN, not the host of record for most sites behind it. A Cloudflare abuse response typically discloses the origin host rather than restoring content itself, so a counter-notice usually needs to go to the actual hosting provider once that disclosure happens, with Cloudflare's response used as supporting evidence of good faith.
Three cases, and how each one resolved
Illustrative scenarios based on typical case patterns. Client details anonymised.
Competitor takedown against a stock-photo listing
A furniture retailer's product photography was pulled from its own Shopify store after a competitor filed a DMCA claim asserting ownership. We confirmed the client held the original camera files with matching EXIF timestamps predating the competitor's site by 14 months. We filed a § 512(g) counter-notice through Shopify's designated agent on day 1. The competitor did not respond within the 14-business-day window, and Shopify restored all 11 listings on day 15. We preserved the file in case of a later § 512(f) claim.
YouTube strike used to silence a product review
A tech reviewer's video was struck after using 40 seconds of a manufacturer's promotional footage in a critical review. We assessed the use against the four fair-use factors, purpose (commentary), amount (under 3% of the source video), and market effect (none), and filed a counter-notification through YouTube's webform. The manufacturer did not file suit. YouTube restored the video on business day 12 and lifted the associated Content ID strike from the channel's record.
Anonymous harassment claim dressed up as a copyright dispute
A consultant's LinkedIn-linked blog post was hit with a DMCA claim from an anonymous account alleging the post copied their material, when in fact the post was original commentary about a business dispute. Filing a counter-notice would have forced disclosure of the claimant's identity, which we suspected was the point, so we first tried the host's fraud-reporting channel. The host reinstated the post in 6 days after reviewing publish-date evidence, without needing to trigger the federal jurisdiction consent at all. For situations where the real problem is reputational rather than a copyright dispute, our defamatory content removal team picks up from there.
10-14 day window tracked
We log the exact business-day count for your platform and chase confirmation of receipt.
All § 512(g)(3) elements
Every counter-notice is statutorily complete, including the jurisdiction consent clause hosts check for.
Platform-correct filing
YouTube, Meta, GitHub and origin-host filing behind Cloudflare, each routed to the right intake.
Counter-notice defense FAQ
Someone filed a counter-notice against my takedown. Can I stop the restoration?
Only by filing a federal lawsuit for copyright infringement and notifying the host within the 10 to 14 business day window set by 17 U.S.C. § 512(g)(2)(C). If you do not file suit in that window, the host must restore the material. There is no administrative appeal, no phone call to the platform that stops the clock. If the counter-notice is facially valid, filing suit or accepting restoration are the only two paths.
What makes a counter-notice legally valid versus something a host can ignore?
Under § 512(g)(3) it must include the subscriber's physical or electronic signature, identification of the material and its location before removal, a statement under penalty of perjury of a good-faith belief the material was removed by mistake or misidentification, the subscriber's name, address and phone number, and consent to the jurisdiction of the subscriber's federal district court (or, if outside the US, any district where the host may be found), plus agreement to accept service of process. Missing the perjury statement or the jurisdiction consent is the most common defect we find when reviewing an incoming counter-notice for a client.
Does filing a counter-notice really force someone to reveal their real identity?
Yes, and that is precisely why most bad-faith takedown filers never respond to a counter-notice at all. Sending it requires the discloser's true name, mailing address and phone number to be passed to the original complainant, plus consent to be sued in federal court. Anonymous defamation and harassment campaigns that hide behind copyright claims usually fold at this step rather than expose the filer to a lawsuit and a § 512(f) claim.
What is 512(f) misrepresentation liability and is it worth pursuing?
17 U.S.C. § 512(f) creates liability for anyone who knowingly materially misrepresents that material is infringing when filing a takedown. Damages include the target's costs and attorney's fees, and in egregious repeat cases, actual damages. It is a high bar, courts require actual knowledge of falsity, not mere carelessness (Rossi v. MPAA, Lenz v. Universal), so we only recommend pursuing it where there is clear evidence the claimant knew the material was not infringing, for example a competitor claiming ownership of stock photography they never licensed.
My content was pulled by a bad-faith DMCA claim. Do I have to file a counter-notice?
No. A counter-notice is one option, but it triggers federal jurisdiction consent and a 10 to 14 day exposure to litigation. Where the claim is really a defamation or harassment dispute dressed up as copyright, we often get faster and lower-risk results through the platform's own trust and safety escalation, or by pursuing the underlying issue directly. See our work on defamatory content removal and content removal for the non-DMCA routes.
How is a platform-specific counter-notice different from the statutory one?
The statutory elements under § 512(g)(3) are fixed, but each platform wraps its own intake around them. YouTube requires the counter-notification through its Copyright Notice webform and will not accept it by email; it also displays a public Content ID strike history separate from the DMCA claim. Meta requires the appeal through its IP form inside Business Help Center, tied to the case ID from the original strike. GitHub processes counter-notices through its DMCA takedown repository on GitHub itself and typically restores within 10 business days if unopposed. Cloudflare is not a host of record for most sites; a Cloudflare abuse response usually needs to be paired with a filing to the actual origin host once Cloudflare discloses it.
Can you file a lawsuit for me if the original complainant does not back down?
We are not a law firm and do not file or litigate federal cases. What we do is draft and file compliant counter-notices, assess the strength and bad-faith indicators of the original claim, preserve evidence to the standard a court would expect, and refer you to a copyright litigator in your jurisdiction when a case genuinely needs one. Most disputes resolve without a filed suit because the original claimant does not want to disclose their own identity or face § 512(f) exposure.
What should I do right now if my content just went down?
Do not re-upload the exact file to the same URL, that can be read as circumventing the takedown. Screenshot the strike notice and case ID immediately, save the platform's removal email in full including headers, and preserve your original proof of authorship or license. Send us these within 24 hours and we will tell you within one business day whether a counter-notice, a platform appeal, or a different removal route is the right move.
Send us the notice and we will assess it free
Tell us which platform, what was claimed, and what proof you have. We come back with the correct route and a quote for your case, usually within one business day.