Your book is on a pirate library an hour after launch. Ask any author with a recent release; that is the routine now. The upside: book piracy is the most provable theft there is, because your publication record is public, dated, and third-party by design. Nobody has to take your word for anything.
DMCA for authors is therefore a process, not a fight. Prove ownership, mostly done for you already. Send notices at the layer that actually controls each copy, remove marketplace counterfeits, delist the listing pages from search, then keep watching for re-lists. Every step can happen this week, without a lawyer. Here is the sequence, in the order that works.
Your built-in proof of ownership
Copyright attached to your manuscript the moment you fixed the words in a tangible medium, 17 U.S.C. § 102, with no registration, notice, or © symbol required to own it. What publication adds is independent proof of a date. Your retail listings, your publisher's catalog entry, your KDP or IngramSpark dashboard, and your ISBN record each timestamp what you published and when, and none of them depends on your say-so.
Stack the private half on top: dated drafts, revision history, editing correspondence, your publishing contract. Add an archived snapshot of your launch page, the web archives show your book existed before the pirate copy appeared, which quietly kills any "we published it first" argument. The full walkthrough on proving content ownership covers how to assemble this, including making drafts and saved files hold up as evidence.
One nuance: an ISBN identifies an edition and its publisher of record, not ownership itself, supporting evidence, not proof. Registration runs on a separate clock. You do not need it to send notices. You do need it before suing a US infringer, and registering within three months of publication preserves the statutory damages and attorney's fees that make litigation rational. Whether copyright registration is worth it depends on your plans; if the book launched last week, decide now.
Where pirated copies of your book actually live
Sort every infringing URL into the layer that controls it before you write anything. Notices aimed at the wrong layer die unread, and that mistake is where most first attempts lose a week. Book piracy runs on four layers:
- The files. EPUBs and PDFs usually sit on third-party download hosts and lockers with their own abuse forms. Kill this layer first.
- The listing pages. Shadow libraries and index sites scrape retailer listings and display links or an in-browser reader; the pages sit on a hosting provider that answers to DMCA notices. Pirated-book operations answer to their hosts and file hosts, not to email.
- Marketplaces. Counterfeit listings on Amazon-style storefronts and print copies on auction sites answer to the platform's infringement form, not to the seller.
- Discovery. Search engines, Telegram channels dropping EPUB files, Reddit threads sharing links, and full audiobook uploads on YouTube, each has its own reporting path.
The big shadow libraries reward study before you fight them: they have been sued and blocked by court order in several jurisdictions, yet mirrors keep reappearing, so working a mirror's host beats working the site's inbox. The shadow-library enforcement history shows the pattern. For channels, Telegram's copyright process is direct, and YouTube's takedown process covers the audiobook uploads. When you cannot tell which layer a URL sits on, learn how to find out who hosts a site before guessing.
What a compliant takedown notice for a book contains
Section 512 of the Copyright Act fixes the required elements: 17 U.S.C. § 512(c)(3), and a notice that omits them never creates the knowledge that forces a host to act. A compliant notice carries:
- your physical or electronic signature
- identification of the copyrighted work
- identification of each infringing URL, specific enough to locate
- your contact information
- statements of good-faith belief and of accuracy under penalty of perjury
For a book, identify the work precisely: title, author name, edition, ISBN or ASIN, and a link to your authorized retail listing. The retailer link does double duty, it identifies the work and pre-rebuts the "we thought it was free" reply. One notice may list many URLs; when reporting several titles on one site, identify each work clearly.
Most failed takedowns are homemade: vague subject lines, missing perjury language, bare URLs with no work identified. The step-by-step filing walkthrough and a template with each element explained prevent all of that in ten minutes of reading. You can send the notice yourself or authorize an agent, who can file a takedown is a short question with a simple answer.
Kill the files first, then the listing pages
Order matters more than volume. File hosts and lockers operate inside safe harbor: they keep their immunity only by expeditiously removing material on valid notices, what safe harbor requires of hosts, so a clean notice to a locker usually lands inside a week. When the file dies, the listing page pointing at it rots on its own. The reverse never happens.
The exception to understand: pirate sites hosting files on their own servers have no one else's safe harbor to lose, so they ignore email entirely. The leverage sits a level up, the provider renting them servers, the upstream network, the abuse desk. And 17 U.S.C. § 512(i) hands you a second lever: safe harbor is conditioned on terminating repeat infringers, so a follow-up notice citing your first one builds the paper trail that termination under repeat-infringer policies requires.
Amazon counterfeits and marketplace listings
The nastiest variant for authors: your book republished under another seller's account, text scraped from a promo copy or preorder, uploaded to KDP, priced just under yours, siphoning launch-week sales. Report through the marketplace's infringement form with the counterfeit's ASIN, your publication date, your dashboard proof. With clean KDP evidence these come down fast, and counterfeiters almost never contest, because contesting means attaching a real name and address to a sworn statement about stolen books. The mechanics for Amazon and eBay-style marketplaces are in the marketplace infringement guide.
Print counterfeits, "resale" copies of a book that was never legitimately sold, and underpriced bundles on smaller storefronts are the same play with a different form, the playbook for someone selling your content cheap covers the sequence. One caution: do not contact the counterfeit seller directly. It warns them, and it never removes the listing.
Delist the pirate pages from Google
A takedown removes the copy from a site. Delisting removes the road signs. File both, every time. Search engines run their own removal processes, a Google removal request covers that engine's results, so repeat with each major engine your readers use. Include every listing URL you have found, and flag duplicates. Delisting is also the tool for copies you can reach but not remove: a listing you cannot kill can still be made invisible, and the pirate copy readers never find stops selling.
Two side effects make delisting disproportionately powerful for books. Notices processed by the major engines become part of the public transparency record, a visible paper trail against repeat sites. And accumulating valid notices against a domain feeds Google's piracy demotion, which downranks every page on that site, including pages listing titles you have not found yet. That is leverage a single file removal cannot buy.
When pirates push back: counter-notices, refusals, fair use
Most book pirates fold: a complete downloadable EPUB has no fair-use story, and penalty-of-perjury statements filter out casual counterfeiters. Pushback comes in three forms.
The counter-notice. Under 17 U.S.C. § 512(g), the person who posted the file can swear it was wrongly removed; the host then restores the material in about two weeks unless you file a court action. That is the first moment litigation becomes real: to sue a US infringer, the work must already be registered, and qualifying US claims can use the Copyright Claims Board small-claims route instead of full federal court. Pirates rarely counter-notice over books; when one does. Here is what happens after a counter-notice.
The refusal. A host that says no, or ignores you, is not the end of the process, it signals you are at the wrong layer. The response to a rejected takedown is escalation: upstream provider, registrar, then the discovery layer.
The fair-use accusation. Plain reviews quoting passages are usually protected by 17 U.S.C. § 107, so leave reviewers alone, filing against protected commentary risks a misrepresentation claim under § 512(f). Learn the boundaries of when not to file before sending anything aggressive. Whole-book distribution is not a close call: it substitutes directly for your sales, and substitution is not what the doctrine protects.
The serial re-list problem: monitoring is the counter
Book piracy is automated. Retailer listings get scraped on a schedule, new titles get indexed within hours of publication, and mirrors re-list within days of every removal. One takedown is one round, not the end of the fight.
Schedule recurring scans: your title and subtitle, your ISBN, and, the strongest key, distinctive phrases lifted from your own prose, because titles repeat but your sentences do not. Weekly during launch season, monthly after that. That is the author and publisher protection setup in practice, and Protection Pro runs the scanning continuously, with the entry tier free.
A whole catalog on one pirate library is a batch case: one notice per site covering every work, all sites at once. A managed takedown runs that as a single case with a single report, the only sane way to handle forty books on twelve mirrors.
Frequently asked questions
Do I need to register my book with the Copyright Office before sending a DMCA notice?
No. Copyright existed the moment your manuscript was fixed in a tangible medium, and no registration is needed to own the book or send a takedown. Registration matters later: US law requires it before you sue a US infringer, and registering within three months of publication preserves statutory damages and attorney's fees. Send the notice today; run the registration in parallel.
What if the pirate site ignores my takedown notice?
Then the site hosts its own files and answers to no one at that address. Escalate a level: the hosting provider's abuse desk, the upstream network, the registrar, and the search engines. Offshore shadow libraries that ignore every channel are the category that eventually attracts court-ordered blocking and payment-network pressure instead.
Does the DMCA work if the pirate library is hosted in another country?
The DMCA is US law, so it binds US hosts, marketplaces, and search engines directly. Offshore hosts honor notices voluntarily as policy, and most do, because compliance costs less than liability. The EU runs its own notice-and-action regime under the DSA, and several jurisdictions block stubborn pirate libraries by court order. Here is how the DMCA travels internationally in practice.
Pirates claim posting my book is fair use. Is that ever true?
Genuine fair use of a book is narrow: reviews, criticism, teaching, and analysis quoting limited passages under 17 U.S.C. § 107. A full downloadable copy substitutes for sales and is not a close call, the Authors Guild v. Google Books ruling protected digitization for search and snippet access, not wholesale distribution. Leave candid reviewers alone; the misrepresentation risk runs both ways.
How fast do book takedowns actually work?
Marketplace counterfeits and file-host copies are among the fastest removals in copyright enforcement, often days, sometimes hours, once the notice is complete. Listing pages follow when their host processes the notice. Offshore, self-hosted shadow libraries are the slow cases, which is why delisting and monitoring belong in the original plan rather than as later upgrades.
Do this, in order
- Archive evidence: screenshots of each infringing URL with visible dates, plus an archived snapshot of your legitimate listings.
- If the book launched recently, decide on Copyright Office registration this week, the three-month statutory-damages window closes on its own schedule.
- Sort every URL into its layer: file host, listing page, marketplace, or discovery.
- Send complete notices, files first, and the marketplace reports in the same session.
- File the search-engine delisting requests before you close the laptop.
- Set up recurring title and phrase scans, and treat every re-list as a new round.
- If a counter-notice lands or a host refuses, escalate to the next layer.