A DMCA counter notice is the uploader's sworn statement that your takedown was filed by mistake or misidentified their material, and it restarts a hard clock. Under 17 U.S.C. § 512(g), the host will put the content back online within 10 to 14 business days unless you tell it you've filed a court action seeking to restrain the uploader. So the decision in front of you is narrow and time-boxed: verify the counter-notice, read what it tells you, then choose between letting the content return, challenging the counter-notice itself, or going to court.
Most counter-notices in routine piracy situations are bluffs that fold when tested. Some are not, and those are the expensive ones. The way to tell the difference is to work the process deliberately, inside the window, starting with what the law actually requires the document to contain.
What a DMCA counter-notice legally is
Section 512(g) of the Copyright Act is the counterweight to the takedown mechanism you just used. Once material comes down, the uploader can swear under penalty of perjury that the removal was a mistake or misidentification. To be effective under § 512(g)(3), a counter-notice must contain all of the following:
- The uploader's physical or electronic signature.
- Identification of the removed material and where it appeared before removal.
- A statement under penalty of perjury of a good-faith belief that the material was removed by mistake or misidentification.
- The uploader's name, address, and telephone number.
- Consent to the jurisdiction of a US federal district court covering their address, or, for an address outside the United States, any US district where the service provider may be found, plus agreement to accept service of process from you or your agent.
Read the last element twice. By counter-noticing, an uploader consents to be sued in US federal court and hands over a real name, address, and phone number. For a pirate hiding behind a VPN and a throwaway email, that is an extraordinary concession, which is why genuine commercial infringers almost never file one.
One nuance most people miss: the perjury attaches to their good-faith belief, not to ownership of the work. A counter-noticer can frankly swear that belief and still be flat wrong on the facts. A counter-notice settles nothing, it just moves the fight somewhere you can actually win it.
The 10–14 business day clock, and why hosts restore
Once the host's designated agent receives a valid counter-notice, § 512(g)(2) requires the host to promptly send you a copy and inform you that it will replace the material in no less than 10 and no more than 14 business days after receipt, unless the host first hears from you that you've filed an action seeking a court order to restrain the uploader.
The host's behavior stops looking strange once you see the safe-harbor math. A provider that follows the counter-notice procedure, including timely restoration, is shielded by § 512(g)(1) from claims based on removing the material or failing to keep it down. A provider that ignores a valid counter-notice complicates its own immunity story. Hosts are structurally indifferent, they are not judging who is right, they are following the statute to keep their protection. If that trade-off is unfamiliar, reading how safe harbor actually works explains most of what platforms do in these situations.
Business days, not calendar days. Two to three calendar weeks, longer when holidays stack up. The window runs from the host's receipt of the counter-notice, not from when you opened the email, a distinction that has cost complainants deadlines they thought they had. Platforms layer policy on top of the statute, too: many will want to see proof of the court filing before they treat the window as frozen.
First moves: verify the counter-notice before you accept the clock
Before you react legally or emotionally, react forensically. Counter-notices get filed wrong constantly, and a defective one never triggers the restoration duty at all. Check the document against the five elements above and look for the defects that recur in real files: a missing signature or a typed pseudonym; a description too vague to identify anything; the jurisdiction and service-of-process consent missing entirely, which is common when foreign uploaders copy a template from a forum; contact details that are obviously nonfunctional.
If you find defects, write the host through the same designated-agent channel you used for the takedown. Quote the specific missing element and ask that the counter-notice be treated as invalid. Hosts do reject defective counter-notices, because honoring an invalid one buys them nothing and adjudicating disputes costs them money. Give the abuse desk a clean, factual reason to rule your way.
Two cautions. Calendar the deadlines anyway, because some hosts restore on a defective counter-notice rather than adjudicate, plan as if the clock runs until the host confirms otherwise. And start assembling your evidence file while you wait: originals, dated copies, registration status, a timeline. If this escalates into a dispute about whose work it is, being ready to prove content ownership before you're under deadline pressure is worth a great deal.
What the counter-notice tells you about the uploader
Whatever else it is, a counter-notice is intelligence. It tells you the uploader exists, is reachable, read your notice, and chose to swear something under penalty of perjury rather than let the takedown stand. What they swore about is a preview of the case you would actually have to fight.
"I made it myself." On a work only you could have made, this misidentification claim dies the moment your originals and timestamped proof of authorship appear. People who actually create things show source files; they don't guess at what happened.
"I had a license." Demand it in writing. If they bought a resale right from some third party, it either doesn't exist or doesn't cover them, and producing a fabricated license under penalty of perjury is how casual infringers promote themselves into defendants.
"It's fair use." This one can be genuinely defensible, and pretending otherwise is how complainants get hurt. Weigh the four factors, purpose and character of the use, nature of the work, amount taken, effect on the market, frankly, before spending a dollar. The same analysis from the filing side is in our guide to when fair use means you shouldn't file a DMCA at all; if their claim survives it, letting go deserves a harder look than your gut wants to give it.
Bluffs follow a pattern: boilerplate with no facts about your specific work, a claimed license nobody could plausibly have sold, recycled phrasing. A real defense names things. A bluff just swears.
Your three options priced
Each of your three moves carries a true price. Price all three before you pick; the option that feels best in the moment is rarely the one the facts support.
Option A: Let it go
Letting the content return is sometimes the correct business call: the page had no traffic, the value is low, or your original claim was shakier than you would want tested in front of a judge. There is no statutory penalty for declining to sue. The costs are quieter. A determined re-poster just learned you fold, and on some platforms an accepted counter-notice also clears the strike from the uploader's account, resetting where they stand under the platform's repeat-infringer rules. Document everything, keep the file, and set a reminder to watch for reposts, a new copy at a new URL is a fresh takedown, not a continuation of this one.
Option B: Challenge the counter-notice itself
This is the defect letter above, plus a substantive response aimed at the host, because the host is the only actor who can do anything right now. If the counter-notice claims a license you know is fake, "I purchased distribution rights from the original site", respond with proof that no such license was ever granted, and say plainly that the sworn statement appears to be a knowing misrepresentation. Misrepresentation claims under § 512(f) cut in both directions: an uploader who knowingly files a false counter-notice can be liable for your damages, costs, and attorney's fees. Most piracy counter-notices fold when challenged this way, specifically, in writing, with the statute quoted back, because the person who filed one never expected anyone to check. The challenge only counts inside the window.
Option C: Sue, or credibly prepare to
Filing a federal copyright action seeking to restrain the uploader stops the restoration, and nothing else does. This is attorney territory: budget several hundred dollars in filing fees plus counsel time, and know that for US works you generally need a registration certificate before an infringement suit can be filed. Registration timing also shapes recovery: without timely registration, statutory damages and fee-shifting are off the table, and actual damages plus profits are all you can pursue. Whether copyright registration is worth it is a question best answered long before a counter-notice forces it.
If court is the destination, a § 512(h) subpoena may be available to make the provider disclose the account holder's identity so you can name a defendant. Note the cheaper alternative and its catch: the Copyright Claims Board hears small copyright claims at a fraction of litigation cost, but § 512(g) speaks of a court order, so do not assume a CCB filing freezes the restoration, confirm what the platform accepts before relying on it.
The move that ends most of these matters costs less than a filing: a lawyer's letter inside the window, attaching a complaint that is signed and ready to file. Counter-noticers are betting you won't spend money. Showing them the bet costs you nothing is often enough.
If the counter-notice is against you
Flip the scenario. Your content was taken down by someone else's bad or botched notice, and you are the uploader. The counter-notice is your remedy: file a proper one and the host restores your material in the same 10 to 14 business days unless the complainant sues. A step-by-step guide to filing a counter-notice covers the § 512(g)(3) elements in the order the statute expects them.
File only if you are right, because the document costs you something either way: the same perjury exposure, your legal address in the complainant's hands, and consent to be sued in federal court. The mechanism also punishes abuse on the other side. In one publicly litigated example, Automattic v. Steiner, a host sued a takedown sender who had filed a bad notice and then abandoned the matter after the uploader's counter-notice, and the court awarded the host its fees under § 512(f). That symmetry is what makes the tool safe for people who use it frankly.
Preventing the next counter-notice
Counter-notices cluster around weak notices: thin ownership claims, overbroad URL lists, gray-area fair-use targets that hand the uploader a defensible sworn statement. A precise, evidence-backed takedown, exact URLs, dated originals, narrow scope, no overreach, draws far fewer challenges, because contesting one costs the uploader something real: their identity, their address, and perjury exposure.
Two habits improve everything downstream. Register important works early, so the certificate already exists if enforcement ever escalates toward court. Keep the evidence file current, originals with creation dates, publication records, chain of title, so the next counter-notice meets a complainant who can document ownership in hours rather than weeks.
If you would rather not hold this kind of deadline yourself, a managed takedown service builds the case file, watches the restore window, and runs the escalate-or-fold analysis when a counter-notice lands, including knowing which defects are worth a letter and which are worth a shrug.
Frequently asked questions about DMCA counter-notices
How long do I have to respond to a DMCA counter-notice?
The host may restore the material as early as 10 business days after receiving the counter-notice and will treat its window as closed by day 14 unless you first report a court filing. The clock runs from the host's receipt of the counter-notice, not from when you read the email, confirm the receipt date with the designated agent and calendar the day-10 and day-14 marks immediately.
Can the host refuse to restore the content?
Nothing in the statute requires a host to put material back up. The restore-in-14-days procedure is how a service provider earns legal immunity, not a mandate, a host can keep content down and simply accept the different exposure that creates. Some platforms' terms also reserve the right to keep material down regardless of a counter-notice. The DMCA sets the default; platform policy can override it in either direction.
What happens if I ignore the counter-notice completely?
The host reinstates the material and, from the platform's perspective, the matter closes. You lose nothing substantively, your copyright still exists, and you can pursue the infringer separately at any time. What you've spent is the platform-level remedy and the leverage the deadline created. Meanwhile the uploader has handed you a signed document with a usable address, which has value if you ever revisit the matter.
Can I re-file the same DMCA takedown after the content is restored?
Hosts generally reject a second identical notice for the same material at the same location, and § 512(f) makes re-asserting a knowingly false claim increasingly expensive, after a counter-notice, you're on notice of their position. A genuinely new instance, though, a fresh upload at a different URL or by a different account, is a new claim you can notice normally. Same content, new location, new takedown.
Can I still sue the uploader after the 14-day window closes?
Yes. The window controls whether the host restores the material; it is not a statute of limitations on your infringement claim, and restoration gives the uploader no license and no immunity. Practically, you've lost the deadline's leverage, and a restored uploader may drift off the platform, making identification harder. If litigation was realistic at all, it is more realistic inside the window.
Your next ten business days
If a counter-notice is on your desk today, work it in this order:
- Calendar both ends of the window now, day 10 and day 14, counted in business days from the host's receipt of the counter-notice.
- Verify the document against the five § 512(g)(3) elements. If it is defective, send the designated agent a factual letter asking that it be treated as invalid.
- Read the sworn statement for what it concedes: identity, address, reachability, and their best theory of defense.
- Assemble the evidence file, originals, dates, registration status, and price all three options against the content's actual value.
- If the content matters, book a copyright attorney consult this week. Initial consultations are frequently free, and knowing when to hire a copyright lawyer before day 10 is the cheapest hour you will spend on this.
- Decide and act before the window closes. Letting it lapse by default is a decision too, make yours on purpose.