Sentence Counter

How to use this tool

1. Paste your text. Drop in your essay, article, or any block of prose.
2. Press Count. Get sentence count, average length, longest, and shortest.
3. Find the long ones. Search your draft for the longest sentence (the tool tells you its word count). Split or rewrite.
4. Re-count and compare. After edits, paste again to confirm the average dropped to your target.

Why average sentence length matters

Sentence length is the single strongest lever on readability. Short sentences are processed quickly and feel energetic; long ones demand that the reader hold several clauses in mind at once. Readability formulas such as Flesch-Kincaid weight average sentence length heavily, which is why plain-language guidelines for government and legal writing cap the average at around 20 words.

The goal is not uniformly short sentences, which read as choppy, but varied rhythm with a sensible average. A draft can feel dense long before you can point to why. Seeing the average and the single longest sentence in numbers tells you exactly where to cut: find that one 60-word sentence, break it at a conjunction, and the whole passage breathes.

Length also interacts with audience. A general newspaper aims for an average around 14 to 18 words because it serves a wide reading level, while a specialist journal can run longer because its readers expect dense, qualified statements. Knowing your target audience first, then checking your average against it, is far more useful than chasing the lowest number you can.

How the splitting works

The tool scans for terminal punctuation and uses it to mark sentence boundaries, then measures each piece.

Split on            . ! ?   followed by whitespace or end of text
Sentences           = number of resulting pieces
Total words         = sum of words across all sentences
Avg words/sentence  = Total words / Sentences
Longest / Shortest  = max / min word count of any one sentence

This rule catches the vast majority of well-edited English prose. It does trip on abbreviations such as "Mr." and on ellipses, where each period looks like a boundary, so expect a small overcount in text that is heavy with either.

Real-world scenarios where this tool helps

What this tool does

• Splits on terminal punctuation: periods, exclamation marks, and question marks followed by whitespace or end-of-text.
• Reports the sentence count rounded to a whole number.
• Reports total words and average words per sentence to one decimal place.
• Reports the longest sentence in words so you can hunt and fix it.
• Reports the shortest sentence too - one-word fragments can drag the average artificially low.

What it does NOT do

• Does not handle abbreviations gracefully ('Mr. Smith' looks like two sentences).
• Does not detect quoted-speech boundaries with embedded periods.
• Does not score readability - use the Reading Time / Flesch-Kincaid tool for that.
• Does not flag run-ons or fragments; it just counts.
• Does not work for languages without trailing punctuation conventions (CJK, Thai, etc.).

Worked example

Suppose you paste a paragraph of four sentences with 22, 8, 41, and 13 words.

1. Sentences: four terminal marks, so the count is 4.
2. Total words: 22 + 8 + 41 + 13 = 84.
3. Average: 84 / 4 = 21.0 words per sentence.
4. Longest: 41 words; shortest: 8 words.

Target average sentence length by context

Different writing tasks expect different averages. Compare your number against these benchmarks.

Common mistakes and pitfalls

• Pasting text with ellipses (...) and getting an inflated count - each `.` triggers a split.
• Treating average sentence length as a readability score by itself; the Flesch-Kincaid grade combines it with syllable counts.
• Forgetting that bullet-list items often lack terminal punctuation and may be undercounted.
• Pasting from Word with hidden non-printing chars that prevent the splitter from firing - the count looks weirdly low.
• Reading abbreviation-heavy text (Mr., Dr., e.g.) and seeing a count 2 to 5 percent too high.
• Chasing a low average so hard that the prose turns choppy; vary length around the target instead.

Related tools

Frequently asked questions