KDP Book Description Guide

Your KDP book description is the primary sales copy on your Amazon product page. It is not a summary — it is the argument for why a reader should buy this book over the hundreds of similar ones they will scroll past. This guide covers the character limit, how to use HTML formatting in the KDP dashboard, a copywriting structure that works for fiction and nonfiction, and how the description relates to search visibility.

What the KDP description field is — and what it's not

The description you enter in the KDP dashboard appears as the main text block on your Amazon product page, below the title and author name. It is separate from:

• Backend keywords — the seven keyword fields in KDP that affect search placement but are not visible to readers. Those are separate from the description and entered in a different step.
• EPUB metadata (dc:description) — the description field in your EPUB's OPF file. KDP does not pull this onto your Amazon product page; the product page description comes from the KDP dashboard only.
• A+ Content — an additional image-and-text content block available to some KDP authors, displayed below the main description.

The description is what readers read to decide whether to buy. Write it as conversion copy — hook, premise, stakes — not as a plot synopsis.

Length and character limit

KDP's book description field accepts up to approximately 4,000 characters, including any HTML formatting tags you add. HTML tags (<b>, <p>, <ul>, etc.) count toward the total — a heavily formatted description will fit fewer words than a plain-text one of the same character count.

The KDP dashboard displays a live character counter as you type. Check the counter directly when writing — it will show your current count and the limit. The exact limit may change; rely on the dashboard counter rather than a memorized number. In practice, most effective descriptions run 200–400 words before formatting. Shorter descriptions (under 150 words) often underuse the available space; longer ones risk losing readers before the call to action.

Supported HTML formatting

KDP's description field accepts a subset of HTML. You enter the tags directly in the description text box — the dashboard renders them in the preview and on the product page. The commonly supported tags:

Tags not supported — they will appear as raw text or be stripped: <a> (links), <div>, <span>, <img>, <table>. KDP's supported tag set may change — preview any tag you depend on in the KDP dashboard before publishing.

Description HTML — example structure

A formatted description that uses HTML to create visual hierarchy:

<h2>Perfect for fans of [Comp Title A] and [Comp Title B].</h2>

<p>Opening hook — one or two sentences that pull the reader in without
revealing too much. Lead with conflict, stakes, or a striking premise.</p>

<p>Three to five sentences expanding the premise: who the protagonist is,
what they want, what stands in their way, and what they risk losing.
Avoid plot synopsis — write toward the feeling of reading the book.</p>

<ul>
  <li>Genre and subgenre signals (e.g., "A slow-burn romance with...")</li>
  <li>Series information if applicable ("Book 2 in the Thornfield series")</li>
  <li>Content signals for readers who need them</li>
</ul>

<p><b>Author Name</b> is the author of [other titles].
[One sentence about author credibility or background, if relevant.]</p>

The <h2> at the top creates a bold visual header above the blurb — commonly used for comp titles, a series label, or an award notation. The <ul> block breaks up a wall of text and gives readers scannable signals about the book.

Copywriting structure

A description that converts has three components:

1. Hook — one or two sentences that establish premise, conflict, or a compelling question. Readers decide in the first line whether to keep reading. Write the hook last, after you have written the full blurb.
2. Blurb — three to five sentences covering protagonist, goal, obstacle, and stakes. For nonfiction: the problem the reader has, what the book gives them, and what changes for them after reading. Do not spoil resolution; end on unresolved tension.
3. Signals — series info, comp titles, content notes, author credibility. These help readers self-select — they confirm the book is right for them before they click Buy.

The most common mistake is writing a plot summary. A description is not a synopsis. It is a promise of an experience. Write toward the feeling of reading the book, not the sequence of events.

Keywords in the description

Amazon's search algorithm uses the description as one signal for keyword relevance. The exact weight it assigns to description keywords versus title, subtitle, series name, and backend keywords is not publicly documented. In practice:

• Write the description for readers first. Forced keyword placement hurts conversion.
• Genre and subgenre terms that readers search for naturally appear in a well-written blurb — "cozy mystery", "enemies-to-lovers romance", "keto diet for beginners" — without stuffing.
• Use your seven KDP backend keyword fields for search terms that cannot be placed naturally in readable prose. The description is not a substitute for backend keywords.

For keyword strategy — how to find the right terms for backend keywords and category placement — see the Amazon keyword research guide and the KDP category keywords guide.

Frequently asked questions

For the full KDP publishing reference — formatting, metadata, and store submission — see the KDP formatting guide. For the OPF metadata that lives inside your EPUB file — separate from the KDP dashboard description — see the EPUB metadata guide. For ebook pricing strategy — how royalty tiers interact with price selection, permafree, and Kindle Unlimited — see the KDP ebook pricing guide.