How do I convert AZW3 to EPUB without losing reflowable text?
+
Upload your AZW3 file and the converter rebuilds the EPUB container around the same reflowable text stream — paragraphs, line wraps, and chapter breaks all adapt to the reader's font size and screen width. We do not flatten reflowable AZW3 into fixed pages.
Will my EPUB keep the table of contents from the AZW3?
+
Yes — the NCX / nav.xhtml / inline TOC in the AZW3 is parsed and re-emitted in the EPUB container's native TOC format. Nested chapters / sub-chapters survive the round-trip and remain clickable on every reader that supports EPUB.
Does the AZW3 to EPUB converter handle DRM-protected files?
+
No — DRM-encrypted AZW3 files (Adobe ADEPT, Kindle KFX with personal device key) are encrypted at the bit level and cannot be processed. Strip DRM with the publisher's authorized tool first, then convert the unprotected AZW3 to EPUB here.
Will images and cover art survive AZW3 to EPUB conversion?
+
Yes — the cover image and every embedded illustration in the AZW3 is extracted and re-embedded in the EPUB container. We preserve original resolution and color profile; the cover is also indexed in the EPUB metadata so reader apps display it correctly in the library view.
Can I read the converted EPUB on my Kindle / Kobo / Nook?
+
Depends on the EPUB 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.
What about embedded fonts in the AZW3?
+
Embedded fonts in the AZW3 are unpacked and re-embedded into the EPUB where the format supports it (EPUB 3, AZW3 / KF8). MOBI 7 has limited font support and falls back to the reader's default. Font licensing in the AZW3 is your responsibility — we do not validate it.
Does the EPUB preserve AZW3 CSS styling (italics, bold, drop caps)?
+
Yes — inline CSS and stylesheet rules in the AZW3 are translated to the EPUB 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.
Will footnotes / endnotes in the AZW3 still work in the EPUB?
+
Yes — popup footnotes (epub:type="noteref") and traditional endnotes round-trip into the EPUB as cross-linked anchors. On Kindle / Kobo readers that support popups, footnotes still tap-to-reveal; on basic readers they fall back to numbered references.
Is my AZW3 file private during conversion?
+
Yes — uploaded AZW3 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/.
How long does AZW3 to EPUB conversion take for a full novel?
+
A 300-page reflowable AZW3 typically converts to EPUB in 5-15 seconds. Conversion is single-pass (parse → re-serialize) without re-rendering page layout, so book length scales linearly with text byte count, not page count.
Why does my EPUB look different from the AZW3 in the reader?
+
Reflowable ebooks are not pixel-perfect by design — each reader chooses its own font, margins, and line spacing. The EPUB contains the same content as the AZW3; visual differences come from the reader app, not the conversion. Use a fixed-layout target if pixel fidelity matters.
Can I batch convert a whole library of AZW3 files to EPUB?
+
Yes — drop dozens of AZW3 files in and we queue them in parallel. Premium users get more parallel workers, so a 50-book library typically finishes in 2-3 minutes. Each EPUB downloads individually or as a single zip.