A valid counter-notice starts a statutory sequence that runs like clockwork. The host forwards the counter-notice to the complainant, warns that the content returns in 10–14 business days, and then restores it, unless the complainant files a court action against the uploader and notifies the host. The host judges nothing. It runs the clock.

That clock is what this page covers: what happens next after a counter-notice is filed, in the order it happens, for both sides. Where the rule is fixed by statute, we say so. Where platform policy or a foreign host changes the outcome, we flag that too.

The counter-notice timeline, day by day

The sequence below assumes a counter-notice that passes inspection. What a valid one must contain, signature, identification of the removed material and where it was, the sworn statement, contact details, consent to jurisdiction, is spelled out in how a DMCA counter-notice works. What follows is what the statute does with a valid one.

  • Day 0, the counter-notice lands. The host checks it against the elements of 17 U.S.C. § 512(g)(3). Defective counter-notices get rejected on paper alone, and a rejected one never starts the clock. Uploaders: read the rejection, fix the named defect, refile. Complainants: reading the counter-notice for defects is the cheapest first move you have, if it's invalid, the content was never going anywhere.
  • Days 1–3, the forward and the warning. § 512(g)(2) requires the host to promptly send the complainant a copy of the counter-notice along with the standard warning: the material will be restored in not less than 10 and not more than 14 business days unless the complainant files a court action. That forward goes to whatever contact information the original takedown listed. If that address is an inbox nobody watches, the window can run out unread.
  • Days 3–10, the decision window. The complainant chooses between three moves: withdraw the takedown, fold, or litigate. Uploaders should not mistake silence for safety. A lawsuit filed on day 9 and communicated to the host before restoration blocks the return just as effectively as one filed on day 1.
  • Days 10–14 (business), restore or hold. No court notice by the end of the window and the host puts the material back. Court notice received and the content stays down, the dispute has left the takedown system entirely. A complainant who withdraws the takedown usually gets the content restored sooner than the deadline.

Business days mean weekends and holidays don't count, so the statutory window typically stretches across two to three calendar weeks. Hosts restore on their own schedule inside the range, often toward the outer edge, and a day or two of platform processing drift is normal. Don't plan around the edges. Plan around the deadline.

What the host does, and never does

The host is a mailbox with a statutory duty, not a judge. It verifies paperwork, forwards notices, runs the clock, and restores on schedule. It will not decide who owns the content, weigh fair use, or investigate either party's story. If your dispute needs a human to rule on the merits, that human wears robes.

The mechanical behavior is not indifference; it is the safe-harbor bargain. A provider that keeps content down after a valid counter-notice with no court notice on file risks the protection that makes hosting other people's material legally survivable. Safe harbor is why the DMCA works the way it does, and the restore duty is one of its load-bearing terms.

Two consequences uploaders tend to miss. First, you generally have no claim against the host for taking the content down in the first place, § 512(g)(1) protects providers who removed material on a facially valid notice, and the counter-notice process is the remedy Congress built for exactly this situation. Second, the host cannot charge you for restoration or demand that you disprove the infringement as a condition of the clock running. A provider that requires you to prove your innocence has stopped following the statute and started adjudicating, which is a different problem entirely.

What "filing a court action" actually requires

The only thing that holds the content past the window is an actual suit: filed in a court, naming the uploader, and seeking an order restraining continued infringement of the specific material. An attorney's stern email does not count. A drafted complaint does not count. A filed case number counts, and only if the host knows about it.

Two requirements decide most outcomes here.

  1. The host must receive notice of the filing. § 512(g) holds the material only if the provider's designated agent receives notice that the suit was filed. A complainant who files quietly and never tells the host can watch the content restore on schedule anyway. Send the case number and a copy of the filed complaint to the host's agent, every US provider's registered agent is searchable through the Copyright Office's DMCA agent directory, and confirm receipt.
  2. The suit must fit the statute's description. The action has to target the uploader and seek an order restraining the infringing activity relating to the material. A case against somebody else, or a case seeking only money for past conduct, doesn't match the text. In practice, complainants file a federal copyright complaint against the counter-noticing user and include a request for injunctive relief.

