How to file a DMCA takedown for unauthorized music re-uploads in 2026

1. What §512(c)(3) actually requires

A valid DMCA takedown notice is a federal statutory document. It is defined by 17 U.S.C. §512(c)(3), the notice-and-takedown subsection of the Online Copyright Infringement Liability Limitation Act. A notice that omits any of the six required elements does not trigger the platform's removal obligation under §512(c)(1)(C) and, per §512(c)(3)(B)(i), is not considered as conferring "actual knowledge" on the service provider. Platforms can — and most major DSPs do — reject malformed notices on sight.

Here are the six elements, verbatim from the statute, with the operational shape each one takes inside a DSP intake form.

1. §512(c)(3)(A)(i)

   "A physical or electronic signature of a person authorized to act on behalf of the owner of an exclusive right that is allegedly infringed."

   In practice: a typed name in the signature block of the form, plus a role line ("Authorized representative, Rightsholder LLC"). E-SIGN (15 U.S.C. §7001) makes the typed name binding when intended as a signature.

2. §512(c)(3)(A)(ii)

   "Identification of the copyrighted work claimed to have been infringed, or, if multiple copyrighted works at a single online site are covered by a single notification, a representative list of such works at that site."

   In practice: track title, artist, release name, label, original release date, ISRC and — when relevant — the original DSP URL. For bulk filings, attach a CSV with one row per work; the statute explicitly authorizes representative lists.

3. §512(c)(3)(A)(iii)

   "Identification of the material that is claimed to be infringing or to be the subject of infringing activity and that is to be removed or access to which is to be disabled, and information reasonably sufficient to permit the service provider to locate the material."

   In practice: the exact DSP URL of the offending upload. Track-level URLs are preferred over album-level URLs; album-level is acceptable only when every track on the release is infringing. Spotify URIs (spotify:track:…) and Apple Music adam-ids work as fallback identifiers.

4. §512(c)(3)(A)(iv)

   "Information reasonably sufficient to permit the service provider to contact the complaining party, such as an address, telephone number, and, if available, an electronic mail address at which the complaining party may be contacted."

   In practice: physical address, phone number, monitored email address. Use a role inbox (legal@, rights@) rather than a personal address; counter-notices and follow-ups land here.

5. §512(c)(3)(A)(v)

   "A statement that the complaining party has 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."

   This is the Lenz clause. Good faith is not a checkbox; it requires a contemporaneous fair-use consideration (see §2 below). Phrase it precisely: "I have a good-faith belief that use of the identified material in the manner complained of is not authorized by the copyright owner, its agent or the law, and I have considered whether the use constitutes fair use under 17 U.S.C. §107."

6. §512(c)(3)(A)(vi)

   "A statement that the information in the notification is accurate, and under penalty of perjury, that the complaining party is authorized to act on behalf of the owner of an exclusive right that is allegedly infringed."

   Two attestations packaged together: accuracy of the facts (no perjury qualifier) and authority to act (under penalty of perjury). Splitting them in the notice avoids the common ambiguity where the "under penalty of perjury" qualifier appears to attach to the entire notice.

Substantial compliance with elements (ii), (iii) and (iv) is enough to confer actual knowledge under §512(c)(3)(B)(ii) — the platform must then promptly contact you to cure defects in the other elements. The other three — signature, good-faith and authority — are hard requirements; a notice missing any of them is treated as if it were never sent.

2. Why §512(f) makes false takedowns risky

17 U.S.C. §512(f) is the DMCA's misrepresentation hammer. It creates a private cause of action against "any person who knowingly materially misrepresents under this section — (1) that material or activity is infringing." A successful §512(f) plaintiff can recover damages, costs and attorneys' fees. For high-volume takedown programs, this is the single largest operational risk.

The leading case is Lenz v. Universal Music Corp., 815 F.3d 1145 (9th Cir. 2016). Stephanie Lenz uploaded a 29-second home video of her toddler dancing to Prince's "Let's Go Crazy." Universal sent a takedown. The Ninth Circuit held that before a copyright holder sends a §512(c)(3) notice it must form a subjective good-faith belief that the use is not authorized by law — and "the law" includes fair use under §107. A purely automated pipeline that never considers fair use can be the basis for §512(f) liability.

