AZW3 is the Kindle Format 8 used by Amazon devices, adding proper CSS layout over the older AZW format.
Common Uses
Kindle eBooks
Amazon reading
Enhanced eBooks
AZW3 Conversion FAQ
What is an AZW3 file?
+
AZW3 (Kindle Format 8) is Amazon's advanced eBook format with enhanced formatting support.
Can I read an AZW3 book on something that is not a Kindle?
+
Only after converting it, in general. AZW3 is Amazon's own format and support outside its apps and devices is patchy, so moving a book to a Kobo, an Apple device or a general-purpose reader means converting first. Store purchases are the exception that stops the whole process: if the file carries Amazon's DRM, no converter can open it, here or anywhere else. AZW3 is Amazon-only, and DRM-protected purchases cannot be converted by any tool.
Why do purchases arrive as AZW3?
+
Because the format is the store's own delivery wrapper, tied to its apps and, for paid content, to your account. That is what makes it convenient inside that ecosystem and awkward outside it. Files that are not account-locked convert normally; protected ones cannot be opened by any converter, which is a deliberate property of the format rather than a limitation here. AZW3 is Kindle Format 8, which Amazon introduced in 2011 to replace the ageing MOBI format.
Why does my purchased AZW3 refuse to convert?
+
Because it is encrypted. A store-bought AZW3 is locked to an account, and the file a converter sees is ciphertext rather than a book — there is nothing to read until the store's software decrypts it for its own reader. Removing that protection is a legal grey area in many countries and is not something this site does. Files you made yourself, or downloaded DRM-free, convert normally.
Does the table of contents survive converting an AZW3?
+
Yes, wherever the target has somewhere to put it. Ebook formats store navigation as real structure — a list of chapter anchors that the reader turns into a jump menu — and that is carried between them. A fixed-layout export turns it into bookmarks instead, and a plain-text export loses it along with everything else structural. Chapter breaks themselves survive all three.
What if my AZW3 is a scan rather than real text?
+
Then nothing downstream can read it until OCR has run. A scanned page is a picture of words: it looks fine, and searching, copying or converting to an editable document all come back empty. Optical character recognition adds a real text layer over the image, after which the words are selectable and the conversion produces an actual document instead of a wrapper around a photograph.
Is the cover image kept when I convert an AZW3?
+
It is, provided the book records one as the cover rather than merely having a picture on its first page. That distinction is why a converted book sometimes shows a blank placeholder in a library: the image is still inside the file, but nothing marks it as the cover, so the reader app displays nothing. It is metadata rather than content, and it can be set afterwards without touching the text.
Does an AZW3 have fixed pages?
+
No — content flows, and pages appear only when something decides on a page size. Change the font, the margins or the screen and the page numbering changes with it. That is why a page reference from an AZW3 is unreliable, and why converting to a fixed-layout format is the step that makes page numbers mean something.
Is an AZW3 really a ZIP archive underneath?
+
It is, and renaming a copy and opening it with any archive tool proves it: inside are the structured parts the format is built from, plus the images and fonts they reference. That design is why these files compress well, why a damaged one can sometimes be partly recovered, and why software that is not the original application can read them at all. It is not an invitation to edit the parts by hand — the manifest has to stay consistent. AZW3 is built on EPUB 3 internals — HTML5 and CSS3 — wrapped in Amazon’s container with optional DRM.
Is AZW3 too new to be widely supported?
+
Support here is a software question rather than a hardware one, which makes it a far smaller problem: there is no decoder chip to wait for, only a reader or an editor that has to be updated. What remains is older applications, and anything that stopped being maintained before the format existed. Converting out of it is a compatibility step rather than a rescue. AZW3 supports embedded fonts, drop caps, fixed-layout pages and proper CSS, so illustrated and technical books survive it.
Is AZW3 usable outside Amazon's ecosystem?
+
Partly. The format itself is documented well enough that several readers and conversion tools handle it, so a DRM-free file moves around fine. Anything bought from the store is a different matter — it is encrypted against your account and cannot be opened by any third-party tool, which is the design working as intended rather than a fault.
Can I convert a whole folder of AZW3 files in one go?
+
With an account, yes — drop them in together and they are queued as one job rather than handled one at a time, with the same settings applied across the batch and the results returned together. Free conversions run a single file at a time (merge tools take two); a paid plan is what unlocks batch processing and the larger per-file limit, which is what makes converting a whole archive practical.
