TEXT WORKSPACE
Word & Character Counter
Inspect text length.
Input is processed on this site only when you run the tool. The application does not save inputs or results.
input.txt
Result result.txt
A little clarity goes here.
Run the tool to see your result.
Result preview
UTF-8 text, at most 262144 bytes per input. Tab leaves the editor. Plain text disables syntax colors. Browser textareas may normalize line endings to LF.
{"count":{"inputMode":"text","options":[]}}{"count":{"input":"Hello world","options":[]}}A QUICK WALKTHROUGH
A familiar workflow,
with room to focus.
Paste UTF-8 text, preserving the line endings you want to count.
Count to see words, code points and UTF-8 bytes.
Read graphemes only when the server has the optional intl capability.
When to use Word & Character Counter
Check text length and the defined word convention before fitting a message into a byte-limited field or documenting a sample.
Read the result
Use the labeled metric: bytes measure UTF-8 storage, code points measure Unicode scalar units, and graphemes can approximate visible clusters only when the optional capability is available.
SEE IT IN PRACTICE
Worked examples
Sample input. A result you can inspect.
Count example
Input
Hello world
Expected result
Hello world has 2 words, 11 Unicode code points and 11 UTF-8 bytes. Grapheme availability depends on the server capability and is labeled in the result.
Formats, limits and common errors
Byte, code-point and visual-character counts can differ. Use the labeled metric required by your target system.
- Words are maximal Unicode letter/mark/number runs; ASCII apostrophes join only when directly between letters.
- This is a defined counting convention, not linguistic segmentation for every language. Emoji and punctuation-only runs do not count as words.
- Code points are not grapheme clusters. Combining sequences can count differently. Graphemes are labeled unavailable when intl is absent.
- Empty text gives zero counts. No normalization or newline conversion.
- Input: 262,144 UTF-8 bytes per text field. Output: at most 524,288 UTF-8 bytes; serialized responses have a separate 1 MiB ceiling. Size/work failures return no partial result.
PHP Unicode-capable regular-expression matching ↗ (opens in a new tab)