KDP has a little tick-box at publication time labelled "Enable digital rights management". You'll see it once, whilst uploading your ebook, tucked near the bottom of the rights and pricing page. Most new indie authors tick it on reflex, on the quiet assumption that it's a sensible anti-piracy measure. Then they publish, forget about it, and move on.
What almost none of them know — and what KDP does not put in bold — is that the tick-box is irreversible. Once a book is published with DRM on, it stays on for that title's lifetime on KDP. You can't toggle it off later. And DRM almost certainly doesn't do what you think it does.
This is one of those slightly niche decisions that's worth being deliberate about, because the default is quiet and the reversal is "publish a new edition under a new ASIN". It's worth five minutes of your time before you click Publish.
What DRM actually is
Digital Rights Management, in Amazon's implementation, is a layer of copy protection applied to your Kindle ebook file. When enabled, it restricts what readers can do with the file in a few practical ways:
- The ebook is tied to the buyer's Amazon account. Sideloading the file onto a non-Amazon device — a Kobo, for instance — isn't straightforward.
- Sharing the file with another reader by email or USB doesn't work cleanly.
- Automated tools for converting between formats (say, KFX to EPUB) hit the DRM wall unless the reader goes out of their way to bypass it.
The intent, at least in theory, is to stop casual copying — a reader emailing your book to ten friends, or a pirate uploading it to a scraper site.
What DRM does not do
Here is where it gets awkward.
Tools for stripping Kindle DRM are the first search result for anyone who knows the phrase. A determined pirate can download your book, run it through a desktop utility, and have a clean EPUB on a file-sharing site within fifteen minutes. This isn't a theoretical weakness. It's the actual, observed behaviour of every Kindle DRM system since the device launched.
The people DRM inconveniences are not the pirates. It's the readers who bought your book legitimately and then try to do normal things with it — read it on a Kobo they already own, load it onto a library e-reader, convert it to read on a flight where their Kindle has decided to die. Those people hit the wall and, understandably, blame you.
The irreversibility problem
KDP's own help documentation is clear on this, even if it's easy to miss whilst you're in the flow of publishing: the DRM choice is made once, at upload, and can't be changed later. If you publish DRM-on and later change your mind, your options are:
- Live with the DRM for the life of that ASIN.
- Unpublish the title and republish it as a new book — fresh ASIN, no review history, no rank, nothing carried over.
The second option is, in practical terms, a nuclear one. You lose the review count you built up, you lose the sales rank history, you lose the also-boughts pointing at the book. It is almost never worth it for a title that has any traction at all.
So the decision really does matter. It's a five-second click with a permanent consequence — which is exactly the kind of thing you want to get right first time.
What most indie authors who've been at this a while will tell you
There's a fairly consistent view in the indie author community, echoed by the likes of Joanna Penn, J.A. Konrath, and the Alliance of Independent Authors, which runs roughly as follows:
- Piracy is real, but DRM does not materially reduce it.
- Readers want flexibility. DRM annoys the honest ones.
- Some readers who can't get a book comfortably on their preferred device simply won't buy it at all.
- The opportunity cost of annoying paying readers, across the lifetime of a book, is larger than the cost of the piracy DRM was meant to prevent.
You can disagree with any one of those. But the combined weight of authors who've run the experiment, looked at their own data, and then moved to DRM-free is considerable.
When DRM might still make sense
I'd be careful not to present this as one-size-fits-all. A few reasonable arguments for enabling it:
- You write in a genre with unusually high piracy rates and the psychology of having "done something" is worth the downsides to you.
- You're risk-averse and the tick-box helps you sleep at night. That is a legitimate reason, as long as you know that's what you're buying.
- Your publisher or rights-holder contract requires DRM. Most indies won't have one; some co-publishing or hybrid deals do.
The counter-argument is essentially that if DRM doesn't actually stop copying, the psychology reason is the only reason — and it's worth being honest with yourself about that before you lock it in forever.
What DRM doesn't touch
Worth saying, because it's a common source of confusion: DRM is a setting on your Kindle ebook file. It has nothing to do with your copyright — you still own and hold the copyright either way. It has nothing to do with your royalty rate. It doesn't affect KDP Select enrolment, KENP payouts, or anything on the paperback side of things. Print-on-demand paperbacks have no DRM concept at all, because a physical book is, by its nature, already a readable object once you've paid for it.
It's also not the same thing as a watermark. Watermarks embed buyer-identifying information into the file and are genuinely useful for tracing leaks back to a source — but KDP doesn't offer author-controlled watermarking. Amazon may apply its own internal identifiers separately; that's not something you configure.
How to actually decide
A short checklist before you tick the box:
- Open a new KDP manuscript, go to the pricing page, and find the DRM tick-box. Get used to seeing it. This stops you from sleepwalking past it next time.
- Ask yourself what you think DRM does, and whether that's actually accurate. (If you got halfway through this article and went "huh, really?" — you're not alone.)
- Consider who your readers actually are. Kindle-only? Mixed Kindle and Kobo? Library users? The more mixed, the more DRM hurts you.
- Check how others in your sub-genre have handled it. Amazon doesn't display DRM status on the public book page, so you'll have to ask around in author Facebook groups or indie forums.
- Decide once, deliberately, and make that your default for every book that follows. Write it down somewhere so future-you doesn't have to re-litigate the question in a hurry at 11pm the night before launch.
Most indies land on DRM-off once they've thought about it properly. A smaller number stay on DRM-on and are at peace with the decision. Both are defensible. The one you want to avoid is "ticked it by accident whilst rushing the upload and didn't realise it was permanent".
Where this fits in a launch
DRM is a decision you make once, near the end of your pre-publish checklist, and it's easy to overlook when everything else — the blurb, the categories, the pre-order window, the ad campaigns — is loudly demanding your attention. That's exactly the kind of small, quiet, permanent choice that keeping a proper launch plan in one place is designed to catch. If you're mapping out your launch end-to-end and would rather not find out six months later that you'd have preferred the other option, WIPsage is built for that sort of thing.