Convert ADOC to MOBI

Why Convert ADOC to MOBI?

Converting AsciiDoc files to MOBI format bridges the gap between professional documentation authoring and portable e-book reading on Amazon Kindle devices. AsciiDoc's powerful markup system excels at creating structured technical content, and MOBI conversion enables sharing that content with readers who use Kindle devices.

The MOBI format, while being superseded by Amazon's newer KF8/AZW3 format, remains highly relevant for compatibility with older Kindle devices such as the Kindle Keyboard, Kindle DX, and early-generation Kindle readers. Many readers still use these devices, making MOBI the safest choice for reaching the widest Kindle audience.

Amazon's "Send to Kindle" feature works excellently with MOBI files, enabling seamless delivery of personal documents to any Kindle device or app. Your documentation syncs reading progress across devices through Amazon's Whispersync technology.

This conversion is ideal for technical writers publishing manuals, tutorials, and documentation as e-books, self-publishing authors targeting Kindle readers, and anyone who wants to read AsciiDoc content on Kindle devices offline.

Key Benefits of Converting ADOC to MOBI:

• Universal Kindle: MOBI works on all Kindle devices including legacy models (Kindle 1-4, Keyboard, DX)
• Amazon Integration: Send to Kindle via email using Amazon's personal document service
• Offline Reading: Enjoy technical documentation on Kindle during travel without internet
• Professional E-Books: Transform manuals and tutorials into distributable e-books
• Preserved Structure: Maintain chapters, TOC, and formatting from AsciiDoc source
• Compact Files: MOBI compression produces smaller files for limited device storage
• Cross-Device Sync: Reading progress syncs across all Kindle devices via Whispersync

Practical Examples

Example 1: Technical Documentation Book

Input ADOC file (api-guide.adoc):

= API Reference Guide
:author: Development Team
:revdate: 2024-01-15
:toc: left

== Introduction

Welcome to the *API Reference Guide*. This document
provides comprehensive documentation for all endpoints.

=== Getting Started

Before using the API, ensure you have:

* Valid API credentials
* HTTPS client library
* JSON parser

NOTE: All API requests require Bearer token authentication.

Output MOBI file (api-guide.mobi):

Kindle E-Book displays:

API Reference Guide
By Development Team | January 15, 2024

[Interactive Table of Contents]

Chapter 1: Introduction

Welcome to the API Reference Guide. This document
provides comprehensive documentation for all endpoints.

1.1 Getting Started

Before using the API, ensure you have:
  • Valid API credentials
  • HTTPS client library
  • JSON parser

Note: All API requests require Bearer token authentication.

Example 2: Code Documentation with Syntax

Input ADOC file (auth-module.adoc):

== Authentication Module

The authentication system uses JWT tokens.

[source,python]
----
import jwt
from datetime import datetime, timedelta

def generate_token(user_id: str) -> str:
    payload = {
        'user_id': user_id,
        'exp': datetime.utcnow() + timedelta(hours=24)
    }
    return jwt.encode(payload, SECRET_KEY)
----

.Token Expiration Times
|===
|Token Type |Duration |Use Case

|Access Token |24 hours |API requests
|Refresh Token |7 days |Token renewal
|===

Output MOBI file (auth-module.mobi):

Authentication Module

The authentication system uses JWT tokens.

[Code - Python]
import jwt
from datetime import datetime, timedelta

def generate_token(user_id: str) -> str:
    payload = {
        'user_id': user_id,
        'exp': datetime.utcnow() + timedelta(hours=24)
    }
    return jwt.encode(payload, SECRET_KEY)

Token Expiration Times:
┌──────────────┬──────────┬─────────────┐
│ Token Type   │ Duration │ Use Case    │
├──────────────┼──────────┼─────────────┤
│ Access Token │ 24 hours │ API requests│
│ Refresh Token│ 7 days   │ Token renewal│
└──────────────┴──────────┴─────────────┘

Example 3: Installation Tutorial

Input ADOC file (install.adoc):

== Installation Guide

Follow these steps to install:

. Download from the official website
. Run the installer with admin privileges
+
[source,bash]
----
sudo ./install.sh --prefix=/usr/local
----
. Configure environment variables
. Verify the installation

WARNING: Back up your config before proceeding.

TIP: Use `--help` flag for additional options.

Output MOBI file (install.mobi):

Installation Guide

Follow these steps to install:

1. Download from the official website

2. Run the installer with admin privileges

   sudo ./install.sh --prefix=/usr/local

3. Configure environment variables

4. Verify the installation

⚠ WARNING: Back up your config before proceeding.

💡 TIP: Use --help flag for additional options.

Frequently Asked Questions (FAQ)

Q: Which Kindle devices support MOBI files?

A: MOBI files are supported by ALL Kindle devices, including older models like Kindle 1, 2, 3, Kindle Keyboard, Kindle DX, and all subsequent generations. This makes MOBI the most universally compatible format for the entire Kindle ecosystem.

Q: How can I send the converted MOBI file to my Kindle?

A: You can send MOBI files using Amazon's "Send to Kindle" service—email the file to your Kindle email address (found in Amazon account settings), use the Send to Kindle app/website, or transfer files directly via USB cable connection.

Q: Will my AsciiDoc code blocks be preserved in MOBI?

A: Yes! Code blocks are preserved as monospaced text blocks. However, syntax highlighting colors won't be visible on e-ink Kindle devices (they display in grayscale), though code structure and formatting remain fully intact.

Q: What happens to AsciiDoc tables in the MOBI conversion?

A: Tables are converted to a readable format optimized for e-reader screens. Due to screen size limitations, complex tables may be simplified. Simple tables with standard columns convert well and remain navigable on Kindle.

Q: Should I use MOBI or AZW3 for my Kindle?

A: For maximum compatibility with older Kindle devices, use MOBI. For newer Kindles (Paperwhite, Oasis, etc.), AZW3/KF8 offers better formatting. MOBI remains the safest choice when you need to support ALL Kindle generations.

Q: Are images from my AsciiDoc document included?

A: Yes! Images are embedded in the MOBI file and optimized for e-reader displays. For best results on e-ink screens, use high-contrast images as they display in grayscale on most Kindle devices.

Q: Will the table of contents work on Kindle?

A: Yes! The AsciiDoc document structure (titles, sections, subsections) is converted to a navigable NCX table of contents. Kindle users can access it through the "Go To" menu for easy chapter navigation.

Q: Can I convert multi-chapter AsciiDoc books?

A: Absolutely! AsciiDoc's chapter structure (level-1 headings) translates to MOBI chapters. Cross-references become internal links, and the table of contents reflects your complete book structure for seamless Kindle navigation.