2026-06-17 · all guides

Why Your ChatGPT Book Looks Wrong on KDP (and How to Fix It)

A chat window produces prose, not a book file

ChatGPT and similar chatbots output text formatted for a chat window: markdown headings, asterisk bullets, short screen-width paragraphs. A publishable KDP book is a different artifact entirely, with page size, mirrored margins, front matter, a working table of contents, and consistent typography. The gap between the two is where most first-time AI publishers lose days, and it is why so many AI books look obviously wrong in the Amazon preview.

None of this is a reason not to draft with AI. It is a reason to treat formatting as its own real step, with its own checklist, rather than assuming copy-paste will carry you from chat to print.

The five failures that show up again and again

First, markdown artifacts: literal asterisks, pound signs, and hyphens-as-bullets survive the paste and appear in the printed book. Second, inconsistent headings: the model drifts between heading levels across a long conversation, so chapter titles render at different sizes and the document outline is garbage, which breaks the ebook table of contents.

Third, no page setup: a pasted document defaults to 8.5 by 11 inches with uniform margins, while a typical KDP paperback is 6 by 9 with mirrored margins and a gutter that grows with page count. Ignore this and KDP will flag content in the margin zone, or the print preview will show text vanishing into the spine. Fourth, missing front matter: no title page, no copyright page, no TOC. Fifth, chapter breaks done with blank lines instead of page breaks, so chapter openings land mid-page the moment any earlier edit reflows the text.

The fixes, in the order to apply them

Start by converting, not pasting. Save the raw output as a markdown file and convert it with a tool that maps markdown to real document styles, or paste into your editor and immediately apply proper Heading 1 and Heading 2 styles to every chapter and section by hand. All formatting must be styles-based: the KDP ebook converter and the document TOC both read styles, not font sizes.

Then set up the page before you touch the prose: trim size (6 by 9 is the safe nonfiction default), mirrored margins, and a gutter sized to your page count per the KDP margin table. Insert page breaks before every chapter. Build front matter: title page, copyright page with your name and year, and an auto-generated TOC from your heading styles. Finally, run the file through the KDP previewer and actually page through it; the previewer catches margin violations and TOC failures before a reviewer or a buyer does.

When it is worth skipping the cleanup entirely

The honest cost accounting: expect several hours of formatting labor per book doing this manually, more the first time, and expect to redo pieces of it after every substantive edit. That is fine for one passion project. It compounds badly if you plan to publish more than once.

The alternative is a pipeline that generates the book as a formatted file rather than chat text. ebookdone produces a KDP-ready PDF and EPUB directly, with page setup, front matter, and TOC handled, for $9 a book; there is an unedited sample at /sample/two-hour-meal-prep.pdf if you want to inspect exactly what the output formatting looks like before deciding. Whether you use a tool or do it by hand, the standard is the same: open the file in the KDP previewer and read it like a stranger who paid money for it.

One reminder that has nothing to do with formatting: a book drafted by AI is AI-generated content under KDP rules and needs the disclosure checkbox during upload, even after all your cleanup. The checkbox is private and does not block publishing, so answer it honestly and move on.

FAQ