Lenz applies inside the Ninth Circuit and has been treated as persuasive elsewhere. The Second Circuit's Yout LLC v. RIAA (2024) decisions on the §1201 side reinforce the broader trend: courts increasingly require the rightsholder to articulate why a use is infringing rather than to assume it.

For a verbatim re-upload of a commercially released sound recording, the §512(f) analysis is usually quick: there is no transformation, no commentary and no plausible fair-use defense. Documenting that analysis contemporaneously — even a one-line note inside your takedown register — is what closes the §512(f) loop.

3. Step-by-step: from detection to removed URL

Below is the seven-step process DSP Watch's own operators use. It is designed to compress to roughly 45 minutes per single-track filing once you have your ownership bundle pre-assembled.

Step 1 — Identify the work and the infringing copy

Capture the canonical URL of your release, the URL of the re-upload, the upload date as displayed by the DSP, the displayed artist name on the infringing upload and (if visible) the ISRC. If the ISRC on the re-upload matches yours, you have a near-conclusive duplicate; if it differs, document the mismatch so DSP review can see both.

Step 2 — Assemble ownership proof

Pull, in one bundle: (a) the distribution agreement or assignment that gives you the relevant exclusive right; (b) the ISRC allocation record from your registrant; (c) the original master file plus a SHA-256 hash; (d) label-copy or metadata sheet showing artist, songwriter, publisher and release date. Save as a zip with a manifest.txt that lists each file with its SHA-256.

Step 3 — Draft the notice with all six §512(c)(3) elements

Use the template in §8. Do not skip the dual attestation in element (vi); rewrite the form's free-text field if the DSP only provides one checkbox. If the form is rigid, paste the §512(c)(3) language into the "additional notes" field so the statutory phrasing is captured in your submission.

Step 4 — Pre-flight the §512(f) analysis

Write one line into your register: "Considered fair use under §107. Verbatim re-upload of commercially released master; no transformation, commentary or licensed cover. No fair-use defense apparent." Date it. That single line, captured before submission, is the contemporaneous record Lenz contemplates.

Step 5 — File via the correct intake

Use the per-DSP table in §4. Do not send a §512(c)(3) notice to an artist-support inbox; it will not reach the designated agent and your clock for the platform's "expeditious" duty under §512(c)(1)(C) does not start until the right desk has it.

Step 6 — Log the submission, watch for counter-notice

Record the platform's receipt ID, the time, the agent who filed it and the SLA. Set a 14-day reminder for counter-notice; if one arrives, §6 below walks the response.

Step 7 — Close the loop with proof

Verify the URL returns HTTP 404, a "content removed" placeholder or otherwise no longer plays the master. Capture the closure screenshot, hash it, and store the closure record alongside the original submission in the takedown register.

4. Per-DSP intake reference

Every major DSP designates an agent under §512(c)(2) and a working intake channel. Where a webform exists, use it — email channels are accepted but routinely slower. Median SLAs below are based on observed first-action timestamps across 1,000+ notices filed Q1 2026 and should be treated as guidance, not promises.

DSP intake URLs and email addresses change. Confirm against the U.S. Copyright Office Designated Agent Directory immediately before filing — service on a non-current agent is not valid notice.

5. What "evidence-grade" looks like

"Evidence-grade" is the standard a takedown bundle must meet to survive both DSP escalation review and, if it comes to it, a §512(f) defense. Four properties define it.

1. Hash-pinned. Every artefact — the master WAV, the captured infringement (screenshot, audio waveform, page HTML) — is fingerprinted with SHA-256 at the moment of capture. The hash, not the file, is what you rely on to prove the bundle has not changed.
2. Timestamped. Each hash is committed to an immutable log — RFC 3161 timestamp tokens, OpenTimestamps Bitcoin attestations or an append-only audit log inside your operations platform. Wall-clock time alone is not evidence; an immutable timestamp is.
3. Signer-attested. The specific agent who captured the evidence is identified by name and role, and the capture environment (browser, IP geo, capture tool version) is recorded. This is the chain that makes the bundle attributable rather than anonymous.
4. Chain-of-custody preserved. Every read, copy or export of the bundle is logged. If the bundle ever ends up in a courtroom, the court will ask who has touched it. You want a complete, immutable answer.