The uploader's counter-notice has already removed the two annoying preliminaries of any lawsuit, where to sue and how to serve. By signing it, the uploader consented to jurisdiction in the federal district of their address, or for uploaders located outside the United States, any district in which the provider is located, and accepted service of process from the complainant. That is the trade at the heart of the counter-notice: your address for your content.

One more nuance. If the host receives court notice, its statutory restore duty is spent. If that suit later collapses, dropped, dismissed, settled, you ask the platform to restore as a matter of policy. The DMCA no longer forces its hand.

For small-value disputes, the Copyright Claims Board looks cheaper than a federal courtroom. It is an administrative small-claims forum, not a court, and whether it satisfies § 512(g)'s hold requirement is unsettled. Do not bet the restore window on it. Treat the Copyright Claims Board as a separate conversation with counsel.

This is also where takedown economics turn into litigation economics. Filing fees, service, attorney time, and the schedule of a real docket replace the flat cost of sending notices; what a DMCA campaign actually costs stops being the relevant number the moment a case exists. Once one does, both sides should be reading when a copyright dispute justifies a lawyer instead of operating on instinct.

If you're the copyright owner: read it, then decide

Start by reading the counter-notice like a clerk. Check the statutory elements. If contact details or the sworn statement are missing, tell the host, a defective counter-notice may never have started the clock, and the content is not going anywhere while the uploader fixes the paperwork.

Then read it like a negotiator. Most piracy counter-notices are filed to see if you blink. The tells: no real name or a fake address (sworn to under penalty of perjury, which is its own problem for them), a license claim with no license attached, jurisdiction consent copied without reading, meaning they have told you where they can be sued. One more thing a bluff hands you: a pirate who counter-notices has provided their real identity and address, sworn under penalty of perjury. Sometimes the counter-notice is worth more than the content was.

Your three moves inside the window:

  1. Withdraw. You retract the takedown and the content returns. This costs nothing but the round, and if you were wrong, it is the cheapest exit in the entire system.
  2. Fold. Let the window lapse without filing. Restoration is not an admission by anyone and forfeits nothing, you can still sue later if the numbers ever justify it.
  3. Litigate. File a real suit and notify the host within the window. The content stays down and the dispute continues in court.

Run the litigation math before choosing. What is the work worth? Are statutory damages and fee-shifting available, which usually turns on whether the work was registered in time; how statutory damages work covers that arithmetic, and can you actually collect from this uploader? A registration-backed claim against a counter-noticing pirate with assets is a different animal from an unregistered claim against an anonymous one.

Two cautions. If there is genuine doubt about ownership or fair use, folding is cheap and doubling down is not, the situations where fair use means you shouldn't have filed at all are worth reviewing before you escalate. And while § 512(f) punishes knowing misrepresentations, the bar is deliberately high: Rossi v. MPAA held that liability requires actual knowledge of falsity, not carelessness. The shield for senders is narrow, but a pattern of aggressive, wrong claims builds the other side's best exhibit.

If you're the uploader: restoration is a round, not a verdict

If your content comes back, you have won the takedown round, not the argument. Restoration means the host's process finished. It does not mean a court agreed with you, and it does not stop the copyright owner from filing a lawsuit afterward, the window controls hosting, not litigation rights.

Three things stay with you after the content returns.

The strike. Strike systems belong to the platform, not the statute. What a DMCA strike is is decided by the platform's rules, and restoration does not automatically erase it. Enough strikes on the account, regardless of this one's outcome, and you meet the platform's repeat-infringer policy, the path to termination runs on the platform's ledger, not the statute's.

The sworn statement. If your counter-notice was truthful, licensed use, misidentification, fair use, restoration stands, the record shows you were right, and that is the whole story. If you bluffed, the statement is now documented with your signature on it, and a knowingly false counter-notice can itself create liability, as the § 512(f) playbook unpacks. A bluff that survives does so because nobody challenged it, not because it was safe.

The address. Your name, address, and phone number are now in the complainant's hands, along with consent to suit in a specific district. For a genuine fair user that is a fair price for restoration. For a pirate, it is a confession with paperwork attached.

How to file a counter-notice properly covers the mechanics, including one nuance many uploaders miss: you can withdraw a counter-notice. If you realize mid-window that the sworn statement was wrong, withdrawing stops the restore clock and the content stays down. Trading a restored video for avoiding a documented lie is, some days, the smart trade.

