Measure UTF-16 units, Unicode scalars, grapheme clusters and UTF-8 bytes, inspect exact offsets and check an optional length budget.
A quick decision brief for this specific tool
Text source
Complete JSON report
A dedicated interactive panel for this data format or operation
Choose your path
Measure UTF-16 units, Unicode scalars, grapheme clusters and UTF-8 bytes; compare optional normalized copies and a user-selected budget without truncation.
Measure storage or transport size without confusing bytes with characters.
Analyze A + emoji + decomposed accent, compare UTF-8 and UTF-16 budgets and inspect exact offsets.
Sees 8 bytes, 5 UTF-16 units, 4 scalars and 3 graphemes with a unit-specific budget verdict.
Explain normalization and combining sequences.
Compare original, NFC and NFD copies while keeping source metrics visible.
Normalized offsets are distinguished from original source and no input is silently rewritten.
Retain BOM, CRLF and a complete long-string measurement record.
Import UTF-8, inspect 220 units with pagination, export JSON and restore an earlier run.
Preview limits do not discard units and a newer unsaved draft remains recoverable.
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.
Tools you might need next
Reverse Unicode grapheme clusters or scalars, preserve line delimiters when selected and inspect exact source-to-output mappings before exporting.
Inspect sentence or line candidates with language-aware segmentation, word/scalar/grapheme lengths, source offsets and complete JSON review reports.
Count vowel and consonant letter clusters with explicit ASCII or canonical Latin-base rules, configurable Y and visible unclassified text.
UTF-8 encoding uses TextEncoder; graphemes use runtime Intl.Segmenter. Source byte totals do not add a BOM or protocol framing.
Optional canonical normalization affects analyzed metrics only. Source metrics remain original; table ranges are zero-based UTF-16 indices in the analyzed copy.
Source is bounded to 100,000 UTF-16 units, report to 4,000,000, and worker runtime to 10 seconds. Errors refuse partial reports; export needed results before leaving.
Updated: August 2026
Measure storage or transport size without confusing bytes with characters. Analyze A + emoji + decomposed accent, compare UTF-8 and UTF-16 budgets and inspect exact offsets.
Explain normalization and combining sequences. Compare original, NFC and NFD copies while keeping source metrics visible.
Retain BOM, CRLF and a complete long-string measurement record. Import UTF-8, inspect 220 units with pagination, export JSON and restore an earlier run.
Choose the unit used by the actual destination; do not infer social or database limits from a generic character count.
Use the indicated analyzed-copy offsets and retain the original file.
Measure UTF-16 units, Unicode scalars, grapheme clusters and UTF-8 bytes, inspect exact offsets and check an optional length budget.
