Reading Time Calculator

The familiar "X min read" label at the top of a blog post or newsletter is one of the most-used pieces of metadata in online publishing — it sets a reader's expectations before they commit to starting, and it is a standard feature of Medium, most blogging platforms, and countless CMS themes. The calculation behind it is intentionally simple: divide the article's word count by an assumed reading speed in words per minute, which is exactly what this tool does, while adding a few conveniences a basic implementation usually skips. Average adult silent-reading speed for general-audience text in English is commonly cited in the 200-250 words-per-minute range, though it varies widely by individual, by text difficulty, and by reading purpose (skimming versus close reading). This tool defaults to 200 WPM — a conservative, widely-used baseline — and offers four quick presets spanning the realistic range people actually read at: Slow (150 WPM, for dense or technical material, or a less practiced reader), Average (200 WPM, the common default), Fast (250 WPM, a comfortable, practiced adult reader), and Speed-reader (400 WPM, an aggressive but achievable pace for someone deliberately skimming or trained in speed-reading techniques). You can also type any custom words-per-minute value directly if none of the presets match your use case. Two input modes cover the two situations people actually find themselves in. Sometimes you have the raw article text in front of you — pasted from a draft, a CMS editor, or a webpage — in which case the Paste Text mode counts words live as you type or paste, using the same whitespace-splitting approach a basic word counter uses. Other times you already know the word count from elsewhere (your CMS shows it, your word processor's status bar shows it, or you're estimating for a piece that hasn't been written yet) and don't want to paste the whole article just to get a time estimate — the direct word-count entry mode handles that case without requiring any text at all. The comparison table exists because a single reading-speed estimate can be misleading in isolation: a "7 minute read" label means something different to a slow, careful reader than to someone skimming quickly, and showing only one number hides that range. By computing the same word count against all four preset speeds side by side, you get an honest sense of how much the estimate actually swings — useful when deciding, for example, whether a long-form piece needs to be trimmed for a general audience versus whether it's fine as-is for a niche readership that reads that kind of content quickly. On rounding: the calculator computes total seconds as `words ÷ wpm × 60`, then floors that value down to a whole number of seconds before splitting it into minutes and seconds for display. Flooring (rather than rounding to the nearest second, or the nearest 5 seconds) means the displayed estimate is always slightly conservative — never longer than the literal formula result — which fits the common expectation that a stated reading time is a reasonable minimum, not a number a fast reader will regularly exceed.