"It's mine" convinces nobody. Every takedown, dispute, and counter-notice lands on the same demand: prove it. When you send a DMCA takedown notice, the law makes you vouch that the work is yours or that you're authorized to enforce it. The person who copied it can claim the opposite. Whoever brings dated evidence a third party can verify wins, and most abuse desks never dig deeper than what's attached.
The good news: you almost certainly have the proof already. It sits in your source files, your publish history, your sales records. Most people just don't know which pieces count, which don't, and how to package them. That's what this guide covers, in the order you'd use it.
The proof hierarchy, strongest first
Evidence ranks. A platform abuse desk triages by what it can check in minutes; a court demands more and rewards preparation. Four tiers, strongest first, each gets a full section below.
- Source files. The RAW photo with its EXIF metadata, the DAW project with stems, the layered design file, the repository's commit history. Internal dates and structure that are hard to fake convincingly, and you already have them. Strongest proof per unit of effort.
- Dated public publication. Your portfolio page, shop listing, video upload, the earlier public record. Pair it with a Wayback Machine capture, and a third party holds the date instead of you.
- Copyright registration. The Copyright Office certificate is the gold standard in court and ends most platform arguments. In the US it also gates statutory damages and attorney's fees.
- Sales and distribution records. Course platform creation dates, distributor release records, self-publishing dashboards. Commerce systems date events by design, and the records live on servers you don't control, which is exactly what makes them credible.
Which tier dominates depends on the venue. In court, the certificate outranks everything; Congress stacked the incentives that way. In a platform dispute, source files usually settle things fastest because they're checkable on the spot. Ownership itself is automatic across most of the world under Berne, it's the proof that has to be assembled.
Source files and publish dates: the proof you already have
Two records do most of the work: the original file, which is private, and the dated publication, which is public. They fail in different ways, so you need both.
The copy you posted isn't your best evidence, the file it came from is. Every step downstream strips information: export settings discard layers, most social platforms strip EXIF data on upload, and a file downloaded back from your own page proves nothing about origin. Keep the untouched original somewhere you don't work, and edit copies.
What the original holds depends on the medium. A RAW photo carries capture time, camera model, sometimes the body's serial number, and how EXIF metadata holds up as evidence depends on it staying intact. A music project holds stems and edit history a finished MP3 doesn't. A layered design file holds named layers and adjustment steps. A hosted repository keeps commit history on someone else's servers, and their timestamps beat your local copy. Writers get the same benefit from cloud documents: platform-stored version history is a dated record you can't backdate.
One caution: dates on your own machine are mutable, and everyone who evaluates evidence knows it. A local "date created" field convinces no one on its own. Originals are necessary; they're not sufficient. That's what publication records are for.
A publish date on your own site is under your control, so alone it proves little. What carries weight is a date held by a party with no stake in your dispute. The Wayback Machine is the easiest: request a capture the day you publish, and the archive holds the timestamp. Platform records come next, a video's upload date, a marketplace listing's creation date, a distributor's release record, all on servers the infringer can't edit.
Commerce records deserve more credit than they get. A course platform's internal creation date, an order history showing the product sold months before the copy appeared, a self-publishing dashboard's first-publish date: business systems date events by design. The same records settle most stolen course content disputes, because the pirate's listing date loses to your creation date.
Email helps more than people expect, a dated message to a client with the deliverable attached is a third party holding both a timestamp and the work. Search engines' first-indexed dates, by contrast, are approximations you don't control. For the mechanics of dating evidence, timestamp evidence in copyright disputes is worth its own read.
Copyright registration: the heavyweight evidence
You don't need a registration to send a takedown. You need it for everything after. Under 17 U.S.C. § 411(a), a US work can't anchor an infringement suit until the Copyright Office has registered it, granted, not merely applied for; the Supreme Court held that in Fourth Estate v. Wall-Street.com. Timing controls the remedies: under § 412, statutory damages and attorney's fees are available only if registration preceded the infringement or landed within three months of first publication. Register late and you're left proving actual losses.
The certificate also does affirmative work. Under § 410(c), a registration issued before or within five years of publication is prima facie evidence of validity, ownership, and date, the burden shifts to the infringer. Combined with statutory damages that reach $150,000 per work for willful infringement, that shift is why the certificate ends arguments: the other side's lawyer reads it the same way the abuse desk does.
Filing fees are modest, and group options bundle multiple works in one application; the full calculus for your catalog is in whether copyright registration is worth it. Past the platform, the small-claims route through the Copyright Claims Board also runs through registration. Non-US creators get one break: § 411's gate applies to US works, so the owner of a Berne-country work can sue in a US court without registering, though § 412 still ties damages and fees to US registration.
What doesn't prove content ownership
Some of the most popular "proof" carries no weight, and knowing that keeps you from leaning on it mid-dispute.
Mailing your work to yourself, poor man's copyright, has no basis in US law. A postmark shows an envelope was mailed on a date. It says nothing about what was inside, and a sealed envelope can be resealed around anything.
Watermarks and © lines are assertions, not evidence; anyone can place one on a stolen file in seconds. They still earn their keep as deterrents and identifiers, watermarking your photos remains smart practice, but they rank far below the real tiers. Site badges belong in the same bucket: a DMCA protection certificate can play a deterrent role, but a badge on your page creates no ownership record anywhere.
Two more that come up constantly: ranking higher in search results proves popularity, not priority. And local file dates, covered above, are mutable.
One modern wrinkle: purely machine-generated output isn't copyrightable, so a log of prompts can't establish ownership of what the machine made. Where that leaves AI-assisted work is covered in AI-generated content and copyright, your protectable interest is your human authorship, and that's proven the traditional way.
Shared, assigned, and client-owned work: prove the chain of title
If you enforce work you didn't create, ownership proof includes the chain of title: the contract, the assignment, the license, documents showing the rights reached you.
The trap is work made for hire, defined in 17 U.S.C. § 101. An employee's work belongs to the employer automatically. Commissioned freelance work does not, unless it falls in one of nine statutory categories and both sides signed a writing saying so. Otherwise the freelancer keeps the copyright and the client holds a license, often narrower than the client assumed when paying. Discovering that mid-dispute is expensive.
Exclusive transfers require a signed writing under § 204(a). Nonexclusive licenses can be informal, which makes them cheap to grant and hard to prove, put them in writing anyway, even a confirming email. For co-owned work, document the other owners' consent to your enforcement.
Then the notice itself. Under § 512(c)(3)(A)(vi), the sender must state that the information is accurate and, under penalty of perjury, that they're authorized to act on behalf of the owner of an exclusive right. Who can file a DMCA takedown turns on exactly that line. If you enforce for clients, DMCA takedowns for agencies start with signed authorizations on file before the first notice goes out.
When the copycat counter-attacks: counter-notices and escalation
The counter-notice is where your hierarchy gets stress-tested. Under § 512(g), the person you reported can swear the material came down by mistake. Once that arrives, the platform will typically restore the content within 10 to 14 business days unless you file a court action. Keeping it down now means suing, and for a US work. That means registering first, because of the § 411 gate.
So after a counter-notice, whoever can escalate to court wins by default. Source files and dated publication still matter, they're your exhibits, but the certificate is what keeps the takedown standing.
Two cautions in this phase. Never overstate your rights: § 512(f) makes a sender liable for damages and costs for knowingly misrepresenting ownership, and misrepresentation claims under § 512(f) cut both ways. And this is the natural moment for counsel, when to bring in a copyright lawyer is, in practice, the moment a counter-notice lands or you decide to file suit. For the full timeline, what happens after a counter-notice walks the procedure.
Build the proof pack before the dispute starts
Disputes don't schedule themselves, and evidence gathered after the fact is always weaker. The creators who win aren't the ones with lawyers on retainer, they're the ones with dated originals and archived pages. Two habits cover most of it: request an archive capture whenever you publish, and keep source files with their metadata intact.
Add a third, newer habit: hashing. A SHA-256 fingerprint, recorded with a timestamp, proves that exact content existed at that moment, change one pixel and the hash changes completely. Hash originals when you finish them. In active enforcement the idea runs in reverse: monitoring that captures and hashes the infringing page the moment it's detected creates evidence before the page can be edited or deleted. That's built into our protection plans.
Assemble the pack once and reuse it forever. What goes in:
- the untouched source file, stored where you don't work
- a dated export plus the platform's publish and sales records
- an archive capture of first publication
- the registration certificate, if you have one
- contracts, assignments, or authorizations, if rights came through anyone
- hashes of the original, recorded when it was made
A fuller evidence checklist for takedowns extends this by platform and medium.
Frequently asked questions
Do I need to register my copyright before sending a takedown notice?
No. A DMCA notice requires the good-faith statement under § 512(c)(3)(A)(vi), not a certificate. Registration matters at the next level: you can't sue over a US work until the Copyright Office grants one, and statutory damages and attorney's fees depend on registration timing. Send the notice now with dated originals attached, and register in parallel if the dispute looks serious.
Is a watermark or copyright line enough to prove the work is mine?
No. A watermark or © line asserts ownership; it doesn't evidence it. Anyone can place one on a stolen file in seconds, and abuse desks know that. They still help as deterrents and identifiers, so keep using them, but in a dispute they rank far below source files, dated publication, and registration. Treat them as a first line of defense, not proof.
Does mailing or emailing my work to myself prove ownership?
No. Poor man's copyright has no basis in US law. A postmark shows an envelope was mailed on a date; it says nothing about what was inside, and envelopes can be resealed. If you want dated proof with legal force, registration does that job, the certificate is prima facie evidence of the facts it states.
What if the work was never published, can I still prove I own it?
Yes, though it's harder. Copyright attaches the moment a work is fixed in tangible form; publication isn't required to own it. Lean on source files with internal dates, dated drafts, correspondence with clients or collaborators, and witnesses to the creation. Registration is especially valuable here, because it creates a public record where none otherwise exists.
Can my employee, agency, or lawyer file the takedown for me?
Yes, as your authorized agent. The notice must state that the information is accurate and, under penalty of perjury, that the sender is the owner or is authorized to act for the owner of an exclusive right, a required element under § 512(c)(3)(A)(vi). Keep the authorization in writing so the agent can prove the relationship if a counter-notice or challenge arrives.
Do this now
- Collect the untouched originals for the work at issue, RAW files, project files, layered files, and keep the exports out of the pack.
- Pull the third-party dates: an archive capture, platform publish records, sales history. Rely on servers, not screenshots.
- Register anything that earns you money, ideally within three months of publication so the damages remedies attach.
- Hash the originals, store the pack somewhere stable, and re-archive your pages at every publish.
- When theft happens, attach the pack to the notice, the DIY takedown template has the ownership statement built in, or hand the file to a managed takedown and let the service handle escalation.