Grapheme Cluster Inspector
Process grapheme cluster inspector locally with complete copy/download and explicit rules.
Enabling local controls…
Results
Review the settings and run. Editing inputs clears old results.
Processing model and limits
Use native Intl.Segmenter extended grapheme clusters and report every cluster, code points, UTF16 start/length and UTF8 byte counts/hex. Includes Unicode17 primary Script counts; Common/Inherited/Unknown do not increase the mixed count. Mixed scripts can be normal and are not a security verdict. ≤4096 graphemes. Runtime Unicode data may vary; a grapheme is not necessarily a rendered glyph, terminal cell, letter, syllable or cursor step in every application. Original normalization remains unchanged. JSON uses Unicode escapes so clipboard normalization cannot change code points. Each text field is limited to 32 KiB; complete output to 1 MiB. Runs in a one-second local Worker, with no network requests.
Data and model checked: ToolHubEN source controls ↗UAX29 grapheme clusters ↗
How to use this tool
Load the example, confirm field units and processing rules, then run locally. Editing any input clears the old result. Copy or download the complete output explicitly.
When not to use it
Use native Intl.Segmenter extended grapheme clusters and report every cluster, code points, UTF16 start/length and UTF8 byte counts/hex. Includes Unicode17 primary Script counts; Common/Inherited/Unknown do not increase the mixed count. Mixed scripts can be normal and are not a security verdict. ≤4096 graphemes. Runtime Unicode data may vary; a grapheme is not necessarily a rendered glyph, terminal cell, letter, syllable or cursor step in every application. Original normalization remains unchanged. JSON uses Unicode escapes so clipboard normalization cannot change code points. Each text field is limited to 32 KiB; complete output to 1 MiB. Runs in a one-second local Worker, with no network requests.