Filing a DMCA Counter-Notice After a Takedown: A Practical Checklist

Intellectual Property > Copyright | Published 16 March 2026 - Updated 3 April 2026 | UpLaw - uplaw.us

A counter-notice is not an "undo" button. It is a sworn statement that flips a burden and starts a clock. Used by the wrongly accused, it is the cleanest way to get lawfully removed work restored. Used by the caught, it is an engraved invitation to a lawsuit you have already told a federal court you will show up for.

Keywords: DMCA counter-notice, Section 512(g), counter-notification, put-back procedure, mistake or misidentification, consent to federal jurisdiction, fair use, restoration clock, Section 512(f) misrepresentation, designated agent, substantial compliance

---

Congress knew that a "remove-on-demand" system would be abused. Any regime that lets a stranger disable your content with a single letter, and rewards the platform for pulling it down fast and asking questions never, is a regime built to be gamed by competitors, cranks, and censors. So the same statute that created the takedown created its counterweight: the counter-notification under 17 U.S.C. § 512(g). It works by inverting the pressure. Send a conforming counter-notice, and the service provider must put the material back, no sooner than 10 and no later than 14 business days after it receives the counter-notice, unless the party who sent the original takedown tells the provider it has filed a lawsuit to restrain the alleged infringement. Do nothing for two weeks, and the content returns on its own.

For most people whose work was wrongly pulled, that is the whole story, and it has a happy ending. The overwhelming majority of improper takedowns are never followed by a federal complaint, because filing one costs money, exposes the sender to a fee-shifting fight, and requires the sender to actually own a copyright and actually believe it was infringed. But "usually works" is not "always safe." The counter-notice is a statement made under penalty of perjury, it hands your name, address, and phone number to the very person who targeted you, and it prospectively consents to being sued in a federal court you may never have set foot in. Treat it with the seriousness of a filing, because that is what it is.

This checklist is written for the recipient of a takedown, the subscriber whose photo, video, article, song, code, or product listing vanished with a terse notice from a platform. It covers the honest self-assessment that has to come first, the audit of the notice that hit you, the five statutory elements you must swear to, the mechanics of sending it and watching the clock, and the aftermath, including the real but narrow exposure under Section 512(f). For the sender's side of the same exchange, see the companion checklist for sending a DMCA takedown notice; for the platform's compliance obligations, see staying inside the DMCA safe harbor.

The mechanism in one breath

Strip away the procedure and the counter-notice does exactly one thing: it shifts the risk of being wrong from you back onto the accuser. Under the notice-and-takedown structure, a platform that receives a facially valid notice takes your content down first and reasons later, because Section 512(g)(1) shields it from your breach-of-contract or other claims when it removes material in good faith. The put-back procedure in § 512(g)(2) is how the platform keeps that shield with respect to you: if you file a proper counter-notice, the platform restores the content and is protected from the copyright owner too, so long as it follows the statutory steps. The result is that after a counter-notice, the platform steps out of the middle, and the fight, if there is one, is between you and the accuser in court. The counter-notice does not adjudicate infringement. It just decides who has to file suit to keep the content down, and the answer is: the person who sent the takedown.

How the notice-and-takedown machine actually runs

Before drafting anything, it helps to see the whole board. Three parties sit at the table, and each is responding to a different incentive.

The copyright owner (or its agent) sends a takedown notice under 17 U.S.C. § 512(c)(3)(A). A substantially compliant notice does two things: it obligates the platform to remove or disable the identified material to keep its safe harbor, and it can supply the platform with the "actual" or "red flag" knowledge that would otherwise cost the platform its protection. See Perfect 10, Inc. v. CCBill LLC, 488 F.3d 1102, 1111-13 (9th Cir. 2007) (a notice that does not substantially comply cannot be used to charge the provider with knowledge).

The service provider wants only one thing: to stay inside the § 512 safe harbors, which convert potentially catastrophic secondary-liability exposure for user infringement into a manageable notice-and-takedown chore. To qualify at all, the provider must satisfy the gateway conditions of 17 U.S.C. § 512(i), including a reasonably implemented repeat-infringer termination policy, and it must have registered a designated agent with the Copyright Office. See BMG Rights Mgmt. (US) LLC v. Cox Commc'ns, Inc., 881 F.3d 293, 303-05 (4th Cir. 2018) (safe harbor lost where the provider's repeat-infringer policy was a sham). Because the statute gives the provider no reason to investigate whether a notice is meritorious, and every reason to remove fast, your content comes down quickly and with little scrutiny. That is a feature of the design, not a malfunction.

