DMCA takedowns: how to send one, and what to do if you receive one
Someone posted your work without permission. Or someone claims you posted theirs. Either way you have landed in 17 U.S.C. § 512 — the notice-and-takedown system — and it runs on a specific set of required elements and a specific clock.
Get the elements right and the process works. Get them wrong and the platform can ignore you, or you can end up on the wrong end of a damages claim.
What §512 actually is
Section 512 is a bargain Congress struck with online platforms. In exchange for following certain procedures, a service provider gets a "safe harbor" — protection from monetary liability for infringing material its users post. Section 512(c)(1) covers "the storage at the direction of a user of material that resides on a system or network controlled or operated by" the provider.
Two things follow that people routinely misread.
First, a DMCA notice is a request to a platform, not a court order and not a lawsuit. The platform's incentive to act is preserving its own safe harbor.
Second, the safe harbor has conditions beyond takedown response. Section 512(i)(1) requires a provider to have "adopted and reasonably implemented" — and to inform subscribers of — a policy providing for termination in appropriate circumstances of repeat infringers, and to accommodate standard technical measures. That is the statutory root of "strike" systems.
Sending a notice: find the designated agent first
Under §512(c)(2), a provider claiming the storage safe harbor must designate an agent to receive infringement notifications, make that contact information publicly available on its site, and provide it to the Copyright Office. The Office maintains a searchable DMCA Designated Agent Directory.
Send your notice to the designated agent. A message to general support, a comment on the post, or an email to the uploader does not start the §512 clock.
The six required elements
Section 512(c)(3)(A) requires a written communication to the designated agent including substantially the following:
A physical or electronic signature of a person authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.
Identification of the copyrighted work claimed to have been infringed — or, if multiple works at a single online site are covered by a single notification, a representative list of those works.
Identification of the material claimed to be infringing or to be the subject of infringing activity, and that is to be removed or access disabled, with information reasonably sufficient to permit the provider to locate it. In practice: exact URLs.
Contact information reasonably sufficient to permit the provider to contact you — address, telephone number, and if available an email address.
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.
A statement that the information in the notification is accurate, and under penalty of perjury, that you are authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.
All six. Section 512(c)(3)(B)(i) provides that a notification failing "to comply substantially with the provisions of subparagraph (A)" is not considered in determining whether the provider has knowledge of infringement — meaning a defective notice may simply be disregarded.
There is one partial rescue. Under §512(c)(3)(B)(ii), if a notice substantially complies with clauses (ii), (iii), and (iv) — the work, the material, and your contact information — but not the rest, the provider must "promptly attempt[] to contact the person making the notification or take[] other reasonable steps to assist in the receipt of notification that substantially complies." Do not plan around that. Send a complete notice.
The most common defects: vague identification of the infringing material, a missing good-faith statement, a missing perjury statement, and notices sent by someone without authority to act for the rights holder.
Before you send: consider fair use
Element 5 asks you to state a good faith belief that the use "is not authorized by the copyright owner, its agent, or the law." The Ninth Circuit read that last phrase seriously in Lenz v. Universal Music Corp., holding that "a copyright holder must consider the existence of fair use before sending a takedown notification under § 512(c)," because the statute "unambiguously contemplates fair use as a use authorized by the law."
The court applied a subjective standard — the question is whether you actually formed the belief, not whether a court would agree with you. But the court also warned that a rights holder who fails to consider fair use at all, or pays "lip service" to considering it, can face a triable issue on whether the required good faith belief was formed.
So: before you send, actually think about whether the use is commentary, criticism, parody, news reporting, or otherwise transformative. Write down that you considered it and why you concluded the use is not fair. That record is your evidence that the belief was real.
Section 512(f) cuts both directions
Section 512(f): "Any person who knowingly materially misrepresents under this section — (1) that material or activity is infringing, or (2) that material or activity was removed or disabled by mistake or misidentification, shall be liable for any damages, including costs and attorneys' fees, incurred by the alleged infringer, by any copyright owner or copyright owner's authorized licensee, or by a service provider, who is injured by such misrepresentation."
Note the symmetry. Bad-faith takedowns and bad-faith counter-notices carry the same exposure. And the Copyright Claims Board can hear DMCA misrepresentation claims, which lowers the cost of bringing one.
Do not use takedowns as a competitive weapon, do not send them for material you do not control, and do not send them over disputes that are really about contract or credit rather than copyright.
If you receive a takedown
First, breathe. A takedown notice is not a lawsuit and it is not a finding.
Second, work out which situation you are actually in:
The claim is right. You used material you did not clear. Leave it down. Fix the underlying clearance problem before you re-upload anything.
The claim is wrong, and you can prove it. You own the work, you have a license, the claimant identified the wrong content, the material is in the public domain, or the use is fair. This is what counter-notification is for.
You are unsure. Do not counter-notice yet. A counter-notice is sworn under penalty of perjury and consents to federal court jurisdiction. Figure out your position first.
Also read the platform's own consequences. Under §512(i) repeat-infringer policies, accumulated strikes can cost you an account and a catalog — sometimes a bigger practical harm than the removed post.
The counter-notice: four required elements
Section 512(g)(3) requires a written communication to the provider's designated agent including substantially:
(A) Your physical or electronic signature.
(B) Identification of the material that has been removed or disabled, and the location at which it appeared before removal.
(C) A statement under penalty of perjury that you have a 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."
(D) Your name, address, and telephone number, plus a statement that you consent to the jurisdiction of the federal district court for the district where you live — or, if you are outside the United States, any judicial district where the service provider may be found — and that you will accept service of process from the person who sent the notice, or that person's agent.
Element (D) is the one to understand before you sign. You are volunteering a forum and agreeing to accept service. If the claimant sues, that is where it happens.
The put-back window: 10 to 14 business days
Section 512(g)(2) sets the mechanics. To keep its protection for taking material down, the provider must:
(A) Take reasonable steps promptly to notify the subscriber that it removed or disabled the material.
(B) Upon receipt of a counter notification, promptly provide the original notice-sender with a copy of the counter notification, and inform that person it will replace the material or cease disabling access "in 10 business days."
(C) Replace the material and cease disabling access "not less than 10, nor more than 14, business days following receipt of the counter notice, unless its designated agent first receives notice from the person who submitted the notification under subsection (c)(1)(C) that such person has filed an action seeking a court order to restrain the subscriber from engaging in infringing activity relating to the material on the service provider's system or network."
Read that as one sentence: after a valid counter-notice, the material goes back up in 10 to 14 business days unless the original sender files suit and tells the provider.
Both sides should plan around it. If you sent the notice and a counter-notice arrives, you have a short window to decide whether you are prepared to file a lawsuit. If you are not, the content returns. If you sent the counter-notice, expect a wait of roughly two to three weeks — and understand that you have handed the claimant a decision point.
Platform realities
Not everything is a §512 process. Large platforms also run private, contractual copyright systems that operate alongside the statute rather than under it. YouTube's Content ID, for example, is an automated matching system available to rights holders with an extensive body of frequently-uploaded original material; when it finds a match, the claimant can block, monetize, or track the video, and the uploader's recourse is YouTube's own dispute process — not a §512 counter-notice. Different system, different rules, different timelines. Read the platform's policy before you assume the statute governs.
Not every host is in the safe harbor. Providers outside the United States, or ones not participating in the §512 framework, may not respond to notices at all. Practical alternatives include the host's own terms of service, the domain registrar, the CDN, payment processors, and search delisting.
Documentation compounds. Keep every notice, every response, every URL, and every timestamp. It supports repeat-infringer escalation, and it is the record any later proceeding will run on.
Bottom line
Sending: use the designated agent, include all six elements, consider fair use first and write down that you did, and identify the material by exact URL.
Receiving: figure out your position before you respond, understand that a counter-notice is sworn testimony plus a consent to jurisdiction, and know that the put-back window is 10 to 14 business days unless the claimant sues.
The system is fast and mostly automated, which means the mistakes are fast and mostly automated too. Anything involving a commercial catalog, a repeat adversary, or a real dispute over ownership or fair use is worth a lawyer's eyes before you press send.
This article is general information about U.S. copyright law, not legal advice, and does not create an attorney-client relationship. Platform policies change; confirm current procedures with the service provider.
Sources:17 U.S.C. § 512 · 17 U.S.C. § 512 (Copyright Office text, Chapter 5) · 17 U.S.C. § 512 (GovInfo, full text) · U.S. Copyright Office, DMCA Designated Agent Directory · Lenz v. Universal Music Corp., 815 F.3d 1145 (9th Cir. 2016) · Copyright Claims Board FAQ · YouTube Help: How Content ID Works