How to Track Your Reading Stats (Pages, Streaks, and Habits)

Which reading stats actually matter

Apps will happily chart anything. These are the stats that change behavior, roughly in order of usefulness:

• Books finished per month — the baseline. Not for bragging: for spotting that March collapsed and asking why. Monthly beats yearly because you can still adjust course.
• Pages or minutes per day — the honest measure of the habit, since one 900-page book can equal three novellas. Minutes work better than pages if you mix in audiobooks.
• Sessions — when and how long you read — the most underrated stat. Two weeks of session data usually reveals something concrete: you think you read at night, but your real reading happens Saturday mornings. Schedule around what the data says, not what you believe.
• Streaks — days in a row with any reading. Powerful for building a daily habit; corrosive if a broken streak makes you quit. Know which type you are before you turn them on.
• Finish rate and DNFs — of the books you start, how many do you finish? A low rate is not shameful, but it might mean your selection method needs work more than your discipline does.
• Author and genre breakdowns — the yearly rearview. This is where you notice that eleven of fourteen books were the same subgenre, or that you read no authors in translation. It only becomes meaningful after months of data, so do not start here.

Stats to treat as decoration: reading-speed percentiles, projected books-per-decade, and anything comparing you to other users. They are fun once and useless after.

The data problem: stats need sessions

Here is the catch most "reading stats" articles skip: finish dates alone cannot produce most of the stats above. If all you record is "finished May 12," no app can tell you your pages per day, your reading times, or your streaks. The unit of real reading data is the session — a start time, an end time, and roughly how far you got.

That is why the tools below split into two camps: shelf-based trackers (Goodreads, and largely StoryGraph) that infer stats from dates and progress updates, and session-based trackers (Leafed, Bookly) that record the reading itself.

Tracking stats with Leafed: sessions + Insights

Leafed treats sessions as a first-class feature. When you sit down to read, start the timer from the book's page; when you stop, the session saves with its duration and your page progress. Forgot the timer? Log the session manually afterwards — a guessed "about 45 minutes" is far better data than nothing. Sessions work fully offline, like the rest of the app.

From there, the Insights view does the arithmetic: pages and minutes per day, session patterns across the week, streaks, goal progress, books per month, and author and genre breakdowns, plus a monthly and yearly wrapped summary when the calendar rolls over. The distinctive part is where this happens: on your device. No reading behavior is uploaded for analysis, there is no account requirement, and nobody's engagement dashboard knows your Tuesday reading time. If you do sign in with the optional free account, your synced library also gets a web Insights view — same data, bigger screen, still only yours.

Where Leafed loses, honestly: it does not gamify. There are goals and streaks, but no achievement badges, no ambient reading soundscapes, no celebratory animations when you hit a target — Bookly does all of that better, and some readers genuinely need it. And Leafed's analytics are about your habits, not your taste: StoryGraph's mood and pacing charts have no equivalent here.

The alternatives, fairly

StoryGraph — the best-presented analytics

StoryGraph's stats pages are the prettiest in the category and uniquely good at taste analysis: moods, pacing, format splits, and diversity of what you read. If your question is "what kind of reader am I?", StoryGraph answers it better than anyone. Its limits: it is an account-based online service, it is not built around a session timer, so habit stats (when you read, minutes per day) are weaker, and some analytics sit behind the paid Plus tier. See Leafed vs StoryGraph.

Bookly — the deepest timer gamification

Bookly is the session-tracking specialist. Its timer drives reading-speed estimates, time-to-finish projections, streak rewards, achievements, and ambient sounds — the fullest gamified reading experience available, and for streak-motivated readers it genuinely works. The trade-offs are the freemium model (book limits and ads on the free tier, real stats behind the subscription) and a thinner library and notes experience than a full tracker. The head-to-head is here: Leafed vs Bookly.

A spreadsheet — unlimited questions, unlimited effort