You, the subscriber, are the party the counter-notice exists to protect. The DMCA "sets out a method for a subscriber to provide notice objecting to the take down of content it posted," and on receiving a proper counter-notice the provider must restore the material to avoid liability to you. The statute does not ask the platform to weigh your fair-use argument or your license. It asks only whether you filed a conforming counter-notice and whether the accuser sued. Everything substantive is deferred to a courtroom that, in most cases, no one ever books.

Two structural points follow from this design, and both matter to your decision.

First, the platform is not your adjudicator, and it is not your ally. It will not evaluate the strength of your fair-use position or referee a factual dispute about who owns a photograph. It processes forms. A counter-notice that "substantially complies" gets your content the automatic restoration; one that does not gets ignored, and the provider has no obligation to help you fix it. That asymmetry is deliberate: while a provider must take reasonable steps to help a sender cure a takedown notice that substantially complies but lacks some contact detail, 17 U.S.C. § 512(c)(3)(B), no parallel duty runs to a subscriber who botches a counter-notice.

Second, the § 512 counter-notice path applies only to certain safe harbors. The hosting safe harbor for material stored at the direction of users (§ 512(c)) and the information-location-tools safe harbor (§ 512(d)) run on notice, takedown, and counter-notice. The conduit safe harbor for transitory digital communications under § 512(a), the one your internet access provider relies on when it merely passes packets, does not use the notice-and-takedown or counter-notice machinery at all. If your ISP forwarded you a copyright complaint under a graduated-response or "six strikes"-style program, a § 512(g) counter-notice is the wrong tool; that is a contract-and-policy problem, not a put-back problem. Know which safe harbor you are inside before you draft.

Phase 1 — The honest self-assessment before you swear anything

A counter-notice is a sworn statement, under penalty of perjury, that your content was removed "as a result of mistake or misidentification." 17 U.S.C. § 512(g)(3)(C). Before you can sign that, you have to be able to believe it in good faith. Phase 1 is the gut check, and it is the single most important part of this checklist, because everything downstream assumes you belong on the counter-notice path in the first place.

• [ ] Confirm the material is not actually infringing. Walk through the ways that can be true: you created the work yourself; you hold a license (express or implied) that covers this use; the work is in the public domain; the material the notice describes is not the material you posted; or the sender does not in fact own the copyright it claims.
• [ ] If you are relying on fair use, work the four factors honestly. Section 107 weighs (1) the purpose and character of the use, including whether it is commercial and whether it is transformative; (2) the nature of the copyrighted work; (3) the amount and substantiality of the portion used; and (4) the effect on the potential market. Commentary, criticism, parody, news reporting, teaching, and scholarship are classic fair-use territory, but "I made a video about it" is not a magic phrase. Reasonable lawyers, and reasonable judges, disagree on close calls.
• [ ] Internalize that fair use is a defense, not an exemption. Your content was removed on a facially valid notice, and the counter-notice is how you assert your defense, not how you prove you never needed one. The merits get sorted, if at all, in litigation.
• [ ] Decide whether the content is worth the risk you are about to take on. A restored meme has a different risk-reward profile than a restored feature film.

Do you actually hold the right? Start with ownership and licensing, because those are binary and provable. If you photographed the sunset, wrote the essay, or composed the track, and you did not assign it away, you own it, and a takedown claiming otherwise is a misidentification you can swear to comfortably. Licenses are subtler. A Creative Commons license, a stock-photo license, a sync license, or a platform's own terms may authorize exactly the use that was flagged, but licenses have scope limits, and "I found it online and it looked free" is not a license. If your right depends on a license, read the license before you swear the removal was a mistake.

Standing on fair use. Fair use is where most legitimate counter-notices live, and it is also where most overconfident ones die. The doctrine is fact-intensive and resists bright lines. A 12-minute video essay that quotes a two-minute clip to build an argument about a film's cinematography is a very different animal from a "reaction" video that replays the film wall-to-wall with an occasional "wow." Transformation is the gravitational center of the modern analysis, but it is not a talisman; the fourth factor, market harm, still bites, especially where your use substitutes for the original rather than commenting on it. If you cannot articulate, in a sentence, what your use adds and why it does not compete with the original, you are not yet ready to bet a perjury oath on fair use.

Worked example — the go/no-go call. Maya runs a film-criticism channel. A studio's agent files a takedown against her 14-minute critique of a new thriller because it contains roughly 90 seconds of clips, spread across eight short excerpts, each paired with her voiceover analysis of lighting and pacing. Maya created all the surrounding footage, chose the clips to illustrate specific points, and her channel does not offer the film for viewing. Maya has a strong fair-use position: transformative purpose (criticism), small and purpose-selected portions, and no market substitution. A counter-notice is the right move, and she can sign the oath in good faith. Change the facts: Deacon runs a channel that uploads full episodes of a streaming show with a 20-second intro reading the plot, then the entire 45-minute episode. Deacon has no fair-use defense worth the name; a counter-notice would swear falsely that the removal was a mistake and hand the studio his contact details, his consent to jurisdiction, and a tidy exhibit for a lawsuit. For Deacon, the counter-notice is not a shield. It is a confession with a return address.

