Why pirated copies come back (and how to stop the re-upload cycle)

You filed the takedown. The host removed the PDF of your book within three days. Two weeks later you search your title and find the same file, same cover scan, on a different domain. A DMCA re-upload like this is the normal case, and it tells you how the notice system works: a takedown removes one copy at one URL. It does nothing to the file sitting on the uploader’s hard drive, or to the mirrors that copied it before you filed.

If you understand where the new copies come from, you can stop treating each one as a surprise and start removing them on a schedule.

What a takedown removes and what it leaves

Under Section 512 of the US Copyright Act, a host keeps its legal safe harbor by removing the specific material you identify once you send a valid notice. The Copyright Office’s Section 512 page covers the details. The key word is specific. You name a URL, the host disables that URL, and its obligation ends there.

So after a successful notice, you still have:

• The original file on the uploader’s machine.
• Any copies other sites scraped while the first one was live.
• Search results that point to the old URL or to a mirror.
• Forum posts and Telegram messages that link to a new host as soon as the old one dies.

The takedown worked. It just covered one of many places the file lives.

Five reasons the copies come back

1. The same uploader posts it again

Many pirate uploaders run accounts on several file hosts at once. When one link dies, they paste a fresh link from another host into the same forum thread. On some sites the uploader gets paid per download, so a dead link costs them money and they replace it fast. You’ll often see the replacement within 24 to 72 hours.

2. Mirror and scraper sites copied it first

Ebook aggregators scrape each other. A book that appears on one library site shows up on several clones within days, often with identical filenames and metadata. Our breakdown of Z-Library, Libgen, and Anna’s Archive shows how shared databases move a single upload across many front ends. Removing it from one front end leaves the rest.

3. Google still sends traffic to it

If you only file with the host, the search result can stay up after the file is gone, pointing to a page that now links somewhere else. Pirate sites also redirect dead pages to new domains. Filing with Google as well removes the result itself. The search delisting guide walks through that process.

4. The site moved to a new domain

When a registrar or host drops a piracy site, the operators restore it from backup on a new domain, sometimes the same day. Your old notices don’t carry over. Every URL on the new domain is a new URL, and the host behind it may be a different company with a different abuse contact.

5. A new platform picks it up

Copies spread sideways. A file that started on a download site ends up in a Telegram channel, a Discord server, a Reddit thread, or a resale listing. Each platform has its own reporting route, and none of them know about the notice you sent elsewhere.

Why each re-upload costs you more than the last

The first takedown takes real work: you find the URL, collect proof, look up the host, and write the notice. The fifth one for the same title takes almost the same work, because hosts treat each notice as a fresh request. Most creators file the first few, get tired, and stop. The uploaders count on that.

Delay costs you too. A copy that stays up for a month collects backlinks and climbs in search for your title. A copy you catch within a few days rarely gets that far. How fast hosts respond also varies a lot. Our site-by-site DMCA response times show some hosts acting within hours and others taking weeks.

How to break the re-upload cycle

You can’t make a file disappear from the internet. You can make each copy short-lived and cheap to remove.

Keep a takedown log. Use one spreadsheet per title, with columns for URL, host, abuse contact, date filed, date removed, and notes. When a copy comes back on the same host, you already have the contact and the wording. It also gives you a record if you need to show a host that this uploader repeats.

Save your notice as a template. Your ownership proof, the work’s description, and the good-faith statement stay the same each time. Only the URL changes. Start from our DMCA takedown notice templates and fill in your details once.

Search on a fixed day each week. Use the same queries every time: your title in quotes, your title plus “pdf” or “epub”, your author name plus “download”, and a distinctive sentence from inside the work. Note anything new in the log. Fifteen minutes on a Monday catches most re-uploads before they rank.

File with the host and with Google together. Sending both notices at once means the search result goes away even if the host is slow, and the file goes away even if the result lingers.

Report repeat uploaders by name. Most large platforms have repeat-infringer policies, because Section 512 requires hosts to have one to keep their safe harbor. When you see the same account or username three times, say so in your notice and include the earlier URLs. Some hosts will close the account, and that hurts the uploader more than losing one file.

Go upstream when a site ignores you. If a site won’t respond, find who hosts its server and who provides its CDN, and send the same notice to them. Upstream providers often act when the site itself won’t. Our walkthrough of what to do when someone steals your content covers how to find them.

Know the sites that matter for your format. Ebooks cluster on a handful of sites. Our OceanofPDF removal guide covers one of the most common, with its reporting route.

When to stop filing by hand

Manual filing works when you have one or two titles and a few copies a month. It stops working when you have a backlist, a course with many modules, or a title that a pirate group has decided to keep alive. At that point your weekly fifteen minutes turns into a lost afternoon, and you start skipping weeks. Skipped weeks are when copies settle into search results.

If you’re logging more than ten new URLs a month for the same work, the time you spend filing is worth more than what a monitoring service costs.

How Clampdown helps

Clampdown runs the weekly routine above for you, every day instead of once a week. It searches piracy sites, file hosts, and search results for your titles, checks that each match is your work, files the host and search removal requests, and keeps checking the same sites so a re-upload gets caught and filed again. It won’t stop a determined uploader from trying. It makes each attempt short-lived, and that is what wears them down.

FAQ

Why did my book reappear after a successful DMCA takedown? The notice removed one URL. The uploader still has the file, and other sites may have copied it before you filed. A new URL needs a new notice.

Can I send one notice that covers future uploads? No. Hosts act on the specific URLs you list. Some large platforms have content-matching systems for registered rights holders, but a standard DMCA notice covers only what it names.

How often should I check for re-uploads? Weekly works for most authors and course creators. Check more often in the first month after a launch, when new copies spread fastest.

Does reporting the same uploader repeatedly help? Yes. Hosts that rely on Section 512 need a repeat-infringer policy. Listing earlier URLs from the same account gives them grounds to close it.

If copies of your work keep coming back, start with a free piracy audit to see how many are live right now, or talk to Clampdown about handling the re-filing for you.