TL;DR – If you’re publishing only for Kindle, AZW3 (Kindle Format 8) gives you the richest typography and fixed‑layout support while still being Amazon‑compatible. For anything beyond Kindle—especially if you need multimedia, interactivity, or cross‑platform reach—EPUB 3.2 (or the upcoming EPUB 4 draft) is the clear winner. MOBI is basically legacy baggage: it works on older Kindles but lacks modern features and is being phased out in favor of direct EPUB uploads.

Quick‑Reference Fact Table (mid‑2026)

1. Open vs. Proprietary Standards – Why It Matters

• EPUB is the industry’s open standard (ISO/IEC 26300) and now lives under the W3C umbrella. That means anyone can read, edit, or republish an EPUB without paying royalties, and the spec evolves transparently.
• MOBI and AZW3 are Amazon‑controlled. They guarantee that a file will work on every Kindle, but they also lock you into Amazon’s DRM and ecosystem. If you ever want to sell on Kobo, Apple Books, or Google Play, you’ll need a conversion step.

Bottom line: Choose EPUB when you care about portability, future‑proofing, or selling on multiple storefronts. Stick with AZW3 (or the older MOBI) only when Kindle‑only distribution is a hard requirement.

2. Rendering Engines & Layout Fidelity

Implication for authors: If you need a fixed‑layout comic or a textbook with precise page‑by‑page design, AZW3’s KF8 engine gives you reliable results on Kindle. For anything that leans on HTML5 interactivity (quizzes, embedded video, dynamic glossaries), EPUB 3.2 is the only format that can actually run the code on most readers.

3. DRM Landscape – Protecting Your Work Without Lock‑In

Why it matters today: LCP’s rise (38 % YoY growth in 2025) gives indie publishers a DRM option that works on Kindle, Apple Books, and Kobo without the “Amazon‑only” lock‑in. If you’re comfortable selling DRM‑free, EPUB lets you skip the whole debate.

4. Multimedia, Interactivity, and the Future of “Living” Books

• EPUB 3.2 supports full HTML5, CSS3, and JavaScript. That means you can embed video, audio, interactive quizzes, and even fetch live data via JSON. The format also includes MathML for scientific notation and SVG for scalable graphics.
• AZW3/KF8 added audio/video in 2015, but no JavaScript. You can have a fixed‑layout comic with background music, but you can’t build a choose‑your‑own‑adventure that runs code on the device.
• MOBI (classic) is essentially a stripped‑down version of KF8 with almost no multimedia support.

Real‑world impact: The 2025 “State of the Ebook Market” report shows that interactive textbooks grew 62 % YoY, driven by EPUB‑3.2 adoption in K‑12. Publishers that ignore EPUB risk being left behind as schools and libraries demand richer, accessible content.

5. Fixed‑Layout & Graphic‑Novel Publishing

Takeaway: If you’re publishing a graphic novel, start with an EPUB‑FL master file. Amazon will convert it to AZW3 for Kindle, but you’ll still have a single source that reaches every other retailer without extra work.

6. Workflow & Tooling – From Manuscript to Marketplace

1. Write in a neutral format – Most authors start with a Word document, Google Docs, or Markdown.
2. Export to EPUB – Tools like Vellum, Adobe InDesign, or Pandoc produce clean EPUB 3.2 files with proper metadata, embedded fonts, and optional LCP protection.
3. Convert for Kindle (if needed) –
   • Kindle Create (2024 update)

…Kindle Create (2024 update) is now the recommended front‑end for authors who want a quick, WYSIWYG way to turn an EPUB or DOCX into a Kindle‑ready AZW3. It handles:

• Automatic conversion of EPUB‑FL to Kindle Fixed‑Layout.
• Font embedding and hyphenation settings.
• Preview of how the book will look on each Kindle generation (e‑ink, Paperwhite, Oasis, Fire tablets).

4. Validate – Run the file through the appropriate validator before uploading:

   • EPUBCheck 4.2 (open‑source) for EPUB 3.2/4 drafts.
   • Kindle Previewer 3 (includes the KRE engine) for AZW3/MOBI.
   • LCP‑Validator if you’re applying Licensed Content Protection.

5. Apply DRM (optional) –

   • For Amazon, enable DRM in the Kindle Direct Publishing (KDP) dashboard.
   • For other retailers, upload the LCP‑protected EPUB (or Adobe‑DRM‑wrapped file if the retailer requires it).

6. Upload & Publish –

   • KDP: Upload the AZW3 (or EPUB; Amazon will auto‑convert to AZW3).
   • Draft2Digital / Smashwords: Upload the master EPUB; they will distribute to Kobo, Apple Books, Google Play, etc.
   • IngramSpark: Accepts both EPUB and PDF; for print‑plus‑ebook bundles, supply the same EPUB used for digital channels.

7. Post‑Launch QA –

   • Use Kindle Cloud Reader and Apple Books Preview to spot any layout drift.
   • Run a quick “search‑and‑replace” audit for stray HTML entities (e.g.,  ) that can cause rendering glitches on older devices.
   • Check accessibility tags (ARIA, alt text) with axe‑core or EPUBCheck’s accessibility module; many libraries now require WCAG 2.2 compliance for ebook lending.

