WebToolArcExact encoding size with newline and normalization context
UTF-8 bytes, UTF-16 payload bytes, CRLF/LF/CR sequences, LF-normalized size, and NFC byte deltas are kept distinct so transport/storage size is not confused with visible characters.
Home / Text Counting & Analysis Tools / Text Byte Counter
Text Counting & Analysis Tools
Text Byte Counter
Measure encoded text size locally and distinguish bytes from code points and user-perceived characters.
0UTF-8 bytes
0Grapheme characters
0Unicode code points
0UTF-16 code units
0.00 bytes / characterUTF-8 byte count uses TextEncoder on the exact text above.
Counts run locally in your browser. When available, word, sentence, and grapheme segmentation uses the browser’s Unicode-aware Intl.Segmenter; fallback rules are used on older browsers.
Core counting & writing metrics
Start with the broad counter that matches the question, then move to focused frequency, reading-time or syllable analysis. Specialist readability, repetition and writing-goal tools remain available from the full hub.
Word CounterWords, characters, structure & reading timeCharacter CounterCharacters, code points & limitsSentence CounterSentence count & average lengthParagraph CounterParagraph blocks, words & linesLine CounterLogical, empty & non-empty linesWord FrequencyTop terms & vocabulary diversityReading TimeWords to minutes at a chosen WPMSyllable CounterSyllable estimate & density
Use this result with confidence
Character count and byte count answer different questions
Unicode text can use one visible character but multiple UTF-8 bytes, and some visible graphemes contain several code points. Use byte count for storage, protocol, and payload limits; use character or grapheme count for user-facing length rules. Do not substitute one metric for the other when validating an external specification.
Normalize text only when the receiving system does
Visually identical Unicode can have different underlying code-point sequences and therefore different byte lengths. If an API, database, or signature process applies NFC or another normalization form, measure the normalized value too. Otherwise preserve the exact input and report the original byte sequence as the authoritative payload.
Watch line endings and invisible characters
CRLF versus LF changes byte counts, as do tabs, zero-width characters, and non-breaking spaces. When a payload is unexpectedly large, inspect the analysis for whitespace and invisible content instead of assuming the visible text explains every byte. Copying through different editors can also change line-ending conventions.
Verify hard limits with the exact encoding path
A browser UTF-8 count is useful, but a real system may add JSON escaping, headers, delimiters, compression, or a different encoding. For a strict request or database limit, serialize the final payload exactly as the destination receives it and compare that byte count with this analysis before sending.