Two counters can look at the same paragraph and disagree by five percent. Neither is broken. They just resolved the same ambiguities differently: whether a hyphenated compound is one word or two, whether numbers count, whether a heading belongs in the body total. If you write to a limit, those decisions matter.
How a Word Counter Actually Decides
Almost every counter, including this one, splits text on whitespace. Any run of spaces, tabs or line breaks acts as a single separator, so double-spacing after a period never inflates your total. What remains between separators is a word.
That simple rule produces the edge cases people argue about. Hyphenated compounds like state-of-the-art contain no whitespace, so they count as one. Contractions count as one for the same reason. Numbers and dates count as words, so 1,500 is one word but 1 500 is two. Em dashes with spaces around them get counted as a word by some tools; this one ignores tokens with no letters or digits, so a stray dash does not pad your total.
Microsoft Word and Google Docs use the same whitespace approach, which is why our totals usually land within a word or two of theirs on ordinary prose. Where they diverge is footnotes, headers and text boxes, which Word can include or exclude depending on a setting most people never open.
Word and Character Targets by Context
Platform limits change. Check the official documentation before you rely on a number for something that matters.
| Where it's used | Target | Unit | What happens at the edge |
|---|---|---|---|
| X post | 280 | Characters | Links always cost 23, whatever their real length |
| LinkedIn post | 3,000 | Characters | Collapses behind "see more" near 210 |
| Instagram caption | 2,200 | Characters | Feed shows roughly the first 125 |
| YouTube description | 5,000 | Characters | Only the first 157 or so reach search results |
| Meta description | 155-160 | Characters | Google rewrites or truncates past the pixel limit |
| Title tag | 50-60 | Characters | Cut by pixel width, not character count |
| Email subject | 40-50 | Characters | Mobile clients clip the rest |
| News article | 300-800 | Words | Inverted pyramid; the lede carries the story |
| University essay | 1,000-5,000 | Words | Ten percent either way is the usual tolerance |
| Novel chapter | 2,000-5,000 | Words | Genre convention, not a rule |
The Truth About Length and Rankings
You will find advice insisting that 1,500 words is the minimum for a page to rank. That number comes from correlation studies, and the correlation is real, but the causation runs the other way more often than the advice admits. Competitive queries tend to need thorough answers. Thorough answers tend to be long. Length is a symptom of covering the topic, not the cause of ranking.
Google's own guidance is explicit that there is no preferred word count. A 400-word page that answers the question completely will outrank a 2,000-word page that buries the answer under preamble. If you find yourself adding paragraphs to reach a number, you are making the page worse.
The practical use of a word count target is different: it tells you whether you have researched enough. If a topic keeps producing 300 words no matter how hard you try, you probably do not know it well enough yet to publish.
Reading time is a rough estimate, not a measurement
Our reading time uses 238 words per minute, an average from silent reading studies of general prose. Technical documentation with code samples reads far slower, often 100 to 150 words per minute. If your content is dense, divide your word count by 150 for a more honest number.
Reaching a Word Count Without Padding
Padding is obvious to readers and to editors. These additions carry their own weight, so the piece gets longer because it got better.
Develop one example properly
A worked example with real numbers, showing what went in and what came out, is worth more than three sentences asserting the same point. It also tends to run 150 to 200 words on its own.
Show the exception
Every rule you state has a case where it fails. Naming that case and explaining why builds trust faster than another supporting argument, and it is the part readers remember.
Explain the mechanism, not just the outcome
Most writing stops at what happens. Explaining why it happens is usually the missing paragraph, and it is what separates a summary from an article.
Answer the question the reader will ask next
Read your draft and note where you would push back if someone else wrote it. Those objections are your next sections.
Add a table when comparing three or more things
Prose comparing four options is hard to follow. A table plus a paragraph explaining what the table shows communicates more in less space, and the surrounding context is real content.
Count your text now
Words, characters, sentences, paragraphs and reading time. Nothing is uploaded.
Where Your Text Goes
Nowhere. The counter is JavaScript that runs on your machine, so the text you paste stays in the browser tab. There is no upload step, no request to a server, no log.
You do not have to take that on faith. Open your browser's developer tools, switch to the Network tab, then paste a long document into the counter. You will see the numbers update with no network activity at all. That test works on any tool making the same claim, and it is worth running before you paste anything confidential into a site you do not control.
Frequently Asked Questions
Related Tools
Keep Reading
Why Character Counts Disagree: Emoji, Accents and SMS Segments
One emoji can cost seven characters, and a single curly apostrophe can triple your SMS bill. The three definitions of a character, and when each applies.
Sentence Length and Readability: The Number Behind Every Score
Flesch-Kincaid, Gunning Fog and SMOG share one dominant input. What the research supports, and why counting sentences is harder than it looks.
Reading Time Estimates: Where 238 WPM Comes From and When It Lies
The number behind every "5 min read" label, why technical content reads at half that rate, and how to time a script for narration.
Title and Meta Description Length: Pixels, Not Characters
Google truncates by rendered width, so a title of capitals runs out thirty characters early. Plus why it rewrites most descriptions anyway.