DeDRM Tools

Last reviewed Aug 26, 2026 · 802 words

The original DeDRM Tools repository stopped in 2021 when its maintainer, Apprentice Harper, retired, and the version you should install today is the community fork maintained under the noDRM name on GitHub. That one sentence resolves most of the confusion around this project: the 15,309-star repository people find first is the archived one, its last release predates modern Calibre, and the plugin that actually loads is the fork. Once you have the right file, DeDRM is a Calibre plugin, not a server, and its job in a self-hosted stack is to turn purchased books into plain EPUBs that Calibre-Web or Kavita can serve to any device you own.

Installation is a plugin, and the fork matters

Download the plugin zip from the fork's releases, open Calibre, go to Preferences, Plugins, Load plugin from file, and restart. The same zip bundles Obok for Kobo. Calibre itself is the only dependency, so the 128 MB of RAM in the catalogue is really Calibre's own footprint, and it runs on Linux, macOS and Windows alike. Keep the plugin updated with Calibre, because Calibre's Python version has moved since the original project stopped, and old plugin builds simply fail to load.

Store by store, what still works

The Adobe row is the workhorse. Adobe Digital Editions 4.5 and later can apply a hardened scheme that the plugin cannot handle, so the standard advice is to install the old 2.0.1 release, authorise it with your Adobe ID, and let DeDRM pull the key from it. The Kindle row is the moving target: Amazon removed the option to download purchases for USB transfer in early 2025, which closed the easiest route for new purchases, and each Kindle desktop app update tends to break key extraction until the community catches up. If your library is mostly Kindle, expect to spend an evening reading current threads before it works, and expect it to break again.

Where it sits in a self-hosted library

The workflow is strictly one-directional. Buy the book, open it once in the store's desktop app so the DRM key is on the machine, import it into Calibre, and the plugin strips the DRM on import; from then on the file is a normal EPUB. Calibre converts it, tags it, and writes it into a library folder that a server-side reader watches. Calibre is a desktop program and does not want to be run as a service, so the pattern that works is Calibre on a laptop writing to a folder that syncs to the server, with Calibre-Web or Kavita reading that folder. Audiobooks go to Audiobookshelf instead. The ebooks category lists the readers; none of them handle DRM, which is why this plugin exists.

The legal position is not uniform

In the United States, circumventing DRM is prohibited by the DMCA's anti-circumvention provisions even for a book you paid for, with narrow exemptions that do not cover general format shifting. Several European countries permit a private copy in principle but forbid breaking technical protection measures to make one, which puts the plugin in a grey zone that has rarely if ever been tested in court against an individual reader. In practice, enforcement against people stripping DRM from their own purchases for personal use is essentially unheard of, and the practical risk is the store's terms of service: an account can be closed. Sharing the stripped files is where the law stops being grey in every jurisdiction. Know which regime applies to you before you decide.

What I'd do

Install the noDRM fork, keep Adobe Digital Editions 2.0.1 around purely as a key source, and buy books from stores that sell DRM-free EPUBs wherever possible so the plugin has nothing to do. For Kobo and library loans the process is reliable and takes seconds per book. For Kindle, decide whether the fight is worth it; I have moved my purchasing away from Amazon rather than keep chasing the format, and the Calibre-to-Kavita library has been quiet ever since. Keep the stripped files private, back them up, and treat the ability to read what you bought on your own hardware as the whole point.