Skip to main content
Conversion
Format conversion

MOBI/AZW3 → PDF

Converting a novel from MOBI/AZW3 to PDF: 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 PDF?

PDF is Adobe's fixed-layout document format. It records what to draw at which coordinate on a page rather than which paragraph a sentence belongs to. The layout is therefore identical everywhere, which suits contracts, papers and scans. The cost is that PDF is inherently hostile to reflow: line breaks are usually visual, extracted text often carries hard returns and scrambled column order, and scanned PDFs contain images only, with no text layer at all.

Extensions.pdf
Typical useDocuments, papers, contracts and scans where the layout must stay exact; also a print and archival format.

What to watch out for when converting MOBI/AZW3 to PDF

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 PDF freezes the content: once generated it cannot reflow, so readers cannot change font size or line width and long text is painful on small screens. For extended reading PDF is usually the wrong target — it suits printing, archiving and layout-critical delivery.

Where the two formats interact

  • Reflow is lost: the target freezes the layout, so readers can no longer change font size or line width. Long novels become zoom-and-pan on small screens — the most common reason a conversion ends up harder to read. Unless you need print or layout-critical delivery, keep a reflowable copy for reading.
  • 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.

What gets lost

  • Clickable table of contents and chapter navigation
  • Adjustable font size and screen-based reflow
  • Text reflow (a generated PDF is fixed for good)

What you gain

  • Identical layout everywhere, ideal for printing

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.
  5. Check margins and that the Chinese font is embedded, otherwise it renders as boxes on another machine.

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.

  • The target has no notion of a table of contents, and not being able to jump to a chapter is the worst part of reading something long. If you will keep reading it, keep a navigable copy as well (EPUB or Kindle) and treat this one as the distribution or archive copy.
  • Once a long novel is in a fixed layout, reading on a phone means zooming and panning. Fiction is the worst fit for fixed layout of any genre: almost no figures, all continuous text. Unless you are printing or submitting it, prefer a reflowable format for novels.
  • 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 PDF

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.

ocrmypdf / Tesseract

FreeCommand line

An open-source way to add a text layer (OCR) to scanned PDFs, with Chinese support. Scanned files must go through this before any text-extraction conversion, otherwise the output is blank. Expect to proofread the recognised characters.

Platforms: Windows / macOS / Linux (command line)ocrmypdf.readthedocs.io ↗

Stirling PDF

FreeOnline service

An open-source PDF toolbox that splits, merges, rotates, compresses and extracts text in the browser, and can be self-hosted so files never leave your network. Good for the PDF side; for reflowable output Calibre remains the better choice.

Platforms: Browser (self-hostable)stirlingpdf.io ↗

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 ↗

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 PDF?

Clickable table of contents and chapter navigation; Adjustable font size and screen-based reflow; Text reflow (a generated PDF is fixed for good).

Which tool should I use to convert MOBI/AZW3 to PDF?

Recommended: ocrmypdf / Tesseract, Stirling PDF, Kindle Previewer, Calibre. ocrmypdf / Tesseract fits this pair best. An open-source way to add a text layer (OCR) to scanned PDFs, with Chinese support. Scanned files must go through this before any text-extraction conversion, otherwise the output is blank. Expect to proofread the recognised characters.

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

Reflow is lost: the target freezes the layout, so readers can no longer change font size or line width. Long novels become zoom-and-pan on small screens — the most common reason a conversion ends up harder to read. Unless you need print or layout-critical delivery, keep a reflowable copy for reading. 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.

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.