Where the script changes: platforms, search engines, and offshore hosts

Three departures from the statutory sequence come up constantly.

Platforms layer their own rules on top. Strike systems, mandatory web forms, and different counters for different claim types are policy, not statute. Fingerprint-matching systems like Content ID run dispute flows that never touch the DMCA clock at all. The 10–14 day rule is the floor; the platform decides everything above it.

Search engines run their own clock. A campaign that hit both the host and a search engine's de-indexing process created two separate proceedings. Your counter-notice to the host does not automatically reach the search engine, and restoration does not restore rankings. If the URL is still de-indexed after your content is back, that notice has its own counter-notice process and its own window. Mirrors of the content on other platforms are separate takedowns with separate clocks too, one restore never cleans the others.

Offshore hosts never promised to follow the DMCA. The restore duty binds providers relying on the US safe harbor; a host in another country answers to its own regime, the EU's notice-and-action framework, Canada's notice-and-notice system, or nothing at all. Where the DMCA does and doesn't reach is the map you need if the counter-notice crossed a border.

The permanent record both sides are building

Every document in this exchange gets archived. Takedown notices received by the major platforms are published to the Lumen Database, and the statements from both directions become part of any later case file. In Online Policy Group v. Diebold, the sender's own notices became the evidence of knowing misrepresentation, and § 512(f) followed with fee-shifting. Write every sentence like a judge will read it eventually. In this system, sometimes one does, and by then the sentence is already sworn.

Questions both sides ask

Does the content always come back after 10–14 business days?

Almost always, when three things hold: the counter-notice was complete, the host processed it correctly, and no court-action notice reached the host inside the window. Platform policy can add friction, and an offshore host never owed you the DMCA in the first place. If the deadline passes on a US host with no restoration, follow up in writing and cite § 512(g), restoring on the clock is the price of the host's safe harbor.

Can the complainant still sue me after the content is restored?

Yes. The window only decides whether the host must put the material back, it resolves nothing about infringement and shields neither side. Letting the clock run costs the complainant nothing procedurally, and the counter-notice has already handed them your address, a pre-consented forum, and acceptance of service. Restoration followed by a lawsuit is a real pattern, especially where the work is registered and statutory damages are in play.

My counter-notice was rejected as defective, did I lose anything?

No. Rejection for missing elements is almost always curable, and because a rejected counter-notice never starts the window, nothing has lapsed. Read the host's rejection for the specific defect, most name it directly, fix it, and refile. The 10–14 business day clock begins when the host receives a valid counter-notice, not when you first attempted one.

Does a counter-notice clear the strike on my account?

No. Strike systems belong to the platform; the statute has nothing to say about them. Restoration puts the content back, and the strike record stays on the account under platform policy. Some platforms let strikes age out or expunge them after an internal process, but that is policy, not a DMCA right, the platform's own copyright rules, not federal law, control your account.

Who actually sees my personal information in the counter-notice?

The host and the complainant, by design, your name, address, and phone number travel to the person you're disputing with, because suing you inside the window is the point of the process. Parts of the exchange can also become public: takedown notices routinely surface in transparency databases, and everything becomes an exhibit if a court gets involved. Use contact details you're comfortable standing behind, and write in a tone that reads well later.

Your next steps

Inside the window, in the order they matter:

  1. Complainants, read the counter-notice today. First for defects, then for merit. A valid one with no merit means fold; a bluff means decide fast.
  2. Complainants, if you file suit, tell the host the same day. Send the case number to the designated agent and confirm receipt. A suit the host never hears about holds nothing.
  3. Uploaders, be upfront about your sworn statement. If it's true, wait out the clock quietly and let restoration do the talking. If it isn't, withdrawal is cheaper than a documented lie.
  4. Uploaders, inventory the other removals. Search results, mirrors, other platforms: separate notices, separate clocks. One restore doesn't clean them.
  5. Both sides, keep the file clean. Every sentence in this exchange is archived and may be read aloud later. Write like it.
  6. If this recurs, serial infringement, serial counter-notices, windows stacking up, have a managed takedown service run the clocks for you instead of running them by hand.