How do I convert EPUB to AZW3 without losing reflowable text?
+
Upload your EPUB file and the converter rebuilds the AZW3 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 EPUB into fixed pages.
Will my AZW3 keep the table of contents from the EPUB?
+
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.
Does the EPUB to AZW3 converter handle DRM-protected files?
+
No — DRM-encrypted EPUB 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 EPUB to AZW3 here.
Will images and cover art survive EPUB to AZW3 conversion?
+
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.
What about embedded fonts in the EPUB?
+
Embedded fonts in the EPUB are unpacked and re-embedded into the AZW3 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 EPUB is your responsibility — we do not validate it.
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.
Will footnotes / endnotes in the EPUB still work in the AZW3?
+
Yes — popup footnotes (epub:type="noteref") and traditional endnotes round-trip into the AZW3 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 EPUB file private during conversion?
+
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/.
How long does EPUB to AZW3 conversion take for a full novel?
+
A 300-page reflowable EPUB typically converts to AZW3 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 AZW3 look different from the EPUB in the reader?
+
Reflowable ebooks are not pixel-perfect by design — each reader chooses its own font, margins, and line spacing. The AZW3 contains the same content as the EPUB; 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 EPUB files to AZW3?
+
Yes — drop dozens of EPUB 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 AZW3 downloads individually or as a single zip.