How to Count Words, Characters and Reading Time

What counts as a word

The standard definition is simple: a word is any sequence of non-whitespace characters. "well-known" is one word, "123" is one word, and "don't" is one word. Everything else - commas, dashes glued between words, URLs - follows the same rule: no whitespace, one word.

Where tools differ is the exceptions they add. Some counters split on punctuation as well as whitespace (making "well-known" two words); some ignore numbers entirely; some exclude markdown or code. If your target platform has its own counter, use that counter as the final word - this tool's whitespace rule is the most common convention, but the platform's rule wins.

Hitting exact limits

Limits come in three shapes, each with a different strategy:

• A ceiling ("max 200 words"): trim from the end of your draft, one clause at a time, checking the counter as you go. Cutting whole sentences at the end loses less than shaving words throughout.
• A range ("500-600 words"): draft to the middle (~550), then expand or cut toward the bound. Writing to the floor and padding upward reads worse than writing to the ceiling and trimming.
• A character limit (titles, statuses, SMS): characters and words are different budgets - 15 words can be 90 characters with long words. Count characters separately, and leave room for anything the limit includes but the counter does not (handles, links, mentions).

Reading time, properly estimated

Reading-time estimates multiply word count by a pace. The commonly used paces: 200-250 words per minute for straightforward prose (the figure most content platforms use), and 150-200 for dense technical or academic material.

The estimate is only as honest as the pace choice: a 2,000-word article is "8 min" at 250 wpm and "13 min" at 150. If your content is dense, use the slower pace - an undersold read time annoys readers, and an oversold one loses them before the first section.

For mixed content (lists, code, images), treat it roughly as: count the prose, add a flat estimate for each visual or code block (30-60 seconds each), and round up.

More than a number: the document health check

A good counter reports more than words. Sentences per paragraph, average sentence length and paragraph count are cheap proxies for readability: long average sentences often need splitting, and paragraphs over ~8 lines are a signal to break. The character count with and without spaces matters for platform limits that count one way or the other. Ten seconds with these numbers saves a round of feedback later.

Frequently asked questions