Sending a DMCA Takedown Notice: A Practical Checklist

Intellectual Property > Copyright | Published 3 July 2024 - Updated 14 August 2024 | UpLaw - uplaw.us

A takedown notice is a private message that carries the force of a legal duty. Send a compliant one to the right agent and a provider must act; send a defective one and it can be filed in the trash without consequence. This checklist is about getting on the right side of that line.

Keywords: DMCA takedown notice, Section 512, 512(c)(3), notice and takedown, designated agent, safe harbor, substantial compliance, good-faith belief, fair use, Lenz v. Universal, Section 512(f) misrepresentation, counter-notice, Section 512(h) subpoena, copyright registration, statutory damages, red-flag knowledge, repeat infringer

Why the notice is the whole ballgame

Section 512 of the Digital Millennium Copyright Act, codified at 17 U.S.C. § 512, is a bargain. Congress offered online service providers a set of safe harbors that immunize them from monetary liability for infringement committed by their users. In exchange, providers agreed to a housekeeping duty: when a copyright owner sends a notice that identifies infringing material, the provider must remove or disable access to that material "expeditiously" to keep its protection. The takedown notice is the mechanism that switches the duty on. Nothing else does.

That structure has a consequence people often miss. The provider is not adjudicating your copyright claim, and it has no incentive to fight you on the merits. It has a powerful incentive to comply, because a provider that ignores a compliant notice risks forfeiting the harbor and exposing itself to statutory damages that can run to $150,000 per work willfully infringed. See 17 U.S.C. § 504(c). The notice-and-takedown system therefore works less like a courtroom and more like a lever: the legal weight is all built into the machine, and your job is to pull the lever correctly. A notice that satisfies the statute produces near-automatic action. A notice missing an element produces nothing, no matter how meritorious your underlying claim.

Because the lever is powerful, so is the temptation to abuse it, and Congress anticipated that too. Section 512(f) imposes liability on anyone who "knowingly materially misrepresents" that material is infringing. The same lever that lets a photographer clear a stolen image in an afternoon lets a thin-skinned business try to erase a critical review, and the statute has teeth for the second person. Sending a takedown is not a consequence-free act of self-help. It is a sworn representation, made under penalty of perjury as to your authority, that triggers real duties and carries real exposure.

This checklist is written for the sender — the copyright owner or the agent authorized to act for one. It assumes you want the material down quickly, cleanly, and without handing the other side a counterclaim. For the receiving side and the mechanics of putting content back, see filing a DMCA counter-notice after a takedown. For the provider's perspective — how a platform earns and keeps the harbor — see staying inside the DMCA safe harbor and the doctrinal overview in the DMCA safe harbors. For both sides of the system in a single narrative, including platform-specific practice, see DMCA takedowns and counter-notices.

How to read the phases below

The checklist moves in the order a careful sender actually works: confirm you have a claim worth asserting, route it to the right recipient, draft the six statutory elements, scope and document it, manage the response, and shore up your position upstream with registration. Each phase pairs a set of checkbox items with a short "Why it matters / traps" note explaining the doctrine and the failure modes. Worked hypotheticals are labeled and invented for illustration; they are not real disputes. Treat this as a research and drafting aid, not legal advice, and confirm both current law and the target platform's live procedures before you send.

Phase 1 — Confirm you have a claim worth asserting

Before you draft anything, satisfy yourself that the material is infringing, that you are entitled to complain about it, and that no legal privilege makes the use lawful. Skipping this phase is the single most common way senders back into § 512(f) trouble.