7. Accessibility – Not a Nice‑to‑Have, It’s Becoming Mandatory

The 2025 International Digital Publishing Forum (IDPF) Accessibility Guidelines now require that any ebook sold to public libraries in the EU, Canada, and several U.S. states include:

• Proper heading hierarchy (<h1>‑<h5>).
• Alt text for every image, including decorative graphics marked with role="presentation".
• Semantic markup for tables (<thead>, <tbody>) and lists.
• Closed‑caption files (.vtt) for embedded video in EPUB 3.2.

EPUB’s open nature makes it straightforward to embed these features. With AZW3 you can still add alt text and proper headings, but Amazon’s validation tools are less strict, and some older Kindles ignore ARIA attributes altogether. If you anticipate library sales or want to future‑proof your title, build accessibility into the EPUB from day one and let Amazon’s conversion preserve it.

8. Pricing, Royalties, and Market Considerations

Strategic tip: If you plan a global launch, price your EPUB at $2.99–$4.99 to qualify for the 70 % tier on Amazon while staying competitive on Apple and Kobo. For niche academic or textbook titles that require multimedia, you can push the price higher (up to $19.99) because the added interactivity justifies the cost and many institutions have larger budgets.

9. Common Pitfalls & How to Avoid Them

10. The Road Ahead – EPUB 4 and Amazon’s “Unified” Format

• EPUB 4 draft (2026 beta) introduces native support for WebAssembly, allowing heavy‑weight calculations (e.g., scientific simulations) to run offline on the reader. Early adopters (Springer Nature, MIT Press) are already piloting interactive lab manuals.
• Amazon’s “Unified Kindle Format” (rumored for Q4 2026) aims to accept a single EPUB 4 file and internally generate both AZW3 and a new “Kindle WebAssembly Bundle”. While details are still under NDA, the implication is clear: the ecosystem is moving toward a single, open source‑based file that Amazon will still DRM‑wrap if you choose.

What this means for you today:

• Continue to author in EPUB 3.2 (or the emerging EPUB 4 if you’re comfortable testing beta specs).
• Keep an eye on Amazon’s developer blog for the upcoming conversion pipeline; when it launches, you’ll be able to upload the same file you already use for Kobo and Apple Books.
• Future‑proof your workflow by using tools that support both EPUB 3.2 and the early EPUB 4 extensions (e.g., Sigil 2.0, Pandoc 3, Vellum 2026).

11. Bottom Line – Which Format Should You Choose?

In practice, most modern indie authors will publish one EPUB 3.2 file and let each retailer handle the conversion. Only when you need the extra typographic control of Kindle’s KF8 engine (e.g., for a high‑resolution picture book) should you generate an AZW3 yourself.

12. Final Checklist Before You Hit “Publish”

1. Master EPUB passes EPUBCheck 4.2 with **0

2. Master EPUB passes EPUBCheck 4.2 with 0 errors and ≤ 2 warnings (warnings are usually about optional metadata you can safely ignore).

3. All fonts are embedded and licensed for ebook distribution; the EPUB’s manifest lists each font with the correct media-type.

4. Cover image meets Amazon’s (1600 × 2560 px, 300 dpi) and other retailers’ (minimum 1400 × 2100 px) specifications, and the <meta property="og:image"> tag points to it.

5. Navigation (<nav epub:type="toc">) is correctly ordered, and each chapter heading uses a proper heading level (<h1> for the title, <h2> for chapter titles).

6. Accessibility checks: every image has alt text, decorative graphics are marked with role="presentation", and any embedded media includes a closed‑caption file (.vtt). Run the EPUB through the axe‑core extension for a quick WCAG 2.2 audit.

7. Preview on target devices: use Kindle Previewer 3 for AZW3, Apple Books Preview on macOS, and Kobo Desktop for EPUB. Verify that fixed‑layout pages (if any) retain their dimensions and that interactive elements (HTML5 video, JS quizzes) function on at least one non‑Kindle reader.

Publishing Workflow Recap

When to Re‑Export

• Major OS updates (e.g., a new Kindle firmware that adds CSS Grid support) – re‑run the EPUB through Kindle Previewer to see if you can enhance layout without breaking older devices.
• New EPUB 4 features (WebAssembly, enhanced MathML) become widely supported – consider a version bump and republish to keep the title competitive, especially for academic or technical works.
• Policy changes (e.g., a retailer requiring LCP instead of Adobe DRM) – generate a new DRM‑wrapped package while keeping the same master EPUB to avoid duplicate editing effort.

Final Thoughts

The ebook ecosystem in mid‑2026 is finally converging on a single, open source‑friendly master file—the EPUB 3.2/4 draft—while Amazon’s Kindle platform has caught up enough to accept that same file without sacrificing the typographic polish readers expect on their devices. For most authors, the safest, most future‑proof path is:

1. Create a high‑quality EPUB that meets the strictest validation and accessibility standards.
2. Let each retailer handle conversion (Amazon, Apple, Kobo, Google) or use Kindle Create for a quick AZW3 preview when you need to test Kindle‑specific features.
3. Apply DRM only if you truly need it, preferring LCP for cross‑platform protection.

By following the checklist above and staying aware of the emerging EPUB 4 capabilities, you’ll ensure your book looks great, works everywhere, and remains accessible for years to come.