Why this matters / the trap. The counter-notice is engineered for the wrongly accused. When the material actually infringes, filing one triggers a process that can end in a federal suit, and if the owner sues and proves infringement, you face liability for statutory or actual damages, the cost of your own defense, and, in some cases, the other side's attorney's fees, all on top of a sworn statement that will read very badly when the judge asks what "mistake" you had in mind. The exposure is not theoretical. Statutory damages for a registered work run from $750 to $30,000 per work, and up to $150,000 per work for willful infringement, before fees. For a sense of the numbers, see what an IP case is worth and the real cost of IP piracy. If Phase 1 leaves you unsure, that uncertainty is itself the answer to a different question, the one about whether you should be signing anything.

Phase 2 — Audit the takedown that hit you

Not every takedown that lands is a valid takedown. Some are procedurally defective, some are substantively baseless, and some are both. Before you escalate to a sworn counter-notice, read the notice that removed your content the way a defense lawyer reads an indictment, looking for what is missing and what is wrong.

• [ ] Run the procedural pass. Does the notice identify a specific copyrighted work and the specific material to be removed with enough particularity for the platform to find it? Does it carry the required statements of 17 U.S.C. § 512(c)(3)(A), including the good-faith statement and the sworn authority statement?
• [ ] If the notice is facially deficient, consider the quiet option first. A short, polite message to the provider (or the sender) pointing out the defect sometimes resolves the matter without a counter-notice, and without your name being forwarded to the accuser.
• [ ] Run the substantive pass. Set the paperwork aside and ask the harder question: was the removal actually justified? If you copied someone else's work without permission and have no defense, a defective notice does not cure your problem; it just means the accuser filed sloppily.

The six things a takedown notice must contain. A substantially compliant § 512(c)(3)(A) notice must include: (1) a physical or electronic signature of a person authorized to act for the owner; (2) identification of the copyrighted work claimed to be infringed (a representative list suffices where multiple works at one site are involved); (3) identification of the allegedly infringing material, with enough detail for the provider to locate it; (4) the sender's contact information; (5) a statement of good-faith belief that the use is not authorized by the owner, its agent, or the law; and (6) a statement, under penalty of perjury, that the information is accurate and that the sender is authorized to act on the owner's behalf. Miss the substance of these, and the notice does not do its job: a non-compliant notice generally does not obligate the provider to remove anything and cannot be counted as knowledge against the provider. See Hendrickson v. eBay, Inc., 165 F. Supp. 2d 1082, 1089-93 (C.D. Cal. 2001); Perfect 10, Inc. v. CCBill LLC, 488 F.3d 1102, 1112-13 (9th Cir. 2007).

The quiet option: a defect letter instead of a counter-notice. Here is a move the statute does not advertise but practice rewards. If the notice is genuinely deficient, and especially if the deficiency goes to authority or identification, you can point that out to the platform without filing a counter-notice at all. A counter-notice forwards your identity and contact information to the accuser and locks you into consent to federal jurisdiction; a defect letter does neither. Platforms are not obligated to reinstate on a defect letter, and many will not, but some do, and even those that decline may flag a pattern of malformed notices to their trust-and-safety team. The trade-off: a defect letter does not start the § 512(g) put-back clock, so if the platform ignores it, you have lost time and may still need to file a proper counter-notice. Use the defect letter when the notice is transparently broken and you would rather not surface your identity; use the counter-notice when you want the automatic, clock-driven restoration.

Worked example — the broken notice. Delta Forge, a small metalworking shop, sells hand-forged kitchen knives through an online marketplace. A competitor files a takedown against Delta Forge's product photos, asserting "copyright infringement of our images." But Delta Forge shot the photos itself, in its own workshop, and the competitor's notice never identifies any specific copyrighted work it owns, it just gestures at "our images." That notice is doubly defective: it fails to identify a copyrighted work (element 2) and, on these facts, the sender lacks a good-faith basis to claim authority over photos it did not create (elements 5 and 6). Delta Forge has two clean paths. It can send the marketplace a short defect letter explaining that it owns the photos and that the notice identifies no work, hoping for quiet reinstatement, or it can file a counter-notice swearing the removal was a misidentification, which starts the 10-to-14-business-day clock and dares the competitor to sue over photographs it does not own. Given the competitor's evident bad faith, the counter-notice also begins building a record for a possible Section 512(f) claim.