• [ ] Confirm you own — or are authorized to act for the owner of — the specific exclusive right allegedly infringed (reproduction, distribution, public display, public performance, or the making of derivatives under 17 U.S.C. § 106).
• [ ] Confirm the material at issue is your protected expression, not an unprotectable idea, fact, method, or stock element (the idea/expression divide of 17 U.S.C. § 102(b)).
• [ ] Consider fair use in good faith before you sign. Fair use is a use "authorized by law" under 17 U.S.C. § 107, and a sender must form a subjective, good-faith belief that the use is not fair before representing that it is unauthorized. See Lenz v. Universal Music Corp., 815 F.3d 1145 (9th Cir. 2016).
• [ ] Confirm the use is not licensed, and not otherwise authorized (implied license, first sale, a platform's own terms of service, or your own prior consent).
• [ ] Confirm you are complaining about copyright infringement, not a trademark, defamation, or privacy grievance dressed up as one. The DMCA is a copyright statute; it does not reach non-copyright complaints.

Why it matters / traps. Standing is not a technicality here. Only "the owner of an exclusive right that is allegedly infringed, or that person's authorized agent," may send a § 512(c)(3) notice. A non-exclusive licensee has no exclusive right to assert. A brand-protection vendor or law firm can send on the owner's behalf, but the notice must say so, and the person signing takes on the perjury representation described in Phase 3. The idea/expression check protects you against a weak claim: you cannot use the DMCA to remove a competitor's recipe list, a factual database, or a scène à faire common to the genre, because those are not protected. And the fair-use gate is not optional. The Ninth Circuit held in Lenz that a copyright holder who fails even to consider fair use before sending a notice cannot have formed the good-faith belief the statute demands, and that failure can support § 512(f) liability. The standard is subjective — the holder need not be right about fair use, only honest — but it is a standard, and it applies at the moment you sign.

Worked hypothetical — the reaction video. Harborview Coffee discovers a food blogger's ten-minute video roasting its rebranding. The video shows the new logo on screen for eight seconds and quotes forty words of Harborview's press release while mocking it. Harborview's exclusive-rights analysis is thin (the logo is a trademark matter, and forty words of a press release is a trivial, transformative quotation in a work of criticism). A takedown here is not enforcement; it is an attempt to censor a lawful review, and if Harborview signs the good-faith statement without a serious fair-use analysis, it has manufactured its own § 512(f) exposure. Contrast Aperture North, a landscape photographer whose full-resolution image of a fjord is lifted whole and posted as the header of a commercial travel site with no license and no attribution. That is a clean § 106 reproduction-and-display claim with no plausible fair-use defense, and it is exactly what the takedown system exists to handle. The difference between the two is the analysis you do in Phase 1.

For the wider fair-use framework — the four statutory factors, the transformative-use inquiry after Campbell v. Acuff-Rose Music, Inc., 510 U.S. 569 (1994), and its recent narrowing in Andy Warhol Foundation for the Visual Arts, Inc. v. Goldsmith, 598 U.S. 508 (2023) — see the fair-use treatment in copyright law: a complete overview and the practical answers in copyright FAQs.

Phase 2 — Route the notice to the right harbor and the right recipient

A perfect notice sent to the wrong place starts no clock. The duty to act runs only from the provider's receipt of a substantially compliant notice by its designated agent. Two routing questions decide whether your notice lands: which safe harbor governs the provider you are targeting, and who its designated agent is.

• [ ] Identify which safe harbor applies. The § 512(c) harbor covers material stored at the direction of users (hosting: image hosts, video platforms, social networks, marketplaces). The § 512(d) harbor covers information-location tools (search engines and directories that link to infringing material). The § 512(b) harbor covers system caching. The § 512(a) harbor covers transitory digital communications — the mere-conduit function of a broadband carrier moving packets.
• [ ] Confirm you are targeting a harbor that the notice-and-takedown procedure actually reaches. Notice-and-takedown applies to the § 512(c) and § 512(d) harbors. It does not apply to the § 512(a) conduit harbor: you cannot serve a § 512(c)(3) takedown on a pure access provider and demand that it disconnect a subscriber's connection.
• [ ] Locate the provider's designated agent in the U.S. Copyright Office's online Designated Agent Directory, maintained under 37 C.F.R. § 201.38, or on the provider's published DMCA/copyright page.
• [ ] Prefer the platform's designated web form or submission portal over a generic email inbox or a support ticket queue.
• [ ] Record the date, time, and channel of submission, and capture the confirmation or reference number the platform returns.

Why it matters / traps. The conduit distinction is not academic. In Recording Industry Ass'n of America v. Verizon Internet Services, Inc., 351 F.3d 1229 (D.C. Cir. 2003), the D.C. Circuit held that the § 512(h) subpoena mechanism — and by extension the notice-and-takedown apparatus — does not reach a service provider acting only as a § 512(a) conduit, because such a provider stores nothing it could take down. The Eighth Circuit reached the same conclusion in In re Charter Communications, Inc., Subpoena Enforcement Matter, 393 F.3d 771 (8th Cir. 2005). If your infringer is a subscriber whose ISP merely carries the traffic, the takedown notice is the wrong tool; you are looking at a suit against the uploader, a § 512(h) subpoena to a hosting provider that actually stores the file, or (for peer-to-peer conduct) the repeat-infringer pressure discussed in Phase 5.

The designated-agent requirement is equally load-bearing. A provider must both register an agent with the Copyright Office and publish the agent's contact information on its site. Registration is not a one-and-done act: under the electronic system that took effect in December 2016, designations must be renewed every three years or they lapse. Courts have treated failure to keep the designation current as a serious defect in the provider's compliance, see Ellison v. Robertson, 357 F.3d 1072 (9th Cir. 2004), but the point for a sender is directional — send to the registered agent through the published channel, because a notice dropped into a general marketing inbox may never reach anyone who can act on it, and the clock does not start until the right hands receive it.

Worked hypothetical — the wrong door. Lumen Records finds its new single ripped and posted on a user-upload video platform and also indexed by a niche music search engine that links to the file on a third host. The correct routing is three separate notices: a § 512(c) notice to the video platform's agent (hosting), a § 512(d) notice to the search engine's agent (linking), and, if Lumen can find it, a § 512(c) notice to the third-party host that actually stores the file. Sending a single notice to Lumen's own broadband ISP demanding it "block the pirates" accomplishes nothing — that ISP is a conduit, and the file is not stored on its system.

Phase 3 — Satisfy the six statutory elements of § 512(c)(3)(A)

This is the heart of the notice. Section 512(c)(3)(A) lists six elements, and the statute measures a notice not by perfection but by substantial compliance. Get the substance of each element right and minor imperfections are forgiven; omit an element and the notice fails.

• [ ] (1) Signature. A physical or electronic signature of a person authorized to act on behalf of the owner of the exclusive right. In practice, /s/ Full Name on a web form or emailed notice suffices.
• [ ] (2) Identification of the copyrighted work. Name the specific work you own. If a single site infringes many of your works at once, § 512(c)(3)(A)(ii) permits a representative list rather than an exhaustive one. Where you have it, add the title, the URL and date of an authorized copy, and the registration number.
• [ ] (3) Identification of the infringing material and its location. Provide information "reasonably sufficient to permit the service provider to locate the material" — in practice, the exact URL(s). On complex platforms, supplement URLs with post IDs, usernames, timestamps, and file names.
• [ ] (4) Contact information. Your address, telephone number, and email — enough for the provider (and, later, the alleged infringer) to reach you.
• [ ] (5) Good-faith statement. A statement that you "have a good faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law." The final three words are where fair use lives.
• [ ] (6) Accuracy-and-authorization statement, under penalty of perjury. A statement that the information in the notice is accurate, and that under penalty of perjury you are authorized to act on behalf of the owner of the exclusive right allegedly infringed.

Why it matters / traps — substantial compliance. The governing standard comes from the text of § 512(c)(3)(A) and the seminal decision in ALS Scan, Inc. v. RemarQ Communities, Inc., 239 F.3d 619 (4th Cir. 2001), which held that a notice need only substantially comply, and that a representative list of infringed works can satisfy element (2) for a site riddled with infringement. But "substantial" is not "sloppy." In Perfect 10, Inc. v. CCBill LLC, 488 F.3d 1102 (9th Cir. 2007), the Ninth Circuit refused to let a copyright owner assemble the statutory elements from a patchwork of separate, individually deficient communications; the owner bears the burden of putting the required pieces into a compliant notice, and the provider is not obliged to stitch a valid notice together from scraps. And the burden of compliance rests on the sender, not the provider — a point the district court underscored in Corbis Corp. v. Amazon.com, Inc., 351 F. Supp. 2d 1090 (W.D. Wash. 2004), where a rights-holder's failure to identify infringing items with the required specificity meant the notices could not be used to charge the provider with knowledge.

Why it matters / traps — the exact URL. Element (3) is the line senders botch most often. The provider cannot remove what it cannot find, and the statute does not send it hunting. A notice that says "someone is using my photos somewhere on your site" identifies nothing and obligates no one. Give the deep link to the specific image, video, listing, or post. On a marketplace or social platform where content is buried under infinite scroll or dynamic URLs, add every locator you have: the seller's username, the listing number, the post's permalink, the upload timestamp, and a description precise enough that a human reviewer can confirm the match in seconds.

Why it matters / traps — the good-faith and perjury statements. Elements (5) and (6) are the sworn spine of the notice, and their scope is asymmetric in a way worth understanding. The penalty-of-perjury oath attaches specifically to the representation that you are authorized to act for the owner — not, on the statute's face, to the substantive belief that the material infringes. The good-faith statement in element (5), by contrast, is the representation Lenz polices: it is where you certify that you have considered whether the law authorizes the use (including fair use) and concluded, in subjective good faith, that it does not. Omit either statement and the notice is non-compliant. Make the good-faith statement without actually forming the belief, and you have created § 512(f) exposure. The statute rewards a sender who does the analysis and says so, and punishes one who signs reflexively.

Why it matters / traps — the § 512(c)(3)(B) cure mechanic. There is a partial safety valve for imperfect notices, but it runs in the provider's favor, not yours. Under § 512(c)(3)(B), if a notice fails to comply as to the work identification (element 2), the material identification (element 3), or your contact information (element 4), the notice is disregarded for knowledge purposes — unless the provider promptly takes reasonable steps to contact you or the notice otherwise substantially complies. In other words, a notice missing those three elements can sometimes be rescued if the provider reaches out and you cure the defect, but you should never rely on a provider's goodwill to fix your paperwork. Send a complete notice the first time.

A note on what the notice does beyond removal

A compliant, specific notice does double duty. Beyond compelling removal, it can supply the provider with actual knowledge of that particular infringement under § 512(c)(1)(A)(i) and § 512(c)(3)(B)(i). That matters if the provider drags its feet: a provider that receives a specific, compliant notice and fails to act expeditiously does not merely ignore a request — it acquires knowledge and then sits on it, which is how a platform loses the harbor. Conversely, a non-compliant notice cannot be used to charge the provider with knowledge; the statute expressly excludes it. Specificity is therefore not just courtesy to the reviewer. It is what converts your notice into a knowledge-triggering event with legal consequences for a provider that stalls.

Phase 4 — Scope it proportionately and build the evidentiary record

How you scope the request determines how smoothly it is honored and how much return fire it draws. The evidence you attach determines whether the notice survives a counter-notice and whether you can prove your case if the dispute escalates.

• [ ] Scope to the specific infringing item. Ask the provider to remove the one photo, the one video, the one listing — not the entire page, account, or domain that also hosts lawful material.
• [ ] Attach or reference a copy of your original work and a dated, authenticated screenshot of the infringement, captured so its provenance can be proved later.
• [ ] Preserve the infringing page independently (a timestamped capture, a Wayback Machine snapshot, a hash of the file) in case the material is altered or vanishes.
• [ ] Submit a clean, well-organized notice through the designated channel, and keep a complete copy of everything you send, including the platform's confirmation.

Why it matters / traps — proportionality. Over-broad takedowns are a strategic error twice over. A request to nuke a whole account to reach one infringing post invites the provider to push back, invites the user to counter-notify, and — if the sweep captures lawful material — supplies the raw material for a § 512(f) misrepresentation claim, because you will have represented that lawful content is infringing. A proportionate request ("remove this image at this URL") is faster to implement, harder to contest, and cleaner to defend. It also keeps you honest: the discipline of pointing to a specific item forces the Phase 1 analysis you should have already done.

Why it matters / traps — the record. The notice is the opening move, not the whole game. If a counter-notice arrives, or if the matter proceeds to suit, you will need to prove that the infringing copy existed, when, and where — and infringers routinely take material down and re-post it elsewhere the moment a notice lands. Authenticated captures made contemporaneously are worth far more than a screenshot you scramble to recreate weeks later. Capture the page, the URL bar, the date, and, where possible, the file's metadata or a cryptographic hash. For the evidentiary standards that govern getting those captures admitted — authentication under Federal Rule of Evidence 901, the hearsay and best-evidence wrinkles, and Wayback Machine practice — see getting website evidence admitted.

Worked hypothetical — the proportionate cut. Aperture North finds its fjord image used as one of twelve photos in a travel blog's otherwise-original "Best of Norway" post. The right notice targets the single infringing image URL and asks the host to disable that image, not to delete the post. The blogger, who wrote the surrounding text herself, has no counter-notice to file about her own words; she simply loses the one photo she should not have used. Had Aperture demanded the whole post come down, it would have claimed authority over eleven images and a body of text it does not own — an over-reach that turns a clean takedown into a § 512(f) target.

Phase 5 — After you hit send: manage the response cycle

A takedown notice starts a sequence, and the sequence has deadlines that cut both ways. Know what happens next before you send, because the counter-notice can force a decision you are not ready to make.

• [ ] Confirm the material was removed or disabled and that the provider notified the uploader (the provider must "take reasonable steps promptly to notify the subscriber," 17 U.S.C. § 512(g)(2)).
• [ ] Watch for a counter-notice. If one arrives, the provider must restore the material between 10 and 14 business days after receiving it — unless, before restoration, you notify the provider that you have filed a court action seeking to restrain the infringer from continuing the infringing activity (17 U.S.C. § 512(g)(2)(C)).
• [ ] Decide, in that narrow window, whether you are actually willing to sue. If you are not, the material comes back and you are out of low-cost options against that copy.
• [ ] For an anonymous or pseudonymous infringer, consider a § 512(h) subpoena from the clerk of a U.S. district court — served on a hosting or linking provider, with a copy of your notice attached — to identify the uploader.
• [ ] For systematic or repeat infringement, prepare to escalate. A single takedown does not stop re-uploading, and your accumulated notices may matter to the provider's own repeat-infringer obligations.

Why it matters / traps — the counter-notice standoff. The counter-notice is the pressure test built into § 512. A counter-notifier certifies, under penalty of perjury, a good-faith belief that the material was removed by mistake or misidentification, and consents to the jurisdiction of a federal district court. Once a valid counter-notice lands, the provider's own safe harbor for taking the material down (under § 512(g)(1)) depends on restoring it on schedule — unless you sue. That is the moment of truth. The takedown system lets you remove content cheaply, but it does not let you keep it removed for free over the uploader's objection. If you calibrate the takedown to a willingness to litigate you do not actually have, a sophisticated counter-notifier can call your bluff and get the content restored in two weeks. Calibrate accordingly, and treat the counter-notice mechanics from the other side as required reading before you send — see filing a DMCA counter-notice after a takedown.

Why it matters / traps — unmasking the uploader. Section 512(h) authorizes a copyright owner to obtain a subpoena from a district court clerk — without filing a full lawsuit — compelling a service provider to identify an alleged infringer, provided the owner attaches a copy of a compliant § 512(c)(3) notice, a proposed subpoena, and a sworn declaration that the information will be used only to protect copyright. The reach of this tool tracks the harbor structure: as RIAA v. Verizon and In re Charter hold, a § 512(h) subpoena reaches providers that host or link to the material, not those functioning as mere § 512(a) conduits. If your infringer sits behind a hosting platform, § 512(h) can pierce the anonymity cheaply. If the infringer is a broadband subscriber known only by IP address, you are back to a John Doe suit and Rule 45 discovery.

Why it matters / traps — feeding the repeat-infringer machine. Your notices are not only a remedy against a single file; they are evidence in a larger system. To keep any § 512 harbor, a provider must "reasonably implement" a policy for terminating repeat infringers in appropriate circumstances (17 U.S.C. § 512(i)(1)(A)). What counts as a valid "strike" against a user is contested, but the Fourth Circuit's decision in BMG Rights Management (US) LLC v. Cox Communications, Inc., 881 F.3d 293 (4th Cir. 2018), made clear that a provider which fails to police blatant repeat infringers can lose the harbor entirely — with catastrophic damages consequences, as the later Sony Music Entertainment v. Cox Communications verdict illustrated. For a sender confronting a serial infringer, the practical lesson is that a documented pattern of compliant notices against the same account builds the record that pressures a provider to terminate the user, not merely the file. That interaction between takedown practice and platform liability is developed in Section 230, the IP carve-out, and platform liability for user-generated infringement.

Why it matters / traps — whack-a-mole. The candid truth of notice-and-takedown is that it addresses copies, not conduct. The same file re-uploaded under a new account at a new URL is a new infringement requiring a new notice. Congress declined to write a "notice-and-staydown" duty into § 512, and courts have not read one in; a provider need not proactively filter for re-uploads of material it has taken down before, though the § 512(i) requirement that it "accommodate and not interfere with standard technical measures" gestures at automated matching that industry never fully standardized. For a rights-holder facing industrialized infringement, the strategic answer is rarely one more notice; it is a coordinated enforcement program, a § 512(h) campaign, a suit against the operator, or all three. The empirical scale of the problem — the automated, high-volume reality of modern takedown practice, and its error rates — is documented in Jennifer M. Urban, Joe Karaganis & Brianna L. Schofield, Notice and Takedown in Everyday Practice (2017), and in the U.S. Copyright Office's Section 512 of Title 17 study (2020). The broader enforcement roadmap lives in copyright enforcement and the DMCA: a roadmap and research guide.

Phase 6 — Strengthen your hand upstream with registration

A takedown notice does not itself require a copyright registration — you can send one for an unregistered work. But everything that happens after a takedown, if the dispute escalates, turns on registration and its timing. The strongest senders register early, long before they ever need to enforce.

• [ ] Register the work early — before the infringement begins, or within three months of first publication — to preserve statutory damages and attorney's fees under 17 U.S.C. § 412.
• [ ] Confirm you hold (or have applied far enough to hold) a registration before you sue, because registration is a precondition to filing an infringement action.
• [ ] Maintain an authenticated evidentiary record — original files with metadata, dated captures — that ties your registration to the specific work in the notice.

Why it matters / traps — the § 412 cliff. Section 412 is the quiet hinge of copyright enforcement economics. It bars an award of statutory damages or attorney's fees for any infringement that began before the work was registered, unless the work was registered within three months of first publication. Miss that window and, even with a slam-dunk infringement, you are limited to actual damages and the infringer's profits — often hard to prove and frequently trivial for a single web repost. Register in time and you can invoke statutory damages of up to $150,000 per work for willful infringement under § 504(c), plus fees under § 505. That is the difference between a defendant who shrugs at a demand letter and one who settles: the number, and § 412 timing controls the number. The registration workflow, the deposit rules, and the timing traps are laid out step-by-step in copyright registration: a practical checklist and analyzed in depth in copyright registration: a comprehensive guide.

Why it matters / traps — registration as the gate to suit. A counter-notice can turn a two-week standoff into a decision about whether to litigate, and you cannot litigate a U.S. work you have not registered. The Supreme Court settled the timing question in Fourth Estate Public Benefit Corp. v. Wall-Street.com, LLC, 139 S. Ct. 881 (2019), holding that registration "has been made" — the trigger for filing suit under 17 U.S.C. § 411(a) — only when the Copyright Office acts on the application, not merely when the applicant submits it. Processing takes time. If you anticipate ever having to back a takedown with a lawsuit, you want the registration in hand before the counter-notice clock starts, not after. For photographers, songwriters, software authors, and website owners, UpLaw maintains medium-specific registration checklists; the roadmap that ties them together is registering copyrights with the U.S. Copyright Office.

Edge cases and recurring failure modes

The core workflow handles the ordinary case. The situations below are where senders most often go wrong, get surprised, or reach for the DMCA when they should reach for something else.

When the takedown backfires: § 512(f) in practice

Section 512(f) is not a dead letter, and the cases that impose liability share a pattern: the sender used a copyright takedown to accomplish a non-copyright goal, or knew the material was authorized. In Online Policy Group v. Diebold, Inc., 337 F. Supp. 2d 1195 (N.D. Cal. 2004), a voting-machine company sent takedowns targeting internal emails that had been published as a matter of public concern; the court found the company knew the material was not a viable infringement target and held it liable under § 512(f). In Automattic Inc. v. Steiner, 82 F. Supp. 3d 1011 (N.D. Cal. 2015), a court entered judgment against a sender who used a bogus takedown to suppress a journalist's reporting, awarding damages and fees. And Lenz itself arose from a takedown of a twenty-nine-second home video of a toddler dancing to a Prince song — a textbook fair use that Universal targeted without, the plaintiff alleged, seriously considering fair use at all. The through-line: the copyright owner who honestly targets a genuine infringement has little to fear from § 512(f), while the one who wields the notice as a censorship or competitive weapon has a great deal to fear. The damages available include the target's costs and attorney's fees, and the reputational and precedential costs of a § 512(f) loss dwarf the value of most improper takedowns.

Copyright only: the DMCA is not a trademark takedown

The § 512 notice-and-takedown procedure reaches copyright infringement and nothing else. Section 230 of the Communications Decency Act contains an intellectual-property carve-out that leaves the DMCA to govern copyright while trademark and other IP claims proceed on their own tracks — a merits-based Lanham Act analysis and each platform's private policy, not a § 512(c)(3) notice. If your grievance is that a counterfeiter is selling knockoffs under your logo, the DMCA is the wrong instrument; you want the marketplace's brand-protection program, a Lanham Act claim, or customs recordation. The two-track world — copyright takedowns on one side, trademark and platform-policy enforcement on the other — is mapped in Section 230, the IP carve-out, and platform liability and, from the brand owner's operational vantage, in defending a brand on the internet and the defending a brand across the digital ecosystem toolkit.

Section 512 is not Section 1201

Two very different DMCA mechanisms share a statute and confuse newcomers. Section 512 is the safe-harbor and notice-and-takedown regime this checklist addresses. Section 1201 is the anti-circumvention rule that prohibits bypassing technological protection measures — the provision behind the fights over device unlocking, jailbreaking, and the triennial Librarian of Congress exemption rulemaking. A takedown notice has nothing to do with § 1201, and a § 1201 circumvention claim cannot be asserted through notice-and-takedown. For the distinct anti-circumvention world, see the legality of unlocking your cell phone: DMCA Section 1201 and the exemption.

Metadata and the § 1202 angle

A related but separate hook lives in 17 U.S.C. § 1202, which forbids the knowing removal or alteration of copyright management information (CMI) — author credits, titles, terms of use, and embedded identifiers — to facilitate infringement. When an infringer crops out a photographer's embedded credit or strips a watermark before reposting an image, the conduct can support a § 1202 claim in addition to the underlying infringement. That does not change how you send a takedown, but it can meaningfully change the damages exposure of a defendant who scrubbed your metadata, and it is worth flagging in a subsequent demand or complaint. The CMI stakes are especially high for image creators; see copyright registration for photographs, and, for how § 1202 is being litigated at the frontier of AI training data, generative AI on trial.

Fair-use-heavy contexts: criticism, news, education, and reaction

Some contexts are so fair-use-laden that a takedown is presumptively risky: commentary and criticism, news reporting, teaching, parody, and research all sit near the core of § 107. The reaction video, the critical review, the scholarly excerpt, and the news clip are the situations where the Lenz good-faith obligation bites hardest, because the odds that a court will find the use "authorized by law" are high. The prudent move is not to avoid enforcement in these contexts categorically, but to raise the bar for your own analysis: document why the use is not transformative, why it substitutes for the original, or why it takes more than criticism requires. A sender who cannot articulate that analysis should not sign the good-faith statement. The scraping and text-and-data-mining context raises parallel questions where copyright, contract, and the Computer Fraud and Abuse Act intersect; see web scraping and the law after hiQ v. LinkedIn.

Platform reality: the form is the law you actually meet

For all the statutory doctrine, the interface most senders touch is a web form built by a platform's trust-and-safety team, and the platforms differ. Some route notices through third-party clearinghouses; some publish their processed notices to transparency databases; some impose their own formatting and evidentiary demands that go beyond the statute. The statute sets the floor — a notice that substantially complies with § 512(c)(3)(A) triggers the duty — but a platform can, and often does, ask for more before it acts, and it can decline to honor a notice that misses its own procedural requirements even where the statutory floor is met. Read the platform's DMCA page before you draft, follow its channel, and keep the confirmation. Social platforms in particular layer content-policy enforcement on top of the DMCA; the interaction is surveyed in social media law: a field guide to the legal stack.

Valuing the dispute before you escalate

Not every infringement is worth a lawsuit, and the counter-notice window forces that valuation on a tight timeline. Before you send a takedown you might have to back with litigation, form a rough view of what the case is worth: whether § 412 timing preserves statutory damages, whether the infringer has assets, whether the use is willful, and what a court is likely to award. That analysis — reasonable royalties, statutory-damages ranges, disgorgement of profits, enhanced damages, and the role of experts — is the subject of what an IP case is worth: a guide to intellectual property damages. The consequences an infringer faces, civil and criminal, are catalogued in the real cost of IP piracy.

A sample takedown notice (annotated, hypothetical)

The following is an illustrative template for a § 512(c) hosting notice, filled with invented facts for Aperture North. It is a drafting aid, not a form to file blindly — adapt it to the platform's own submission requirements and to your facts.

To: DMCA Designated Agent, [Platform], via [designated web form / agent email] Re: Notice of Copyright Infringement under 17 U.S.C. § 512(c)(3)

I am the copyright owner of the photographic work described below and submit this notice under the DMCA. (Element 4 — sender/contact) My contact information is: Aperture North LLC, [address], [phone], [email].

1. Copyrighted work infringed. (Element 2) The original photograph titled "Geiranger at Dawn," first published at https://aperturenorth.example/geiranger on 12 March 2023, U.S. Copyright Office Reg. No. VA-0-000-000.

2. Infringing material and its location. (Element 3) An unauthorized full-resolution copy of the above photograph appears as the header image at https://[platform]/user/traveltales/best-of-norway (posted by username "traveltales," post ID 48213, captured 2 July 2024). I request that this specific image be disabled or removed; I do not seek removal of the surrounding text or other images on that page. (Phase 4 — proportionality)

3. Good-faith statement. (Element 5) I have a good-faith belief that the use of the material described above is not authorized by the copyright owner, its agent, or the law. I have considered whether this use is a fair use and concluded, in good faith, that it is not. (Phase 1 — Lenz)

4. Accuracy and authorization. (Element 6) The information in this notice is accurate, and under penalty of perjury I am authorized to act on behalf of the owner of the exclusive right that is allegedly infringed.

Signature: (Element 1) /s/ [Name], for Aperture North LLC. Date: 2 July 2024.

Enclosures: copy of the original photograph; dated screenshot of the infringing page with URL visible.

Every bracketed element maps to a checklist item above. The proportionality sentence in paragraph 2 and the explicit fair-use consideration in paragraph 3 are the two lines that most often separate a clean, defensible notice from a § 512(f) liability.

Common mistakes — a quick reference

• Providing no exact URL or other locator, so the provider cannot find the material and is not obliged to look.
• Sending to a general inbox or support queue instead of the registered designated agent's published channel.
• Serving a § 512(c)(3) takedown on a § 512(a) mere-conduit ISP that stores nothing to take down.
• Omitting the good-faith statement, the accuracy statement, or the under-penalty-of-perjury authorization.
• Signing the good-faith statement without actually considering fair use — the Lenz trap.
• Sending a notice for a work you do not own and are not authorized to enforce.
• Over-broad requests that sweep in lawful content and manufacture § 512(f) exposure.
• Trying to build one valid notice out of several individually deficient communications (CCBill).
• Using the DMCA to attack a trademark, defamation, or competitive grievance it was never built to reach.
• Sending a takedown you are unwilling to back with a lawsuit, then being called out by a counter-notice.
• Never registering the work, and discovering at the counter-notice deadline that you cannot sue and cannot claim statutory damages.

Primary and secondary authority

Statutes and regulations. 17 U.S.C. § 512 (safe harbors; (a)–(d) harbor categories; (c)(3)(A) takedown-notice elements; (c)(3)(B) substantial compliance and knowledge; (f) misrepresentation liability; (g) counter-notice and restoration; (h) subpoena to identify infringer; (i) conditions of eligibility and repeat-infringer policy); 17 U.S.C. § 106 (exclusive rights); § 102(b) (idea/expression); § 107 (fair use); § 411(a) (registration as precondition to suit); § 412 (registration timing for statutory damages and fees); § 504(c) (statutory damages); § 505 (costs and attorney's fees); § 1202 (copyright management information). 37 C.F.R. § 201.38 (designation of agents to receive takedown notices).

Cases. Lenz v. Universal Music Corp., 815 F.3d 1145 (9th Cir. 2016); Rossi v. Motion Picture Ass'n of America, Inc., 391 F.3d 1000 (9th Cir. 2004) (subjective good-faith standard); ALS Scan, Inc. v. RemarQ Communities, Inc., 239 F.3d 619 (4th Cir. 2001) (substantial compliance; representative list); Perfect 10, Inc. v. CCBill LLC, 488 F.3d 1102 (9th Cir. 2007); Corbis Corp. v. Amazon.com, Inc., 351 F. Supp. 2d 1090 (W.D. Wash. 2004); Viacom Int'l, Inc. v. YouTube, Inc., 676 F.3d 19 (2d Cir. 2012); UMG Recordings, Inc. v. Shelter Capital Partners LLC, 718 F.3d 1006 (9th Cir. 2013); BMG Rights Mgmt. (US) LLC v. Cox Commc'ns, Inc., 881 F.3d 293 (4th Cir. 2018); Recording Indus. Ass'n of America v. Verizon Internet Servs., Inc., 351 F.3d 1229 (D.C. Cir. 2003); In re Charter Commc'ns, Inc., Subpoena Enforcement Matter, 393 F.3d 771 (8th Cir. 2005); Online Policy Group v. Diebold, Inc., 337 F. Supp. 2d 1195 (N.D. Cal. 2004); Automattic Inc. v. Steiner, 82 F. Supp. 3d 1011 (N.D. Cal. 2015); Fourth Estate Pub. Benefit Corp. v. Wall-Street.com, LLC, 139 S. Ct. 881 (2019); Campbell v. Acuff-Rose Music, Inc., 510 U.S. 569 (1994); Andy Warhol Found. for the Visual Arts, Inc. v. Goldsmith, 598 U.S. 508 (2023).

Secondary sources. U.S. Copyright Office, Section 512 of Title 17: A Report of the Register of Copyrights (May 2020); Jennifer M. Urban, Joe Karaganis & Brianna L. Schofield, Notice and Takedown in Everyday Practice (2017); 3 Melville B. Nimmer & David Nimmer, Nimmer on Copyright § 12B (safe harbors and notice-and-takedown); U.S. Copyright Office, DMCA Designated Agent Directory.

Related UpLaw Resources

Related Checklists

• Filing a DMCA Counter-Notice After a Takedown: A Practical Checklist
• Staying Inside the DMCA Safe Harbor: A Compliance Checklist
• Getting Website Evidence Admitted: A Practical Authentication Checklist
• Copyright Registration: A Practical Checklist
• Copyright Registration for Photographs: A Practical 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
• Copyright Registration: A Comprehensive Guide
• Copyright FAQs: Plain-Language Answers to the Questions People Ask Most
• Defending a Brand on the Internet: A Strategic Enforcement Playbook
• The Real Cost of IP Piracy: Civil Damages, Criminal Charges, and Secondary Liability
• The Legality of Unlocking Your Cell Phone: DMCA Section 1201 and the Exemption

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
• Defending a Brand Across the Digital Ecosystem: A Strategic Toolkit and Resource Library

---

This checklist is a research resource and general information, not legal advice. Section 512 doctrine, § 512(f) case law, and individual platform procedures change; confirm current law and the target platform's live process before relying on any step here, and consult qualified counsel for a specific matter.