What is the Amazon product description character limit?
Amazon staff guidance for retail descriptions uses a maximum of 2,000 characters. The current Product descriptions help page describes this as a text-only field and says character limits vary by product category. Treat that as a useful starting reference, then confirm the current requirements of your actual field and category. Read the Amazon staff guidance.
A product title, retail description, KDP book description, bullet field, and backend search-term field are separate inputs. A number copied from a guide to one of them is not automatically the rule for another. Even a familiar retail-description number should be checked against the marketplace, product type, category guidance, and current input validation.
For an ordinary product description, first open the field in your current listing workflow. Check its help text and validation, then consult the applicable category or product-type instructions. Keep the field’s label and the source of the limit together in your notes.
Visible text, HTML source, and platform limits
- Visible text: the words and spaces a person reads in the editing canvas.
- Source length: the literal representation you copy, which can contain tags, entities, and line-break notation.
- Destination count: what the receiving platform actually validates. Confirm its definition instead of assuming it matches either local count.
For a specific example of a separate system, KDP documents a 4,000-character book-description limit and includes HTML in its count. That is a book-field rule; it should not be transplanted to a retail listing description.
Count HTML tags and escaped characters: worked examples
These examples use ASCII characters so the arithmetic is unambiguous. Spaces are included. They demonstrate source overhead, not a universal platform-counting specification.
Daily carry 11 visible characters / 11 source characters <p>Daily carry</p> 11 visible characters / 18 source characters <strong>Daily carry</strong> 11 visible characters / 28 source characters
The paragraph version adds seven source characters around the same eleven visible characters. The strong-emphasis version adds seventeen. Repeating that structure through a long draft increases source overhead even though the text itself has not grown.
Why can an ampersand use five source characters?
Visible text: Care & fit Literal HTML: Care & fit Visible length: 10 Literal length: 14
The source & represents an ampersand. Copying the source string and copying the rendered text therefore produce different lengths. A destination may normalize what it receives, so compare its actual count rather than assuming it always checks a raw string.
Check description length with text and HTML counters
The export panel shows Output text and HTML source together. A third value below the preview gives the exact length of the selected output: plain text, line-break HTML, or filtered editor HTML. These counts use Unicode code points and include spaces and LF newlines.
For example, 😀 counts as one code point, é as two, and 👩💻 as three. A visible character can therefore occupy more than one code point. These are not UTF-8 byte counts, UTF-16 code-unit counts, or a promise that the destination uses the same rule. The original editor word counter remains available and can use a different unit.
Paragraphs and list items become separate lines in the text export. Explicit inner blank lines stay; outer blank lines are removed. Ordinary HTML whitespace is normalized, and nonbreaking spaces become spaces. Line-break HTML escapes ampersands and angle brackets before replacing each LF with <br>. That source can be longer than the plain text.
Choose a format to review the actual string, then use its matching Copy button. If browser permission blocks copying, the panel selects the output for manual copying. Neither changing the output nor copying modifies your draft. No category limit is automatically selected or imposed; check the field’s current validation separately.
Shorten product descriptions without losing key facts
- Remove repetition first. Keep one clear explanation instead of several versions of the same promise.
- Replace vague praise with a fact. A measurement or compatibility condition is more useful than a long string of adjectives.
- Keep the exclusions. Do not delete fit limitations, included quantities, or care restrictions merely to make a counter pass.
- Simplify unnecessary source structure. Only where the destination accepts the resulting representation, remove redundant wrappers and repeated blank lines.
- Recheck after saving. Confirm that the platform accepted the final version and the information still reads coherently.
Use the template guide when the problem is organization rather than length. Use the HTML guide when unsupported formatting is the cause.