Word Counter & Text Analyzer
Paste or type your text below to get instant word count, readability scores, keyword density, sentiment analysis, and AI-powered writing insights.
Recent Analyses
Your text analyses will appear here. History persists across sessions.
Your Data Never Leaves Your Device
Unlike other tools that upload your text to remote servers, everything here runs 100% in your browser. Built by a cybersecurity professional who believes privacy shouldn't be optional.
100% Client-Side
All text analysis runs entirely in your browser. Your words never leave your device — not even temporarily.
No Server Storage
We don't operate backend servers that process your data. This is a static site served via CDN — there's nowhere to store it.
No Tracking Without Consent
Analytics only activate after you explicitly accept cookies. Decline and we track nothing — zero scripts, zero pixels.
Open Architecture
Built as a static export with no API calls. You can verify this yourself — inspect network traffic and see zero outbound data.
How a word counter is actually supposed to be used
A practical guide from someone who has run thousands of word counts for academic essays, conference talks, marketing copy, and novel manuscripts.
The two numbers most people get wrong
Most people who paste text into a word counter are looking for one of two numbers. The first is the obvious one — how many words are in this document. The second is the one that actually matters in practice — how long this will take to read or to deliver. The gap between those two questions is where most writing decisions get made, and it is also where the most common mistakes happen.
A 1,200-word document at the standard 250 words-per-minute silent reading pace takes 4 minutes 48 seconds to read. The same 1,200 words delivered aloud at a typical 130 words-per-minute speaking pace takes 9 minutes 14 seconds. That is the entire difference between a blog post that says "5 min read" and a conference talk that runs 9 minutes over its 10-minute slot. The word count did not change. The use case did.
Why speaking pace and reading pace are so different
Silent reading pace runs roughly twice spoken-delivery pace for the same text. The reason is that the brain processes visual text faster than it produces audible speech. An adult reader can take in 250 to 300 words per minute of prose without effort, and trained speed-readers can clear 500 or more — but those same readers, asked to deliver the same text aloud at a pace an audience can follow, settle into 130 to 150 words per minute almost regardless of practice.
Audiobook narration runs slightly faster than presentation pace (typically 150 to 170 wpm), and YouTube narration runs faster still (150 to 180 wpm for explainer channels, 170 to 190 for vlog content). The pattern is that the more controlled the recording environment, the faster the narrator can go without losing the listener. Live presentation pace is slower because the speaker is reading the audience while delivering, and the audience needs a beat to absorb each idea before the next one arrives.
All of this matters for the simple reason that the same 1,000-word document will produce wildly different "how long is this" answers depending on what you plan to do with it. A 1,000-word blog post is a 4-minute read. A 1,000-word podcast script is a 7-minute episode. A 1,000-word keynote talk is an 8-minute slot. The right word count is always a function of the use case, never an abstract number on its own.
What counts as a word, and why tools disagree
The boring-but-important detail behind every word counter is the definition of "word." Microsoft Word, Google Docs, and most academic word counters define a word as a sequence of non-whitespace characters separated by one or more spaces, tabs, or newlines. Under that definition, "state-of-the-art" counts as one word, "e-mail" counts as one, and "U.S.A." counts as one. Hyphenated compounds stay together; space-separated phrases do not.
Most discrepancies between word counters come from edge cases in this definition. Counters that split hyphenated compounds into multiple words will report higher counts for the same document. Counters that ignore bullet markers, line numbers, or table cells will report lower counts than tools that treat those tokens as words. For most practical purposes the differences are small — typically under one percent — but for an essay with a hard 650-word cap or a manuscript at a 100,000-word ceiling, even small definitional differences can be the difference between submitting and being rejected.
The tool on this page follows Microsoft Word's conventions on every edge case we have tested against, which is also what most academic style guides, hiring-manager review templates, and editorial submission guidelines assume. If you see a meaningful gap between this counter and Word, it is almost always because Word counted a header, footer, footnote, or citation that did not come along when you pasted the text into the counter.
How to use the count instead of just looking at it
A word count is a measurement, not a verdict. The two productive ways to use it are to check whether a draft fits a known constraint (a 650-word college essay, a 280-character tweet, a 5-minute speech) and to translate between formats (knowing that your 1,500-word blog post would be a 12-minute podcast monologue or a 75-minute lecture, if you decided to repurpose it). Both uses turn a static number into a real decision.
The two unproductive ways to use a word counter are to grade your draft by length (longer is not better — most well-edited writing is shorter than its first draft by 15 to 30 percent) and to chase a target without understanding what the target is for. A high school student who writes exactly 1,000 words because the assignment says 1,000 has done less useful work than a student who writes 850 words that fully develop the argument. Counting words is easy; using the count well is the actual skill.
When to trust the count and when to count by hand
For prose written in standard formatting — paragraphs, sentences, normal punctuation — automated word counters are reliable enough that counting by hand is wasted effort. They handle every edge case that shows up in academic essays, blog posts, business writing, and most creative writing without drift.
Counters become less reliable when the document contains heavy formatting that the input strips away: tables, bulleted lists with their markers, code blocks, equations, citations in citation-manager format, or footnotes. In those cases the counter may include or exclude content depending on how the formatting was preserved in the paste. If you are writing to a hard limit (a Common App essay, a manuscript ceiling, a tweet), paste a clean text-only version of the document and count that. The 30 seconds of cleanup is cheaper than a rejected submission.
None of this is unique to the tool on this page. The same constraints and conventions apply to every word counter you can use — Microsoft Word, Google Docs, the counter built into your phone keyboard, or any online tool. What changes between tools is mostly the interface and the extra analyses layered on top of the count (readability scores, keyword density, sentiment, reading-time estimates). The underlying count itself is largely a solved problem.
How word count is computed
words = text.trim().split(/\s+/).length
characters = [...text].length // Unicode-safe
reading_time = words / 238 wpm // adult silent reading
speaking_time = words / 150 wpm // conversational pace
flesch_ease = 206.835 − 1.015·(words/sentences) − 84.6·(syllables/words)Every count is computed in your browser the instant you type. Words are defined as whitespace-delimited tokens; characters are full Unicode code points (so an emoji counts as one visible character). Reading speed uses the widely cited 238 words-per-minute baseline for adult silent reading, and the Flesch Reading Ease score uses the classic Rudolf Flesch 1948 formula — higher is easier to read.
Examples
College admissions essay (650-word limit)
The Common App caps personal statements at 650 words. If you paste your draft here and see 712 words, you need to cut 62 words — roughly 9% of the total. A tightly written 650-word essay averages about 4,000 characters with spaces and reads in just under 3 minutes at the 238 wpm baseline.
LinkedIn post optimized for reach
LinkedIn truncates the feed preview at around 210 characters on mobile and shows a "see more" link. Aim for your hook in the first 210 characters and a full post between 150–300 words for strong engagement. Check the character count here before posting — you want the reveal to land mid-sentence on a cliffhanger, not mid-word.
5-minute conference talk script
At a conversational 150 words per minute, a 5-minute talk is about 750 words. Type or paste your script here: the speaking time card will say 5.0 min when you hit 750 words exactly. Going over? Either cut filler or drop a slide — audiences forgive shorter talks, not longer ones.
SEO blog post with target keyword density
If your target keyword appears 18 times in an 1,800-word blog post, the keyword density panel will report 1.0% — right in the "safe, not stuffed" zone most SEO tools recommend (0.5%–2.5%). The density panel also flags which two-word and three-word phrases you use most often, which tells Google what your page is really about.
Common questions
A word is any sequence of non-whitespace characters separated by one or more spaces, tabs, or newlines. "state-of-the-art" counts as one word; "e-mail" counts as one; "U.S.A." counts as one. Hyphenated compounds stay together, but "well written" counts as two. This matches how Microsoft Word, Google Docs, and most academic word-count tools behave.
Most of the time it matches exactly. The two main sources of drift are (1) how hyphens and em-dashes are handled and (2) whether bulleted list markers are counted. We follow Word's conventions on both. If you see a gap of more than one or two words, it's usually because Word counted a stray footnote or header that you did not paste in.
No. The entire analysis — word counting, readability scoring, keyword density, sentiment — runs inside your browser using JavaScript. Your text never leaves your device. You can open DevTools → Network and confirm there is zero traffic while you type. This also means the tool works offline once the page has loaded.
It's an estimate based on 238 words per minute, the average adult silent-reading speed established by a 2019 meta-analysis in the Journal of Memory and Language. Your audience might read faster or slower: technical docs slow people down, breezy newsletters speed them up. Use the estimate as a ballpark, not a stopwatch.
General audiences (e.g. newspaper readers): aim for 60–70. Plain-language government or healthcare content: 70–80. Marketing copy meant for a broad audience: 70+. Academic writing typically scores 30–50, which is fine for journal articles but too dense for a landing page. If you see a score under 30 and you're not writing for PhDs, shorten your sentences — every point of Flesch ease comes from cutting words per sentence or using shorter words.
Yes — it is especially useful there. Aim for 400–600 words on a one-page resume and 250–400 words on a cover letter. The readability panel will flag if your bullets are too dense (grade-level 14+), and the keyword density panel shows whether the role's key terms appear often enough for ATS matching without repeating awkwardly.