321Kit Tools ready in 3, 2, 1.

Text & content / Quick tool

Word & Character Counter

Count words, characters, lines, sentences and estimated reading time locally.

● Processed locally in your browser
Processed locally in your browser
Text statistics Choose an action to process the input.

Processed locally in your browser

Method, example & boundaries

Word & Character Counter: from input to a reviewable result

Measure a draft in one local pass: words, Unicode characters, non-space characters, lines, sentences, and estimated reading time. The counters are shown together so a writer can distinguish a platform character limit from an editorial word target instead of treating them as the same number.

Worked example: a launch note with a blank line

Example input
“321Kit converts files locally. Your document stays on this device.”
Example output
Ten words, two sentences and three lines, because the blank line between the blocks is itself a line, plus the matching character totals.

How to interpret it

Lines come from splitting on line breaks, so a blank line between blocks counts as a line; character counts retain punctuation while non-space counts exclude whitespace.

Unicode-aware text measurement

The browser splits the text on line breaks, CRLF included, counts Unicode code points, matches runs of letters and digits as words, detects sentence-ending punctuation, and estimates reading time from the word count. The input never leaves the page.

Counting boundaries

  • Hyphenated terms, URLs, emoji sequences, and mixed CJK text may be counted differently by another editor.
  • Reading time is a planning estimate, not a measurement of a particular reader.
  • Publisher limits may count UTF-16 units, bytes, or grapheme clusters instead of Unicode code points.

← Back to text workbench