Knowing how to write a book description for Amazon KDP is one of the highest-leverage skills you can develop as a self-published author. By the time a shopper lands on your book page, your cover and title have already done their job — the description is your last pitch before they hit Buy or scroll away. Amazon's algorithm also factors in conversion rate as a ranking signal, which means a weak description doesn't just lose the sale in front of you — it quietly erodes your search visibility over time.
The 4,000-Character Limit (And Why It's Less Than It Sounds)
KDP allows up to 4,000 characters in a book description. The critical detail most authors miss: HTML tags count toward that limit. Every formatting element you add — bold, italic, a heading — eats into the character budget before a single visible word is printed. Bolding the word "test" (4 characters) costs you 11 characters total once you include the opening and closing <b></b> tags. A heading like <h4></h4> adds 9 characters of overhead on top of whatever text sits inside it.
In practical terms, 4,000 characters is roughly 600 words of plain text. Once you account for HTML formatting, the visible word count drops to somewhere in the 300–400 word range. That is not a lot of room, and every character needs to earn its place.
Mobile makes this tighter still. On most phone screens, only the first 3–4 lines of your description appear before a "Read more" link. The opening of your description has to work completely on its own — readers who never tap "Read more" are real buyers you can still convert if your hook is strong enough.
If you want to understand how your description fits into the broader picture of a book's performance, the BSR Sales Calculator can help you estimate how current sales rank translates to actual monthly sales volume.
HTML Formatting Amazon Actually Supports
KDP's description editor accepts a specific subset of HTML. Using anything outside that list either gets stripped silently or triggers an error. Here is what is officially supported:
- <b></b> — bold text
- <i></i> or <em></em> — italic / emphasis
- <u></u> — underline
- <p></p> — paragraph
- <br> — line break
- <h4></h4> through <h6></h6> — section headings
- <ul></ul> with <li> — bulleted lists
- <ol></ol> with <li> — numbered lists
A common mistake pulled from outdated guides: h1, h2, and h3 tags are not supported. If you paste a description using those tags, they may render unexpectedly or get stripped. The supported heading range is h4 through h6 only. Similarly, links, images, divs, and spans are not in the supported set.
One formatting quirk worth knowing: multiple spaces between words are not reflected on the live book page. If you are using spacing to create visual separation, it will not carry through — use a paragraph tag or line break instead.
On the bracket side, a single angled bracket after text is allowed, but double brackets (<< or >>) and empty brackets (<>) are not. Clean these out before publishing to avoid invisible character issues.
What Amazon Prohibits in Descriptions
Amazon's content policy for KDP descriptions is more specific than most authors realise, and it has tightened up. As of May 2024, reviews, quotes, and testimonials are explicitly prohibited — including lines like "A gripping read — BookBlog.com." If you have seen guides recommending blurbs in your description, those guides are outdated. Remove any you have.
The full prohibited list includes:
- Phone numbers, email addresses, URLs, or physical addresses
- Reviews, quotes, or customer testimonials
- Requests for reviews
- Time-sensitive information (tour dates, seminar schedules, limited-time offers)
- Spoiler information
- Unicode emojis
- Keyword or book tag phrases stuffed unnaturally into the copy
The emoji prohibition catches a lot of authors off guard because many third-party tools and guides still suggest using them as bullet-point alternatives. They are not permitted under official KDP policy, regardless of what you may have seen work in the past.
Fiction Description Formula
A fiction description has one job: make the reader feel something and then make them want to know what happens next. A five-part structure works well for this:
- Hook (1–2 sentences) — Drop the reader into tension, a question, or a situation they cannot ignore.
- Setup (2–3 sentences) — Establish the protagonist, their world, and what they want.
- Conflict (2–3 sentences) — Introduce the obstacle or antagonist that makes getting what they want hard.
- Stakes (1–2 sentences) — Make clear what is lost if they fail.
- Closer (1–2 sentences) — A call to read, a tantalising final line, or a genre signal that confirms this is exactly what their kind of reader picks up.
Given the mobile truncation issue, your hook and setup need to appear within those first 3–4 lines. Front-load the most compelling part of the story — do not bury the stakes at the bottom where most shoppers never scroll.
Non-Fiction Description Formula
Non-fiction buyers are outcome-driven. They are asking "will this book solve my problem?" before they ask anything else. A Problem → Promise → Proof → Push structure maps directly onto that mindset:
- Problem — Name the specific pain point your reader is experiencing. Be precise; vague problems create vague interest.
- Promise — State clearly what transformation or result the book delivers.
- Proof — List 4–6 specific, concrete things the reader will learn or be able to do after reading. This is where a bulleted list earns its character cost.
- Push — A direct, low-pressure call to action. "If you are ready to [outcome], scroll up and grab your copy" is a clean closer that does not beg.
The proof section is where most non-fiction descriptions fall flat. Vague promises ("you'll gain clarity and confidence") move no one. Specific outcomes ("learn the three-step system for pricing services without underselling yourself") give shoppers something concrete to evaluate.
Keywords in Your Description
Your KDP description carries less search weight than your book title and backend keywords — but it is not worthless. Including 3–5 relevant keywords naturally woven into the copy contributes to discoverability without requiring you to sacrifice readability. The operative word is naturally. A sentence that exists only to contain a keyword reads like a sentence that exists only to contain a keyword, and it erodes trust before a sale happens.
Do not stuff keyword phrases at the bottom of the description — the prohibition on "book tag phrases" in the content policy covers exactly that pattern. Integrate your terms as you would in any piece of writing: where they belong, in context. For deeper niche research to inform your keyword choices, browse the KDP niche pages on Pubscout.
How to Add or Update Your Description
The process is straightforward once you know where to look:
- Sign in to kdp.amazon.com
- Go to your Bookshelf
- Click the ellipsis (…) next to the book title
- Select Edit Details
- Modify the Description field (remember: 4,000 characters including tags)
- Click Save and Continue
- Publish from the Pricing page
To inspect the raw HTML of an existing description, go to Bookshelf, click the ellipsis, select Edit details, scroll to the Description section, and click Source. This shows you exactly what markup is live — useful for auditing a description you imported or had written for you.
Testing Your Description
Writing a description is not a one-time event. The first version is a hypothesis, and you should treat it like one. Run changes for at least two weeks with a consistent traffic source before drawing conclusions — shorter windows produce noise rather than signal. Swap one variable at a time: hook versus hook, or closing line versus closing line. Changing the entire description at once makes it impossible to know what moved the needle.
The KDP Royalty Calculator can help you model what a meaningful improvement in conversion rate means in actual royalty terms — sometimes the numbers make it obvious how much a description rewrite is worth prioritising.
The KDP how-to guides on Pubscout cover other levers alongside description — categories, keywords, and pricing — if you want to work through them systematically.
If you want live data while you are evaluating a competitor's page or researching your niche, the Pubscout Chrome Extension shows BSR, estimated monthly sales, and niche data directly on any Amazon book page — useful context when you are trying to benchmark what a good conversion rate looks like in your category.
Common Errors and Fixes
The most frequent description error authors encounter is: "Description may not contain invisible characters." This happens when you copy text from a Word document, Google Doc, or PDF and paste it directly into the KDP editor. Those sources often embed hidden formatting characters that KDP rejects. The fix is straightforward but annoying: type the description manually rather than pasting it. Alternatively, paste into a plain-text editor first to strip hidden characters, then copy from there into KDP.
If you are seeing unexpected rendering on your live page — missing line breaks, collapsed spacing, or garbled formatting — use the Source view in the KDP editor to inspect the raw HTML. What looks clean in the visual editor is not always what gets published. Checking the source before you finalise is a quick habit that saves a lot of re-publishing cycles.