Convert AsciiDoc to AZW3

Drag and drop files here or click to select.
Max file size 100mb.
Uploading progress:

AsciiDoc vs AZW3 Format Comparison

Aspect AsciiDoc (Source Format) AZW3 (Target Format)
Format Overview
AsciiDoc
AsciiDoc Markup Language

Lightweight markup language created by Stuart Rackham in 2002 for technical documentation. Uses plain-text syntax with = headings, *bold*, _italic_, source code blocks (----), admonitions (NOTE:, TIP:), cross-references, and include directives. Processed by Asciidoctor into multiple output formats.

Markup Language Technical Docs
AZW3
Amazon Kindle Format 8 (KF8)

Amazon's proprietary ebook format introduced with Kindle Fire in 2011. Based on HTML5 and CSS3 with DRM capabilities. Supports rich formatting, embedded fonts, SVG graphics, and advanced layout features. The primary format for Kindle devices and apps, offering superior rendering compared to older MOBI.

Kindle Format Amazon Ecosystem
Technical Specifications
Structure: Plain text with markup directives
Encoding: UTF-8
Format: Human-readable markup
Compression: None
Extensions: .adoc, .asciidoc, .asc
Structure: HTML5/CSS3-based binary container
Encoding: Binary with embedded resources
Format: Proprietary Amazon KF8
Compression: PalmDOC compression
Extensions: .azw3
Syntax Examples

AsciiDoc markup syntax:

= Book Title
Author Name
:doctype: book

== Chapter One

This has *bold* and _italic_.

NOTE: Important information.

[source,java]
----
System.out.println("Hello");
----

AZW3 renders as formatted ebook:

[Kindle-formatted ebook]
- Styled chapter headings
- Bold and italic text rendered
- Note blocks with styling
- Syntax-highlighted code
- Table of contents navigation
- Page-turn animations
- Adjustable font sizes
Content Support
  • Section headings (= through =====)
  • Bold, italic, monospace formatting
  • Source code blocks with highlighting
  • Admonitions (NOTE, TIP, WARNING)
  • Tables with complex layouts
  • Cross-references and anchors
  • Include directives
  • Images, links, footnotes
  • HTML5-based rich formatting
  • Embedded fonts (custom typography)
  • SVG graphics support
  • CSS3 styling and layout
  • Table of contents with navigation
  • Embedded images
  • Text-to-speech (limited)
  • DRM protection support
  • Adjustable font sizes
Advantages
  • Human-readable plain text
  • Version control friendly
  • Single source for multiple outputs
  • Powerful include and modular system
  • Excellent for technical content
  • Free and open source tooling
  • Optimized for Kindle devices
  • Advanced HTML5/CSS3 rendering
  • Embedded font support
  • Smaller file sizes than MOBI
  • Better typography than MOBI
  • Page-turn animations
  • Kindle ecosystem integration
Disadvantages
  • Not a final presentation format
  • Requires processing to view formatted output
  • Learning curve for advanced features
  • Not directly readable on e-readers
  • Amazon proprietary format
  • Limited to Kindle ecosystem
  • Not supported by other e-readers
  • DRM restrictions possible
  • Cannot be edited directly
  • Not human-readable
