Reading Time
Estimate how long a piece takes to read silently or to deliver out loud by dividing its word count by a words-per-minute pace. Switch between presets for skimming, careful reading, and speaking, or set any pace from 60 to 500 with the slider. A per-paragraph breakdown shows which section of a long document carries the most reading time, and every figure is reproducible by hand.
How Reading Time works
Paste your article, script, or talk.
Set a reading pace, or use the silent-reading and speaking presets.
Read the estimate in minutes and seconds.
Check the per-paragraph breakdown to find sections that run long.
When to use Reading Time
- Adding a “5 min read” label to a blog post or newsletter and wanting the figure to match the word count rather than a rough guess.
- Timing a conference talk or podcast script against the Speaking preset to check it fits a fifteen- or thirty-minute slot before you rehearse.
- Setting a custom words-per-minute pace for a specialist audience — a legal brief read slowly, or a familiar internal memo skimmed quickly.
- Using the per-paragraph breakdown to find the one section of a long-read that carries a disproportionate share of the reading time.
- Bracketing how long a document really takes by reading the Skimming estimate against the Careful one, so you can quote a range instead of a single number.
- Deciding whether to split a page into two: if the Average estimate crosses ten minutes, a shorter piece often reads better.
- Sizing a script to a voiceover budget, where each minute of narration has a cost and the Speaking estimate is what the studio bills against.
- Sanity-checking a “reading time” number another platform generated, since many use an undisclosed pace and you can reproduce it by matching the slider.
Examples
Input
A 1,200-word explainer on local-first software.
Output
At the Average preset of 225 words per minute the estimate is 5 min 20 sec to read silently. The Details panel also shows the speaking figure — at 140 words per minute the same text runs 8 min 34 sec aloud.
Both numbers come from one word count divided by two different paces, then rounded to the nearest second.
Input
The same 1,200 words at the Skimming preset, then at a custom 400 wpm.
Output
Skimming at 300 words per minute lands on exactly 4 min. Dragging the slider to 400 words per minute brings it to exactly 3 min, and the pace label switches to “Custom” once the value leaves a preset.
The slider runs from 60 to 500 words per minute in steps of 10.
Input
A 2,000-word keynote script on the Speaking preset.
Output
At 140 words per minute the estimate is 14 min 17 sec — enough to confirm it overruns a fifteen-minute slot once you allow for pauses, questions, and slide transitions the word count cannot see.
Speaking is slower than silent reading, which is why the same script reads in under nine minutes but speaks in over fourteen.
Input
A 45-word status update.
Output
At any preset the estimate reads “< 1 min”, because the tool shows anything under sixty seconds as a single band rather than a misleadingly precise “12 sec”.
Exactly 140 words at 140 words per minute is the boundary case — it reads “1 min” on the nose.
How Reading Time works under the hood
The estimate is a single division: word count divided by the selected words-per-minute pace, multiplied by sixty and rounded to the nearest second. There is no per-character weighting, no sentence-length adjustment, and no correction for difficulty — it is deliberately the transparent formula every “reading time” badge is built on, so you can reproduce any of its numbers by hand.
Words are counted with the same rule as the Word Counter: the text is trimmed and split on any run of whitespace. A hyphenated compound like “state-of-the-art” is one word, and so is “don’t”, which keeps this tool’s word figure identical to the one shown across the rest of NeatKit.
Four presets seed the pace. Average is 225 words per minute, a typical adult silent-reading speed for online prose; Careful is 150 for dense or technical material; Skimming is 300 for a quick pass; and Speaking is 140, roughly a clear presentation delivery. Selecting a preset sets the slider, and moving the slider to a value that no longer matches a preset flips the label to “Custom”.
The label is formatted for reading, not precision. Zero words shows “0 min”, anything from one to fifty-nine seconds shows “< 1 min”, a whole number of minutes drops the seconds (“4 min”), and everything else reads “m min s sec”. A pace of zero or below is guarded — it falls back to the 225 default rather than dividing by nothing.
The Details panel always carries a Speaking estimate at 140 words per minute alongside whatever pace you have chosen, so you can plan a talk and a silent read at once without toggling presets. The main tile follows your selected pace; the speaking row is fixed.
The per-paragraph breakdown splits the text on blank lines — one or more line breaks with only whitespace between — and lists up to the first eight paragraphs, each with its own estimate at the current pace and a short preview of its opening. It is where the reading weight of a long document actually sits, which the single top-line figure hides.
Common mistakes
- Treating the number as exact for technical content. Code blocks, tables, equations, and figures are counted as ordinary words or not at all, yet they take far longer to work through than prose. For a tutorial or a reference page, read the estimate as a floor and add headroom.
- Quoting the silent-reading figure for a talk. Presenting is slower than reading in your head, so a script that “reads in nine minutes” will run closer to fourteen when spoken. Use the Speaking preset or the fixed speaking row in Details for anything delivered aloud.
- Forgetting that pace dominates the result. The same 1,200 words swing from about four minutes to about nine depending only on the words-per-minute you pick. If you compare two documents, hold the pace constant, or you are measuring the slider rather than the writing.
- Assuming every platform uses 225. Many badges quietly use 200, 238, or an internal figure, so a discrepancy with another site’s number is usually a pace difference, not a bug. Match their pace on the slider and the figures line up.
- Reading the “< 1 min” band as “instant”. It only means the estimate fell under sixty seconds; a 200-word abstract at a careful pace still asks for real attention even though the label rounds it away.
- Overlooking the per-paragraph list on long pieces. A single dense section can hold a quarter of the total reading time while the average looks fine — the breakdown is what surfaces it, so scan it before you decide a long-read is balanced.