Decide what you are counting
A word count needs a rule. Splitting a string at every space is a convenient approximation for some English drafts, but repeated spaces, punctuation and languages that do not put a space between words make it unreliable. Our counter uses the browser’s Unicode word segmenter when available, and a letter-and-number fallback otherwise.
An editor can count a hyphenated phrase differently from a submission portal. If a publisher sets a limit, its counting method is the final contract. Leave a small margin and check the destination rather than assuming that two counters must agree. Code, citations, headings and footnotes can have separate inclusion rules.
Work through the time estimate
Take a draft of 1,190 words. At 238 words per minute, 1,190 ÷ 238 = 5 minutes. At 150 words per minute for a spoken delivery, it takes about 7.93 minutes before you add pauses, demonstrations or audience interaction. Keep both the unit and the pace beside the result.
A reading-time label is a planning estimate, not a speed requirement. Technical terms, unfamiliar names, equations and links can slow a reader down. To estimate a talk, read a representative passage aloud and time it. A real rehearsal is more useful than increasing the assumed speaking speed until a script fits.
Try it with your own input
Your result
Characters are not always bytes
The character total here counts Unicode code points. An emoji made from several code points can look like one symbol while contributing several characters. A server limit measured in UTF-8 bytes can be different again. If an API sets a byte limit, a character counter alone cannot validate it.
Compare a plain ASCII name with a Turkish name or an emoji. The number of visible symbols may be similar while the UTF-8 byte length is not. The Base64 tool makes the text-to-bytes step explicit; see the encoding guide before treating encoded length as document length.
Use length to edit the structure
Count the draft once, then inspect its sections. A long paragraph may need an example, a heading or a clearer transition rather than simply fewer words. A short paragraph may still contain three competing ideas. Length helps reveal the shape; it does not judge whether the reasoning is useful.
For a time-limited page, choose the reader’s task first. Put the direct answer near the start, keep the working example close to the rule and move secondary details into clearly labeled sections. Use Markdown Preview to see the outline and Text Case Converter for mechanical cleanup after the substantive edit.
Turn minutes into a sustainable reading plan
For book planning, multiply daily reading minutes by a measured reading pace, then divide by the book’s approximate words per page. Both pace and page density vary, so use a range rather than a promise. The yearly reading guide carries that calculation through to a realistic goal.
Keep a few spare days in the plan. Reading a difficult chapter twice can be more valuable than meeting a daily page target without understanding it. Track completion with NextRead, and use your own experience to update the estimate. The tool should serve the habit, not turn it into an arbitrary score.
Common questions
Why does another editor give a different count?
Tokenization and inclusion rules vary. Hyphenated words, citations and headings can be treated differently. Use the destination’s rules for a formal limit.
Are spaces counted as characters?
The total includes spaces and line breaks. A separate result removes whitespace so you can compare both measures.
Does the reading estimate include comprehension?
No fixed speed can measure comprehension. Use a passage and a comprehension check in ReadPace for a more personal planning estimate.
Is my draft uploaded or saved?
No. The counter processes the draft in memory in this tab. Copy or download work you need to keep before closing.
Can I use the speaking estimate for a presentation?
Use it as a first pass at 150 wpm, then rehearse aloud with pauses, slides and demonstrations included.