Common Uses
  • Technical documentation and manuals
  • Software API references
  • Book manuscripts (O'Reilly, etc.)
  • Project documentation (README, guides)
  • Knowledge base articles
  • Kindle ebook distribution
  • Amazon KDP publishing
  • Personal Kindle library
  • Technical books for Kindle
  • Offline reading on Kindle devices
  • Self-published ebooks
Best For
  • Writing and maintaining documentation
  • Multi-format publishing workflows
  • Collaborative technical writing
  • Version-controlled content
  • Kindle device reading
  • Amazon marketplace distribution
  • Self-publishing on KDP
  • Offline ebook reading
Version History
Introduced: 2002 (Stuart Rackham)
Modern Processor: Asciidoctor (2013)
Status: Active, widely adopted
Evolution: Asciidoctor 2.x (current)
Introduced: 2011 (Amazon, with Kindle Fire)
Based On: KF8 (Kindle Format 8)
Status: Active, primary Kindle format
Evolution: Replaced MOBI as Kindle standard
Software Support
Asciidoctor: Full support (Ruby/JVM/JS)
GitHub: Native rendering
VS Code: AsciiDoc extension
Other: IntelliJ, Atom, Sublime Text
Kindle: All Kindle devices and apps
Calibre: Read and convert
KindleGen: Amazon creation tool
Other: Kindle Previewer, Kindle for PC/Mac

Why Convert AsciiDoc to AZW3?

Converting AsciiDoc to AZW3 enables you to publish your technical documentation, books, and articles directly to the Amazon Kindle ecosystem. AsciiDoc's rich markup capabilities -- including structured headings, code blocks with syntax highlighting, admonitions, tables, and cross-references -- translate beautifully into the AZW3 format's HTML5/CSS3 rendering engine, creating professional ebooks for Kindle devices and apps.

AZW3 (Kindle Format 8 / KF8) is Amazon's modern ebook format, introduced in 2011 to replace the older MOBI format. Built on HTML5 and CSS3, AZW3 supports embedded fonts, SVG graphics, advanced layout features, and rich typography. This makes it an excellent target format for AsciiDoc content, which often contains complex technical elements like code listings, tables, and admonition blocks that benefit from AZW3's superior rendering capabilities.

The AsciiDoc-to-AZW3 workflow is particularly popular among technical authors and self-publishers. Organizations like O'Reilly Media have long used AsciiDoc as their source format for producing books across multiple formats, including Kindle editions. By converting AsciiDoc to AZW3, you can maintain a single source of truth for your documentation while distributing polished ebooks through Amazon's Kindle Direct Publishing (KDP) platform.

The conversion process transforms AsciiDoc's plain-text markup into a fully formatted ebook with a navigable table of contents, styled chapters, formatted code blocks, and proper typography. Images are embedded, cross-references become clickable links, and admonitions are styled as highlighted callout boxes. The result is a professional ebook ready for reading on any Kindle device or the Kindle app on phones, tablets, and computers.

Key Benefits of Converting AsciiDoc to AZW3:

  • Kindle Publishing: Publish directly to Amazon KDP marketplace
  • Superior Rendering: HTML5/CSS3-based formatting for rich content
  • Code Block Support: Syntax-highlighted code renders cleanly on Kindle
  • Embedded Fonts: Custom typography for professional appearance
  • Navigation: Automatic table of contents from AsciiDoc headings
  • Offline Reading: Read technical docs offline on Kindle devices
  • Single Source: Maintain one AsciiDoc source for multiple output formats

Practical Examples

Example 1: Technical Book for Kindle

Input AsciiDoc file (programming-guide.adoc):

= Java Programming Guide
John Developer
:doctype: book
:toc:
:icons: font

== Getting Started

Install Java from https://openjdk.org[OpenJDK].

[source,java]
----
public class Hello {
    public static void main(String[] args) {
        System.out.println("Hello, World!");
    }
}
----

TIP: Use an IDE like IntelliJ for better productivity.

Output AZW3 file (programming-guide.azw3):

Kindle-ready ebook:
- Professional book layout with title page
- Navigable table of contents
- Styled chapter headings
- Syntax-highlighted Java code blocks
- Clickable hyperlinks
- Formatted tip callout box
- Adjustable text size on Kindle
- Ready for KDP upload

Example 2: API Documentation for Offline Reading

Input AsciiDoc file (api-docs.adoc):

= REST API Reference
:toc: left

== Authentication

All requests require a Bearer token.

|===
| Endpoint | Method | Description
| /api/users | GET | List all users
| /api/users/{id} | GET | Get user by ID
| /api/users | POST | Create new user
|===

WARNING: Never expose API keys in client-side code.

Output AZW3 file (api-docs.azw3):

Kindle-formatted API reference:
- Structured table of contents
- Formatted API endpoint tables
- Warning callouts styled prominently
- Easy navigation between sections
- Readable on Kindle Paperwhite
- Perfect for offline reference
- Search within document supported

Example 3: Self-Published Tutorial Series

Input AsciiDoc file (docker-tutorial.adoc):

= Docker from Zero to Hero
:author: DevOps Expert
:revdate: 2025-06-01

== What is Docker?

Docker is a platform for containerization.

.Docker Architecture
image::docker-arch.png[Docker Architecture]

[source,dockerfile]
----
FROM openjdk:17-slim
COPY app.jar /app.jar
CMD ["java", "-jar", "/app.jar"]
----

NOTE: Docker requires Linux kernel 3.10+.

Output AZW3 file (docker-tutorial.azw3):

Professional ebook for Kindle:
- Cover page with title and author
- Embedded Docker architecture image
- Dockerfile syntax highlighting
- Note blocks with distinctive styling
- Chapter navigation via TOC
- Ready for Amazon KDP submission
- Compatible with all Kindle devices

Frequently Asked Questions (FAQ)

Q: What is AZW3 format?

A: AZW3, also known as Kindle Format 8 (KF8), is Amazon's modern ebook format introduced in 2011. It is based on HTML5 and CSS3, supporting rich formatting, embedded fonts, SVG graphics, and advanced layouts. AZW3 replaced the older MOBI format as the primary Kindle ebook format.

Q: Can I publish AsciiDoc content on Amazon KDP?

A: Yes! By converting your AsciiDoc files to AZW3 (or EPUB, which KDP also accepts), you can publish directly on Amazon's Kindle Direct Publishing platform. Many technical authors use AsciiDoc as their source format and produce Kindle editions for distribution on Amazon.

Q: Are code blocks preserved in the AZW3 output?

A: Yes, AsciiDoc source code blocks are converted to formatted, monospaced text in the AZW3 output. Syntax highlighting may be preserved depending on the conversion tool used. The code blocks remain readable on Kindle devices, though very long lines may wrap on smaller screens.

Q: How are AsciiDoc admonitions rendered in AZW3?

A: Admonitions (NOTE, TIP, WARNING, CAUTION, IMPORTANT) are converted to styled callout boxes in the AZW3 output. They appear as visually distinct blocks with appropriate icons or labels, making them easy to spot while reading on a Kindle device.

Q: What happens to AsciiDoc tables in AZW3?

A: AsciiDoc tables are converted to HTML tables in the AZW3 output. Simple tables render well on Kindle. However, very wide tables may not display optimally on smaller Kindle screens (like Paperwhite). Consider simplifying complex tables for ebook output.

Q: Can I read AZW3 files on non-Kindle devices?

A: AZW3 files are primarily designed for the Kindle ecosystem. You can read them using Kindle apps on iOS, Android, Windows, and Mac. For non-Amazon e-readers like Kobo or Nook, consider converting to EPUB instead. Calibre can also open AZW3 files on desktop computers.

Q: Is the AsciiDoc table of contents preserved?

A: Yes, the AsciiDoc document structure (= headings at various levels) is converted into a navigable table of contents in the AZW3 ebook. Kindle devices use this TOC for chapter navigation, allowing readers to jump between sections easily.

Q: What is the difference between AZW3 and MOBI?

A: AZW3 (KF8) is the newer, more capable format based on HTML5/CSS3, while MOBI is the older format with limited formatting support. AZW3 supports embedded fonts, SVG, CSS3 styling, and better typography. Amazon recommends AZW3 for all new content, and most modern Kindle devices prioritize AZW3 rendering.