Ebook Template
Most downloadable ebook templates are Word .docx files — which means they share the same structural problem as any other Word document: they can't generate a valid EPUB 3.0 file on their own. Instead of starting from a template, BookKraft AI's EPUB Formatter converts your existing Word document into a valid EPUB 3.0 file that passes KDP, Apple Books, and Kobo validation automatically.
Write in Word with Heading Styles
Apply Heading 1 to every chapter title. Use Normal for body text. Don't add tab indents or decorative fonts — these don't survive conversion cleanly.
Upload to EPUB Formatter
Upload your .docx file. The formatter applies EPUB 3.0 structure — chapter breaks from Heading 1, nav document, clean CSS, correct package metadata.
Download Valid EPUB
Download a file that passes KDP, Apple Books, and Kobo validation. No template to configure, no styles to match — the structure is handled automatically.
Why Word ebook templates don't produce valid EPUBs
An ebook template built in Word can only produce what Word produces — and Word's EPUB output has four structural problems that cause retailer rejections:
Word templates output EPUB 2.0
Most downloadable ebook templates were built for older formatting tools. When exported through Word, they produce EPUB 2.0 files — the format Apple Books and Kobo reject in favor of EPUB 3.0.
No nav document is generated
EPUB 3.0 requires a nav.xhtml file — a clickable table of contents that links to each chapter. Word cannot generate this file. Apple Books rejects EPUBs that lack a conforming nav document.
Inline CSS from Word styles breaks e-readers
Word embeds its paragraph formatting as inline style attributes on every HTML element. This produces bloated output that breaks on Kobo's rendering engine and causes layout inconsistencies on older Kindle models.
Template styles conflict with EPUB CSS
Even when a template uses Word's built-in styles correctly, those styles get exported as Word-specific class names that don't map to EPUB semantics. The formatting that looks right in Word doesn't transfer.
Word ebook template vs. BookKraft AI EPUB Formatter
| Feature | Word Template | BookKraft AI |
|---|---|---|
| Output format | EPUB 2.0 (requires template setup) | EPUB 3.0 (generated automatically) |
| Nav document | — (not generated) | ✓ Auto-generated from Heading styles |
| Chapter breaks | Manual page breaks | ✓ From Heading 1 style |
| CSS | Inline Word styles | ✓ Clean external stylesheet |
| KDP validation | Often fails | ✓ Passes epubcheck |
| Apple Books | Frequently rejected | ✓ Passes strict validator |
| Setup required | Yes — match template styles | None — upload and convert |
Frequently asked questions
What is an ebook template?
An ebook template is a pre-built file structure — usually a .docx or HTML file — meant to give your manuscript a starting point for formatting. Most templates available online are Word .docx files with predefined styles for headings, body text, and indentation. The problem: Word templates export to EPUB with the same structural issues as any other Word document. BookKraft AI's EPUB Formatter bypasses the template step entirely — you write in a normal Word document, upload it, and the formatter applies correct EPUB structure automatically.
Why do Word ebook templates produce bad EPUBs?
Word ebook templates are formatted for how the document looks in Word, not for how EPUB retailers read structure. They don't include a nav document (required by EPUB 3.0 and Apple Books), they embed proprietary inline CSS that breaks on e-readers, and they often output EPUB 2.0 rather than the EPUB 3.0 that current retailers require. A template that looks correct in Word will still fail KDP and Apple Books validation.
Do I need a separate template for KDP and Apple Books?
No. EPUB 3.0 is the standard format accepted by Amazon KDP, Apple Books, Kobo, and IngramSpark. BookKraft AI outputs EPUB 3.0 regardless of where you plan to publish. Platform-specific differences (cover image specs, metadata fields, content requirements) are caught by the free EPUB Validator — not by using different templates.
What about Vellum or Atticus book templates?
Vellum's themes and Atticus's styles are visual design templates, not structural ebook templates. They handle drop caps, chapter ornaments, and font choices. BookKraft AI handles the structural layer — clean EPUB output, valid metadata, correct nav document — that sits underneath those design layers. The two aren't competing: BookKraft AI prepares a clean file that Vellum or Atticus can import.
Can I use a Google Docs template to make an ebook?
Yes, with a conversion step. Format your Google Doc with Heading 1 for chapter titles, export as .docx (File → Download → Microsoft Word .docx), then upload to the EPUB Formatter. The formatter generates a valid EPUB 3.0 file. Google Docs has no built-in EPUB export — it would route through Word format anyway, so the conversion step is unavoidable.
What heading styles does the EPUB Formatter use to create chapters?
Heading 1 in Word becomes a chapter break in the EPUB. Heading 2 becomes a sub-section. Body text and paragraph spacing come from Word's Normal style. If chapter titles are manually bolded body text rather than Heading 1, the formatter has no way to detect chapter boundaries — the EPUB will be one long unsectioned file with no table of contents entries.
Converting from Word specifically? See the Word to EPUB conversion guide. For the full EPUB formatting workflow including metadata and table of contents, see the EPUB formatting guide. If you're starting from scratch, see how to make an EPUB file.
Format your ebook — free, no account needed.
Upload a .docx file. Download EPUB 3.0. Passes KDP, Apple Books, and Kobo validation.
Open EPUB Formatter →