Log sessions as rows (date, minutes, pages, book) and a spreadsheet can compute anything any app offers plus the questions no app asks — pages per dollar, fiction ratio by season, whatever you care about. The cost is entering every session by hand, forever. Most readers who try it keep the app for capture and use the sheet for analysis: Leafed's CSV/JSON export exists for exactly this.

Four stat-tracking traps (and how to dodge them)

Reading stats have failure modes, and they are predictable enough to name:

• Optimizing the number instead of the reading. Once "books per month" becomes a target, short books start looking suspiciously attractive. If you notice yourself dodging a 700-page novel you actually want to read, switch your goal to minutes per day — it is the one metric that cannot be gamed by picking thinner books.
• The broken-streak spiral. For some readers, a 40-day streak ending on day 41 kills the habit entirely — the streak was carrying the motivation, not the reading. If that is you, track "days read this month" instead: same signal, no cliff.
• Audiobook accounting. Pages-per-day quietly excludes listening, which can erase a third of some readers' actual reading. Log audio sessions in minutes and let minutes be your cross-format truth.
• Comparing your dashboard to someone else's. Public reading challenges turn a private habit into a leaderboard, and leaderboards reward volume over anything else. One advantage of on-device stats — the Leafed model — is structural: there is no feed to compare against, so the only reader your numbers answer to is last month's you.

The common thread: stats should describe the habit, not become it. The moment a metric starts choosing your books for you, retire that metric for a season.

A four-week starting plan

1. Weeks 1–2: just capture. Log every session — timer or manual — without judging the numbers. You are establishing a baseline, and the first surprise is usually how different reality is from your self-image.
2. Week 3: read the sessions. Find your real reading windows and protect the best one. If the data says lunch breaks beat bedtime, believe it.
3. Week 4: set one goal. One — minutes per day or books per month, slightly above your baseline. Stacked goals in week one is how stats tracking dies.
4. Ongoing: check monthly, not daily. Daily stat-checking turns reading into a dashboard job. A monthly ten-minute review (your wrapped, your streaks, your rut check) is enough to steer.

And a permission slip: if tracking ever makes reading feel like a treadmill, drop every stat except the log itself. A plain list of finished books — see reading log apps — preserves the record with none of the pressure, and you can resume stats whenever they sound fun again.

What to do with a year of data

The payoff for twelve months of sessions is the December review, and it is worth doing deliberately rather than just admiring the wrapped graphic. Three questions extract most of the value. What did the habit actually look like? — total books and minutes, yes, but especially the shape: which months collapsed, and what else was happening then. What did I love, and what predicted it? — line up your five-star reads and look for the common thread; it is often format or length rather than genre. What is one deliberate change for next year? — one, not five: a genre to visit, a reading window to protect, a lower goal that you will actually clear.

Leafed's yearly wrapped assembles the raw material on-device, and the CSV export means you can go deeper in a spreadsheet if a question nags at you. However you run it, write the three answers into a note — next December, the comparison is the best reading stat you will own.

Related reading

• Reading log apps: keeping a digital reading log
• Leafed vs Bookly: tracker vs reading timer
• Leafed vs StoryGraph
• Best book tracker apps (2026)

FAQ

What reading stats should I track?

Books per month, pages or minutes per day, and session times are the core three. Add streaks if they motivate you, and genre/author breakdowns once a few months of data exist.

Is there a reading stats app that works without an account?

Yes — Leafed records sessions and computes all stats on your device, free, offline, with no account. Signing in to the optional free account adds a web Insights view of the same data.

How do reading sessions work in Leafed?

Start the timer when you begin reading, stop it when you finish — or log the session manually afterwards with duration and pages. Sessions feed goals, streaks, daily figures, and the monthly and yearly wrapped.

Which app has the best reading statistics?

For taste analytics, StoryGraph. For gamified timer stats, Bookly. For complete habit stats that stay private and on-device, Leafed. A spreadsheet beats all three for custom questions — at the cost of manual entry.