Key takeaway
Estimated reading time ≈ word count ÷ words-per-minute. Many publishers use ~200–250 WPM for English prose.
Show honest estimates; adjust for technical audiences.
What it means
WPM assumptions drive the minute count.
Code blocks and tables inflate word counts without equal reading cost — adjust mentally.
Rounding up is common so readers are not undersold.
When you would use it
Blogs, docs, newsletters, course outlines, resource hubs.
How to use the tool
Use the matching TCB Tools page and work top to bottom:
- Open Reading Time Calculator.
- Paste text or use word count.
- Set WPM if adjustable.
- Read minutes.
- Recalculate after edits.
No account is required. Results update as you type.
Formula / method + worked example
Minutes = words ÷ WPM (often round up).
900 words at 225 WPM ≈ 4 minutes.
Pair with the Word Counter for the raw words.
How to read the result
Estimates are not promises.
Technical posts may need slower WPM.
Planning/editorial aid.
Common mistakes
- Counting huge code as prose. Adjust.
- One WPM for every format. Tune.
- Never updating after heavy edits. Recalc.
- Using reading time as SEO spam. Be honest.
Related ideas
Put reading time near the title.
Recompute when translating languages.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit reading time weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure reading time; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about reading time, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions reading time.
If leadership wants only a headline, still keep working notes for reading time in your own folder.
Seasonality and promotions change reading time; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for reading time.
Revisit assumptions about reading time after tool, tracking or pricing changes.
A short checklist for reading time beats relying on memory during busy weeks.
Put reading time near the title.
Recompute when translating languages.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit reading time weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure reading time; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about reading time, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions reading time.
If leadership wants only a headline, still keep working notes for reading time in your own folder.
Seasonality and promotions change reading time; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for reading time.
Revisit assumptions about reading time after tool, tracking or pricing changes.
A short checklist for reading time beats relying on memory during busy weeks.
Put reading time near the title.
Recompute when translating languages.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit reading time weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure reading time; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about reading time, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions reading time.
If leadership wants only a headline, still keep working notes for reading time in your own folder.
Seasonality and promotions change reading time; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for reading time.
Revisit assumptions about reading time after tool, tracking or pricing changes.
A short checklist for reading time beats relying on memory during busy weeks.
Put reading time near the title.
Recompute when translating languages.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
Try the tools
Open the Reading Time Calculator.