MarginaGet Margina
Articles

Publié

MOBI vs. AZW: Why Your Kindle Files Won't Open Anywhere Else

You email yourself a .mobi review copy or move an old Kindle backup to a new phone, and nothing opens it. The reason isn't a bug — it's two separate design choices, a closed format and DRM, stacked on top of each other. Here's what MOBI, AZW, AZW3, and KFX actually are, and where that leaves a file you already own.

What it is (one-paragraph answer)

MOBI and AZW aren't two competing inventions. They're the same lineage. MOBI is the format a French company called Mobipocket built starting in 2000. Amazon bought Mobipocket in 2005 and used it as the base for AZW, the format that shipped with the first Kindle in 2007. From there the family kept branching: AZW3, also called KF8, arrived with the Kindle Fire in 2011 and added support for a slice of HTML5 and CSS3, and KFX followed in 2015 with a more capable typesetting engine for hyphenation and kerning. Different names, same root — and the same basic decision underneath all of them: keep the format inside Amazon's ecosystem.

Why it matters

That decision has two separate parts, and they're worth pulling apart, because most explanations flatten them into one.

The first part: Amazon's Kindle formats are proprietary. EPUB, by contrast, is an open, XML-based standard maintained by the International Digital Publishing Forum — exactly why it's the format almost every other e-reader, Kobo, Nook, Sony, Apple Books, is built around. Kindle devices sit on the other side of that line. They read AZW, AZW3, KFX, unprotected MOBI, and plain text natively, but they can't open an EPUB directly. Amazon's own Send to Kindle service works around that by converting EPUB files on the way in, which tells you which direction the compatibility actually flows.

The second part is DRM, a separate mechanism layered on top of the format itself. Mobipocket's original DRM scheme added a unique signature and timestamp to a file at the moment of purchase, tied to the account that bought it; annotations were stored in their own encrypted files, out of reach of other apps. No competing e-reader ever implemented that encryption scheme, and that's really the root of the lock-in — not the file extension, but what's encrypted inside it. One distinction is worth keeping straight: an unprotected MOBI file opens fine in plenty of non-Kindle tools. It's DRM-protected files, purchased through Amazon, that stay closed.

Where you'll see it

This shows up in ordinary moments, not edge cases. A friend emails you a .mobi review copy of their manuscript. A library loan lands on your phone as an AZW file. You dig up an old Kindle backup and want to read it on a different device. In each case, opening the file on something that isn't a Kindle app usually does nothing — no error message that explains why, just a file that won't launch.

The open alternative is worth knowing for exactly this reason: an EPUB file behaves the same way everywhere, because nothing about the format itself is trying to keep you inside one company's apps. And if the book you're after doesn't need to come from a Kindle store at all, there are free, out-of-copyright sources that hand you an EPUB or PDF you can open anywhere from the start.

How Margina handles it

Margina reads unprotected MOBI files directly, alongside PDF, EPUB, Word documents, and plain text — no conversion step, no account required to open what you already have. That's part of a broader idea about owning your books as files, not apps: a document that lives on your device is yours in a way a locked library entry isn't.

We'll say the honest limit plainly, because it matters more than a sales pitch: a DRM-protected AZW or KFX file purchased through Amazon is still locked to that ecosystem. Margina doesn't open it, and it never will. That's not a missing feature — it's what DRM is designed to prevent, by any reading app. If you want a file you can genuinely open anywhere, the format that gets you there is EPUB or plain, unprotected MOBI, not the encrypted version. Margina is on the App Store and Google Play.

Frequently Asked Questions

What's the difference between MOBI and AZW?

MOBI is the original Mobipocket format Amazon acquired in 2005. AZW is Amazon's own variant of it, built for the first Kindle in 2007, with a different serial-number scheme and Amazon's DRM layered on top. Close cousins, not separate inventions.

Can I open a Kindle AZW file on a Kobo or in Apple Books?

Not natively. Kobo, Nook, and Apple Books are built around EPUB and PDF, and none of them support Amazon's proprietary formats — so an AZW or KFX file simply won't open there without an intermediate tool.

Why does Amazon use a closed format instead of EPUB?

Because EPUB is an open standard anyone can implement, which makes it easy to move a book between devices. Amazon's formats are proprietary and DRM-wrapped by design, keeping purchased books tied to Kindle apps and devices tied to an Amazon account.

Does Margina open MOBI or AZW files?

Margina opens unprotected MOBI files along with PDF, EPUB, Word, and plain text. A DRM-locked AZW or KFX file is still locked to Amazon's ecosystem — no reading app, Margina included, can open a file that's encrypted against your Kindle account.

Conclusion

The walled-off feeling a Kindle file gives you on a non-Kindle device isn't one problem. It's two, stacked together: a closed format, and DRM layered on top of it. Once you can name which one you're running into, "why won't this open" stops being a mystery and starts being a question with a plain answer.