Reposting is not the same thing as theft, and the difference decides which button you press. If someone used a platform's built-in repost or duet feature, your video is still attributed to you and the platform considers that normal use. If someone downloaded your video, stripped your handle, and re-uploaded it as their own, that is infringement — and the in-app report button is usually the wrong tool for it.
The mistake almost everyone makes
Every major platform has two completely separate reporting systems, and they lead to different teams:
- The in-app "Report" button routes to community-guidelines moderation. That team evaluates harassment, spam, and prohibited content. Copyright is not their remit, and a genuine infringement complaint filed here is frequently closed as "no violation found."
- The dedicated copyright / intellectual-property form routes to the legal team that processes DMCA notices. This is a legal instrument, it carries penalty-of-perjury declarations, and it is the only path that reliably results in removal.
Before you file: build the evidence
A takedown is a claim of ownership, and the platform will not investigate on your behalf. Assemble this first — it takes ten minutes and materially changes your success rate:
- The original file. Not the exported upload — the source. Project files, camera originals, and higher-resolution masters are strong evidence because a thief cannot produce them.
- Publication dates. A screenshot of your post with its timestamp, plus the infringing post's timestamp. Earlier publication is the simplest proof of priority.
- Direct URLs to every infringing copy. Most forms accept a list. Filing once for eight URLs is far better than filing eight times.
- Anything embedded in the file itself. If your video carries an invisible watermark, a detector result tying the stolen copy to your specific file is the strongest single piece of evidence available, because it survives the cropping and re-encoding that destroys everything else.
Why video theft is harder to find than image theft
Reverse image search barely helps here. Google and TinEye index still images; a stolen video is thousands of frames, usually re-encoded, often cropped to a different aspect ratio, sometimes speed-adjusted to dodge automated matching. The practical approaches:
- Keyframe search. Extract several distinctive frames and reverse-search each one individually. Searching only the cover frame misses most reposts, because the thief usually changes the cover.
- Audio lineage. On TikTok, an original sound page lists other videos using that audio. If a repost kept your audio, this finds it immediately.
- Caption fragments. Lazy reposters copy captions verbatim. Search a distinctive phrase in quotes.
- Watermark detection. The only method that works when the thief cropped, re-encoded, recoloured, or AI-upscaled the video — because it reads the file rather than matching its appearance. How to check a file.
What to expect after filing
Responses typically take days rather than hours, and the outcome is usually removal plus a copyright strike against the uploader. The uploader can file a counter-notice; if they do, the platform restores the content unless you initiate legal action within a statutory window. Counter-notices are rare for straightforward reposts and common when the reposter believes they had permission — which is why documented dates and originals matter.
Filing knowingly false claims carries real liability. Be certain you own what you are claiming, and be aware that a licence you granted — a brand's usage rights, for example — may cover the use you are objecting to. Check what you actually granted before filing against a brand.
The part you can only do beforehand
Every method above works better when the file itself carries proof. Once a video is downloaded, re-encoded, and re-uploaded, the metadata is gone, the handle overlay may be cropped, and you are left arguing from timestamps. An invisible watermark embedded before publishing survives that pipeline and turns an ownership argument into a detection result. There is no way to add one retroactively to a copy already in the wild.