AZW to MOBI - Repackage Older Amazon Books for Any Kindle

AZW is Amazon's original Kindle format, introduced with the first Kindle in 2007. Under the surface it is a close cousin of MOBI: Amazon licensed the Mobipocket engine and wrapped it with its own DRM layer, producing the .azw files the earliest Kindle Store sold.

A few years later Amazon moved on to AZW3 (Kindle Format 8), a much richer format based on a modern HTML/CSS subset. AZW and AZW3 are not the same thing — AZW is the older, simpler one, closer to plain MOBI.

The practical upshot: if you have an old .azw that is DRM-free, converting it to MOBI is often close to a repackaging exercise, because the two formats share the same underlying structure.

If you are converting many files at once or prefer working from a terminal, Calibre's ebook-convert command does the same AZW → MOBI transformation that this web tool performs — just without the browser round-trip.

Install Calibre (free, cross-platform) first, then run:

ebook-convert input.azw output.mobi

That single line handles the full pipeline: it unpacks the legacy AZW container, rebuilds the content, and packages it as a plain MOBI file that older Kindles and a wide range of readers can open. For batch jobs, wrap it in a loop:

for f in *.azw; do ebook-convert "$f" "${f%.azw}.mobi"; done

Key Calibre flags you may find useful: --enable-heuristics repairs minor formatting issues automatically, and --extra-css lets you inject custom styles. Older AZW files were sometimes bound to a device PID; strip that first with the appropriate tool so Calibre can read the book.

The web converter above is better for one-off conversions where you do not want to install software. Calibre is the right choice when you have dozens of files, need consistent batch settings, or want to automate the conversion as part of a larger ebook workflow.

MOBI is the foundational Kindle format. Every Kindle ever made reads it, from the 2007 original to the latest Paperwhite. It is simple, predictable, and maximally compatible.

That compatibility is exactly why you might want it. If a file needs to open on an unknown or older Kindle, MOBI is the format least likely to fail. The cost is presentation: MOBI drops embedded fonts and most CSS, keeping the text clean and readable rather than styled.

People often treat "AZW" and "AZW3" as the same label, but they are different enough to matter here.

AZW is the 2007-era format, essentially MOBI with Amazon's DRM. Converting DRM-free AZW to MOBI is straightforward.

AZW3 is the 2011-era format (KF8) with embedded fonts, real CSS, and fixed-layout support. It is a richer file and converts to MOBI by shedding those extras.

If your file is .azw3, use the AZW3 to MOBI converter instead — this page is specifically for the older .azw files. Mixing them up just sends you to the wrong tool.

1. Upload your AZW file. Drag it in or browse. Free accounts accept files up to 4MB, which covers virtually all AZW books.

2. Conversion runs. The AZW container is read, its content is simplified to MOBI-compatible HTML and CSS, and the chapter structure is rebuilt. Most files convert in well under a minute.

3. Download and sideload. Connect your Kindle by USB and copy the .mobi into the documents folder. It shows up on the home screen.

DRM blocks this entirely. Books downloaded from the Kindle Store carry Amazon's DRM and cannot be read by any converter. This works only on DRM-free AZW files you exported yourself, or titles from DRM-free sources.

You have an old DRM-free AZW. Maybe a personal export, a developer sample, or a book from a store that sold DRM-free AZW. Turning it into MOBI makes it open on any Kindle.

You want maximum compatibility. MOBI is the one format every Kindle reads. If you are handing a file to an older device or an unknown reader, MOBI removes the guesswork.

You are consolidating formats. Keeping one universal format for your personal library is easier to back up than a mix of legacy containers.

If your file came directly from the Kindle Store, it is DRM-protected and will not convert — no tool can decrypt it. In that case the only path is to download it through Amazon's own apps, which deliver a readable copy tied to your account.

Because AZW and MOBI share roots, the conversion is gentle.

Preserved:

• All the text — nothing is truncated
• Chapter breaks — structure holds
• Basic emphasis — bold and italic
• Metadata — title and author

• Embedded fonts — the device uses its built-in typefaces
• Advanced CSS — custom margins and colored text flatten
• Fixed layouts — reflow into standard text

AZW and MOBI are close enough that a repackage is usually invisible — which is exactly why you should check.

• The file opens on your Kindle — sideload it and confirm the library shows the cover, not a blank tile.
• Internal links still jump — AZW files from Amazon sometimes carry store-injected navigation; check that a TOC entry lands on the right chapter.
• Fonts did not collapse — older AZW files rely on the reader's own fonts, so text reflows differently than on the device it came from.
• Annotations are not expected back — highlights and notes live in Amazon's cloud, not inside the file. Treat the MOBI as a read-only copy.
• The original AZW is untouched — keep it. This conversion is a fallback for older hardware, not an upgrade.

A clean source file is half the battle. Before you upload, take one minute to verify three things.

• The file is really AZW — a wrong extension or a corrupted download is the most common cause of a failed conversion.
• It is DRM-free — files locked by a store or rights system cannot be read by any converter; you need the original unlocked copy.
• It is under the size limit — free accounts accept files up to 4MB, which covers most books; very large or image-heavy files may need a desktop tool.

Most conversions are clean, but a few patterns show up often enough to recognize in advance.

• Pages out of order — usually a source file with a broken reading-order manifest; re-export from the original.
• Blank pages — often a scanned image the converter could not decode; check the source.
• Garbled text — a character-encoding mismatch in the original; the content is there but needs a re-save as UTF-8.
• Missing images — media the source stored outside the main container; not every file bundles everything.