TEXT & DATA

Word Counter

Count words, visible characters, sentences, paragraphs and lines, then inspect reading time, speaking time and repeated words. The text stays in your browser.

WORD COUNTER

Write or paste text

Live Unicode-aware statistics. Nothing is uploaded.

Browser-local
0 / 250,000 characters

FREQUENCY

Top words

Unicode segmentation

Start typing to see word frequency.

What this counter measures

Words use Unicode-aware segmentation where the browser provides it. Characters are counted as grapheme clusters, which is closer to what a person sees than JavaScript string length for accents, combining marks and joined emoji. A separate code-point count is kept in the engine for diagnostic clarity.

Reading and speaking time

The default estimates use 200 words per minute for reading and 130 words per minute for speaking. Change either rate in the workbench if your audience or delivery pace is different.

Word frequency

The ten most frequent words are ranked by a normalised Unicode form while preserving a readable form for display. Frequency percentages use the full detected word count as the denominator.

Privacy and limits

Core counting is browser-local. PBT does not upload, persist or include your text in analytics payloads. Input is capped at 250,000 characters to keep the interface responsive on ordinary devices.

Frequently asked questions

Does it work with non-English text?

Yes. The engine is Unicode-aware and is tested against Latin text, accents, apostrophes, hyphens, Arabic, Hebrew, CJK, combining marks and joined emoji.

Why can character count differ from code length?

A visible character may contain several Unicode code points or UTF-16 code units. This tool reports grapheme clusters as characters because they better reflect what users see.

What standard does it follow?

The segmentation policy is anchored to Unicode Standard Annex #29. Browser implementations may use their shipped Unicode/ICU version; the fallback path has explicit deterministic compatibility semantics.

PALLAS / SUPPORT

Report an issue

Tell us what went wrong. Technical context is attached automatically; your files and tool inputs are not.

Your email is required so we can follow up on this report. Do not include passwords, confidential files or sensitive source content. Privacy