The KDP Book Description Formula: Hook, Promise, Proof and Formatting That Converts

What the description has to do

A shopper reaches your description after your cover and title have already done their job. They are interested, not convinced. The description’s only task is to turn that interest into a sample download or a purchase. It is not a summary, a synopsis or a table of contents.

On a phone, Amazon shows only the first few lines before a “Read more” link. Those lines carry most of the weight.

The three-part structure

1. The hook

One or two sentences, visible above the fold. It should name the reader’s situation or the story’s central tension and make them want the next line.

Approaches that work:

• A direct question the reader is already asking themselves.
• A one-line statement of the problem the book solves.
• For fiction, the protagonist, the stakes and the clock in a single sentence.

Avoid starting with “This book is about” or “In this comprehensive guide”. Both tell the reader to stop.

2. What you get, and what changes

This is the middle and the longest section. Two questions, in order.

What is in it. For non-fiction, a short bulleted list of the concrete things the book contains: the method, the templates, the number of exercises, the chapters that matter. For fiction, the setting, the central conflict and the kind of experience the reader can expect (slow burn, fast paced, dark, cosy).

What changes for the reader. The outcome. Non-fiction readers buy a result, not a page count. Fiction readers buy a feeling. Say it plainly: “By the end, you will have a weekly plan you can actually keep” or “A mystery for readers who want to guess wrong twice before the end.”

Keep paragraphs to two or three lines. Shoppers skim.

3. Proof and a closing line

If you have genuine social proof, it goes here, after the promise, not before it. Genuine means an actual review quote you have permission to use, a real award, or a verifiable credential. Do not invent testimonials; KDP’s content guidelines treat fabricated reviews as misleading, and readers can tell.

If you have no proof yet, skip it. An honest description with no quotes beats one with a fake one.

End with a single line that tells the reader what to do: “Download the sample and read the first chapter” or “Start with the ten-minute setup in chapter one.”

Formatting with KDP’s supported HTML

KDP allows a limited set of HTML tags in the description field. The useful ones:

• <b> and </b> for bold
• <i> and </i> for italics
• <h4> through <h6> for small headings (larger heading tags may be rejected or rendered inconsistently)
• <ul>, <ol> and <li> for lists
• <br> for line breaks and <p> for paragraphs

Check the current list in KDP’s help pages before relying on any tag. Then:

• Use bold for one phrase per paragraph at most. Bold everywhere is the same as bold nowhere.
• Use a heading to separate the “what’s inside” block from the hook.
• Use bullets for a list of three to six items. Longer lists get skipped.
• Preview the result. KDP shows a rendered preview; also check the live listing on a phone after publishing, because the mobile layout truncates and spaces things differently.

Some authors use third-party description generators that produce HTML. They are fine, but paste the output into KDP and confirm it renders rather than trusting the tool.

How long should it be

KDP imposes a character limit on the description (check the current number in the help pages). You do not need to use all of it.

A working range:

• Non-fiction: 150 to 300 words. Enough for a hook, a bulleted contents list, an outcome paragraph and a close.
• Fiction: 100 to 200 words. Fiction blurbs that run long give away too much and lose tension.
• Low-content and no-content books (journals, planners, logbooks, colouring books): 80 to 150 words. State the format, page count, size, paper and the specific use, then stop.

The first couple of hundred characters matter most because they are what appears before “Read more” on mobile. Write those first and rewrite them last.

Fiction, non-fiction and low-content: the differences

Fiction

• Lead with character and stakes, not with world-building.
• Name the subgenre tropes readers search for, in natural language. Readers of a specific subgenre know what they want and will look for the signals.
• Do not reveal the twist. Do not summarise the plot past the first act.
• One short sentence on tone at the end helps readers self-select: “A standalone with a guaranteed happy ending.”

Non-fiction

• The hook is the problem. The middle is the method. The close is the result.
• Use a bulleted list for concrete contents. Numbers help: “12 templates”, “a 4-week plan”.
• State who the book is not for. It builds trust and reduces returns.
• If your credential is relevant, one sentence is enough.

Low-content

• Specifications first: trim size, page count, paper colour, layout. Buyers of journals and planners are comparing specs.
• Name the exact use case in the first line: “A 90-day habit tracker for people who have tried apps and quit.”
• Mention what is on each page type if the interior has structure.
• Keep it short. Nobody reads 300 words about a notebook.

A quick check before you paste it in

• Can a reader understand what the book is from the first two lines alone?
• Does every paragraph either promise something or prove something?
• Is there any claim you could not back up if asked?
• Does it contain any phrase that breaks the metadata rules covered in the keyword research guide, such as comparisons to named authors or “bestseller” claims?
• Have you previewed it on a phone?

Next step

The description works with the cover, not instead of it. If the cover does not earn the click, the description is never read. Go to how to brief a KDP cover for a cover that holds up at thumbnail size.