Amazon HTML tags not working? Field rules and fixes

Seller Central, KDP, and A+: which field are you editing?

“Amazon description” can mean an ordinary retail product description, a KDP book description, or rich content created through a separate module. Begin by opening the actual destination. Write down the marketplace, product type, and field name; a screenshot of the field label is a useful reference while you edit.

The current Product descriptions help describes the retail field as text-only. The US product detail page rules restrict code in ordinary detail-page content and list line breaks as a special case. KDP publishes separate book-description instructions. Neither a free editor’s toolbar nor an old tutorial establishes what a particular destination accepts today.

HTML tags: editor support and Amazon field rules

HTML adds structure around words. For example, <b>Daily carry</b> marks emphasis, while <ul><li>One item</li></ul> describes a list. The fact that a browser renders either example does not establish permission to use it in an Amazon field.

The current AMZEditor configuration retains p, br, b, em, ul, ol, li, strong. That is the tool’s own filter. It is intentionally described separately from marketplace rules: the retained set can be broader than the destination permits, and narrower than all formatting options of a different publishing system.

• Paragraphs and lists: inspect whether the destination supports them before keeping the tags.
• Emphasis: a bold-looking word may be HTML, inherited styling, or a special Unicode character. These are different representations.
• Links, images, styles, and scripts: do not treat a description box as a general-purpose web page. The current editor is not an A+ layout builder.

Convert description HTML to plain text or line breaks

Keep an untouched copy first. Then work paragraph by paragraph rather than deleting every tag blindly. Tags can be the only separators between ideas or list entries; stripping them without adding readable spacing can join unrelated words.

<p>Cable organizer</p>
<ul><li>Two compartments</li><li>Zipper closure</li></ul>

A plain-text drafting version could read:

Cable organizer
Two compartments.
Zipper closure.

This example changes representation, not product facts. Recheck that a real item has those features before using the words. When line-break markup is appropriate for your field, an illustrative source representation is:

Cable organizer<br>Two compartments.<br>Zipper closure.

Use the break representation accepted by the actual field and inspect the saved result. In the editor’s export panel, choose Plain text to keep the words and line breaks, or Line-break HTML for escaped text separated only by <br>. The HTML option retains the editor’s filtered markup. Switching output never rewrites the draft. Review the selected preview and the destination rules before copying.

Clean up descriptions pasted from Word or Google Docs

1. Save a backup. Preserve the original words and any formatting you may need to restore.
2. Paste a short section first. Check whether headings, blank lines, bullets, and spacing arrive as expected.
3. Simplify unnecessary styling. In the existing HTML-code workspace, clear formatting if you want a simpler starting point. Rebuild only meaningful structure.
4. Inspect the source. Look for unnecessary nesting, leftover style attributes, encoded brackets, or list tags the destination does not accept.
5. Check meaning again. Ensure a removed bullet or paragraph boundary has not changed an instruction, compatibility condition, or included quantity.

Removing a font is not the same as validating a claim. A clean-looking description can still contain the wrong measurements, an unsupported certification, or an omitted compatibility limitation.

Fix missing formatting and visible HTML tags

Why do HTML tags appear as text?

Check whether you copied code into a field expecting plain text. A second possibility is double encoding: <p> represents escaped bracket text rather than a paragraph element. Inspect the representation before repeatedly repasting it.

Why do spacing and line breaks disappear?

Check the field’s supported formatting and whether the copied representation contains LF newlines or line-break markup. The export panel lets you compare plain text with line-break HTML. Also check whether the draft relied on repeated spaces instead of readable sentences or appropriate breaks. A platform can normalize spacing even when the editor shows a gap.

Why does bold formatting disappear?

Confirm that the destination permits that form of emphasis. Do not work around a restriction by substituting decorative Unicode letters or by guessing new tags.

Why is HTML source rejected as too long?

Compare the exact copied source with the destination’s counter. Tags and entities can make source length differ from visual text. Continue with the character-count guide.

Choose a description editing workflow for your field

Choose the task first: drafting and copying, rule-based conversion, or book publishing. This comparison describes workflows visible on the linked pages checked on 29 Oct 2026. It is not a test of clipboard reliability, conversion quality, or paid plans; no product copy, email, or account details were submitted to those tools.

Workflow fit does not replace field rules. Do not assume every tool uses the same counting unit. If needed, check a short, non-sensitive sample before processing a full draft.

Check the saved description on desktop and mobile

Record which field you checked and keep the version you submitted. After saving, review the actual listing on desktop and mobile. If the result differs, compare a small changed section rather than rebuilding the whole description at once.

For the words themselves, use the product-description templates. For editing, return to the free workspace. This guide describes preparation and verification; it does not submit a listing or certify acceptance.

Sources checked 29 Oct 2026: US detail page rules, Amazon HTML notice, KDP description help, and A+ guidance.

Amazon product description not showing or spaced incorrectly

Why is my Amazon product description not showing?

1. Confirm the exact marketplace, ASIN and field you changed. Keep a copy of the saved draft and any validation message.
2. Check whether the saved value is present in the editing workflow. A rejected save is different from an accepted value that is not visible on the detail page.
3. Inspect the actual page on desktop and mobile. Distinguish the ordinary description from an A+ module; do not assume the same region appears in both layouts.
4. If a saved value remains missing, review listing status and relevant support messages in Seller Central. Provide support with the ASIN, field, marketplace, save time and observed result. This editor cannot diagnose or clear an account-side publishing issue.

Why are there large spaces in an Amazon product description?

Compare three things: empty paragraphs or repeated breaks in the source, spaces or nonbreaking spaces in the text, and spacing added by the destination layout. Preserve a backup, test a short section as plain text, then compare it with line-break HTML only if the field accepts it. Removing every separator can join sentences or list entries; review meaning after cleanup. Do not add CSS to compensate for a field that does not accept it.

Open the product description editor

Open the editor ↗