Estimate reading time instantly โ paste text, enter word count, or upload a book.
Enter a number like 50,000 or 943399. Commas and spaces are ignored.
Drop your file here
or click to browse
Paste text, enter a word count, or upload a file to see detailed stats.
This Read Time Calculator turns a piece of text, a word count, or an uploaded document into an estimated reading time along with speech time, a readability score, and detailed text statistics. It’s built for bloggers checking a “5 min read” badge, students sizing up an assignment, speakers timing a script, and anyone who just wants to know how long something will take to get through. You can paste text directly, type in a word count, or upload a TXT, PDF, DOCX, or EPUB file, then choose a reading speed to see the result.
The core calculation is simple: reading time = word count รท reading speed (WPM). Enter or paste your content, the tool counts the words, divides by your selected words-per-minute rate, and displays the result as minutes and seconds.
The word count behind that number matters as much as the formula. Where supported, the calculator uses the browser’s built-in word segmentation to identify word-like tokens rather than simply splitting on whitespace. In browsers without that support, it falls back to a whitespace-based count, which works well for English and other space-delimited languages but is less precise for languages without spaces between words, such as Chinese or Japanese.
Every field updates live. As you paste text, adjust the word count, or switch reading speeds, the reading time, word count, and character count recalculate automatically.
Paste Text. Drop a full article, email, script, or chapter into the text box and get an exact word count from the actual content. This is also the only mode that enables readability scoring and sentence-level statistics, since those require the real text rather than just a number.
Word Count. If you already know the total, from a CMS word counter or a publisher’s word-count target type the number directly (commas and spaces are ignored, so “50,000” and “50000” both work) and go straight to the time estimate. Readability and sentence stats aren’t available in this mode, since there’s no text to analyze.
Upload File. For content too long to paste comfortably a manuscript, report, or ebook upload it directly. Supported formats are TXT, PDF, DOCX, and EPUB, up to 50MB, with one file processed at a time. The extracted text is then processed using the same reading-time, speech-time, and readability calculations as pasted text.
Below the input area, Clear All resets everything, and Copy Results copies the current stats to your clipboard so you can drop a reading-time estimate into a post, email, or note.
Reading speed varies significantly from person to person and depends on the reader, the language, familiarity with the subject, and how difficult the content is. Rather than assuming one “correct” speed, the calculator offers four starting-point presets plus a custom option:
| Preset | Speed | Typical use |
|---|---|---|
| Slow | 150 WPM | Dense, technical, or unfamiliar material; readers newer to a language |
| Average | 225 WPM | General-purpose reading estimate |
| Fast | 300 WPM | Confident readers, casual or narrative content |
| Expert | 400 WPM | Trained speed-readers, skim reading |
| Custom | 20โ1,000 WPM | Matching a specific audience or your own measured pace |
None of these are a universal “correct” answer, they’re general-purpose estimates. If your audience or content doesn’t fit any of them, Custom accepts any value from 20 to 1,000 WPM, useful for early readers well under 150 WPM or professional speed-readers above 400.
Switching presets doesn’t require re-entering your text, the word count stays put and the time recalculates instantly, which makes it easy to see how far apart a slow and a fast estimate really are for the same content.
Here’s how common content lengths translate at each preset, calculated directly from the formula above:
| Word Count | Slow (150 WPM) | Average (225 WPM) | Fast (300 WPM) | Expert (400 WPM) |
|---|---|---|---|---|
| 250 | 1m 40s | 1m 7s | 50s | 38s |
| 500 | 3m 20s | 2m 13s | 1m 40s | 1m 15s |
| 1,000 | 6m 40s | 4m 27s | 3m 20s | 2m 30s |
| 1,500 | 10m 0s | 6m 40s | 5m 0s | 3m 45s |
| 2,500 | 16m 40s | 11m 7s | 8m 20s | 6m 15s |
| 5,000 | 33m 20s | 22m 13s | 16m 40s | 12m 30s |
A 1,000-word blog post, for instance, reads as roughly 4 minutes 27 seconds at the Average preset โ a figure you can reproduce yourself by typing “1000” into Word Count mode and comparing presets.
File upload is one of the calculator’s strongest features, so it’s worth knowing exactly what happens to each format:
Files are processed locally in your browser, the document itself isn’t uploaded to a server for parsing. That’s a meaningful difference from tools that require a server round-trip, and it’s why the practical size limit is 50MB plus whatever your own device can comfortably handle, rather than a server-side quota.
Once a file loads, you’ll see its name, size, and for PDF and DOCX an estimated page count, along with a status indicator confirming it parsed successfully. A remove button clears the file and its preview without affecting anything else you’ve entered.
The default view shows a headline reading time plus word and character counts. Selecting Show More Stats opens three additional panels.
Speech Time. If you’re prepping a talk rather than an article, silent reading speed isn’t the number that matters โ speaking pace is. The calculator converts the same word count into three delivery-pace estimates: Normal Speech at 130 WPM, Presentation at 110 WPM (slower, to leave room for emphasis and pauses), and Podcast at 150 WPM. These are starting points, not fixed rules, actual delivery speed depends heavily on the speaker. As an example, a 1,500-word script comes out to about 11 minutes 32 seconds at Normal Speech pace, 13 minutes 38 seconds as a Presentation, and 10 minutes at Podcast pace.
Readability. Using the pasted or uploaded text, the calculator computes a Flesch Reading Ease score โ a formula based on average sentence length and average syllables per word โ and translates it into a plain-language label:
| Score | Label |
|---|---|
| 90+ | Very Easy |
| 70โ89 | Easy |
| 60โ69 | Fairly Easy |
| 50โ59 | Standard |
| 30โ49 | Fairly Difficult |
| Below 30 | Difficult |
This score is calibrated for English prose specifically and is best treated as an estimate rather than a precise measurement, it doesn’t reliably apply to non-English text or code-heavy content. It also isn’t available in Word Count mode, since it depends on real sentences to analyze, not just a total. Readability isn’t something word count alone can tell you: two texts with the same word count can score very differently depending on sentence length and word complexity.
Text Statistics. A more granular breakdown covers sentence count, paragraph count (detected by blank-line breaks), characters excluding spaces, average word length, and average sentence length. Paired with the readability score, these numbers are useful for spotting clarity issues โ a long average sentence length alongside a “Difficult” label is a concrete signal to start cutting.
Bloggers, freelancers, and content teams use the reading-time output to set expectations before a visitor commits to an article, and use Word Count mode during drafting to check whether a piece lands in the right length range. Freelancers working on content projects can also use a Freelance Hourly Rate Calculator to estimate a sustainable rate based on their target income, working hours, and expenses.
Students and researchers paste assigned readings to plan study sessions realistically, especially when a syllabus lists page counts rather than word counts.
Speech writers and presenters rely on the Speech Time panel rather than the silent reading time, a script that takes 4 minutes to read silently will generally take longer to deliver aloud, and Presentation pace accounts for that gap.
Podcasters and voice-over readers use Podcast pace as a starting point for estimating recording length, then adjust based on their own measured speed over time.
Editors use the readability score and sentence-length stats as a quick clarity check before a piece goes out.
Treating the Average preset as the only correct answer is the most common one, 225 WPM is a reasonable starting point, not a universal constant, and real readers cluster across a wide range around it. Confusing reading time with speaking time is another: a script that “reads” in four minutes will typically run longer once delivered aloud, which is why the Speech Time panel uses separate, slower rates. With file uploads, assuming a scanned PDF will work is a frequent snag, if a PDF is a photographed or scanned page rather than digital text, there’s nothing for the parser to count, and the tool will return an error rather than a false number.
Reading time = word count รท reading speed (WPM). Paste your text, enter a word count, or upload a file, then choose a speed preset or a custom WPM to see the result in minutes and seconds.
At the Average preset (225 WPM), about 4 minutes 27 seconds. At Slow (150 WPM) it’s 6 minutes 40 seconds, and at Fast (300 WPM) it’s 3 minutes 20 seconds.
Reading time estimates silent reading speed; speech time estimates how long the same text takes to read aloud, which is slower. The calculator’s Speech Time panel offers Normal Speech, Presentation, and Podcast pace estimates specifically for scripts, talks, and recordings.
At the Average preset (225 WPM), roughly 675 words. At Slow (150 WPM) it’s about 450 words, and at Fast (300 WPM) about 900, enter your own word count and switch presets to see the exact figure for your reading speed.
Yes, as long as the PDF has selectable text. Upload it directly and the calculator extracts the text page by page and calculates reading time the same way it would for pasted text. Scanned or image-only PDFs aren’t supported, and password-protected files need the password removed first.
Yes. Both formats are supported for upload, up to 50MB. DOCX page counts are estimated using a 250-words-per-page assumption; EPUB doesn’t show a page count since ebook pagination varies by device.
Word counting works reasonably well across languages, particularly in browsers that support built-in word segmentation. Readability scoring, however, is calibrated for English specifically treat readability results on non-English text as unreliable.
Word counts can vary depending on how hyphenated words, numbers, and punctuation are handled. This calculator counts word-like tokens rather than just spaces, which is generally more accurate but can differ slightly from a simple space-count on text with lots of numbers or special characters.