Why this matters / the trap. An invalid notice should not have triggered removal in the first place, and it cannot be used to charge the provider with knowledge under § 512(c)(3)(B). But do not confuse a procedural defect with a substantive defense. If your use actually infringes, the accuser's clumsy paperwork is a delay, not a defense; fix your position, not your rhetoric. And do not overread the "representative list" rule: a notice that lists one album to stand in for fifty tracks at the same URL is not defective merely because it is efficient.

Phase 3 — Draft the counter-notice: the five elements of Section 512(g)(3)

A counter-notice is short, but every clause is load-bearing. To be effective it must be in writing and sent to the provider's designated agent, and it must substantially include the following five elements. 17 U.S.C. § 512(g)(3).

• [ ] Element 1 — Signature. A physical or electronic signature of the subscriber. § 512(g)(3)(A). An electronic signature is fine; a typed name on a web form generally suffices where the platform's process treats it as your signature.
• [ ] Element 2 — Identify the removed material and its former location. Identify the specific material that was removed or disabled and the location where it appeared before removal. § 512(g)(3)(B). The URL of the specific page is usually enough, but add detail where a bare URL is ambiguous, and use a schedule if many items are involved.
• [ ] Element 3 — The sworn mistake-or-misidentification statement. A statement, under penalty of perjury, of your good-faith belief that the material was removed or disabled "as a result of mistake or misidentification of the material to be removed or disabled." § 512(g)(3)(C). You are not required to explain your reasoning, but a brief, accurate basis (fair use, your own authorship, a valid license, or misidentification of the work) can help.
• [ ] Element 4 — Name, address, and telephone number. § 512(g)(3)(D). This information will be forwarded to the party that sent the takedown. Consider a business address and a business phone if you have legitimate privacy concerns, but the information must be real and sufficient for service.
• [ ] Element 5 — Consent to jurisdiction and acceptance of service. A statement that you consent to the jurisdiction of the federal district court for the district in which your address is located (or, if your address is outside the United States, any district in which the provider may be found), and that you will accept service of process from the party that sent the takedown notice (or its agent). § 512(g)(3)(D).

On Element 3, "good faith" is a real standard. The oath is not a formality, and it mirrors the standard that governs the sender. Under Rossi v. Motion Picture Ass'n of America, Inc., 391 F.3d 1000, 1004-05 (9th Cir. 2004), the good-faith belief a party must hold when it swears a DMCA statement is measured subjectively, not by whether a court would ultimately agree. That cuts both ways. For senders, it means Section 512(f) liability requires an actual, knowing misrepresentation, not merely a mistaken legal conclusion. For you, the counter-notice filer, it means you are safe swearing to a mistake-or-misidentification belief you actually and honestly hold, even if a court might later disagree about fair use, but you are not safe swearing to a belief you do not hold. If you know the removal was correct, "mistake" is a lie, and the subjective standard offers you no cover.

On Element 5, the consent is the price of admission, and it is real. By filing, you prospectively agree to be sued in a specified federal court and to accept service from your adversary. For a domestic subscriber this is usually a modest concession, you would likely be suable there anyway, but do not sleepwalk past it. For a non-U.S. subscriber it can be a serious decision, because the statute requires consent to jurisdiction in any U.S. district where the provider may be found, which for a large platform can mean a plaintiff-friendly forum thousands of miles from home. A Berlin developer who counter-notices a takedown filed against code hosted on a U.S. platform is agreeing, in advance, to defend a U.S. copyright suit in the United States, and to accept service of that suit. That is a real cost to weigh against the value of the restored content. See the discussion of cross-border service in the Hague Convention service checklist.

Substantial compliance, not perfection. As with takedown notices, a counter-notice need only substantially comply with § 512(g)(3) to be effective. A typo in a URL or an inartful phrasing of the perjury statement will not doom a counter-notice that plainly hits all five elements. But "substantial" is not "optional," and the safest course is to include all five cleanly. Many platforms publish their own counter-notice forms precisely to standardize the format; using the platform's form is often the path of least resistance, though you should confirm the form actually captures every statutory element before relying on it, and you should keep your own copy of what you submitted.

