Promotional image for Kindle eBook Formatting with screens showing document editing and a Kindle device.

Kindle eBook Formatting Walkthrough for KDP

Gary Whittaker

```html

COMPLETE ACCESS Member Training

Promotional image for Kindle eBook Formatting with screens showing document editing and a Kindle device.Kindle eBook Formatting in Google Docs and Microsoft Word: A Step-by-Step KDP Cleanup Walkthrough

This guide shows COMPLETE ACCESS Members how to inspect, clean, track, export, preview, and prepare a Kindle eBook manuscript before KDP upload.

The public guide explains what Kindle formatting requires. This member training shows the working process using Google Docs, Microsoft Word, Google Sheets, Kindle Create, the Previewer in Kindle Create, Kindle Previewer when needed, and KDP.

Read this before touching your manuscript

A manuscript can look finished and still need Kindle-specific cleanup. The words may be written, the chapters may be in order, and the images may already be inserted. That does not mean the file is ready for Kindle.

Your goal is not to make the file look perfect inside Google Docs or Word. Your goal is to create a clean source file, export it correctly, preview it inside the Kindle workflow, fix the issues, and prepare the right upload file for KDP.

Workflow expectation

This is not usually a one-sitting cleanup for a full manuscript. Work phase by phase. Stop after each gate, update the tracker, and only continue when the previous phase is clean enough to move forward.

This fits the Jack Righteous creator path: create the work, communicate it clearly, and own the publishing process before rushing the file into public release.

How to use this guide

Do not skim this guide while making random changes. Read the full process once first. Then return to the beginning and complete one phase at a time.

Recommended workspace

  • Left window: this guide.
  • Middle window: your manuscript in Google Docs or Microsoft Word.
  • Right window: your Google Sheets tracker.
  • Folder window: your project folder with images, exports, and preview notes.
  • Use a desktop or laptop. Do not try to complete the full workflow on a phone.

The rule for every phase

Each phase should answer these questions:

  • What do I click?
  • What do I look for?
  • What should happen next?
  • What does a mistake look like?
  • Where do I log it?
  • When do I stop and ask for COMPLETE ACCESS support?

Tools you need before starting

This guide uses five tools. You do not need to be an expert, but you do need to understand what each tool is responsible for.

Tool Use it for Do not use it for
Google Docs Writing, basic cleanup, heading styles, document outline, simple page breaks, links, and DOCX export. Forensic inspection of damaged formatting, deep section-break cleanup, or complex print layout repair.
Microsoft Word Hidden formatting marks, Navigation Pane, Track Changes cleanup, section breaks, headers, footers, page numbers, and DOCX cleanup. Trying to design a Kindle eBook like a paperback page.
Google Sheets Issue log, image inventory, TOC audit, link audit, preview issue tracking, and support request preparation. Editing the manuscript text itself.
Kindle Create Importing the cleaned DOCX, detecting chapters, reviewing layout, previewing, and exporting KPF. Repairing a badly damaged manuscript source file.
KDP Uploading the final manuscript file, cover, metadata, description, categories, keywords, rights, territories, and pricing. Fixing manuscript formatting after the file should already have been checked.

Do not use Canva, a PDF, or page screenshots as the main manuscript source for this workflow unless you are intentionally building a fixed-layout project. The working source for this guide should be Google Docs or Microsoft Word, then DOCX.

Beginner glossary

Use this glossary before the technical steps. These terms appear throughout the guide.

Term Meaning Why it matters
DOCX A Microsoft Word document file format. This is the bridge file you import into Kindle Create.
KPF The Kindle Create publishing file. If you use Kindle Create, this is the file you upload to KDP.
KCB The Kindle Create project file. This is the file and project folder you keep if you need to update the book later.
TOC Table of contents. Readers need working navigation, not print page numbers.
Reflowable Text adjusts when the reader changes device, font size, spacing, or orientation. Most text-first Kindle books should use this path.
Fixed layout A locked visual layout where page design is preserved. Useful for some picture books, comics, and visual books, but not the default for text-first books.
Hard return Pressing Enter to create a paragraph break. Hard returns should not be used at the end of every visible line.
Heading style A real document style such as Heading 1 or Heading 2. Bold and large text is not enough. Real headings help outlines and navigation.
Track Changes Word's review mode that marks edits. Existing tracked changes must be accepted or rejected before export.
Alt text A short image description for accessibility. Meaningful images should be described. Decorative images should be marked appropriately.

Practice before using your full manuscript

First-time users should practice the workflow on a short test file before editing a full book. This prevents confusion and gives you a safe place to learn the tools.

Create a practice file with:

  • title page
  • copyright page
  • table of contents
  • one chapter title
  • three body paragraphs
  • one image
  • one link
  • about the author page

Run the practice file through headings, DOCX export, Kindle Create import, and preview before touching the full book.

Step 1: Set up the project folder

Never clean the only copy of your manuscript. Make a safe workspace first.

What to click

  1. Create a new folder on your computer or Google Drive.
  2. Name it BookTitle_Kindle_eBook_Cleanup.
  3. Inside that folder, create these subfolders:
    • 01 Original Files
    • 02 Working Manuscript
    • 03 Images
    • 04 Exported DOCX
    • 05 Kindle Create Project
    • 06 Preview Notes
    • 07 Final Upload
    • 08 Support Request Materials
  4. Place the original manuscript in 01 Original Files.
  5. Do not edit the file in 01 Original Files.

What good looks like

You should have one project folder with clear subfolders. The original manuscript should be stored safely and untouched.

Stop and ask for support if

You do not know which file is the real manuscript, or you only have a PDF and no Google Docs or Word source.

Step 2: Create the master cleanup copy

The cleanup copy is the file you will edit. The original remains untouched.

In Google Docs

  1. Open the original Google Doc.
  2. Click File.
  3. Click Make a copy.
  4. Name the copy BookTitle_kindle_cleanup_working.
  5. Save it in the 02 Working Manuscript folder.
  6. Close the original and work only in the copy.

In Microsoft Word

  1. Open the original Word file.
  2. Click File.
  3. Click Save As.
  4. Name the copy BookTitle_kindle_cleanup_working.docx.
  5. Save it in the 02 Working Manuscript folder.
  6. Close the original and work only in the copy.

In the Phase Comparison tab, mark Original saved and Working copy created as Approved.

Step 3: Build the Google Sheets tracker

Google Sheets is the control center for this workflow. The manuscript is where the book gets cleaned. The tracker is where the work stays organized.

What to click

  1. Open Google Sheets.
  2. Click Blank spreadsheet.
  3. Click the title area in the upper left.
  4. Rename the file BookTitle_Kindle_eBook_Cleanup_Tracker.
  5. Rename Sheet1 to Phase Comparison.
  6. Click the plus button at the bottom to add more sheets.
  7. Create these tabs:
    • Manuscript Issue Log
    • Google Docs vs Word Checklist
    • Image Inventory
    • TOC and Link Audit
    • Preview Issue Log
    • KDP Upload Readiness
    • Support Request
  8. In each tab, type your column names in Row 1.
  9. Bold Row 1.
  10. Freeze Row 1 using View, then Freeze, then 1 row.
  11. Turn on filters using Data, then Create a filter.
  12. Use dropdowns and checkboxes where needed.

Suggested dropdown values

Status: Not started, In progress, Needs fix, Fixed in source, Re-exported, Preview checked, Approved.

Risk: Critical, High, Medium, Low.

Fix location: Google Docs, Word, Kindle Create, Image source, KDP metadata, Undecided.

Image action: Keep, Resize, Replace, Recreate, Convert text to live text, Remove.

Device view: Phone, Tablet, Kindle e-reader, Previewer in Kindle Create, KDP Online Previewer.

Quality gate

Do not diagnose the manuscript until the tracker exists and the tab names are created.

Step 4: Set up each tracker tab

The tracker needs to be usable, not just created. Build each tab with clear columns and sample rows.

Tab Columns to add Sample row
Phase Comparison Section, Phase, Goal, Google Docs action, Word action, Kindle Create action, KDP requirement, Risk level, Status, Notes Project setup, Backup, Preserve original, Make a copy, Save As, Not applicable, Source must be clean, Critical, Approved, Original saved
Manuscript Issue Log Issue ID, Location, Issue type, Description, Tool found in, Fix needed, Fixed in source, Re-exported, Preview checked, Status, Notes 001, Chapter 1, Manual word break, “ex-plaining” is split, Word, Replace with “explaining”, No, No, No, Needs fix, Source issue
Google Docs vs Word Checklist Cleanup item, Google Docs check, Word check, Required before DOCX export, Status, Notes Heading 1 applied to chapters, Yes, Yes, Yes, In progress, Check outline and Navigation Pane
Image Inventory Image ID, File name, Book location, Image type, Contains text, Original file available, Readable on phone, Alt text needed, Decorative or meaningful, Action, Status, Notes IMG-001, chapter_01_opener.png, Before Chapter 1, Chapter opener, Yes, Yes, Unknown, Yes, Meaningful, Check in preview, Not started, Text may be small
TOC and Link Audit Entry or link text, Type, Location, Target, Works in source, Works in Kindle Create, Works in preview, Fix needed, Notes Chapter 1, TOC, Table of contents, Chapter 1 heading, Yes, Unknown, Unknown, TBD, Test after import
Preview Issue Log Issue ID, Device view, Location, Problem, Fix location, Priority, Fixed, Rechecked, Notes P-001, Phone, Chapter 3 image, Text too small, Image source, High, No, No, Consider live text below image
KDP Upload Readiness Item, Required, Ready, File type, Notes KPF exported, Yes if using Kindle Create, No, KPF, Export after final preview
Support Request Field, Member response Known issues, Manual hyphenation, image readability, TOC page numbers

Step 5: Diagnose the manuscript

Diagnosis means you are looking for problems before changing the file. Do not fix while scanning. Log first, fix after.

What to inspect

  • What file type are you starting with?
  • Is the manuscript final or still being rewritten?
  • Are chapter titles consistent?
  • Are there page numbers?
  • Are there headers or footers?
  • Is the TOC linked or typed manually?
  • Are print page numbers inside the TOC?
  • Are there “see page” references?
  • Are original image files available separately?
  • Are there text-heavy images, cards, charts, or diagrams?
  • Are there text boxes, shapes, or floating objects?
  • Are there hard returns after every visible line?
  • Are there manually split words?
  • Are Track Changes or comments present?
  • Are tables, footnotes, or external links present?
  • Are there permissions concerns for images, scripture, lyrics, quotes, or AI-generated visuals?

Diagnosis rating

Green: clean source, minor cleanup only.

Yellow: usable, but needs formatting cleanup.

Red: source is damaged, copied from PDF, filled with hard returns, image-heavy, or structurally unclear.

Stop and ask for support if

The manuscript came from a PDF and every line is broken, or you cannot identify the real source file.

Step 6: Learn how to find common problems

Beginners often know something is wrong, but not how to find it. Use these searches and visual checks.

Problem How to find it Warning Where to log it
Manual word breaks Use Find. Search for fragments like -ing, -tion, -ment, and -ly. Inspect each result manually. Do not replace blindly. Some hyphenated words are correct. Manuscript Issue Log
Page references Search for “see page,” “page,” “p.”, and print-style TOC numbers. Kindle pages change by device and reader settings. TOC and Link Audit
Headers and footers In Google Docs, click the top or bottom margin. In Word, double-click the top or bottom margin. Remove them for a normal Kindle eBook source. Manuscript Issue Log
Hard returns In Word, click Home, then ¶. Look for a paragraph mark after every visible line. Each paragraph should usually have one paragraph mark at the end, not one after every line. Manuscript Issue Log
Section breaks In Word, show formatting marks using Home, then ¶. Look for section break labels. Do not delete section breaks randomly. Check what they control first. Manuscript Issue Log
Heading problems Use Google Docs outline or Word Navigation Pane. Real headings should appear there. Large bold text is not the same as Heading 1. Google Docs vs Word Checklist

Step 7: Decide Google Docs or Word path

You do not always need both tools. Choose the path based on the condition of the manuscript.

Use Google Docs if:

  • the manuscript was written in Google Docs
  • the file is mostly clean
  • you need headings, simple page breaks, simple TOC review, and DOCX export
  • there are no serious hidden formatting problems
  • there are no unresolved Track Changes or complex section breaks

Use Microsoft Word if:

  • the file came from multiple sources
  • there are strange spaces or line breaks
  • you need to inspect hidden formatting marks
  • headers, footers, page numbers, or section breaks keep returning
  • Track Changes or comments are present
  • the Google Docs outline does not show chapters correctly

Beginner rule: if the document behaves strangely, move inspection to Word before exporting to Kindle Create.

Step 8: Decide reflowable or fixed layout

Do not move forward until the format decision is made. Reflowable and fixed layout are not style preferences. They are production paths.

Reflowable is usually best for:

  • devotionals
  • Christian nonfiction
  • memoirs
  • novels
  • Bible studies
  • reflection books
  • teaching guides
  • books where images support the text but do not control every page

Fixed layout may be needed for:

  • children's picture books
  • comics
  • manga
  • graphic novels
  • art books
  • highly designed visual books
  • books where text and images cannot separate without losing meaning

In Phase Comparison, add a Format decision row and mark Reflowable, Fixed layout, Print Replica, or Undecided.

Step 9: Google Docs beginner cleanup path

Use this path when the manuscript is mostly clean and you are working in Google Docs.

What to click

  1. Open the cleanup copy in Google Docs.
  2. Confirm the document is in Pages format if you need page breaks. Page-break features are not available in pageless format.
  3. Click View, then Show outline.
  4. Click and drag across the book title.
  5. Open the style dropdown in the toolbar. It may say Normal text.
  6. Choose Title for the book title.
  7. Click and drag across each chapter title.
  8. Choose Heading 1 for each major chapter title.
  9. Click and drag across major internal section titles.
  10. Choose Heading 2 for major subsections.
  11. Select body text and confirm it uses Normal text.
  12. Place your cursor before each chapter title.
  13. Click Insert, then Break, then Page break.
  14. Remove page numbers from the Kindle TOC.
  15. Remove headers and footers.
  16. Search for manual word breaks such as -ing, -tion, -ment, and -ly.
  17. Check links by clicking each one.
  18. Export only after the outline, TOC, images, and issue log are updated.

What good looks like

The document outline should show the major chapter list. If Chapter 1, Chapter 2, Chapter 3, and the rest of the main chapters do not appear in the outline, the headings are not ready.

Do not do this in Google Docs

  • Do not manually make headings by changing size and bold only.
  • Do not use blank lines to push content down.
  • Do not keep page numbers in the Kindle TOC.
  • Do not paste screenshots of manuscript pages as the book content.
  • Do not export until the document outline looks correct.

Step 10: Microsoft Word beginner cleanup path

Use this path when the file needs deeper inspection, has tracked changes, has section breaks, or came from multiple sources.

What to click

  1. Open the cleanup copy in Microsoft Word.
  2. Click File, then Save As, and confirm you are working in the copy.
  3. Click Home, then ¶ to show formatting marks.
  4. Click View, then Navigation Pane.
  5. Click Review, then Track Changes, and turn Track Changes off.
  6. Accept or reject any existing tracked changes.
  7. Resolve or delete comments.
  8. Click each chapter title and apply Heading 1.
  9. Click each major subsection and apply Heading 2.
  10. Confirm body text uses Normal style.
  11. Check the Navigation Pane. Chapter headings should appear under Headings.
  12. Remove headers, footers, and page numbers.
  13. Use formatting marks to find hard returns and section breaks.
  14. Fix paragraphs broken line by line.
  15. Review images, wrapping, placement, and alt text needs.
  16. Save as DOCX after cleanup.

What good looks like

In the Navigation Pane, the chapter list should appear under Headings. If the pane is empty or only shows random text, your chapter titles are not using heading styles correctly.

Do not do this in Word

  • Do not leave Track Changes on.
  • Do not ignore comments.
  • Do not delete section breaks randomly without checking what they control.
  • Do not use tabs or spaces to indent body text.
  • Do not trust the file if the Navigation Pane is empty.

Step 11: When the formatting is too messy, rebuild clean

Sometimes cleanup takes longer than rebuilding. If the manuscript was copied from a PDF, built from many sources, or broken line by line, use a clean-text rebuild.

Clean-text rebuild method

  1. Make a copy of the manuscript.
  2. Create a new blank Google Doc or Word file.
  3. Copy one chapter title and one chapter at a time.
  4. Paste without formatting where available.
  5. Apply Heading 1 to the chapter title.
  6. Apply Normal text to the body paragraphs.
  7. Reinsert images from original image files only.
  8. Do not copy image screenshots from the damaged file unless no original exists.
  9. Rebuild the TOC from real headings.
  10. Log this as a rebuild decision in the tracker.

Stop and ask for support if you cannot decide whether cleanup or rebuild is the better path.

Step 12: Fix headings and document outline

Headings are the structure of your Kindle file. They help you, Word, Google Docs, Kindle Create, and readers understand the book.

Bad heading example

Chapter 1 is centered, bold, and large, but it does not appear in the Google Docs outline or Word Navigation Pane.

Good heading example

Chapter 1 uses Heading 1 and appears in the document outline or Navigation Pane.

Do not continue until all major chapters appear in the outline or Navigation Pane.

Step 13: Fix page breaks, hard returns, and spacing

Page breaks are useful for major structure. Hard returns at the end of every visible line can damage the Kindle reading experience.

Keep page breaks before:

  • title page
  • copyright page
  • dedication
  • table of contents
  • each chapter
  • conclusion
  • about the author and major back matter

Fix or remove:

  • breaks used to imitate paperback layout
  • hard returns after every visible line
  • paragraphs split mid-sentence
  • blank-line stacks used to force spacing
  • page breaks after every small content block

What good looks like

A normal paragraph should have one paragraph mark at the end. If every visible line has its own paragraph mark, the text is broken line by line.

Step 14: Remove print-only elements

If an element exists only to control a printed page, remove it from the Kindle eBook source unless there is a Kindle-specific reason to keep it.

  • headers
  • footers
  • page numbers
  • print TOC page numbers
  • 6 x 9 trim-size assumptions
  • bleed language
  • paperback margin controls
  • “see page” references
  • cover image inside the manuscript

Critical rule: the Kindle cover is uploaded separately during KDP setup. Do not place the cover inside the manuscript for a normal Kindle eBook upload.

Step 15: Fix manual hyphenation and dash decisions

Manual hyphenation means the word itself is typed with a visible break. That is different from Kindle line wrapping.

Fix source-created word breaks

Examples to fix:

  • show-ing becomes showing
  • ex-plaining becomes explaining
  • heal-ing becomes healing
  • re-membering becomes remembering

We can fix “show-ing” when the hyphen is typed into the source. We cannot control every future line ending on every Kindle device.

Style decisions to log

  • em dashes allowed or replaced with en dashes?
  • smart quotes or straight quotes?
  • double spaces removed?
  • scripture reference style?
  • chapter title capitalization?
  • paragraph spacing style?

Step 16: Build front matter and back matter

For Kindle, order and clarity matter more than left-page or right-page placement. Do not bring paperback page-side rules into the eBook source.

Recommended Kindle front matter order

  1. Title page
  2. Copyright
  3. Disclaimer, if needed
  4. Scripture or quotation note, if needed
  5. Dedication, if used
  6. Table of contents
  7. Introduction, if used
  8. Chapter 1

Recommended Kindle back matter order

  1. Conclusion
  2. Reader note or next step
  3. About the author
  4. Other books or resources
  5. Newsletter or website link
  6. Companion resource note, if relevant

Quality gate: do not export until the full front matter and back matter order is final.

Step 17: Build and test the table of contents

A Kindle eBook with chapters or sections needs working navigation. Do not approve a Kindle file until every TOC entry has been clicked and tested.

Google Docs TOC path

  1. Apply Heading 1 to each chapter.
  2. Place the cursor where the TOC belongs.
  3. Click Insert, then Page elements, then Table of contents.
  4. Choose a linked TOC style.
  5. Click each entry and confirm it jumps to the right chapter.
  6. Remove print page numbers if present.
  7. Refresh the TOC after heading changes.

Word TOC path

  1. Apply Heading 1 to each chapter.
  2. Open View, then Navigation Pane.
  3. Confirm chapters appear under Headings.
  4. Use References, then Table of Contents if using Word's TOC.
  5. Remove print page numbers if inappropriate for Kindle.
  6. Test the final TOC again after Kindle Create import.

Kindle Create TOC path

  1. Review detected chapters after import.
  2. Confirm the TOC entries match the chapter structure.
  3. Preview navigation.
  4. Log incorrect entries in the TOC and Link Audit tab.

What bad and good look like

Bad Kindle TOC: Chapter 1 ................................ 7

Good Kindle TOC: Chapter 1: Acknowledge the Pain, with a working link and no print page number.

Step 18: Build the image inventory

Images need their own audit. Do not judge images only by how they look in Google Docs or Word. Judge them by how they read in preview.

For each image

  1. Save the original image file in the 03 Images folder.
  2. Rename it by order and purpose, such as chapter_01_opener.png or card_03_reflection.png.
  3. Add it to the Image Inventory tab.
  4. Mark whether it contains text.
  5. Mark whether the text is essential.
  6. Decide whether the same text should appear as live text below the image.
  7. Mark whether alt text is needed.
  8. Mark whether the image is decorative or meaningful.
  9. Check it in phone view during preview.
  10. Choose Keep, Resize, Replace, Recreate, Convert text to live text, or Remove.

Important: if text can be separated from the image and still make sense, use live text. Do not trap essential text inside an image unless the visual design requires it.

Step 19: Use the image-with-text decision tree

Cards, charts, quote graphics, maps, diagrams, and screenshots need special review because they often contain text.

Decision tree

  1. Does the image contain text?
    • No: treat it as pictorial or decorative.
    • Yes: continue.
  2. Is the text essential?
    • No: it may be decorative or supporting.
    • Yes: continue.
  3. Can the text be live text?
    • Yes: place the image, then add the essential text as live text below it or nearby.
    • No: recreate the image larger and test in phone preview.
  4. Does it pass phone preview?
    • Yes: mark Preview checked.
    • No: log the issue and choose Resize, Replace, Recreate, Convert text to live text, or Remove.

Step 20: Handle tables without turning them into unreadable screenshots

Tables can be difficult in reflowable eBooks. Do not turn a table into a screenshot unless there is no better option.

  1. Ask whether the table is necessary.
  2. Reduce columns if possible.
  3. Avoid paragraph-heavy table cells.
  4. Consider turning the table into a list if it reads better on Kindle.
  5. Avoid making the table a screenshot unless there is no better option.
  6. If using an image, split wide tables into smaller readable images.
  7. Repeat essential information as live text when needed.

Quality gate: every table, chart, and text-heavy visual must be checked in phone view before approval.

Step 21: Audit links

Links should serve the reader. Avoid vague link text when clear text is possible.

Track every link:

  • link text
  • URL or target
  • location in book
  • purpose
  • internal or external
  • tested in source
  • tested in Kindle Create
  • tested in preview
  • fix needed

Better link text: “Join COMPLETE ACCESS.” Weak link text: “Click here.”

Step 22: Use the export gate before creating DOCX

Exporting too early creates extra loops later. Use this gate before creating the DOCX.

Do not export until these are complete

  • Tracker created.
  • Original preserved.
  • Working copy created.
  • Headings applied.
  • Outline checked.
  • Hard returns fixed.
  • Headers removed.
  • Footers removed.
  • Page numbers removed.
  • TOC reviewed.
  • Images inventoried.
  • Links audited.
  • Track Changes off.
  • Comments resolved.
  • Style decisions complete.
  • Known issues logged.

Step 23: Export to DOCX

DOCX is the bridge into Kindle Create. Export only after the source cleanup has passed the export gate.

Google Docs export

  1. Click File.
  2. Click Download.
  3. Click Microsoft Word (.docx).
  4. Save the file in the 04 Exported DOCX folder.
  5. Name it BookTitle_exported_docx_for_kindle_create.docx.

Microsoft Word export

  1. Click File.
  2. Click Save As.
  3. Choose DOCX format.
  4. Save the file in the 04 Exported DOCX folder.
  5. Name it BookTitle_exported_docx_for_kindle_create.docx.

Mark DOCX Export Approved in the KDP Upload Readiness tab.

Step 24: Import into Kindle Create

Kindle Create is not where you repair a messy manuscript. It is where you confirm that a cleaned DOCX converts properly.

What to click

  1. Open Kindle Create.
  2. Click Create New.
  3. Choose the correct book type for a reflowable text-first book.
  4. Select the cleaned DOCX file from the 04 Exported DOCX folder.
  5. Wait for import to finish.
  6. Review the list of detected chapters.
  7. Accept or correct chapter detection.
  8. Open the first chapter.
  9. Check chapter title, first paragraph, image placement, and paragraph spacing.
  10. Move through every chapter.
  11. Save the project in the 05 Kindle Create Project folder.
  12. Do not export the KPF yet. Preview first.

What good looks like

The chapters should appear in order.

The body text should flow without forced line breaks.

Images should be near the intended content.

The TOC should match the chapter structure.

Step 25: Preview the book before export

The source document is not the final test. Use the Previewer in Kindle Create to check the reader experience before export. If you are formatting outside Kindle Create, use the standalone Kindle Previewer. After upload, use the KDP Online Previewer for a final check.

What to check

  • phone view
  • tablet view
  • Kindle e-reader view
  • larger font size
  • TOC navigation
  • title page
  • copyright page
  • chapter starts
  • image placement
  • image readability
  • paragraph spacing
  • line breaks
  • lists
  • tables
  • links
  • back matter
  • final page

Quality gate: do not export the final KPF until the preview issues are logged, fixed, and rechecked.

Step 26: Decide where each fix belongs

Beginners often try to fix everything in the wrong place. Use this table before making changes.

Fix location Fix these issues there
Google Docs or Word Headings, hard returns, body text, chapter order, page breaks, headers, footers, page numbers, manual hyphenation, missing text, image source problems.
Google Sheets Issue tracking, image decisions, link audit, readiness status, support request details.
Kindle Create Chapter detection, simple TOC confirmation, theme choice, simple image placement review, final KPF export.
KDP Metadata, categories, keywords, pricing, territories, cover upload, final upload settings.

Every fix should respond to a logged issue. Do not make random changes and hope the file improves.

Step 27: Export KPF or prepare DOCX upload

Your upload file depends on the workflow you chose.

If you use Kindle Create, export and upload the KPF file.

If you format directly from Word without Kindle Create, upload the DOC or DOCX file and still preview before publishing.

Before upload, confirm:

  • final DOCX archived
  • Kindle Create project saved
  • KPF exported, if using Kindle Create
  • images checked
  • links checked
  • TOC checked
  • preview reviewed
  • rights confirmed
  • cover uploaded separately in KDP
  • description ready
  • categories and keywords prepared
  • pricing and territory decisions ready

Step 28: KDP upload readiness gate

The Kindle manuscript file is only one part of upload readiness. KDP also needs book information and publishing decisions.

Confirm before upload

  • title
  • subtitle
  • author name
  • book description
  • keywords
  • categories
  • cover file
  • manuscript file
  • rights confirmation
  • pricing
  • territories

Common first-time mistakes

Avoid these mistakes before they turn into upload problems.

  • Starting with the only copy of the manuscript.
  • Trying to make Kindle match paperback pages.
  • Putting the cover image inside the manuscript.
  • Keeping page numbers.
  • Forgetting to remove headers and footers.
  • Using screenshots of text instead of live text.
  • Manually bolding chapter titles instead of applying Heading 1.
  • Pressing Enter after every visible line.
  • Ignoring the TOC because it looks fine.
  • Not checking phone view.
  • Changing random things after preview instead of logging the issue.

Exact issue language for support requests

Use clear issue language when asking for help. This keeps COMPLETE ACCESS support focused on the real problem.

“Manual word break found in Chapter 2: ‘heal-ing’ should be ‘healing.’”

“TOC entry for Chapter 4 does not jump to Chapter 4 in preview.”

“Chapter opener image contains text that is readable in desktop view but too small in phone view.”

“Page numbers remain in footer after DOCX export.”

“Kindle Create detected subsection headings as chapters.”

Final Kindle eBook formatting checklist

Use four gates before upload: source file ready, images ready, Kindle Create ready, and KDP upload ready.

Gate 1: Source file ready

  • final manuscript confirmed
  • backup copy saved
  • working copy created
  • chapter order confirmed
  • headings applied
  • hard returns fixed
  • print page numbers removed
  • headers and footers removed
  • Track Changes off
  • comments resolved
  • manual word breaks fixed
  • dash style confirmed

Gate 2: Images ready

  • image inventory complete
  • original files saved
  • text-heavy images checked
  • essential image text repeated as live text where needed
  • alt text planned or added
  • decorative images identified

Gate 3: Kindle Create ready

  • DOCX imported
  • chapters detected
  • TOC reviewed
  • images reviewed
  • project saved
  • KPF exported if using Kindle Create

Gate 4: KDP upload ready

  • cover ready and uploaded separately
  • description ready
  • metadata ready
  • categories ready
  • keywords ready
  • rights confirmed
  • pricing ready
  • territories selected

Stop and ask for COMPLETE ACCESS support if

Ask for help when the next step is unclear or the file keeps producing the same problem.

  • The outline does not show chapters after applying Heading 1.
  • The manuscript came from a PDF and every line is broken.
  • Images contain text that cannot be read in phone preview.
  • Kindle Create detects the wrong chapters.
  • The TOC links go to the wrong places.
  • You cannot remove headers or page numbers.
  • Track Changes will not turn off or changes remain visible.
  • You are unsure whether the book should be reflowable or fixed layout.
  • The file uploads but preview looks broken.

What to send for COMPLETE ACCESS support

Bring the actual problem. Do not send only a screenshot and ask, “Is this okay?”

Send:

  • current manuscript file
  • exported DOCX
  • original images
  • Google Sheets tracker link
  • screenshots of preview problems
  • tool used: Google Docs, Word, Canva, PDF, or other
  • desired format: reflowable or fixed layout
  • whether the manuscript is final
  • whether proofreading is complete
  • whether the cover is ready
  • whether there are links, quotes, scripture, or permissions concerns

Support request template

Book type:

Tool used:

Current file format:

Target format:

Known issues:

Image issues:

TOC issues:

Preview issues:

What I already tried:

What I need help deciding:

Member resources to pair with this guide

This HTML training page should be paired with working resources so members can apply the process instead of only reading about it.

  • Google Sheets Cleanup Tracker template
  • one-page Kindle eBook cleanup checklist
  • image inventory template
  • support request template
  • Google Docs practice file
  • Word practice file
  • screenshot checklist for future training updates

Official resources to keep open

KDP tools and requirements can change. Check official guidance before final upload.

Do not format for the page. Format for the reader.

The process keeps the work honest: diagnose, clean, export, import, preview, fix, and only then prepare for KDP.

When you need support, bring your manuscript notes, issue log, image inventory, and preview screenshots into COMPLETE ACCESS so we can work from the actual problem instead of guessing.

Continue in COMPLETE ACCESS Support

Apply the workflow in order: diagnose, track, clean, export, import, preview, fix, and prepare for KDP.

Bring the Google Sheets tracker, manuscript file, DOCX export, image folder, and preview screenshots when you need help.

Return to COMPLETE ACCESS

```

Back to blog

Leave a comment

Please note, comments need to be approved before they are published.