Word to HTML for Amazon KDP — Format Your Manuscript for Kindle

Amazon KDP accepts HTML files for Kindle ebook publishing — and clean HTML produces better ebook formatting than uploading a .docx file directly. Converting your Word manuscript to HTML first gives you more control over how chapter headings, paragraph spacing, and special formatting render on Kindle devices. Here is how to do it free, without installing anything.

Why Authors Use HTML for KDP Instead of DOCX

KDP accepts both .docx and .html uploads, but they do not produce the same results. When you upload a .docx, Amazon converts it internally using its own process — and that process sometimes mangles chapter spacing, drops special characters, or misinterprets your heading hierarchy.

With HTML, you have explicit control. The tags Amazon sees are exactly the tags you write. Chapter headings in <h1> tags become chapter titles in the Kindle table of contents. Paragraph breaks are explicit <p> tags. Bold and italic are semantic tags that survive the conversion reliably.

Authors who format multiple books recommend HTML for anything beyond a short ebook. The upfront few minutes of conversion saves hours of troubleshooting KDP conversion issues later.

Converting Your Manuscript From Word to HTML

The conversion process:

1. Finalize your manuscript in Word. Make sure chapter titles use the Heading 1 style, not just manually bolded large text. Subheadings should use Heading 2 or Heading 3. Body text should use Normal style.
2. Save as .docx
3. Go to the Word to HTML converter — your file never leaves your device
4. Drop the .docx file, wait a moment
5. Click Download .html to get a file you can upload directly to KDP

The resulting HTML will have your chapters in proper heading tags, which KDP uses to build the Kindle table of contents automatically. That is a critical structural requirement for ebooks that many authors miss when formatting manually.

Sell Custom Apparel — We Handle Printing & Free Shipping

What Gets Preserved (and What Does Not)

Preserved in the output:

• Chapter headings (H1, H2, H3) — essential for Kindle TOC generation
• Bold and italic — preserved as semantic tags
• Ordered and unordered lists
• Links (important for back matter and author URLs)
• Table content
• Images (as base64 data)

Not preserved:

• Custom fonts — Kindle readers use their own typography
• Exact font sizes — KDP normalizes these
• Page breaks — use a class or a dedicated page-break div in HTML instead
• Headers and footers — not supported in Kindle HTML
• Complex table formatting — background colors and merged cells may not survive

For a standard prose manuscript (novel, memoir, business book), the HTML conversion captures everything that matters. Non-fiction books with complex tables or heavy formatting may need additional HTML editing before upload.

Adding KDP-Specific Elements

After conversion, you may want to add a few HTML elements that KDP specifically looks for. Open the downloaded .html file in a text editor and add these at the very top of the content (before your first chapter heading):

<!-- Table of Contents -->
<nav epub:type="toc">
  <h1>Table of Contents</h1>
  <ol>
    <li><a href="#chapter1">Chapter 1: Title</a></li>
    <li><a href="#chapter2">Chapter 2: Title</a></li>
  </ol>
</nav>

Then add matching id attributes to your chapter headings:

<h1 id="chapter1">Chapter 1: Your Title</h1>

KDP uses these anchors to populate the Kindle's built-in table of contents navigation. Without them, readers cannot jump to chapters via the TOC menu on their device.

This is a 10-minute addition that makes a significant difference in the reading experience. It is the single most important HTML customization you can make for KDP ebook publishing.

Testing Before Upload

Before uploading to KDP, preview your HTML file in a browser. Open the .html file in Chrome or Firefox and check:

• Chapter headings appear at the right hierarchy level
• Paragraph spacing looks correct
• Lists display properly
• No duplicate content or missing sections

Then use Amazon's Kindle Previewer (free desktop app) to see exactly how the book will look on Kindle devices before you publish. The previewer catches formatting issues that the HTML file looks fine with in a browser but renders differently on a Kindle.

Most authors find that a Word-to-HTML conversion via our tool produces clean enough output to pass KDP's review process on the first try — especially for prose-heavy books. Technical books with lots of code blocks or mathematical notation may need additional formatting work.

Frequently Asked Questions

Can I upload the HTML file directly to Amazon KDP?

Yes. KDP accepts HTML files for Kindle content. Log in to KDP, create a new title, and in the Manuscript section choose to upload a file. Select your .html file. KDP will convert it to Kindle format automatically.

Does Word Save As HTML work for KDP?

Word's built-in Save As Web Page produces bloated HTML with hundreds of proprietary style attributes. Amazon's converter struggles with that markup and often produces inconsistent results. A clean HTML conversion produces more predictable ebook output.

What about images in my manuscript?

Images convert as base64 data in the HTML output. KDP accepts base64 images, but for better quality and file size management, consider using externally hosted image URLs or placing images as separate files in a ZIP package with your HTML.

Do I need to know HTML to use this for KDP?

No. For a standard prose manuscript, the conversion output is ready to upload as-is. If you want to add a clickable TOC or custom chapter anchors, a few minutes of basic text editing is all that is required — no coding knowledge needed.