Quick reads
65 books are estimated to take under an hour. These are perfect for a short break or a single sitting. Many are poetry collections or short stories.
Reading Tracker
Choose a book, record where you are, and set a daily goal. Your progress is stored in localStorage in this browser; it is not uploaded to a user account.
No sign-up required
Stored in your browser
Estimated time remaining
Choose a book
If the EPUB has no fixed print pagination, the tool starts with an estimated page count and lets you replace it with the page total shown by your own reader.
Reading progress
0%
0 / 0 pages
Remaining
—
Estimated time left
—
At your daily goal
—
Stored locally
Reading history
| Date | Start | End | Read |
|---|
How the progress estimate works
The Reading tool helps you plan how much time to set aside for a book. Each entry includes an estimated reading time based on its word count, assuming an average reading speed of about 230 words per minute. This is an approximation; your actual time may differ.
In this catalog, the median word count is 18,111, which corresponds to a median reading time of 79 minutes. Most books are classified as 'quick' reads (65 titles), meaning they can be finished in under an hour. A few longer works require more commitment.
Steady reads
20 books fall into the 'steady' category, taking one to three hours. These offer a more substantial reading experience without a huge time investment.
Immersive and marathon reads
6 books are 'immersive' (three to six hours) and 6 are 'marathon' (over six hours). These are likely to be longer collections or epics, such as a three-volume poetry set.
Planning a Page-Based Reading Pace
The Reading Tracker records progress in pages, not in minutes or sections. You set a current page, a total page count, and a daily page goal, and the tracker estimates how many days remain. The default daily goal is 20 pages, but you can adjust it to match your actual reading speed. Because the catalog does not supply fixed page counts, the tracker estimates pages from word counts using a configured words-per-page value of 250, and you are encouraged to replace that estimate with the page count from your own edition.
Setting Your Total Pages
The first step is to know your total page count. The tracker offers an initial estimate based on word count: it divides the word count by 250 to get a page count, rounding up to the nearest whole page. For example, Accolon of Gaul, with Other Poems — Themes and Context (id 219) has 30,582 words, so the estimate would be ceil(30582 / 250) = 123 pages. That is a reasonable starting point, but if your edition has different pagination, you can override it.
Why does this matter? The remaining time and finish date are calculated as proportions of the total pages. If your actual edition has 150 pages instead of 123, the tracker will project a longer reading period. Using your own page count makes the tracker's estimates more accurate for your physical or digital copy.
Choosing a Daily Page Goal
The daily page goal is the number of pages you plan to read each day. The default is 20, but you can set it lower or higher depending on your available time. The tracker then estimates the finish date as ceil(remaining_pages / daily_page_goal). For a 123-page book, a goal of 20 pages per day would finish in 7 days (ceil(123/20) = 7). A goal of 10 pages per day would take 13 days (ceil(123/10) = 13).
The estimated remaining time is proportional: estimated_minutes × remaining_pages / total_pages. If you have read 23 pages of a 123-page book with an estimated reading time of 133 minutes, the remaining time would be 133 × (100/123) ≈ 108 minutes. This gives you a sense of the total time investment, not just the calendar days.
Tracking Progress Without Overcomplicating
The tracker's simplicity is its strength. It does not record sections or minutes as progress; it only cares about pages. This means you do not need to estimate how much of a section you finished or how many minutes you read. You simply update the current page number, and the tracker recalculates the remaining pages and days. This is especially useful for long poems that may not have clear chapter breaks.
Your progress history is stored in localStorage in your current browser, and no account is required. This means your data stays on your device, but it also means it will not sync across browsers or devices. If you switch computers, you will need to re-enter your current page. That is a minor inconvenience for the benefit of not needing an account.
Example: Planning Accolon of Gaul
Let us walk through a concrete example using Accolon of Gaul, with Other Poems — Themes and Context (id 219). The catalog lists a word count of 30,582 and an estimated reading time of 133 minutes. The tracker estimates 123 pages. If you set a daily goal of 20 pages, you will finish in 7 days. If you have already read 30 pages, the remaining pages are 93, and the estimated remaining time is 133 × (93/123) ≈ 100 minutes.
This example shows how the tracker turns a vague intention into a concrete plan. You know exactly how many pages to read each day and when you will reach the end. You can adjust the goal if your schedule changes, and the tracker will update the finish date accordingly. A useful approach is to use the page count that matches your edition, not to rely solely on the estimate.