Amazon HTML Description: What Actually Renders in 2026

Here is the single answer, checked against Amazon-published pages on 2026-08-07: Amazon announced in 2021 that it would stop supporting HTML tags in the product description on product detail pages, and it has never published a list of tags that remain permitted. Every “but this one tag still works” claim you can find — <br>, </br>, <b>, <ul> — traces back to replies written by other sellers on the Seller Forums, not to Amazon. The supported path to formatted, visual content on a detail page today is A+ Content, and Amazon staff say so on the forums themselves.

That is the whole verdict. The rest of this guide shows the receipts, explains why the </br> myth is so persistent (the answer is in the HTML parsing specification, not in Amazon policy), and gives you the replacement workflow.

Three announcement dates, one policy

Search results for this topic contradict each other on the date — you will see June 2021, July 17, 2021, and July 30, 2021 quoted as “the” cutoff. All three are real. Amazon’s news account, News_Amazon, posted the change more than once, to different forums, with different effective dates. Data checked 2026-08-07.

So the date conflict in the wild is not sloppiness by any one blog. It is three separate Amazon posts being quoted by three separate groups of writers. The rollout was staggered by marketplace, and the last US-facing date in Amazon’s own posts is July 30, 2021.

Two details in those posts matter. The stated reason is identical in each — “to provide security for our customers as well as versatility to list products on non-HTML devices” — which is a rendering-surface argument, not a style preference. And the consequence is spelled out: “if you use HTML tags in one line of a product description, the line might be removed or shown without HTML formatting, depending on the usage of the tag.” Note removed. A stray tag can cost you the whole line, not just its styling.

Does the description field accept any HTML in 2026?

No Amazon-published page says it does. Both US announcements direct sellers to the Product detail page rules help page: “Refrain from using HTML content on detail pages, as outlined on our product detail page rules.” That help page renders only inside Seller Central’s signed-in shell — fetched as a plain document on 2026-08-07 it returns the Seller Central landing page, not the policy text — so its current wording could not be verified from outside an account.

What can be verified from outside is this: across the three announcements and the public help surface, Amazon has never published a permitted-tag list for the product description field. The absence is the finding — a platform wanting to carve out an exception for line breaks had four chances to say so and took none.

The practical reading: treat the description as plain text, and write it so it reads correctly with zero formatting, because that is the only rendering you can rely on.

Tag by tag: the claim, the source, the status

Most articles on this topic repeat seller folklore in the register of policy. Here is each claim with its actual provenance, checked 2026-08-07.

One staff reply is worth quoting in full. In a thread titled “How do I create a product description in bold and italics with line breaks?”, an Amazon moderator answered: “If you are unable to do this with your product descriptions, you may want to look into A+ content, where you have more creative freedom!” Given an obvious opening to say “use <br>,” Amazon named no tag and redirected to a different product.

Why </br> seems to work — it is a parser rule, not a policy

The </br> claim survives because sellers genuinely do paste it and genuinely do see line breaks. The explanation has nothing to do with Amazon.

</br> is not valid HTML. br is a void element; it has no closing tag. But the WHATWG HTML Standard specifies exactly what a parser must do when it meets one anyway. In the “in body” insertion mode, for an end tag whose tag name is br, the specification says: “Parse error. Drop the attributes from the token, and act as described in the next entry; i.e. act as if this was a br start tag token with no attributes, rather than the end tag token that it actually is.” (WHATWG HTML Standard, tree construction, checked 2026-08-07.)

Read that carefully, because it settles the argument. To any browser, </br> is <br>. They cannot have different outcomes on a rendered page. So the widely repeated pairing — “<br> was banned but </br> still works” — is not a rule anyone could implement; it describes a distinction that disappears at the parsing layer.

The likely origin: sellers whose descriptions still broke into lines assumed the odd-looking </br> was the cause, and the tip propagated. If breaks appear in your live description today, the cause is whatever the platform does with your text, not a secret tag allowance.

Formatting a description without HTML

Assume plain text and design for it. The techniques that survive any renderer:

• One idea per sentence. A description read as a single wrapped block is fine if each sentence closes cleanly. Long clauses chained with semicolons are what become unreadable without line breaks.
• Carry structure lexically. Write transitions (“For sizing:”, “In the box:”) that signal sections in words, since they may render as continuous text.
• Move scannable specs into the bullet points, which are the field shoppers actually read.
• Never paste from Word or Google Docs directly. Rich-text editors inject markup you cannot see, and per Amazon’s own wording an unsupported tag can cause the line to be “removed” — silent content loss. Route it through a plain-text editor first.

AMZEditor is a free, no-account browser tool built for that cleanup step — it describes itself as an editor that will “CLEAN messy Word Doc HTML into clean Amazon HTML,” with a live character and word counter (checked 2026-08-07). Be clear about what it earns in 2026: since the description field no longer renders markup, the value is stripping Word’s junk and checking length, not the tags it emits. Copy the readable text, not the markup, when the destination is a Seller Central description box.

A+ Content: the route Amazon actually points you to

