Amazon Backend Keyword Byte Counter
Amazon caps backend search terms at 250 bytes in most categories — not 250 characters. For a seller writing in plain English the two are the same number, which is why the distinction goes unnoticed. For everyone else it is the difference between a field that indexes and a field that silently gets cut in half.
An umlaut costs two bytes. A Japanese character costs three. An emoji costs four. A German seller who fills the field to “250characters” using a normal character counter can be forty bytes over the limit with no warning anywhere in Seller Central — the terms at the end are simply never indexed.
This counts the field the way Amazon counts it, shows exactly which terms would be dropped, and finds the bytes going to duplicates, stop words and punctuation.
Free, no signup, runs entirely in your browser — nothing you type is sent anywhere. Last updated .
135 bytes left of 250.
4 hidden bytes. Your text is 111 characters but 115 bytes, because these characters cost more than one byte each:
- ü × 4 · 2B
This is the reason a character counter tells you there is room left when there is not. Nothing here is wrong — accented and non-Latin characters simply cost more, and your budget has to account for it.
Wasted bytes
29- Punctuation and separators5B
,
Separate terms with a single space. Amazon splits on whitespace already, so commas and semicolons are bytes spent on characters the search engine throws away.
- Stop words8B
forthe
Amazon discards these before matching. They cost bytes and return nothing. This does not apply inside your title or bullets, where they keep the copy readable.
- Repeated terms16B
küchenmaschine
A term is indexed once no matter how many times it appears. Repetition does not raise ranking — it only shortens the field.
- Already in your titleYour call41B
küchenmaschineedelstahlrührschüssel
Your title is already indexed. Backend search terms are for what the title has no room for — synonyms, the misspellings buyers actually type, and use cases. Repeating the title is not penalised, but it spends the field on coverage you already have.
Cleaned field
küchenmaschine edelstahl rührschüssel teigknethaken kitchen mixer standmixer backen
86 bytes · 164 free for terms you are not yet ranking for
The limit varies by category and marketplace. 250 bytes is the documented figure for the majority of categories, but Amazon publishes different values for some, and the field is set per marketplace rather than globally. Check your category style guide in Seller Central and set the limit above to match — the counter honours whatever you enter.
Method
How this is calculated
Byte counting is exact and not open to interpretation. What each byte buys you is where the judgement lives.
- 1
A byte is not a character
Text is stored as UTF-8. Characters in the ASCII range — a-z, 0-9, spaces, hyphens — take one byte each. Accented Latin characters (ä, é, ñ, ü, ß), Greek and Cyrillic take two. Chinese, Japanese, Korean, Hindi and Arabic take three. Emoji take four. This counter encodes your text as UTF-8 and reports the true length, which is the number Amazon enforces against.
- 2
Truncation is silent
Amazon does not reject an over-length field with an error you would notice. It reads up to the limit and discards the rest. Seller Central shows the text you typed, so nothing looks wrong. The only visible symptom is that the listing never appears for the terms at the end — which is indistinguishable from those terms simply being competitive.
- 3
Punctuation is pure loss
Amazon tokenizes on whitespace. Commas, semicolons and pipes are treated as separators and thrown away, but they occupy a byte before they are discarded. Thirty comma-separated terms means thirty bytes spent on characters that never reach the index.
- 4
Repetition adds nothing
A term is indexed once, however many times it appears in the field. Repeating a keyword does not raise relevance for it — the practice comes from search engines that worked that way twenty years ago. Here it only shortens the field.
- 5
Stop words are discarded before matching
Amazon's own style guides list a, an, and, by, for, of, the and with as terms to leave out. They are removed before matching, so including them is a byte cost with a guaranteed return of zero. This applies only to the backend field — in your title and bullets they keep the copy readable for humans, which matters more.
- 6
The field is for what the listing cannot say
Title, bullets and description are all indexed. A term already present in them is searchable without spending backend bytes. The field earns its keep on synonyms, regional names, the misspellings buyers genuinely type, and use cases the visible copy has no room for. That is why this tool flags overlap with your title as an advisory rather than fixing it automatically — dropping it is a strategy decision, not a correction.
Reference
What a byte costs, by script
| Characters | Example | Bytes each | Fits in 250 bytes |
|---|---|---|---|
| English, digits, spaces | wireless mouse | 1 | 250 |
| Accented Latin, Greek, Cyrillic | küche · café · ñ · ß | 2 | 125 |
| CJK, Devanagari, Arabic, Thai | キーワード · 键盘 · कीबोर्ड | 3 | 83 |
| Emoji | 🔥 · ⭐ | 4 | 62 |
The last column is the part worth sitting with. A seller writing English gets 250 characters of backend search terms. A seller writing Japanese gets 83 — a third as much room for the same job, on the same marketplace, against the same limit. Emoji, which occasionally turn up in fields copied from social copy, cost four bytes to contribute nothing at all: Amazon does not index them.
None of this is documented prominently, and every free character counter on the web gets it wrong by not attempting it. If you sell on Amazon.de, .fr, .es, .it, .co.jp or .in and have been filling the field to what a character counter told you, it is worth pasting your live search terms above.
Questions
Backend search terms, answered
How many characters can Amazon backend keywords be?
The question has no clean answer, because Amazon does not measure the field in characters. Backend search terms are capped in bytes — 250 bytes for most categories. In plain English (a-z, 0-9, spaces) one character is one byte, so 250 bytes looks like 250 characters. The moment you use an accented or non-Latin character the two diverge: 'ü' is one character but two bytes, and '日' is one character but three.
What happens if I go over the byte limit?
Amazon truncates the field at the limit and ignores everything past it. It does not warn you, does not highlight the field, and in Seller Central the text still looks saved. The terms are simply never indexed, so the listing quietly fails to rank for them. In some categories an over-length value causes the whole field to be rejected rather than trimmed.
Do I need to repeat words from my title in backend keywords?
No. Amazon indexes your title, bullets and description already, so a term that appears there is searchable without spending backend bytes on it. The backend field is for what the visible copy has no room for: synonyms, the misspellings buyers genuinely type, alternative names for the product, and use cases. Repeating the title is not penalised, but it spends a scarce field on coverage you already have.
Should I separate backend keywords with commas?
No. Use single spaces. Amazon splits the field on whitespace, so commas and semicolons are discarded as separators but still consume one byte each. On a field with thirty terms that is thirty bytes — more than a tenth of the budget — spent on punctuation the search engine throws away.
Does word order matter in backend search terms?
Order does not affect matching within the field, and Amazon combines your terms with words from the rest of the listing to form phrase matches. What order does affect is what survives truncation: if you are near the limit, terms at the end are the ones dropped. Put the terms you most want indexed first.
Do plurals and misspellings need separate entries?
Plurals generally do not — Amazon handles common singular and plural forms from one entry, so including both wastes bytes. Misspellings are different and are worth the space when buyers genuinely type them. So are alternative spellings across English variants, since 'organiser' and 'organizer' are distinct queries.
Writing to a visible field instead? The listing character counter checks titles, bullets and descriptions against Amazon, Walmart, Etsy and eBay limits at once — those fields are counted in characters, so the two tools are not interchangeable.
More free tools
Other calculators
Amazon FBA Fee Calculator
Estimate referral fee, FBA fulfilment fee and net profit per unit from your dimensions, weight, category and price.
ACoS Break-Even Calculator
Work out the ad spend percentage at which a sale stops making money, and the ACoS you need to hit a target margin.
Listing Character Counter
Live character counts for titles, bullets and descriptions against Amazon, Walmart, Etsy and eBay limits at once.
Working out the numbers is the easy half
Writing the listing is the part that takes the afternoon. ListIQ Pro generates the full field set your marketplace asks for, plus product images and video, from one photo. Free plan, no card.