How to Capture Evidence for a DMCA Takedown Notice
Published April 2, 2026
Someone copied your content. Maybe it is a blog post reproduced word for word on another site. Maybe it is your product photos appearing on a competitor's listing. Maybe it is your code, your design, or your creative work - taken without permission and published as if it were theirs.
You want to file a DMCA takedown notice to get the infringing content removed. But before you send that notice, you need evidence. And the quality of your evidence will determine whether your takedown succeeds or gets ignored.
What a DMCA Takedown Notice Requires
Under the Digital Millennium Copyright Act (17 U.S.C. Section 512), a valid DMCA takedown notice must include several specific elements. Two of the most important are:
- Identification of the copyrighted work - you must clearly identify the original content you own that is being infringed. This means providing a URL or description of your original work.
- Identification of the infringing material - you must identify the specific material that infringes your copyright and provide the URL where it is located so the hosting provider can find and remove it.
The notice also requires a sworn statement, made under penalty of perjury, that you are the copyright owner (or authorized to act on behalf of the owner) and that the information in the notice is accurate. This is a legal declaration - you need solid evidence backing it up.
Hosting providers and platforms receive thousands of DMCA notices. The ones that include clear, well-documented evidence get processed. The ones that include a vague description and a bare screenshot often get pushed to the bottom of the queue - or rejected outright.
Why You Need Evidence Before Sending the Notice
Here is a mistake many copyright holders make: they spot the infringement, immediately fire off a DMCA notice, and only then think about evidence. The problem is that once you alert the infringer - either directly or through their hosting provider - they can modify or remove the infringing content before anyone reviews your claim.
If the content disappears before the platform investigates, your notice has no teeth. You claimed infringement existed at a URL, but when the reviewer checks, the page looks different or returns a 404. Without timestamped evidence proving what the page contained when you filed the notice, your claim is difficult to verify.
This is why evidence collection must happen first, before any communication with the infringer or their platform. Capture everything while the infringing content is still live and unmodified.
Step-by-Step Guide to Documenting Infringement
Follow these four steps to build an evidence package that makes your DMCA takedown notice airtight.
Step 1: Capture the infringing page with URL and timestamp
Take a full-page screenshot of the infringing content that includes the complete URL and the exact date and time of capture. A regular screenshot from your browser will not cut it here - there is no way for a reviewer to verify when it was taken or whether the page content was manipulated before you captured it.
You need a server-side capture that independently visits the URL and records what it finds. This removes any possibility that you edited the page using browser developer tools. The URL and UTC timestamp should be embedded directly in the image, not stored as separate metadata that can be stripped or altered.
Step 2: Capture your original content for comparison
Your DMCA notice needs to identify both the infringing work and your original. If your original content is published online, capture it with the same level of documentation - a server-side screenshot with an embedded URL and timestamp. This creates a side-by-side evidence pair: your original and the copy, both independently verified.
If your original is not published online (for example, it is a local file, a draft, or an offline creation), keep a separate record with a clear timestamp. But when both works are web-based, having documented captures of each makes the comparison straightforward and credible.
Step 3: Save the underlying HTML source
A screenshot shows what a page looked like visually. But copyright infringement often goes deeper than surface appearance. Saving the full HTML source of the infringing page proves code-level copying, not just visual similarity.
The HTML source can reveal copied text that is hidden from view, identical CSS class names, matching code comments, or embedded metadata that was carried over from your original. These details are invisible in a screenshot but can be decisive evidence of direct copying rather than independent creation.
A complete DOM capture preserves the full structure of the page - every element, every link, every hidden tag - as a machine-readable, searchable record that complements the visual evidence.
Step 4: Get a cryptographic hash and trusted timestamp
The final piece is proving when your evidence was captured - and proving it has not been altered since. A SHA-256 cryptographic hash computed at the moment of capture acts as a digital fingerprint. If even a single pixel of the screenshot or a single character of the HTML source is changed after capture, the hash will no longer match.
Pair this with an RFC 3161 trusted timestamp from an independent Time Stamp Authority, and you have a mathematically verifiable proof of exactly when the capture was made. The timestamp does not come from your computer - it comes from a third party whose clock and signing key you cannot control. This is the standard courts and arbitration panels recognize as trustworthy.
How Snapoena Automates All of This in One Click
Following the four steps above manually is time-consuming and error-prone. You would need to coordinate a server-side capture tool, a DOM extraction tool, a hashing utility, and an RFC 3161 timestamp service - then assemble the results into a coherent evidence package.
Snapoena handles all of this in a single step. Paste the URL, click capture, and Snapoena's server:
- Visits the URL independently and takes a full-page screenshot with the URL and UTC timestamp embedded directly in the image
- Captures the complete HTML source and DOM structure of the page
- Computes a SHA-256 hash of the screenshot and source
- Sends the hash to an independent RFC 3161 Time Stamp Authority for cryptographic certification
- Packages everything into a downloadable evidence bundle ready to attach to your DMCA notice
Do this once for the infringing page and once for your original content. You now have a complete, timestamped, cryptographically verified evidence package that shows exactly what both pages contained and when you captured them - all before the infringer has any reason to modify their content.
Make Your DMCA Notice Stick
A DMCA takedown notice is only as strong as the evidence behind it. Platforms process takedown requests faster when the evidence is clear and verifiable. And if the dispute escalates - to a counter-notice, to litigation, or to repeat infringement claims - having documented, timestamped, cryptographically verified evidence from the start puts you in a far stronger position.
Do not wait until after you have sent the notice to think about evidence. Capture first, then file.
Ready to document copyright infringement?
Paste the infringing URL and get a server-side screenshot with HTML source, SHA-256 hash, and RFC 3161 timestamp. Free to use.
Capture Evidence Now