Unicode Segmentation Inspector
Inspect browser grapheme, word or sentence boundaries with original UTF-16 source offsets.
Loading tool…
How to use Unicode Segmentation Inspector
See where your runtime divides text without silently rewriting it. The report preserves each segment, its start index and word-like status when available.
- Enter input, locale.
- Choose the settings for unicode segmentation inspector, then run the tool.
- Review the result and any limitations before copying or downloading it.
Good to know
- 20,000 source characters and10,000 segments. Input must be well-formed Unicode; offsets are UTF-16 units.
- This is runtime segmentation evidence, not language detection, a pinned UAX29 conformance claim or a font-width measurement.
- Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.
Common questions
Why can two browsers disagree?
Their internationalization data and segmentation support can differ. The report records the resolved locale and runtime caveat.
Is this input sent to a server?
No. The application processes this input inside your browser tab and does not save it to persistent storage.
Keep going with related tools
All text →Character Counter
Measure visible characters, Unicode code points, UTF-16 length, and UTF-8 bytes without uploading text.
TextWord Counter
Count words, visible characters, sentences, and lines locally, with Unicode-aware word boundaries.
TextUnicode Code Point Converter
Convert text to U+ values or Unicode escape notation and decode valid scalar-value tokens back to text.
EducationVocabulary Coverage Reviewer
Compare a reading passage with your own vocabulary list and inspect covered tokens and unknown-word evidence.
TextLocalization String Budget Reviewer
Check keyed translations against your declared grapheme, UTF-8 byte and logical-line budgets.
TextPrintf Translation Argument Checker
Compare a restricted printf source/translation argument contract without running either format string.