Reading time is the product of two numbers — a word count divided by a reading rate measured in words per minute — and the result is only as trustworthy as both inputs. To calculate reading time in Word, you need the document's word count from Microsoft Word's status bar or Word Count dialog, then divide it by a rate that matches the kind of reading you actually care about: silent reading, reading aloud, or delivering a speech. The default silent-reading figure used by most reliable calculators is 238 words per minute for non-fiction, drawn from a 2019 meta-analysis of 190 studies. Reading aloud runs slower, around 183 words per minute in the same meta-analysis, because the mouth has to articulate every word while the eyes still track. These two rates are different numbers, and any tool that reports a single duration is silently making a choice about which one to use. Microsoft Word itself only reports one figure based on a generic assumption, which is why writers who need a trustworthy estimate for a presentation slot or a content deadline usually want a separate calculation they can verify by hand.
What Microsoft Word's built-in reading time actually shows you
Microsoft Word has a reading-time feature, but it is quietly limited. Word shows a word count in the status bar at the bottom of the window by default. To see a reading time, you open Review > Word Count (or click the word count in the status bar), then tick the box labelled "Display the reading time." The dialog then shows a single number based on a fixed rate inside Word's source code — roughly 200 words per minute for English — and the rate is not adjustable inside Word itself.
That single figure blurs two different questions. A blog post that someone will read silently on a phone takes a different amount of time than the same post read aloud on a stage. Word does not let you set separate silent and speaking rates, and it does not let you pick a rate that matches your actual audience, such as a slower presenter or a faster-than-average reader. The duration Word prints is also based on Word's internal word count, which generally follows Microsoft Office's tokenization rules but is not printed beside the number for verification. When two tools disagree about reading time for the same document, they almost always disagree about what counted as a word, not about the division.
Three ways to pull your word count out of Word
The first half of the reading-time calculation is the word count. Word gives you that number three different ways.
The fastest path is the status bar at the bottom of the Word window. If the word count is not visible, right-click the status bar and choose Word Count from the Customize Status Bar menu. Clicking the number opens the Word Count dialog. The dialog shows Pages, Words, Characters with and without spaces, Paragraphs, and Lines.
The second path is the Review tab on the ribbon. Click Review, then Word Count in the Proofing group, which opens the same dialog. This is useful when you have collapsed the status bar or are working on a smaller screen.
The third path is File > Info > Properties > Show All Properties, then scroll to the Statistics section. This view also reveals the page count, character count and line count, and stays visible while you work on the document.
Once you have the word count, copy it down or leave Word open while you open a dedicated reading-time page in your browser. If you want a live count that updates as you edit inside Word, a separate word counter can paste the same text and show counts in real time.
Calculate reading time step by step with a dedicated tool
The Reading Time Calculator separates silent and speaking rates and prints the word count it actually used, so the math is auditable. Here is the workflow.
- In Word, select all text with Ctrl+A, then copy with Ctrl+C. Alternatively, note the word count from the Word Count dialog.
- Open the Reading Time Calculator in your browser. Paste the copied text into the main field, or switch the calculator into word-count mode and type the number from Word.
- Choose a preset reading rate from the silent-reading menu — for most non-fiction drafts, the default is 238 words per minute. For fiction, the default rises slightly. To match your own pace, type any rate into the custom field.
- Set the speaking rate from the read-aloud menu. The default 183 words per minute reflects measured oral reading; the 228 words-per-minute option reflects standardized test passages; the roughly 150 words-per-minute option reflects the public-speaking convention.
- Read both durations the calculator prints side by side, one silent and one spoken.
- Look under the result at the word count and the counting rule. If a number surprises you, the rule explains why, and you can recompute the arithmetic by hand.
For example, a 1,000-word blog post at 238 wpm is 1,000 divided by 238, which equals 4.202 minutes, or 4 min 12 sec after rounding. The same text at 183 wpm, read aloud, is 1,000 divided by 183, which equals 5.464 minutes, or 5 min 28 sec. The arithmetic is small enough to check with a phone calculator.
Reading rate presets and what they actually measure
The presets in a serious reading-time calculator are not folklore. They come from published studies, and each one measures a slightly different task. The table below lists the rates the Reading Time Calculator offers, what each one measures, and where it comes from.
| Rate (wpm) | Task measured | Source |
|---|---|---|
| 238 | Silent reading, adult, English non-fiction | Brysbaert 2019 meta-analysis (190 studies) |
| 260 | Silent reading, adult, English fiction | Brysbaert 2019 meta-analysis |
| 183 | Reading aloud, natural prose | Brysbaert 2019 (77 oral-reading studies) |
| 228 | Standardized reading-test passages | Trauzettel-Klosinski & Dietz 2012 (IReST) |
| ~150 | Public-speaking convention | No retrievable study; speech-coach rule of thumb |
The Brysbaert meta-analysis is hosted as a PDF at gwern.net and aggregates roughly 190 studies for silent reading and 77 for oral reading, putting average adult English non-fiction silent reading at 238 wpm and oral reading at 183 wpm. The IReST figure of 228 wpm comes from a different task — adults reading short standardized paragraphs under a stopwatch — and is offered alongside the Brysbaert oral figure so you can see how task design changes the rate. The 150-wpm presentation figure is labelled honestly as a convention used by speech coaches, because no published study asserts it. You can ignore every preset and type any rate of your own.
Why two reading time calculators rarely agree
When two pages return different reading times for the same document, the difference almost always lives in the word count, not the rate. Counting rules vary. Microsoft Word, Google Docs, common JavaScript libraries and academic word counters all split text on whitespace, but they disagree on edge cases.
A hyphenated compound like "state-of-the-art" is one token in some counters and three in others, depending on whether word-joining dashes are treated as separators. A contraction such as "don't" is one word to most counters but two to anyone splitting on the apostrophe. A number written as "3.14" or "1,000" is one word under most rules, but a script that splits on punctuation can split it into fragments. Even a string of punctuation alone may or may not be counted.
This is why a calculator that prints both the word count and the counting rule underneath the result is genuinely more useful than one that just prints a duration. If a number looks wrong, you can see exactly why. The Reading Time Calculator prints the rule it uses: text is split on whitespace after word-joining dashes are treated as separators, and a token counts as a word when it contains at least one letter or digit. So "state-of-the-art" counts as one word, "don't" counts as one, "3.14" counts as one, and a line of only punctuation counts as none. Anyone can redo the arithmetic with that rule and confirm the displayed count.
Practical scenarios where reading time matters
Reading-time estimates are most useful for three kinds of decisions.
Presentation slots. Conference talks, webinar segments and pitch rehearsals are usually bounded to a fixed number of minutes. A speaker with a 12-minute slot and a draft at 1,800 words needs to know whether the script will fit at the 150-wpm speaking convention — roughly 12 minutes — or whether it overflows and has to be trimmed. Knowing the silent time as well tells the speaker how much time is left for audience questions if the deck is being read quietly off the screen.
Blog and content deadlines. Editors who promise a target reading time to readers — "a 5-minute read" — need to know the number matches what their audience will actually experience. A 1,200-word draft at 238 wpm takes just over 5 minutes, which is the headline figure most content tools display. A draft that promises 3 minutes but actually takes 7 is a credibility problem, and the right tool catches it before publication.
Reader expectations. School worksheets, onboarding documents, help-centre articles and email sequences all set expectations about how long the reader will spend. A staff policy that takes 14 minutes to read silently needs to be labelled as such, and a 90-second welcome email should not silently turn into a 4-minute scroll.
In every case, the calculator's output is a planning figure, not a promise. The same Brysbaert meta-analysis that anchors the 238-wpm default also reports that most adults read silently between 175 and 300 words per minute, which means any single reader's true time can differ from the estimate by a third in either direction. Use the number to compare drafts, budget slots, and set expectations, not to commit to an exact minute count for one specific person.