Hitting a 280-character X/Twitter limit, a 160-char SMS, a 155-char SEO meta description, or a 100-word LinkedIn intro. Word-budgeting an essay, blog post, abstract, or grant application against a hard limit. Estimating how long a script will take to read aloud (podcasts, presentations, voice-overs). Spotting overused words by looking at the "most frequent" list before submitting. Checking whether a translation came in roughly the same length as the source.

Sentence detection is naïve. "Mr.", "U.S.", "e.g.", "3.14", and ellipses can inflate the sentence count. The figure is a useful estimate, not a guarantee. Twitter/X counts code points, not characters. A flag emoji (🇸🇰) is 2 code points but renders as one symbol — Twitter treats it as 2 characters. This tool matches that. SMS character limits depend on encoding. Plain ASCII fits 160 chars per segment; once you include a non-GSM character (em dash, smart quote, accented letter), the whole message switches to UCS-2 and the limit drops to 70. The tool reports the GSM limit; check your provider's behaviour for the actual cost. Word counts vary by tool. Word, Google Docs, and journal-submission systems can disagree by a few percent — they handle hyphens, em dashes, and numbers differently. If a hard limit matters, count in the same tool the gatekeeper uses. "Most frequent" doesn't filter stop words. "the" and "a" almost always top the list. Look at the longer entries for actual signal. Reading-time estimates are personal. 250 wpm is the median; technical content runs slower, fiction faster. Treat the number as a planning guide, not a prediction.

Compteur de Mots

Comptez mots, caractères, phrases, paragraphes et estimez le temps de lecture et de parole en direct.

Entrée

Résultat

Words

Characters

Characters (no spaces)

Sentences

Paragraphs

Lines

0:00

Reading time

0:00

Speaking time

What is this for?

Counting words and characters by hand is tedious and error-prone, but the numbers matter all the time: tweet limits, SMS segments, essay word counts, SEO meta descriptions, journal submission lengths. This tool gives you live counts as you type — words, characters (with and without spaces), sentences, paragraphs, lines — plus reading and speaking time estimates and a quick word-frequency pass for the top five recurring words.

When to use it

Hitting a 280-character X/Twitter limit, a 160-char SMS, a 155-char SEO meta description, or a 100-word LinkedIn intro.
Word-budgeting an essay, blog post, abstract, or grant application against a hard limit.
Estimating how long a script will take to read aloud (podcasts, presentations, voice-overs).
Spotting overused words by looking at the "most frequent" list before submitting.
Checking whether a translation came in roughly the same length as the source.

What each number means

Words — runs of non-whitespace characters separated by whitespace. "Twenty-one" counts as one word; "twenty one" counts as two.
Characters vs characters (no spaces) — both count Unicode code points, not bytes. An emoji can be 1–2 "characters" here but more bytes when stored.
Sentences — segments ending in ., ! or ? (or end-of-text). Heuristic, see gotchas.
Paragraphs — separated by blank lines.
Reading time assumes 250 wpm (silent adult reading).
Speaking time assumes 130 wpm (typical conversational pace; news readers run faster, audiobooks slower).

Common gotchas

Sentence detection is naïve. "Mr.", "U.S.", "e.g.", "3.14", and ellipses can inflate the sentence count. The figure is a useful estimate, not a guarantee.
Twitter/X counts code points, not characters. A flag emoji (🇸🇰) is 2 code points but renders as one symbol — Twitter treats it as 2 characters. This tool matches that.
SMS character limits depend on encoding. Plain ASCII fits 160 chars per segment; once you include a non-GSM character (em dash, smart quote, accented letter), the whole message switches to UCS-2 and the limit drops to 70. The tool reports the GSM limit; check your provider's behaviour for the actual cost.
Word counts vary by tool. Word, Google Docs, and journal-submission systems can disagree by a few percent — they handle hyphens, em dashes, and numbers differently. If a hard limit matters, count in the same tool the gatekeeper uses.
"Most frequent" doesn't filter stop words. "the" and "a" almost always top the list. Look at the longer entries for actual signal.
Reading-time estimates are personal. 250 wpm is the median; technical content runs slower, fiction faster. Treat the number as a planning guide, not a prediction.