For images, headings, comparison tables, and controlled layout, A+ Content is the supported mechanism. From Amazon’s A+ Content page, checked 2026-08-07:

• What it is: “A+ Content is a tool that helps you showcase your products and share your brand’s story on product detail pages by adding videos, enhanced images, customized text placements, shoppable comparison charts, and more.”
• Who can use it: “To use A+ Content, you need a Professional selling account. You also need a Brand Representative or Reseller role assigned to a brand enrolled in Amazon Brand Registry, or have generic products in your catalog.”
• Cost: “A+ Content is free for sellers who meet eligibility requirements.”
• Amazon’s own effect claim, quoted as Amazon states it: “Basic A+ Content can increase sales by up to 8%—and well-implemented Premium A+ Content can increase sales by up to 20%.” Treat “up to” figures as vendor marketing, not as a forecast for your catalog.

The gate is Brand Registry, and it has a hard prerequisite. Amazon’s Brand Registry requirements page states: “To enroll a brand in Brand Registry, your brand must have an active registered trademark or a pending trademark registration,” and that mark “must be a text-based mark (word mark) or an image-based mark with words, letters, or numbers (design mark) from approved government intellectual property (IP) offices.” It also requires that “your brand name must be clearly visible and permanently affixed to your products or packaging in the images you provide during enrollment” — printing, sewing, etching, or engraving qualify; removable stickers and hang tags do not. The Amazon Brand Registry guide covers the enrollment path in detail.

Resellers and unbranded sellers are not shut out entirely — the eligibility sentence includes the “generic products in your catalog” clause — but for most private-label sellers the sequence is trademark, then Brand Registry, then A+ Content. Nothing puts formatting back into the description field.

What the same rule change means for your other fields

The European announcement is worded more broadly than the US ones — “stop supporting the use of HTML tags on detail pages,” not just in the description. Apply the plain-text assumption across the listing:

• Bullet points are plain text. Structure them with word order and punctuation, not markup. Amazon does not publish a single global character cap for them; limits are set per category in the style guides inside Seller Central, which are not publicly readable, so any specific number you see quoted online could not be verified against an Amazon page on 2026-08-07.
• Titles have their own separate constraints, covered in our 75-character title limit guide.
• Search terms are a backend field and were never a rendering surface; markup there is wasted characters.

The through-line for ranking is the same either way: the words matter, the tags never did. See our Amazon listing optimization framework for how the fields work together, and the Amazon SEO guide for the indexing side.

Marketplace and category differences

Two caveats before you generalize one result across a catalog. The rollout dates above differ by marketplace, which is direct evidence that this policy did not land everywhere at once, so verify each store you sell in rather than assuming US behavior. And description length caps are category-specific, living in the Seller Central style guides — a description that fits in one category may be truncated in another. Neither the per-marketplace current state nor the per-category limits could be verified from public Amazon pages on 2026-08-07; both require a Seller Central account to read.

Description formatting checklist

1. Assume the description renders as plain text. If it does not read correctly with zero formatting, rewrite it.
2. Strip all markup before pasting. Route Word or Docs content through a plain-text editor first.
3. Remove any legacy tags still sitting in old listings — per Amazon’s wording an unsupported tag can cause the line to be removed, not merely unstyled.
4. Do not spend time on </br> variants. They are the same token as <br> to every conforming parser.
5. Put scannable facts in bullet points, where shoppers actually look.
6. If you need visual structure, start the Brand Registry path — trademark, then enrollment, then A+ Content.
7. Re-verify per marketplace and per category rather than generalizing from one listing.
8. Record the date you checked. Detail page rules change without a migration notice.

Frequently Asked Questions

Can I use <br> in an Amazon product description in 2026?

No Amazon-published page says you can. The 2021 announcements say Amazon stopped supporting HTML tags in the product description and name no exceptions, and the “<br> still works” claim traces to seller replies on the Seller Forums rather than to Amazon. Could not be verified on 2026-08-07.

Is </br> really allowed when <br> is not?

That distinction cannot exist. The WHATWG HTML Standard instructs parsers to treat an end tag named br exactly as if it were a <br> start tag, so the two forms are identical to any browser. The claim comes from seller forum posts, not from Amazon.

What happens to my old listings that still contain HTML?

Amazon’s announcement states that a line containing an unsupported tag “might be removed or shown without HTML formatting, depending on the usage of the tag.” That means silent content loss is possible, so audit legacy descriptions rather than assuming the tags are simply ignored.

What is the supported way to get formatted content on a detail page?

A+ Content. It requires a Professional selling account plus a Brand Representative or Reseller role on a brand enrolled in Amazon Brand Registry, or generic products in your catalog, and Amazon states it is free for eligible sellers.

Conclusion

One verdict, no hedging: Amazon ended HTML support in the product description in 2021, published no exception list then or since, and points sellers to A+ Content for anything visual. Write descriptions as plain text, audit your legacy listings for tags that could be swallowing whole lines, and put your formatting effort where the platform actually supports it. Data checked 2026-08-07.