Text workspace
Type, paste or import a text file. Counts update instantly.
0 graphemes · 0 bytes
Select text for selection stats
0Graphemes
0Code points
0No spaces
0Words
0UTF-8 bytes
0Lines
Characters are not one universal unit. Compare grapheme clusters, Unicode code points, UTF-16 units and UTF-8 bytes, then inspect limits, SMS segments and invisible characters without sending your text anywhere.
Type, paste or import a text file. Counts update instantly.
It depends on the system. A browser string can count UTF-16 code units, an API may enforce a UTF-8 byte limit, Unicode defines code points, and a reader usually perceives grapheme clusters. That is why two counters can disagree without either being broken.
A user-perceived character. A letter plus a combining accent or a multi-person emoji sequence can remain one grapheme.
A Unicode value such as U+0041. A visible symbol may contain one code point or several joined code points.
Storage and network limits often care about encoded bytes. UTF-8 uses one byte for ASCII and more for many other characters.
All analysis in this standalone build runs in your browser. SMS segmentation is a standards-based estimate rather than a carrier billing guarantee. Locale-aware word segmentation depends on browser support, and Unicode rendering can vary by font and operating system.