The short version: your KDP book description can run to 4,000 characters, and that count includes the HTML tags, not just the words readers see. Paste in a blurb that looks like 3,700 characters on screen and you can still be told it's too long. Or the text goes in and the formatting comes out as something odd.

This article covers how KDP counts, which tags it accepts, what usually goes wrong when you paste from a word processor, and a cleanup routine that takes about ten minutes.

How the KDP book description limit is counted

KDP caps the description at 4,000 characters. Spaces count. Line breaks count. And if you format the description with HTML, every character of every tag counts too.

That last part catches people. A few tag costs, to make it concrete:

  1. A paragraph wrapped in <p> and </p> costs 7 characters of overhead.
  2. A bolded phrase wrapped in <b> and </b> costs 7 more.
  3. A line break, <br>, costs 4 each time.

Say your blurb has 14 paragraphs, 10 bolded phrases and a short bulleted list of 5 items. That's roughly 98 characters for paragraphs, 70 for bold, and around 100 or more for the list wrappers and items. You've spent 270 or so characters before writing a single word. If you're sitting at 3,800 visible characters, you're over.

Most good descriptions are far shorter than the cap anyway. The limit matters mainly if you've pasted in a long series blurb, a stack of review quotes, an author bio, and a "also by" list all in one block.

Why the visible count misleads you

Word processors and most online counters measure what you see. KDP's limit is measured on what gets stored, which is the text plus markup. If you count in one place and submit in another, expect the numbers to disagree. Always do your final count on the version you intend to paste, tags and all.

Which HTML tags a KDP book description supports

KDP's description box accepts a short list of simple tags. As of this writing, the help pages list these:

  1. Text styling: <b>, <strong>, <i>, <em>, <u>
  2. Structure: <p>, <br>, <ul>, <ol>, <li>
  3. Headings: <h4>, <h5>, <h6>

Check KDP's current help page before you rely on this list, because Amazon changes things quietly. But for nearly every blurb, you need only three or four of these: paragraphs, bold for a hook line, italics for a title or a quote, and maybe a short list.

Notice what's missing. There's no <h1>, <h2> or <h3>. There are no <div> or <span> wrappers, no tables, no images, no font or color controls, and no inline styles. Links aren't something to plan on either. If you want readers to find your newsletter or website, put it in the book itself and on your author page.

The two heading sizes people actually use

If you want a visible tagline above the body, <h4> renders as a modest bold heading. It's easy to overdo. One heading, if any, is plenty for a description that's a few hundred words.

What breaks when you paste a blurb into KDP

The most common trouble starts in a word processor. Copy from Word or Google Docs into KDP's editor and you often drag along hidden formatting: span wrappers, style attributes, font names, class names. KDP either strips these, which can change your layout, or leaves them in, where they use up characters.

Here are the usual symptoms and their causes.

  1. Blank lines vanish or multiply. Extra returns in your source become stray <br> tags or empty paragraphs, or collapse entirely. Use real <p> paragraphs and don't stack empty ones for spacing.
  2. Bold or italics appear in the wrong places. A tag was opened and never closed, so formatting runs on through the rest of the description.
  3. The count is higher than expected. Hidden style markup is the usual culprit, or you counted visible characters only.
  4. Odd symbols where punctuation should be. Curly quotes, long dashes and special characters usually survive, but copy artifacts from other apps sometimes don't. Look at the preview before you publish.
  5. Bullets look like plain dashes. You typed a dash or a symbol instead of using <ul> and <li>.

None of these is hard to fix. The trouble is that you often don't see them until the description is live on the product page, because the KDP editor and the final Amazon page don't always look identical.

How to clean your KDP book description in five steps

Do this once and keep the clean version as your master. Each time you change the blurb, change the master and paste again.

  1. Start from plain text. Paste your blurb into a plain text editor, such as Notepad, to strip all hidden formatting. What survives is just your words.
  2. Add only the tags you need. Wrap each paragraph in <p>. Bold your hook line. Italicize book titles. Use <ul> for a list if you truly need one.
  3. Remove anything unsupported. Delete divs, spans, inline styles, font tags and any heading above <h4> or below <h6> in the numbered scale. If something doesn't appear in the supported list, assume it won't help you.
  4. Count the full string, tags included. You want a total comfortably under 4,000, with a little room in case you add a review quote later.
  5. Check the preview, then check the live page. Once the book is published or the update goes through, view the product page on desktop and on mobile.

For step four, you can paste your description into the free KDP Description Checker on Pendrilo, which is built for exactly this kind of check: length against the 4,000 limit, and markup KDP won't accept. It works without an account, so it's a fast sanity pass before you touch the KDP dashboard.

Trimming a long description without gutting it

If the count is over, cut in this order. First, remove markup you don't need: decorative bold, extra line breaks, empty paragraphs. That alone often recovers 100 to 300 characters. Second, move material that doesn't sell the book. Your bio belongs in the Author Central profile, and long review lists work better in the editorial reviews area.

Third, tighten the blurb itself. Readers on a product page see the opening lines first and may never expand the rest, so the first two or three sentences carry the job. Put the hook, the stakes and the genre signal there. Everything after is supporting detail for the people who read on.

A practical target for most novels is somewhere between 150 and 300 words. That's about 900 to 1,800 characters, which leaves generous room for tags. Nonfiction authors sometimes use more, especially with a short bulleted list of what the reader will learn, but you still rarely need to approach the cap.

Keep a version you can trust

Series authors tend to have the most trouble. You'll have a base blurb, a series tagline, a "Book 2 of 5" line, and updates every time a new book launches. Keep each of those as clean text in one file, and assemble the final description from it each time. If you write in Pendrilo Studio, the Publishing Desk has a 4,000-character description counter built in, so you can watch the length while you draft. If you'd like to try it, you can sign up for the beta. Either way, the habit is the same: draft clean, add minimal markup, count the whole string, and preview before you submit.

A quick pre-publish checklist

  1. Total length, tags included, is under 4,000 characters.
  2. Only supported tags remain, and every opened tag is closed.
  3. Paragraphs use <p>, not stacked blank lines.
  4. The first two or three sentences work on their own.
  5. You've viewed the finished product page on a phone.

That last check is worth the extra minute. Many readers see your description on a small screen first, and a stray bold run or a wall of unbroken text shows up there immediately.