Yes — the NCX / nav.xhtml / inline TOC in the EPUB is parsed and re-emitted in the AZW3 container's native TOC format. Nested chapters / sub-chapters survive the round-trip and remain clickable on every reader that supports AZW3.
Yes — the cover image and every embedded illustration in the EPUB is extracted and re-embedded in the AZW3 container. We preserve original resolution and color profile; the cover is also indexed in the AZW3 metadata so reader apps display it correctly in the library view.
Can I read the converted AZW3 on my Kindle / Kobo / Nook?
+
Depends on the AZW3 format. MOBI and AZW3 work on Kindle (Paperwhite, Oasis, Scribe). EPUB works on Kobo, Nook, Apple Books, and any reader except older Kindles. For Kindle compatibility specifically, target AZW3 (KF8) — it preserves layout better than legacy MOBI.
Does the AZW3 preserve EPUB CSS styling (italics, bold, drop caps)?
+
Yes — inline CSS and stylesheet rules in the EPUB are translated to the AZW3 stylesheet equivalent. Drop caps, small caps, italics, bold, and inline color all survive. Reader-side overrides (e.g. Kindle ignoring publisher fonts) are out of our control.
Yes — uploaded EPUB files are processed in isolated workers and deleted within minutes. We never read the manuscript content, store the file long-term, or share it. The full data-retention policy is at /privacy/.