6. Counter-notice handling

17 U.S.C. §512(g) is the alleged infringer's response valve. If the subscriber files a counter-notice that meets §512(g)(3)'s elements — signature, identification of removed material, good-faith statement under penalty of perjury and consent to jurisdiction — the platform forwards it to you and then waits. Under §512(g)(2)(C), if you do not file an action seeking a court order to restrain the subscriber within 10–14 business days, the platform restores the material and is shielded from liability for doing so.

Practical playbook on receiving a counter-notice:

1. Diary the deadline immediately — the clock is short and runs from receipt.
2. Verify the counter-notice's §512(g)(3) elements. Defective counter-notices do not start the restoration clock; tell the platform.
3. Pull the evidence bundle and re-confirm ownership and §512(f) analysis with counsel.
4. If you intend to escalate, file a complaint and seek a TRO in the proper U.S. district court. Send the platform a copy of the file-stamped complaint before the 10-day window closes.
5. If you do not intend to litigate, send the platform a letter standing down. This preserves the relationship for future filings.

7. Common mistakes and how to avoid them

8. Sample notice template (annotated)

Paste this into the DSP's intake form or email it to the designated agent. Annotations in {curly braces} explain which §512(c)(3) element each block satisfies; delete the annotations before submission.

Subject: DMCA Notice of Claimed Infringement — [Track Title] — [DSP]

To: DMCA Designated Agent, [DSP Legal Name]

I am the authorized representative of [Rightsholder Legal Name]
("Rightsholder"), the owner of the exclusive right of reproduction,
distribution and making available of the sound recording identified below.
{(c)(3)(A)(vi) — authority}

1. Identification of the copyrighted work     {(c)(3)(A)(ii)}
   Title:      [Track Title]
   Artist:     [Recording Artist]
   Release:    [Album / Single Title]
   Label:      [Label]
   Released:   [YYYY-MM-DD]
   ISRC:       [XX-XXX-YY-NNNNN]
   UPC:        [NNNNNNNNNNNN]
   Authorized URL on [DSP]:
               https://[dsp]/track/[id]

2. Identification of the infringing material  {(c)(3)(A)(iii)}
   Infringing URL:
               https://[dsp]/track/[id-infringing]
   URI / id:   [platform-specific id]
   Displayed artist on upload: [as shown]
   Upload date as shown:       [YYYY-MM-DD]

3. Contact information                        {(c)(3)(A)(iv)}
   Name:       [Signer Name], Authorized representative
   Address:    [Street, City, State/Country, Postal Code]
   Phone:      [+1 ...]
   Email:      legal@[rightsholder].com

4. Good-faith statement                       {(c)(3)(A)(v)}
   I have a good-faith belief that use of the identified material in
   the manner complained of is not authorized by the copyright owner,
   its agent or the law. I have considered whether the use constitutes
   fair use under 17 U.S.C. §107 and concluded that it does not, because
   the upload is a verbatim duplicate of the commercially released
   master with no transformation, commentary, parody, criticism or
   licensed cover use.

5. Accuracy and authority attestations        {(c)(3)(A)(vi)}
   The information in this notification is accurate. Under penalty of
   perjury, I am authorized to act on behalf of the owner of an
   exclusive right that is allegedly infringed.

6. Signature                                  {(c)(3)(A)(i)}
   /s/ [Signer Name]
   [Signer Name], Authorized Representative
   [Rightsholder Legal Name]
   Dated: [YYYY-MM-DD]

Attachment:
   evidence-bundle.zip
     - master.wav
     - master.sha256
     - capture.png (infringement page)
     - capture.sha256
     - manifest.txt
     - rfc3161-timestamp.tsr

The annotations map each clause to its statutory element. When the DSP intake form has fixed fields, paste the corresponding clause body into each field and put the §512(c)(3) language into the "additional notes" area so the statutory phrasing is preserved in your submission.

9. FAQ — ten takedown-process questions