Format a KDP Book Description With Allowed HTML

The paperback is ready, but the store description box rejects half your paste because of illegal tags, and you are not sure whether bold even survived. KDP Description Formatter turns plain text into the small set of HTML tags a book-store description typically accepts—or cleans existing HTML by keeping allowed tags—and shows a preview plus a 4,000-character length check.

This guide covers one job only: write or clean the description, preview it, copy HTML into the store, and re-check the store’s own preview before publish. Draft longer manuscript work in Book Writing Toolbox, count words with Word Counter, and convert other markup with Markdown HTML Converter. Category: text tools.

What stores usually allow

Amazon KDP commonly accepts paragraphs, line breaks, bold, italic, underline, headings h4–h6, and bulleted or numbered lists. Stores change rules—always use the store preview. In plain-text mode: blank line starts a paragraph; lines starting with - become bullets; 1. starts a numbered list; # a heading; bold, italic and underline work inline. Clean mode keeps allowed tags, turns divs into paragraphs, maps large headings down, and strips styles, classes, links, images and scripts while keeping text.

Worked example: mystery novel blurb

An indie author pastes a three-paragraph blurb with a bullet list of tropes. Plain text to HTML produces clean paragraphs, a short bullet list and a bold first line. The character counter shows 1,240 of 4,000. They copy HTML into KDP, then verify bold and lists in Amazon’s preview. A second pass cleans an old Word-exported HTML full of span styles.

Steps on KDP Description Formatter

1. Open KDP Description Formatter.
2. Choose Plain text to HTML or Clean existing HTML.
3. Paste the blurb or the messy HTML.
4. Use markdown-like markers for bold, lists and headings in plain mode.
5. Read the preview as a reader would.
6. Watch the HTML length against the 4,000-character guidance.
7. Review the change list when cleaning HTML.
8. Copy the HTML into the store description field.
9. Confirm formatting in the store’s official preview.
10. Save a plain-text source copy so future edits stay clean.

Common mistakes

• Pasting Word HTML with tracked changes and inline styles straight into KDP.
• Writing past 4,000 characters and discovering truncation after publish.
• Using h1/h2 thinking bigger is better when stores prefer smaller heading tags.
• Putting live links or images into a description that strips them.
• Skipping the store preview and trusting only the tool preview.

Limits and good to know

The tool follows a common allowed-tag set; marketplace policies can change without notice. It does not publish to KDP for you. Among FreeDailyPro’s 300+ professional tools, premium applications and workflow products it supports the publishing handoff, not the whole book pipeline—use Book Writing Toolbox for manuscript work. Where downloads count toward the daily allowance, expect 10 trial usages for kdp description formatter, then a day pass or monthly options when you need more.

Edge cases

Translated descriptions: keep HTML structure identical across languages where possible. Series books: reuse a cleaned template and swap the hook line. Box sets: watch the character budget carefully for multi-book blurbs.

Blurb structure that sells the click

Bold hook line, two short paragraphs of stakes, then a short bullet list of reader promises. End before you spoil the ending. Read it aloud once before you convert.

Series and edition notes inside the limit

Series books burn characters fast if every blurb repeats the entire series pitch. Keep a shared 400-character series spine paragraph, then write a unique 600–900 character hook per title. Clean mode is useful when you paste from a web page that injects tracking spans—review the change list so you know what disappeared. Never rely solely on the in-tool preview; marketplace previews apply their own CSS and may collapse extra breaks.

Mobile preview pass

Most store browsers show descriptions on phones first. After pasting HTML, open the store preview on a narrow window and ensure the bold hook is visible without scrolling past a wall of list items.

Keywords versus description

The description is prose for humans; backend keywords are a separate field. Do not stuff the HTML with comma lists of search terms—that reads as spam and wastes the 4,000-character budget. Use the formatter for readable paragraphs and lists, then handle keywords in the store’s keyword boxes.

Edition differences

Hardcover, paperback and ebook descriptions can share a spine paragraph but should note format-specific bonuses (large print, audiobook codes) only on the matching page. Clean HTML once, then fork the last paragraph per format.

Avoid pasting emoji-heavy blurbs if the store strips them inconsistently. Prefer words. If you clean existing HTML from a previous retailer, read the change list carefully—links and inline styles will disappear by design.

Keep a plain-text source of record for every live description. HTML in the store is a rendering, not your manuscript of marketing copy.

Test the blurb on three screens

Open the store preview on a desktop, a phone and a narrow browser window. Check that the bold hook is visible at the top, that bullet lists render as lists, and that no paragraph has collapsed into its neighbour. The tool preview is a guide, but the store applies its own styles, so the final judgement belongs to the store preview you see just before you publish.

Edit the plain-text source, not the HTML

When you want to change a line later, edit your plain-text source and convert it again. Editing the HTML inside the store box by hand is how stray tags and unclosed paragraphs appear. Keep the source file in the same folder as the book files and add the date to its name.

Next step

Clean HTML is boring in the best way: it survives the store box and still looks intentional. Open KDP Description Formatter, convert or clean your blurb, and verify in the store preview.

Would A/B blurb slots or series-template packs help your catalogue? Share ideas at contact.