Worked example — the counter-notice that writes itself. Priya, a wedding photographer, discovers that a template-selling website used one of her images without permission. She files a takedown; the template seller retaliates by filing its own takedown against Priya's portfolio page, falsely claiming her photo is theirs. Priya's counter-notice is straightforward and honest: Element 1, her electronic signature; Element 2, the portfolio URL and a description of the removed image; Element 3, a sworn statement that the removal resulted from misidentification because she is the photographer and author of the image (she can attach or reference her registration certificate); Element 4, her studio's mailing address and phone; Element 5, consent to the federal district court for her district and acceptance of service. She has every element, an actual good-faith belief, and documentary backup. If the template seller wants the photo to stay down, it now has to sue Priya over a photograph she demonstrably took, an unappealing prospect that also exposes the seller to a § 512(f) claim for its retaliatory notice.

Phase 4 — Send it and watch the clock

Drafting is half the job. The counter-notice only works if it reaches the right inbox and if you understand the timeline it triggers.

• [ ] Send it to the designated agent. The counter-notice goes to the same designated agent that processed the original takedown, not to a general support address, not to the CEO, not to the sender. Providers register agents (name, physical and email address, phone) with the U.S. Copyright Office under 37 C.F.R. § 201.38, and the Copyright Office maintains a searchable online Designated Agent Directory. If the platform offers a counter-notice web form, that is the agent's channel.
• [ ] Understand what the provider does next. On receiving a proper counter-notice, the provider must promptly forward a copy to the party that sent the takedown and tell that party the material will be restored in 10 business days. § 512(g)(2)(B).
• [ ] Mark the restoration window. The provider must restore the material between 10 and 14 business days after receiving your counter-notice, unless, before restoration, the sender notifies the provider that it has filed an action seeking a court order to restrain your alleged infringement. § 512(g)(2)(C).
• [ ] If no suit is filed, expect the content back automatically. You generally do not need to follow up, though it is reasonable to ask the provider to confirm restoration.

Read the clock carefully. The statute sets a floor and a ceiling. The material may not come back before the tenth business day, which is the window Congress gave the sender to decide whether to sue, and it must come back by the fourteenth business day if no suit is filed. Business days exclude weekends and, in practice, holidays, so the calendar wall-clock is typically two to three weeks. The provider's job is ministerial: forward, wait, restore. It is not weighing your fair-use argument during those days; it is counting.

The suit-filing exception is the only off-ramp. The one thing that stops restoration is the sender's notice, delivered to the designated agent before the put-back deadline, that it has filed an action to restrain the infringement. Note the precision: the sender must actually file suit, not merely threaten one, and must inform the provider. A blustering email that says "we will sue if you restore this" does not stop the clock; only a filed action, communicated to the agent, does. This is the pressure the counter-notice was built to apply. It forces the copyright owner to put up or shut up. Sitting on their hands for two weeks means the content returns; suing means the content stays down while the case proceeds, but now the owner has to actually litigate a copyright claim, with the costs, discovery, and fee-shifting risk that entails.

Worked example — the two-week wait versus the lawsuit. Orion Labs, a startup, posts a comparison chart on its site that reproduces a competitor's published pricing table. The competitor files a takedown; the page comes down. Orion, believing the table is uncopyrightable factual data arranged in an obvious way, files a counter-notice. Two scenarios unfold. In the first, the competitor does nothing, calculating that a fight over a pricing table is not worth a federal filing fee. On the fourteenth business day, the page returns automatically, and Orion never hears from the competitor again. In the second, the competitor's counsel, before day 10, files a copyright complaint in federal court and forwards the file-stamped complaint to the platform's designated agent. The page stays down, and Orion is now a defendant, litigating whether its chart infringed and whether the material was even protectable in the first place. Same counter-notice, two very different outcomes, and which one occurs is entirely up to the party that sent the takedown. That is the mechanism working as designed: it does not decide the merits, it decides who has to go to court.

Why this matters / the trap. There is no middle path built into § 512(g). The copyright owner either sues within the window or watches the content return. But "no middle path in the statute" is not "no risk to you." Restoration is not vindication; it is the status quo ante, and a determined owner can still file suit after restoration (the suit-filing exception is about stopping the put-back, not about any deadline to sue). A restored page can be re-targeted with a better-drafted notice. And if the owner does sue, you are litigating in the forum you consented to, served by the process you agreed to accept.

Phase 5 — Manage the downside and the aftermath

The counter-notice is a safety valve, not a force field. Phase 5 is about the risks that survive a successful put-back and the tools that exist when the takedown itself was the abuse.

• [ ] Budget for the possibility of suit. A well-resourced rights holder can and sometimes will file, and even a defense you eventually win costs money, time, and attention. Weigh that against the value of the content before you file, not after you are served. For a framework, see assessing a civil lawsuit.
• [ ] Do not file a false counter-notice. Swearing that a removal was a mistake when you know it was correct risks liability under 17 U.S.C. § 512(f) for a knowing, material misrepresentation.
• [ ] If the takedowns are a campaign, document the pattern. Repeated bogus notices from a competitor build a record that strengthens any eventual § 512(f) claim and may interest the platform's trust-and-safety team.
• [ ] Keep everything. Preserve the original notice, your counter-notice, the platform's communications, timestamps, and the restored URLs. If this ends up in court, the paper trail is your case.

