KDP Listing Optimization
Mastering Your KDP Book Description HTML Formatting for Indie Author Success
Amazon KDP only allows a small, specific set of HTML tags in your book description — and most guides online get the heading tags wrong. Here’s exactly which tags work, which ones Amazon silently strips, and how to use them to turn browsers into buyers.
A bland, wall-of-text book description costs you clicks. HTML formatting in your KDP description — bolding, line breaks, bullet points — lets you structure your pitch so a browsing reader can actually scan it, rather than bounce off a dense paragraph. It won’t rank your book higher on its own, but it directly affects whether someone who lands on your page actually reads far enough to hit “Buy.”
What KDP Book Description HTML Formatting Actually Is
KDP book description HTML formatting means using a small set of HTML tags inside the Description field on your book’s KDP dashboard. Instead of one plain block of text, these tags let you bold key phrases, italicize a title or an internal thought, break your pitch into short paragraphs, and list benefits as bullet points. In a marketplace with millions of titles, your description is often the deciding factor after the cover — a well-structured one signals professionalism and makes your pitch easy to skim.
Which HTML Tags Are Actually Allowed (Straight From Amazon’s Own Docs)
This is the part most articles on this topic get wrong, including earlier versions of this one — Amazon’s own official KDP help page is the only source worth trusting here, since third-party guides frequently disagree with each other about headings and lists. Here’s what it actually says, tag by tag:
| HTML Tag | Purpose | KDP Allowed? | Notes |
|---|---|---|---|
<b> |
Bold text | Yes | The most useful tag for drawing the eye to a hook, a name, or a benefit while scanning. |
<i> / <em> |
Italicize / emphasize text | Yes | Good for a book title mentioned inline, or an internal thought in fiction. |
<u> |
Underline text | Yes | Use sparingly — underlined text on a webpage often reads as a broken link. |
<br> |
Line break | Yes | Use two in a row (<br><br>) to create a visible blank line. |
<p> |
Paragraph | Yes | Adds a line break automatically after the closing tag — the cleanest way to separate paragraphs. |
<ul> / <ol> + <li> |
Bulleted / numbered lists | Yes | Each list needs the outer <ul> or <ol> tag AND a <li> tag around every item — a common source of broken formatting is forgetting the <li> tags. |
<h4>, <h5>, <h6> |
Section headings | Yes — but only these three | <h4> is the largest, <h6> the smallest. This is the detail most guides get wrong. |
<h1>, <h2>, <h3> |
Larger headings | No | Amazon’s docs explicitly call these out as not supported — use bolded <p> text instead if you need something heading-sized. |
<font>, <span>, <div>, <a>, <img> |
Styling, links, images | No | Silently stripped — you won’t get an error, the tag just does nothing and the text stays but loses the formatting. |
One formatting quirk worth knowing: KDP counts every character of your HTML tags against your 4,000-character description limit. The word “test” is 4 characters; bolded as <b>test</b> it counts as 11. Heavy formatting on a long description can eat more of your limit than you’d expect.
Crafting an Irresistible KDP Book Description: Best Practices
Knowing which tags are allowed is only half the job — how you use them is what actually sells the book. Your description is a compressed sales pitch, and every formatting choice should serve that pitch:
- Open with a hook. Your first line should earn the next one. Bold it if it’s short enough to scan in half a second.
- Name the conflict or the problem. What does your protagonist face, or what pain point does your non-fiction book solve?
- Hint at the payoff. Briefly gesture at how the story resolves or what the reader walks away knowing — without giving away the ending.
- List concrete benefits with bullets. A
<ul>list of what the reader gets is far more scannable than the same points buried in a paragraph. - Break text into short paragraphs.
<p>tags keep the description readable on a phone screen, where most Amazon browsing happens. - Bold selectively. Two or three bolded phrases draw the eye; bolding half the description draws nothing.
- End with a clear next step. A short, specific line — not a vague “click here” — that tells the reader what happens if they buy.
Tools to Simplify KDP Book Description HTML Formatting
You can type the tags by hand, but a few tools make it faster, especially if you’re not comfortable writing raw HTML:
| Tool | Type | What It Does | Cost |
|---|---|---|---|
| KDP’s own Description editor | Built-in | Visual toolbar for bold/italic/lists, with a “Source” view to check the raw HTML it generates. | Free |
| Third-party KDP HTML generators (e.g. Kindlepreneur’s, Author Imprints’) | Online generator | Format visually, then copy out KDP-compatible HTML — useful if you want more control than the built-in editor gives you. | Free |
| Book research tools with a description feature (Publisher Rocket, BookBeam) | Software feature | Bundled into broader keyword/category research tools rather than being a dedicated formatter. | Paid |
If you’re still deciding which research tool to invest in, our Helium 10 Cerebro vs. Publisher Rocket comparison and our Kip Scout vs. KDP Spy breakdown cover the two main decision points most authors face.
Common Mistakes to Avoid
- Over-formatting. Too much bolding or mixed styles makes a description look unprofessional and harder, not easier, to read.
- Ignoring mobile. Preview your description on a phone — long unbroken paragraphs that look fine on desktop often fail there.
- Using unsupported tags.
<div>,<span>, or custom styling get silently stripped, sometimes leaving your layout broken with no error message telling you why. - No clear next step. A description that just stops, with nothing telling the reader what to do, wastes the pitch you just built.
- Writing features instead of benefits. “It has magic” describes the book; “discover a world where magic has a price” sells it.
FAQ: KDP Book Description HTML Formatting
Can I use any HTML tag in my KDP book description?
No. Amazon supports a specific, limited set: <b>, <i>/<em>, <u>, <br>, <p>, <ul>/<ol>/<li>, and headings <h4> through <h6> only. Everything else, including <h1>–<h3>, <div>, <span>, and links, is stripped.
Does formatting help my book rank higher on Amazon?
Not directly — Amazon’s search algorithm weighs keywords, categories, and sales performance, not description formatting. What formatting does is improve the click-to-buy conversion once a reader is already on your page, which can indirectly help sales velocity.
Do I need to know HTML to format my description?
No. KDP’s built-in editor has a visual toolbar, and several free online tools will generate the HTML for you if you want more control than that toolbar offers.
Why did my bullet list or heading not show up?
The two most common causes: forgetting the <li> tags inside a <ul>/<ol>, or using <h1>–<h3> instead of the only headings KDP actually supports, <h4>–<h6>.
How often should I update my description?
Whenever sales are lagging, you’ve picked up new strong reviews, or you’re running a promotion — treat it as a page you revisit, not a one-time task.
Formatting won’t save a weak pitch, but a strong pitch buried in a wall of text won’t convert either. Get the tags right — especially the heading levels most guides get wrong — structure your benefits as a scannable list, and end with one clear next step instead of a vague call to action.
Next step: How to Start KDP