Character Counter measures JavaScript string length, alongside a no-whitespace count, whitespace-separated words and lines. That character number is UTF-16 code units, not necessarily the number of symbols a reader sees.
Use an example that exposes the difference
Paste A😀. The current character counter reports 3 characters because the emoji occupies two UTF-16 code units and A occupies one. The Word Counter can report two grapheme characters for the same input. Both measurements have a purpose; the destination field decides which one matters.
For Hello world, the expected results are 11 characters and 10 without whitespace. A newline contributes to string length. Empty text has zero lines here; a final newline after one line creates a second line.
Why one emoji can use 11 positions in a form
A UTF-16 code unit is a storage unit in a JavaScript string. A Unicode code point identifies a component of the text. A grapheme cluster groups components into a reader-facing character, such as a letter with an accent or a joined emoji. These are different measurements, not interchangeable definitions of a form's limit. See MDN's String.length explanation and Unicode's text-segmentation specification.
The following exact strings were checked in this site's existing local Character Counter and Word Counter workspaces. The code-point column was calculated separately; neither counter displays it. No spaces or newlines are included in the samples.
| Sample | UTF-16 units | Code points | Graphemes |
|---|---|---|---|
A😀 | 3 | 2 | 2 |
é (U+00E9) | 1 | 1 | 1 |
é (U+0065 + U+0301) | 2 | 2 | 1 |
👨👩👧👦 (joined family) | 11 | 7 | 1 |
🇮🇳 (India flag) | 4 | 2 | 1 |
For example, a field enforcing a maximum of 10 UTF-16 code units cannot accept the complete family sequence above: it uses 11 units even though Word Counter reports one grapheme. This is an illustrative limit, not a claim about a particular website. Native HTML maxlength measures UTF-16 units; an application's own counter or server can apply another rule. A visually short string is therefore not proof that a submission will fit.
The joined family contains four emoji code points and three zero-width joiners. Do not delete the joiners just to reduce the total: that changes the sequence and can change its appearance. Fonts and devices can also render a sequence differently. Word Counter uses Intl.Segmenter where available; its older-browser fallback counts code points and will not reproduce every grapheme result in this table.
Do not remove spaces merely to pass a limit
The no-spaces figure removes whitespace for counting, but the original text still contains it. A form may count those characters on submission. Likewise, an SMS service or API can use encoded byte length rather than either number shown here.
Compare exact strings
Preserve the same newline style, combining marks and punctuation when reproducing a discrepancy. Two visually identical words can have different internal Unicode representations. MDN's String.length reference explains the UTF-16 measure used by this implementation.
The two accented-letter rows illustrate this: é and e\u0301 can look the same while using one and two UTF-16 units. In the latter notation, \u0301 identifies the combining acute accent; do not paste the six literal escape characters when testing. NFC normalization can turn that specific decomposed pair into U+00E9. Neither counter silently normalizes your input, and normalization does not turn the family emoji into one UTF-16 unit. Do not rewrite identifiers, signed data or names without checking the receiving system's rules.
Diagnose a rejected draft without changing its meaning
- Check whether the destination limits UTF-16 units, code points, graphemes or encoded bytes. Ask for its documented rule when the label only says “characters.”
- Copy the exact plain text, preserving intentional spaces, combining accents and line breaks. Use synthetic examples when reporting a discrepancy.
- Compare Character Counter's UTF-16 total with Word Counter's grapheme total. Neither displayed number is a byte count.
- Shorten the wording deliberately, then check the complete draft in the destination's own field. Its validation and server response decide acceptance.
Use the destination's own validation for its final limit. This page does not promise a particular social platform's current character allowance or automatically rewrite text to fit it.