Section 512(f), the trap pointed at you. The same misrepresentation provision that lets you go after an abusive sender points back at you when you file a counter-notice. Section 512(f) imposes liability on "[a]ny person who knowingly materially misrepresents" that material "was removed or disabled by mistake or misidentification," for the damages, including costs and attorney's fees, that the copyright owner, licensee, or provider incurs from restoring the material in reliance on your counter-notice. 17 U.S.C. § 512(f). Under the Rossi subjective standard, this is not liability for guessing wrong about fair use; it is liability for lying. But do not treat "hard to prove" as "safe to ignore." The person best positioned to prove you knew the removal was justified is the copyright owner whose work you copied, and a counter-notice reading "removed by mistake" over content that is a verbatim copy is not a close case.

Section 512(f), the sword against abusive takedowns. Facing the other direction, § 512(f) is the recipient's affirmative remedy, and it has teeth in egregious cases even though it disappoints in ordinary ones. The doctrinal anchor is Lenz v. Universal Music Corp., 815 F.3d 1145 (9th Cir. 2016), the "dancing baby" case, which held that a copyright holder must consider fair use in good faith before sending a takedown notice, and that a failure to do so raises a triable issue on whether the holder formed the subjective good-faith belief § 512(c)(3)(A) requires. Id. at 1151-54. Lenz also held that a successful § 512(f) plaintiff may recover damages proximately caused by the misrepresentation, including nominal damages where the loss is not readily quantifiable. Id. at 1157. The subjective-good-faith framework traces back to Rossi v. Motion Picture Ass'n of America, Inc., 391 F.3d 1000 (9th Cir. 2004), and courts have found § 512(f) liability where a sender used a takedown to suppress speech it had no colorable copyright basis to reach. See Online Policy Grp. v. Diebold, Inc., 337 F. Supp. 2d 1195, 1204-05 (N.D. Cal. 2004) (voting-machine company knowingly misrepresented infringement to silence critics); Automattic Inc. v. Steiner, 82 F. Supp. 3d 1011, 1027-30 (N.D. Cal. 2015) (awarding damages and fees where a takedown targeted a journalist's reporting).

Two cautions keep § 512(f) honest. First, the standard is subjective and forgiving: a sender who actually, if unreasonably, believed the use was infringing is not liable, which is why most § 512(f) claims fail. And second, the fair-use-consideration rule of Lenz is not universally embraced; a Massachusetts district court in Tuteur v. Crosley-Corcoran, 961 F. Supp. 2d 333, 343-46 (D. Mass. 2013), declined to hold that a sender must affirmatively verify the absence of a fair-use defense before filing. So § 512(f) is a real remedy for genuine, provable abuse, and a poor bet for garden-variety overreach. Treat it as a tool for the egregious case, not a routine counterpunch.

Serial takedowns and the platform's own machinery. When the abuse is a pattern, a competitor firing off notice after notice, or a repeat filer weaponizing an automated system, your best leverage may be the platform itself. Providers must maintain and reasonably implement a repeat-infringer policy to keep their safe harbor, 17 U.S.C. § 512(i), and many run internal "strike" systems that can suspend or terminate accounts, including the accounts of senders who abuse the notice process. Documenting a campaign of bogus notices, with dates, URLs, and the counter-notices that went unchallenged, gives the platform's trust-and-safety team something to act on and builds the record for a § 512(f) claim if you ever bring one. It also matters to you defensively: because counter-notices can affect how a platform counts strikes against your account, a clean, well-documented counter-notice history is worth maintaining.

Edge cases and special situations

The core workflow covers most takedowns. A handful of recurring wrinkles deserve their own treatment.

Non-U.S. subscribers. As noted under Element 5, a foreign subscriber's consent to jurisdiction is materially heavier than a domestic one, because § 512(g)(3)(D) requires consent to any U.S. district where the provider may be found. Before filing, a non-U.S. subscriber should weigh whether the content is worth agreeing, in advance, to defend a U.S. copyright suit in the United States and to accept service of that suit. Sometimes it plainly is; sometimes a defect letter, a re-post in a modified form, or simply walking away is the better business decision.

Section 512(a) conduits have no counter-notice path. If the "takedown" came through your internet access provider under a graduated-response or copyright-alert program, you are in the transitory-communications safe harbor, § 512(a), which does not use notice-and-takedown or counter-notice at all. Your recourse there is the ISP's own dispute procedure and your contract, not § 512(g). Sending a counter-notice to a conduit is sending it to the wrong regime.

Not every "takedown" is a DMCA takedown. Platforms remove content for many reasons, terms-of-service violations, trademark complaints, defamation reports, and more, and only copyright removals under § 512 come with the § 512(g) put-back right. A "takedown" premised on trademark or on a platform policy is not answerable by a § 512(g) counter-notice, because § 512 is a copyright statute. The line matters because platform immunity itself splits along it: Section 230 shields platforms from most state-law and non-IP claims but carves out intellectual property, and trademark complaints run on a merits-based track rather than the DMCA's notice-and-counter-notice mechanics. See Section 230, the IP carve-out, and platform liability and, for the broader platform picture, social media law. If your removal was a trademark or policy action dressed up in "copyright" language, the counter-notice may be the wrong instrument.

Do not confuse Section 512 with Section 1201. The DMCA has a second, unrelated half. Section 512 governs hosting and takedowns; Section 1201 governs anti-circumvention, the ban on breaking technological protection measures, with its own triennial exemption rulemaking. A dispute about jailbreaking, unlocking, or bypassing DRM lives in § 1201 and has nothing to do with counter-notices. See DMCA Section 1201 and the phone-unlocking exemption. Filing a § 512(g) counter-notice against a § 1201 problem is a category error.

Partial takedowns and multi-work notices. When a single takedown sweeps in several works, or when only part of a page was disabled, be precise in Element 2 about which material you are contesting. You may counter-notice as to the items you have a good-faith basis to restore and leave the rest down. Swearing that "everything" was a mistake, when some of it plainly infringed, converts a clean counter-notice into a § 512(f) problem for the infringing portion. Segment the fight, and only swear to what you can honestly swear to.

Registration, remedies, and the shadow of litigation. A counter-notice does not require you to have registered anything, you are the defendant-in-waiting, not the plaintiff. But registration matters to the fight you may be inviting. A copyright owner generally must register (or have a refused application) before suing, Fourth Estate Public Benefit Corp. v. Wall-Street.com, LLC, 139 S. Ct. 881 (2019), and timely registration unlocks statutory damages and fees under 17 U.S.C. § 412. If you own the work you are restoring, as Priya did in the example above, your own timely registration turns the tables: it lets you pursue meaningful remedies against the person who copied it and filed the retaliatory notice. For the registration mechanics, see the copyright registration guide and the roadmap for registering copyrights.

Common mistakes

• Filing a counter-notice for content that actually infringes. The single most expensive error. It swears a false oath and hands your adversary a defendant.
• Treating fair use as an automatic pass. Fair use is a fact-intensive defense, not a checkbox. If you cannot say what your use adds and why it does not substitute for the original, do not bet a perjury oath on it.
• Underestimating the consent to federal jurisdiction. Element 5 is binding, and for non-U.S. subscribers it can mean agreeing to defend a suit in a distant, plaintiff-chosen U.S. forum.
• Sending the counter-notice to the wrong place. It must reach the designated agent, not general support and not the sender. The Copyright Office directory and the platform's counter-notice form are the correct channels.
• Swearing that "everything" was removed by mistake when a multi-work notice caught some genuinely infringing material. Segment the counter-notice.
• Confusing regimes. Using a § 512(g) counter-notice against a § 512(a) ISP alert, a § 1201 circumvention dispute, or a trademark/policy removal. Wrong tool.
• Treating restoration as vindication. Put-back restores the status quo; it does not adjudicate anything, and the owner can still sue.
• Firing a § 512(f) counterclaim as reflex. The subjective standard defeats most § 512(f) claims; reserve it for provable, egregious abuse.

Quick-reference checklist

Before you file

• [ ] Confirm you own, license, or otherwise have the right to the material, or that the notice misidentified it.
• [ ] If relying on fair use, work the four § 107 factors honestly and articulate the transformative purpose and the absence of market substitution.
• [ ] Audit the takedown for § 512(c)(3)(A) defects; consider a defect letter if the notice is transparently broken.
• [ ] Decide the content is worth the risk of consenting to jurisdiction and possibly being sued.

The five elements (§ 512(g)(3))

• [ ] Physical or electronic signature.
• [ ] Identification of the removed material and its former location (URL plus detail; use a schedule for multiple items).
• [ ] Sworn, penalty-of-perjury statement of good-faith belief in mistake or misidentification (optional brief basis).
• [ ] Name, address, and telephone number (will be forwarded to the sender).
• [ ] Consent to federal district-court jurisdiction and acceptance of service of process from the sender.

Send and track

• [ ] Deliver to the designated agent (Copyright Office directory or platform form).
• [ ] Keep a copy; note the receipt date.
• [ ] Calendar the 10-to-14-business-day put-back window.
• [ ] Watch for a notice that the sender filed suit (the only thing that stops restoration).

Aftermath

• [ ] Preserve the notice, the counter-notice, and all platform communications.
• [ ] If served, treat it as litigation; get counsel.
• [ ] If the takedown was abusive, document the pattern and evaluate § 512(f).

Primary and secondary authority

Statutes and regulations. 17 U.S.C. § 512(g) (counter-notification and restoration; § 512(g)(2)(B)-(C) provider obligations and the suit-filing exception; § 512(g)(3)(A)-(D) elements); § 512(c)(3) (takedown-notice requirements and substantial compliance; § 512(c)(3)(B) effect of non-compliant notice on knowledge); § 512(f) (knowing material misrepresentation); § 512(i) (safe-harbor gateway and repeat-infringer policy); § 512(a) (transitory communications; no notice-and-takedown); § 512(m) (no duty to monitor); § 107 (fair use); § 412 (registration as a predicate to statutory damages and fees). 37 C.F.R. § 201.38 (designation of agent).

Cases. Lenz v. Universal Music Corp., 815 F.3d 1145 (9th Cir. 2016) (fair use must be considered before takedown; subjective good faith; nominal damages under § 512(f)); Rossi v. Motion Picture Ass'n of America, Inc., 391 F.3d 1000 (9th Cir. 2004) (subjective good-faith standard); Online Policy Grp. v. Diebold, Inc., 337 F. Supp. 2d 1195 (N.D. Cal. 2004) (§ 512(f) liability for a takedown used to suppress speech); Automattic Inc. v. Steiner, 82 F. Supp. 3d 1011 (N.D. Cal. 2015) (damages and fees for a bad-faith takedown); Tuteur v. Crosley-Corcoran, 961 F. Supp. 2d 333 (D. Mass. 2013) (declining to require affirmative fair-use verification); Perfect 10, Inc. v. CCBill LLC, 488 F.3d 1102 (9th Cir. 2007) (non-compliant notice not knowledge); Hendrickson v. eBay, Inc., 165 F. Supp. 2d 1082 (C.D. Cal. 2001) (notice-compliance requirements); BMG Rights Mgmt. (US) LLC v. Cox Commc'ns, Inc., 881 F.3d 293 (4th Cir. 2018) (repeat-infringer policy); Viacom Int'l, Inc. v. YouTube, Inc., 676 F.3d 19 (2d Cir. 2012) (knowledge and willful blindness); Fourth Estate Public Benefit Corp. v. Wall-Street.com, LLC, 139 S. Ct. 881 (2019) (registration predicate to suit).

Secondary sources. U.S. Copyright Office, Section 512 of Title 17 (2020) (the Office's study of the notice-and-takedown system and its shortcomings); U.S. Copyright Office, DMCA Designated Agent Directory; 3 Melville B. Nimmer & David Nimmer, Nimmer on Copyright § 12B (Matthew Bender) (safe harbors, notice, and counter-notification).

Related UpLaw Resources

Related Checklists

• Sending a DMCA Takedown Notice: A Practical Checklist
• Staying Inside the DMCA Safe Harbor: A Compliance Checklist
• Copyright Registration: A Practical Checklist
• Serving a Foreign Defendant Abroad: A Hague Convention Checklist

Related Guides

• The DMCA Safe Harbors: How Online Service Providers Earn Protection From User Infringement
• Copyright Law: A Complete Overview
• What an IP Case Is Worth: A Guide to Intellectual Property Damages

Related Articles

• DMCA Takedowns and Counter-Notices: Both Sides of the Notice-and-Takedown System
• Section 230, the IP Carve-Out, and Platform Liability for User-Generated Infringement
• Social Media Law: A Field Guide to the Legal Stack
• The Legality of Unlocking Your Cell Phone: DMCA Section 1201 and the Exemption
• Copyright FAQs: Plain-Language Answers to the Questions People Ask Most
• The Real Cost of IP Piracy: Civil Damages, Criminal Charges, and Secondary Liability
• Assessing a Civil Lawsuit: A Comprehensive Early-Case Framework
• Copyright Registration: A Comprehensive Guide

Related Toolkits

• Copyright Enforcement and the DMCA: A Roadmap and Research Guide
• Registering Copyrights with the U.S. Copyright Office: A Roadmap and Resource Library

---

This checklist is a research resource from UpLaw (uplaw.us) and is general information, not legal advice. The DMCA, platform procedures, and case law evolve; on close calls, and before signing any statement under penalty of perjury, consult qualified counsel.