THE PRACTICAL GUIDE · NORMANDIN SYSTEMS
Get more from Text statistics
Text Statistics measures a passage entered in one multiline field and automatically displays counts for characters, words, sentences, lines, UTF-8 bytes, unique words, and several character categories. It also estimates reading time. The workspace reports properties of the input; it does not transform the document or provide a replacement text result. These counts are useful only when their definitions match the question you are asking. A character limit, a byte limit, and a word limit can produce different outcomes for the same passage. Use a controlled short example first, then compare the relevant statistic with the rules of the application, editor, or publishing workflow that will receive the text.
Guide updated October 13, 2026
How to use this tool
- Paste the passage into the multiline text field. Start with Hello world to reproduce the simple example below.
- Read Character count, Word count, Line count, and Byte size. They measure different properties and update automatically as the text changes.
- Inspect the additional statistics, including unique words, case-insensitive unique words, reading time, and character-category counts when those are relevant.
- Compare the chosen metric with the destination's actual counting rule. There is no document-conversion step or transformed output to download.
SEE IT IN PRACTICE
A worked example
Hello world
Character count: 11; word count: 2; line count: 1; byte size: 11 bytes
The space contributes to character and byte counts. Each character in this ASCII example occupies one UTF-8 byte and one JavaScript string code unit, so those two measures happen to agree.
Characters, code units, and bytes are distinct
The visible letter e, an accented character, and an emoji can have different underlying representations. A sequence that looks like one symbol can contain multiple Unicode code points, and a supplementary code point uses two UTF-16 code units in a JavaScript string. UTF-8 byte size is another encoding-dependent measurement. When enforcing a platform limit, reproduce that platform's rule instead of assuming any field labeled characters has the same semantics as this counter.
Counting rules can change the interpretation
Whitespace-separated tokens are convenient for many passages but do not provide language-aware word segmentation for every writing system. Removing punctuation before a unique-word comparison can join parts that were separated by punctuation, while lowercasing can merge case variants. Sentence counting likewise uses a punctuation-based heuristic rather than a grammar parser. Test a short passage containing mixed case, a blank line, punctuation, and a non-ASCII symbol to learn the model before interpreting a large document's numbers as a quality measure.
When this tool is useful
- Compare a draft against a known word or character limit
- Explore how Unicode changes byte and character counts
- Inspect unique-word and whitespace behavior in a short passage
Tips for a better result
- Character count uses JavaScript string length, which counts UTF-16 code units rather than user-perceived symbols. Some emoji therefore count as more than one.
- Byte size uses UTF-8 encoding. Accented letters and emoji can require several bytes even when they appear as one symbol.
- Treat sentence count and reading time as mechanical estimates. They do not assess grammar, comprehension, or the difficulty of technical content.
Frequently asked questions
Why does an empty field still have one line?
The implementation splits the input at CRLF, CR, or LF line endings. Splitting an empty string leaves one empty segment, which this tool counts as one line. Other counters may define an empty document differently.
How are words and unique words counted?
The ordinary word count splits trimmed text on whitespace. Unique-word counts first remove Unicode punctuation, then compare the resulting tokens. The case-insensitive unique count additionally lowercases them, so it can differ from the case-sensitive count.
How is reading time estimated?
The tool uses the punctuation-stripped word count and a fixed rate of 200 words per minute. It does not inspect topic complexity, audience familiarity, pauses, or whether the passage is read aloud.
What happens to the information I enter?
The utility processes your input in this browser. Some tools retain field values in browser storage or the URL; avoid entering secrets in shareable fields. Page and asset requests still go to the hosting provider. Read the privacy and offline-use notes for details.