EPUB vs MOBI vs AZW3: eBook Formats Explained
Why eBook Formats Still Cause Headaches in 2026
Buy a novel on Kobo, then try to read it on your Kindle Paperwhite. Download a free public-domain book from Project Gutenberg, then wonder why the fonts look broken on your phone. These are not edge cases — they are the everyday friction caused by three competing eBook formats that have never fully agreed on a common standard. EPUB, MOBI, and AZW3 each emerged from different corporate and community priorities, and understanding their differences is genuinely useful before you convert, buy, or distribute any eBook. This article breaks down what each format actually is under the hood, where each one performs best, and what you lose or gain when you move between them. There are no magic solutions here — some conversions are lossless, others degrade the reading experience in measurable ways, and a few are blocked entirely by DRM. Knowing the difference will save you time and prevent the frustration of a 400-page book that renders as a wall of unstyled text.
EPUB: The Open Standard That Most Devices Support
EPUB (Electronic Publication) is maintained by the W3C through its predecessor organization, the IDPF, and the current version — EPUB 3.3, finalized in 2023 — is built on the same trio of technologies that powers the web: HTML5, CSS3, and JavaScript. Structurally, an EPUB file is a ZIP archive. Rename any .epub file to .zip, open it, and you will find an OPF package file describing the metadata, an NCX or nav document for navigation, and a series of XHTML content documents for each chapter. This transparency is one of EPUB's core strengths. Calibre, Apple Books, Kobo devices, Google Play Books, Adobe Digital Editions, and virtually every non-Amazon reading ecosystem accepts EPUB natively. EPUB 3 supports fixed-layout books — meaning precise page positioning for children's books or cookbooks — as well as audio, video, MathML for scientific notation, and right-to-left scripts for Arabic and Hebrew. A reflowable EPUB novel will typically weigh between 200 KB and 2 MB depending on embedded fonts and cover art. One honest limitation: EPUB rendering is inconsistent across apps. A CSS rule like 'page-break-before: always' works correctly in Apple Books but is sometimes ignored in older Kobo firmware. If you are publishing professionally, you need to test on at least three readers. Amazon Kindle devices do not natively support EPUB — that gap is what gave MOBI and AZW3 their entire reason to exist.
MOBI: Amazon's Legacy Format and Why It Still Circulates
MOBI originated with the Mobipocket reader, a French company Amazon acquired in 2005. Amazon used MOBI as the foundation for its early Kindle ecosystem, and for nearly a decade it was the format you needed if you wanted to sideload books onto a Kindle device. Technically, MOBI is based on the older PalmDOC format with Mobipocket extensions layered on top. It supports basic HTML formatting, inline images, tables, and a limited subset of CSS. What it does not support well includes complex multi-column layouts, embedded fonts (early MOBI versions strip them), and anything requiring JavaScript. The maximum image resolution in standard MOBI is 500×600 pixels — a constraint that makes illustrated books look noticeably soft on a modern Kindle Paperwhite's 300 PPI display. Amazon officially deprecated MOBI for personal document delivery in 2022. If you email a .mobi file to your Kindle's send-to address today, Amazon's servers will convert it server-side rather than deliver it as-is. Despite this, MOBI files remain common. Many independent authors who published between 2010 and 2018 distributed MOBI files directly, and those files still circulate on personal devices and in library archives. Older Kindle models — the Kindle 3 (Keyboard), for instance — read MOBI reliably but cannot handle AZW3 at all. So if your audience includes people on older hardware, MOBI is not entirely irrelevant. For anything new, though, there is no good reason to create a MOBI file from scratch.
AZW3: Amazon's KF8 Format and What It Actually Does Better
AZW3 is Amazon's internal name for the KF8 (Kindle Format 8) container, introduced in 2011 alongside the Kindle Fire tablet. The file extension .azw3 and the container format KF8 are used interchangeably. AZW3 is a significant technical improvement over MOBI: it supports HTML5 and CSS3 properly, allows embedded fonts (including custom typefaces), handles complex tables, supports SVG vector graphics, and allows media queries for responsive layout adjustments. A KF8 file can even contain both a KF8 version and a legacy MOBI7 version inside the same container — Kindle calls this a 'Print Replica' or 'combo file' — so that older devices fall back gracefully. When Amazon's KDP (Kindle Direct Publishing) generates a file for distribution, it produces AZW3. The .azw extension you see on books purchased directly from Amazon is essentially AZW3 with DRM applied via Amazon's proprietary Topaz or KFX layer. AZW3 without DRM is technically convertible; AZW3 with Amazon DRM is not, at least not through any legal tool. CocoConvert can convert DRM-free AZW3 files to EPUB or other formats, but if you purchased a Kindle book through the Amazon store, that file carries DRM and cannot be converted here or anywhere else through legitimate means. This is not a limitation of our converter — it is a legal and technical boundary that applies universally. The practical ceiling for AZW3 is that it only works within Amazon's ecosystem. No Kobo, no Apple Books, no Google Play Books reader opens AZW3 natively.
Conversion Quality: What Survives and What Gets Lost
Converting between these formats is not like converting a PNG to JPEG, where quality loss is predictable and uniform. eBook conversion involves re-interpreting semantic markup, and the results depend heavily on how well the source file was constructed. EPUB to AZW3 is generally the cleanest conversion path. Tools like Calibre (free, open-source) and Amazon's own KindleGen (now integrated into the Kindle Previewer 3 application, downloadable from Amazon's KDP portal under Tools > Kindle Previewer) handle this conversion well. Embedded fonts survive. Complex CSS mostly survives, though CSS Grid and Flexbox layouts may be simplified. Tables with merged cells sometimes flatten incorrectly. EPUB to MOBI is lossier. Embedded fonts are stripped. Images are downscaled to fit MOBI's 500×600 pixel ceiling. Footnotes that use EPUB3's aside element may convert to inline parenthetical text, which disrupts academic or heavily annotated books. AZW3 to EPUB works reasonably well for clean files. Calibre's conversion engine (Edit > Convert Books > AZW3 to EPUB in the Calibre desktop app) preserves chapter structure and most formatting. The main casualty is Amazon-specific metadata — reading position sync data, X-Ray character definitions, and Whispersync markers — none of which have EPUB equivalents. MOBI to EPUB is the most unpredictable path. Because MOBI files often contain stripped-down HTML with inline styles rather than clean semantic markup, the resulting EPUB may need manual cleanup. A 300-page MOBI novel might convert cleanly; a MOBI textbook with tables and images might require hours of post-conversion editing. CocoConvert handles EPUB ↔ AZW3 and EPUB ↔ MOBI conversions. For MOBI to AZW3 directly, we recommend converting to EPUB as an intermediate step rather than going MOBI → AZW3 in one pass, because intermediate EPUB allows you to inspect and fix the markup before locking it into Amazon's format.
Which Format Should You Actually Use?
The answer depends on your role and your destination. If you are a reader who wants maximum device compatibility, EPUB is the correct format to keep in your personal library. Store your books as EPUB, convert to AZW3 only when you need to sideload onto a Kindle, and discard the converted copy when you are done. If you are an independent author self-publishing through Amazon KDP, you submit an EPUB file to KDP and Amazon generates AZW3 for you automatically. You do not need to produce AZW3 yourself. If you are distributing outside Amazon — through Draft2Digital, Smashwords, Ingram Spark, or directly to readers — EPUB is the universal deliverable. If you are building a private reading library from older files you legally own, you may encounter MOBI files that were purchased or downloaded before 2015. Convert those to EPUB using Calibre or CocoConvert and store the EPUB version. The MOBI file can be archived as a backup but EPUB will serve you better going forward. If you are a publisher producing fixed-layout books (illustrated children's books, cookbooks, art books), EPUB3 fixed-layout is the right choice for non-Amazon distribution. For Amazon, fixed-layout KF8 (AZW3) is required. These are genuinely different production workflows and the same source file cannot reliably produce both without specific tooling like InDesign's EPUB export with fixed-layout settings enabled. One scenario where none of these formats is the right answer: academic and institutional distribution. PDF remains the standard there because of its precise pagination, citation stability, and universal rendering. eBook formats are not a replacement for PDF in academic contexts — they are a different tool for a different purpose.
Using CocoConvert for eBook Format Conversion
CocoConvert supports conversions between EPUB, MOBI, and AZW3 for files that are not DRM-protected. Upload your file on the conversion page, select your target format, and the converter will process the file and return a download link within seconds for files under 50 MB. For larger files — some illustrated EPUB3 books with embedded fonts and high-resolution images can exceed 100 MB — processing time increases proportionally, and files above 200 MB are not currently supported. This is a real limitation for heavily illustrated fixed-layout books. For those, Calibre running locally on your own machine is a better option because it has no file size ceiling and gives you access to detailed conversion settings, including image compression thresholds, font embedding toggles, and chapter detection rules. Where CocoConvert adds value is convenience and accessibility: no software installation, no command-line knowledge required, and the conversion runs on our servers rather than your device. If you are on a Chromebook, a tablet, or a machine where you cannot install desktop software, browser-based conversion is genuinely useful. After conversion, always open the resulting file in a reader application before considering the job done. For EPUB output, Adobe Digital Editions (free, Windows and Mac) is a reliable validator. For AZW3 output, the Kindle Previewer 3 application shows you exactly how the file will render on Kindle hardware, including the Paperwhite, the Oasis, and the Fire tablet, selectable from a dropdown in the preview interface. Skipping this verification step is the most common reason people end up with a converted file that looks wrong on their device.