Skip to main content
All articles
Format conversion

MOBI/AZW3 → Markdown/DOCX

Converting a novel from MOBI/AZW3 to Markdown/DOCX: what each format is, what gets lost, the pitfalls for long fiction, and the right tools.

Tide Reader Editorial6 min read

What is MOBI/AZW3?

Mobipocket (.mobi) was long the default format Amazon accepted for Kindle delivery. AZW3 (also called KF8) is its successor with fuller HTML5/CSS support, and .azw is an earlier Amazon container. All three reflow and carry navigation and metadata, so they behave as one family. They are proprietary to Amazon's ecosystem, and since 2022 Amazon sends KFX/EPUB instead, so .mobi is mostly a legacy format now.

Extensions.mobi.azw3.azw
Typical useReading on Kindle devices and the Kindle app; one of the most common proprietary formats in existing libraries.

What is Markdown/DOCX?

Markdown (.md) and Word documents (.docx) are grouped here because they play the same role in conversion: lightweight structured authoring sources. Markdown is plain text plus markers (# headings, ** bold) — clean but limited. A .docx is a ZIP of Office Open XML with far richer layout (pagination, headers, footers, comments, tracked changes). Both are good conversion sources rather than final reading formats.

Extensions.md.docx
Typical useAuthoring and layout source files; an intermediate format before converting to EPUB or TXT.

What to watch out for when converting MOBI/AZW3 to Markdown/DOCX

Extracting from the source

.mobi/.azw3 are proprietary Amazon binary containers with no official parsing spec; third-party tools rely on reverse engineering and occasionally fail or drop metadata. AZW3 stores HTML internally, so extracting text is easier than preserving layout.

Writing the target format

Producing .docx suits further editing, but reading is not its goal: pagination shifts with Word versions and fonts, and phone rendering is fragile. If the destination is an e-reader, EPUB is the right endpoint.

Where the two formats interact

  • The source carries real navigation while the target has no concept of chapters, so reading becomes one long scroll. If navigation still matters, keep explicit, uniformly formatted chapter heading lines in the output.
  • The source is a proprietary binary container and the target is an archive with a mandated directory structure. This is not unpack-and-repack: a real parse and rebuild must happen in between, so use a mature tool — hand-rolling it almost always yields a file no reader accepts.

What gets lost

  • Both sides are structurally similar; only fine typographic detail is lost

What you gain

  • An editable, annotatable source document

Post-conversion checklist

  1. Convert the first three chapters as a trial and check for lost text, interleaved lines or misplaced blocks before doing the whole book.
  2. Jump to five random spots and search a character name to confirm the text is fully searchable.
  3. Confirm illustration count and placement — check that images are not all dumped at the end of a chapter.
  4. Fill in title, author and language — a wrong language tag breaks typesetting such as Chinese line breaking.

Converting novels: what is different

Fiction is the most common and the most peculiar kind of e-book: hundreds or thousands of chapters, almost no figures, often nothing but a TXT source, and Chinese sources that frequently carry anti-piracy garbling. These are the points that bite hardest.

  • A long novel can run to hundreds or thousands of chapters, so the table of contents decides whether the result is usable. Normalise chapter headings to one recognisable pattern first — say "Chapter N Title" alone on its own line — or the target will miss chapters, merge them, or collapse the whole book into one.
  • Volume markers ("Volume One", "Volume Two") usually degrade to ordinary headings, losing the volume/chapter hierarchy. If that matters, promote volume headings one level in an editor afterwards so they are not siblings of chapter titles.

Tools for converting MOBI/AZW3 to Markdown/DOCX

Any of the tools below can handle this direction; pick one by your operating system and how many files you have. Read the previous section first — doing the steps out of order (converting a scanned file before running OCR, for instance) usually means starting over.

Kindle Previewer

FreeDesktop app

Amazon's official tool: it converts EPUB/DOCX to AZW3 and previews the result exactly as a real Kindle would render it. It is the most reliable way to verify how a conversion actually looks on a Kindle, and avoids hand-building the proprietary container.

Platforms: Windows / macOSkdp.amazon.com/en_US/help/topic/G202131100 ↗

Pandoc

FreeCommand line

The Swiss army knife of document conversion, driven by a single command. Its Markdown, DOCX, HTML and EPUB conversions are the highest quality available and it is ideal for authoring-source-to-e-book pipelines. It does not handle MOBI/AZW3 or comic archives.

Platforms: Windows / macOS / Linux (command line)pandoc.org ↗

Calibre

FreeDesktop app

The de-facto standard for e-book conversion, free and open source. It converts EPUB, MOBI, AZW3, PDF, TXT, FB2, DOCX, HTML and nearly everything else, generating tables of contents, fetching metadata and batch-processing whole libraries. The interface is utilitarian, PDF output is mediocre, and the option set takes time to learn.

Platforms: Windows / macOS / Linuxcalibre-ebook.com ↗

Common questions

What is lost when converting MOBI/AZW3 to Markdown/DOCX?

Both sides are structurally similar; only fine typographic detail is lost.

Which tool should I use to convert MOBI/AZW3 to Markdown/DOCX?

Recommended: Kindle Previewer, Pandoc, Calibre. Kindle Previewer fits this pair best. Amazon's official tool: it converts EPUB/DOCX to AZW3 and previews the result exactly as a real Kindle would render it. It is the most reliable way to verify how a conversion actually looks on a Kindle, and avoids hand-building the proprietary container.

What should I watch out for when converting MOBI/AZW3 to Markdown/DOCX?

The source carries real navigation while the target has no concept of chapters, so reading becomes one long scroll. If navigation still matters, keep explicit, uniformly formatted chapter heading lines in the output. The source is a proprietary binary container and the target is an archive with a mandated directory structure. This is not unpack-and-repack: a real parse and rebuild must happen in between, so use a mature tool — hand-rolling it almost always yields a file no reader accepts.

Converted it — now what do you read it with?

Tide Reader opens TXT and EPUB, detects chapters on import, lays the text out the way you like it, and syncs your reading position across Windows, macOS, iOS and Android. Drop the converted file in and start reading.

Download Tide Reader

TXT and EPUB; local-first reading, with optional cloud sync and WebDAV.