Ankore
Content & Editorial · Free

Word Counter & Reading Time

Live word, character, sentence, and paragraph counts plus reading time, speaking time, Flesch reading ease, and a most-used word breakdown — all in your browser.

  • No signup, no email required
  • Works entirely in your browser
  • Output you can copy and paste directly
  • Built by a working SEO team, not gated by upsells

Paste or type your content

Live counts

0
Words
0
Characters
0
No spaces
0
Sentences
0
Paragraphs
Avg. word length
Reading time0 sec
Speaking time0 sec

Reading: 240 wpm (silent, average adult). Speaking: 130 wpm (typical conversational pace).

Reading ease

What it does

Paste any text and this tool tells you, in real time:

  • Word count — actual word tokens, not character heuristics
  • Character counts — both with and without whitespace, since some platforms count differently
  • Sentence and paragraph counts
  • Reading time at 240 words per minute (the average adult silent reading speed) and speaking time at 130 wpm (typical conversational pace)
  • Flesch Reading Ease score and Flesch-Kincaid grade level — readability metrics that estimate how accessible the text is
  • Most-used words with stop-words filtered, useful for spotting accidental repetition or keyword density issues

Everything runs in your browser. The text never leaves your device, there is no server endpoint, and there is no character limit. Paste an entire book if you want.

Why word count still matters in 2026

The "long-form content ranks better" era is over. Google does not reward word count directly — it rewards content that fully answers the query. But word count remains useful as a proxy for completeness and as a hard constraint for specific contexts:

  • Meta descriptions are pixel-limited to ~155–160 characters before truncation in most SERPs.
  • Title tags truncate around 50–60 characters depending on character width.
  • Tweets / X posts still cap at 280 characters for non-Premium accounts.
  • LinkedIn postshide content beyond ~210 characters behind a "see more" link.
  • FAQ schema answers work best at 40–300 words.
  • AI Overview citations tend to extract from paragraphs in the 60–120 word range.
  • Email subject lines often truncate around 40–50 characters on mobile.

Reading time is a separate signal worth tracking. It is what readers actually see displayed at the top of an article ("8 min read") and it informs editorial pacing — a 14-minute read better deliver 14 minutes of unique value, not five minutes of padding.

How to use this counter

  1. Paste or type into the textarea. Counts update on every keystroke.
  2. Read the panel on the right. Word count is highlighted; the reading time and speaking time cards show time formatted readably; the Flesch card shows ease score, grade level, and a plain-English label.
  3. Check the most-used words list at the bottom. Common stop-words (the, and, of, etc.) are filtered out automatically, so what you see is the words that actually carry meaning. If your top word appears 30 times in a 600-word article, that is a signal to reach for a thesaurus.
  4. Use Load sample to populate with example text if you want to see how the tool behaves before pasting your real content.

Ideal word counts by content type

These are guidelines based on what tends to perform across our client work, not hard rules. Quality always beats word count.

  • Pillar / topic-cluster page: 1,800–3,500 words. Long enough to fully cover the topic; short enough that readers actually finish.
  • Standard blog post: 1,200–1,800 words for informational; 800–1,200 for tactical how-tos.
  • Comparison / alternatives page: 1,500–2,500 words to fairly cover each option.
  • Service / landing page: 600–1,200 visible words. Past 1,500 the content fights with the conversion goal.
  • Product page: 300–800 words plus structured data. More than that and you are writing a blog post on a product page.
  • Guest post: 1,000–1,500 words is the sweet spot for most publishers. Premium tier outlets often want 1,500–2,000+.
  • Newsletter: 400–900 words. Beyond that, open rates hold but click-through drops sharply.
  • FAQ answer: 40–300 words per answer for both schema eligibility and AI Overview extraction.
  • Meta description: 140–155 characters (not words).

How to read the Flesch reading ease score

The Flesch Reading Ease score runs 0–100 (and occasionally above or below depending on text). Higher means easier to read.

  • 90–100: Very easy. 5th-grade level. Children's books, simple how-tos.
  • 80–89: Easy. 6th-grade level. Conversational web copy.
  • 70–79: Fairly easy. 7th-grade. Most blog content sits here when written well.
  • 60–69: Standard. 8–9th-grade. Mainstream news, B2C marketing copy.
  • 50–59: Fairly difficult. High school senior. B2B SaaS landing pages often land here.
  • 30–49: Difficult. College reading level. Academic, technical documentation.
  • 0–29: Very difficult. College graduate level. Legal, scientific papers.

For most marketing content, 60–70 is the target. Below 50, your conversion rate suffers from comprehension friction even with a technical audience. Above 80, your content can read as condescending to a B2B audience. There is no SEO penalty for either extreme — just human-side cost.

Word count best practices

  • Set the target before you write, not after. Decide the right length for the content type, the search intent, and your audience. Then write to it.
  • Trim before you publish. First-draft word counts are almost always too high. A 25–30% cut on the second pass is normal and almost always improves the piece.
  • Watch for repetition. The most-used-words list in this tool surfaces accidental repetition. If a word (especially a noun) appears more than ~1% of the total word count, consider varying it.
  • Optimize sentence length, not just word count. Average sentence length above 25 words drops Flesch ease sharply. Mix short and long sentences for rhythm.
  • Use the reading-time estimate honestly.If your article shows "12 min read" at the top, the reader expects 12 minutes of value. Padding to hit a target word count destroys that contract.

Frequently asked questions

Is there a word limit?

No. The tool runs entirely in your browser — paste any length, including full books. Performance stays smooth up to several hundred thousand words on a typical machine.

Why is the reading time set to 240 words per minute?

240 wpm is the average silent reading speed for adults reading a moderately complex text in their native language. Children read slower (~180), college students faster (~280), specialists in their domain faster still (~350+). 240 is the sensible default for general content.

Why is the speaking time slower?

Conversational speech averages 130 wpm; presentations and audiobook narration sit around 150–160 wpm. Use the speaking time when timing video scripts, podcast segments, or webinar talks. Add 15–20% extra time for slides, demos, and natural pauses.

How accurate is the syllable count for Flesch?

We use a vowel-group heuristic that handles most English words correctly. It misses some edge cases (silent letters in compound words, rare diphthongs). The Flesch score is accurate to within ~2 points of academic syllable counters for typical English text — fine for editorial decisions, not for academic citation.

Does this work for non-English text?

Word and character counts work for any language. Sentence detection works for most Latin-script languages. The Flesch reading ease score is English-only — equivalents exist for other languages (LIX for Swedish, Gulpease for Italian, etc.) but those are not implemented here.

What counts as a sentence?

Anything terminated by a period, exclamation mark, or question mark followed by whitespace. Abbreviations ("Dr.", "e.g.") inside sentences may inflate the count slightly — for academic-grade precision, run your text through a proper NLP segmenter.

What counts as a paragraph?

Any block of text separated by a blank line (double newline). Single line breaks within a block do not start new paragraphs.

Will this tool save my text?

No. The text never leaves your browser — there is no server, no logging, no analytics on your input. Close the tab and the text is gone.