Reading Time Calculator

Treat the result as a planning number, not a promise. Dense technical material reads closer to 100–150 words per minute, skimming runs much faster, and images or code blocks add time the word count never sees. For display, most sites round up to whole minutes: "7 min read." Text meant to be read aloud needs a speaking pace instead: about 130–150 words per minute.

Drafts kept in a Ferra content table with a word-count column and a computed reading-time column carry a current estimate for every piece as you write.

The speed is the lever. Enter a word count and a words-per-minute figure; the calculator returns the estimated reading time in minutes. Pick the speed for your actual audience rather than accepting the default blindly: the same 1,800 words run 8 minutes at 225 words per minute and 12 minutes at 150.

Take 1,800 words at 225 words per minute: 1,800 / 225 = 8 minutes. The formula is linear, double the length, double the time at the same speed.

Your choice of speed matters more than the precision of the count. The same 1,800 words at 150 words per minute, a realistic pace for a technical tutorial the reader is actually following along with: takes 1,800 / 150 = 12 minutes, half again the original estimate. Unsure? Run it at two speeds and quote the range.

Scripts are where estimates go wrong. Podcast and video scripts run spoken, at roughly 130–150 words per minute, presentations too, so estimating a script with 225 wpm undercounts its runtime by about a third. The reverse error, a listening speed applied to a blog post, makes an ordinary article look intimidatingly long.

Around 7 minutes, roughly 1,600 words at typical speeds, gets cited as the engagement sweet spot for blog posts: long enough to say something substantive, short enough that most readers who start will finish. News briefs and marketing emails do their work under 2–3 minutes. In-depth guides and research pieces routinely run 15 minutes or more and still perform, because that audience came for depth.

Read the number against intent, never against a universal target. A short reading time on a how-to guide can signal thin content as easily as efficiency; a long one on an announcement post usually means it needs an edit. The estimate earns its keep as a label, publishing "8 min read" sets expectations, and as an editing check: a reading time that surprises you means the piece is probably the wrong length for its job.

Reading time estimates attention, not seconds on a stopwatch. These keep the estimate honest and useful.