Pre-release leak protection: 6 things music publishers do (authors can steal)

Record labels have spent twenty years losing albums before release day. A finished master passes through mastering engineers, pressing plants, radio pluggers, journalists, and playlist curators, and any one of them can end up as the source of a leak. The industry got good at pre-release leak protection because it had no choice.

Authors face the same problem on a smaller scale. Your advance reader copies go to reviewers, bloggers, BookTok accounts, and early readers in the weeks before launch. If one of those files reaches a shadow library, the pirated copy ranks for your title before your retailer page has a single review. The six habits below come straight from how music publishers handle unreleased work, adjusted for a book.

1. Send streams, not files

Labels stopped emailing MP3s to press years ago. A journalist reviewing an unreleased album usually gets a login to a private streaming portal. They can listen as often as they want, but they never hold a file they could forward.

The book equivalent is a reading link instead of an attachment. If you send ARCs through a review platform, pick the option that keeps the book inside a reader app or a browser session. If you send files yourself, prefer a delivery service that issues one download link per reader over a shared Dropbox folder anyone can open. A reviewer can still screenshot pages, but a screenshot of 300 pages is a lot of work, and pirates skip titles that take effort.

You lose some reach this way. A small number of reviewers insist on a plain EPUB. That trade is worth making for the bulk of your list, and you can make exceptions for people you know.

2. Watermark every copy to a named person

When a label sends out advance audio, each copy often carries an inaudible watermark tied to the recipient. If the album turns up on a torrent site, the label can trace the file back to whoever received it. Most people on a promo list know this, and knowing it changes behaviour.

You can do a cruder version with no special tools. Put the reader’s name and email on the copyright page and in the footer of every chapter. Some ebook delivery services stamp this for you. A visible watermark won’t stop a determined uploader, since they can strip text from an EPUB in minutes. It does stop the casual share, where a reviewer sends the file to a friend who sends it to a group chat, because nobody wants their name on the leaked copy.

Keep a list of which version went to whom. If a copy surfaces, you want to check the name in under a minute.

3. Shrink the window between access and release

Labels learned that the longer a finished album sits in other people’s hands, the more likely it leaks. Some artists now announce and release on the same day, and others cut the press window from months to a couple of weeks.

For a book, the equivalent is to stop sending ARCs six months out unless a trade review outlet needs that lead time. Early readers who post on Goodreads and social media need two to four weeks, not a season. Every extra week a file circulates before launch is a week a pirate can post it while your own listing sits empty.

If you do need long lead times for trade reviews, send those early copies to a short list and hold the wider reader team until closer to launch.

4. Tier your list by trust

A label doesn’t give the same access to a national music critic and a new playlist curator it found last month. People with a track record get the full album early. Newer contacts get a single or a stream a few days out.

Split your ARC list the same way:

• Tier one: reviewers and readers who have read your advance copies before and posted real reviews. They get the full book first.
• Tier two: new contacts from a sign-up form or a promo service. They get the book later, or a sample of the first chapters, with a watermarked full copy once they respond.

This does two things. It cuts the number of full copies that exist early, and if a leak happens, it narrows the suspects to a group small enough to check. Our audiobook piracy guide covers the same idea for ACX promo codes, which leak the same way.

5. Register and fingerprint before release, not after

Labels deliver reference files to platforms like YouTube before an album goes public, so the platform’s matching system recognises the tracks the moment someone uploads them. They don’t wait for a leak to start that paperwork.

Authors have fewer automated matching systems to feed, but the principle holds: do the ownership work ahead of launch.

• Register the copyright with the US Copyright Office if you plan to. Registration isn’t required for a takedown, but it strengthens your position if a dispute ever goes further.
• Keep your final manuscript, your publishing contract, and your retailer listing links in one folder. When you file a notice, you want proof of ownership ready to paste.
• Prepare your takedown wording now. We publish DMCA takedown notice templates you can fill in before launch week, so you are only adding a URL on the day.

6. Run a watch team for launch week

When a big album is due, labels have people searching torrent indexes, file hosts, and social platforms from the moment advance copies go out through the first weeks after release. They file removals within hours, because an early leak spreads fastest in its first day.

You don’t need a team, but you do need a plan for the fortnight around your launch. Search your title plus “epub”, “pdf”, and “free download” every day. Check the usual destinations, which we list in 10 places pirated copies of your book end up. When you find a copy, file with the host that stores the file first, then with the page linking to it, then ask Google to delist the URL. Our guide to removing pirated copies from Google covers that last step, and response times vary a lot by site, so start early.

Speed matters more before launch than after. A pirated copy that ranks for your title while your own listing has no reviews takes searches you will never get back.

What authors can skip

Some music industry habits don’t translate. Forensic audio watermarking and custom listening portals cost more than most indie authors earn from a launch. Legal action against individual leakers rarely makes sense for a book. And labels can lean on platform relationships that a solo author doesn’t have.

The cheap habits carry most of the benefit: fewer files, named copies, shorter windows, a tiered list, ownership proof ready to go, and someone watching in launch week. If you have one afternoon, spend it on the watermark and the tiered list.

How Clampdown helps

Clampdown handles the watching. You register your book before launch, and we scan piracy sites, file hosts, shadow libraries, and forums for copies from the day your advance copies go out. We confirm each match is your work, then file the host takedowns and search delisting requests for you. When a leaked copy comes back on a new site, we catch it and file again without you having to notice first.

FAQ

Should I stop sending ARCs to avoid leaks? No. Reviews at launch sell books, and most reviewers never share a file. Send fewer full copies early, watermark them, and keep the rest of your reader team closer to launch.

Does DRM on an ARC stop leaks? It slows casual sharing, and people who want to strip it can. Our piece on what ebook DRM stops goes through the trade-offs. A visible name on every page works on a different lever: it makes the reader who leaks it identifiable.

Can I file a takedown for a book that isn’t published yet? Yes. You own the copyright from the moment you write the work. Hosts act on notices for unreleased books the same way they do for published ones, and it helps to link your preorder page as proof.

What if I find out which reviewer leaked my ARC? Take them off your list and file the takedowns. Confronting them rarely removes the copy, and the takedown is what gets the file off the sites where readers find it.

If you want to know whether an early copy of your book is already circulating, start with a free piracy audit.