Compare UTF-16 units, Unicode code points and grapheme clusters. Choose a publishing field to inspect its weighted-character, Unicode or UTF-8 byte rule.
Choose your path
Describe the exact entered text with separately named UTF-16 code-unit, Unicode code-point, grapheme-cluster and non-whitespace counts without claiming a universal platform limit or user-perceived-character guarantee.
See why emoji, combining marks and non-BMP text can produce different counts.
Enter the exact final draft, compare all three character representations and verify the current target composer.
Can reproduce the record without calling one count the universal platform length.
Distinguish JavaScript String.length from code points and grapheme segmentation.
Test ASCII, surrogate pairs, combining marks, ZWJ sequences, whitespace and empty input, then inspect the stated runtime method.
Can identify the exact counting basis and fallback rather than receiving an unexplained “characters” number.
Operate a focused input and understand that counts do not prove clarity or accessibility.
Use the labeled editor, metric cards, copy/save controls and method boundary without a color-only or quota-only verdict.
Can accept, revise or reject the text using the target context and affected-person review.
Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.
This tool is part of these guided projects. Each project provides step-by-step instructions with checklists and all the tools you need in one place.
Prepare one source-led, rights-cleared, accessible, rendered and owner-approved article package without promising ranking, traffic, publication, or audience response.
Prepare one governed social-content release from audience purpose, rights and claim evidence through versioned copy metrics, accessible media, target-channel review, authorization and correction controls.
Tools you might need next
Analyze Unicode scalar or grapheme frequencies with explicit text policies, correct percentages, invisible-character review and complete JSON reports.
Inspect Unicode counts, word frequencies, reading time and English readability in one workspace. Compare a selected publishing field and copy the results.
Count words, Unicode characters, sentences and paragraphs. Inspect English readability, estimate reading time and compare a selected publishing length rule.
JavaScript String.length counts 16-bit UTF-16 code units. A supplementary Unicode code point therefore uses two units.
Array iteration counts code points. Intl.Segmenter with grapheme granularity estimates extended grapheme clusters such as combining sequences and many emoji sequences; the panel discloses when it falls back to code points.
General character counts do not establish a universal platform limit or visible width. Choose a publishing field for the separately named length comparison, then verify the exact destination and final draft.
Updated: September 2026
Compare a plain letter, a precomposed letter, a combining sequence and a ZWJ emoji before handing the exact draft to a target composer.
Save the exact draft and all named count representations into the Social Content Release Record without claiming a universal limit.
Record the required counting convention for an identifier or field and verify encoding, storage, display and truncation in that exact system.
Name it UTF-16 code units and compare code points and grapheme clusters.
Verify current platform documentation and the actual composer for the exact account, format and content.
Paste the exact text you need to inspect. The panel names three different meanings of character instead of collapsing them into one number. Current platforms may count, transform, shorten, normalize or truncate content differently, so verify the final text in the target composer.