Calculatorbook to anki cards calculator

Book To Anki Cards Calculator

Estimate how many Anki cards a reading plan will generate before you export a book and accidentally build a deck larger than the habit can carry.

FreeInstant resultNo upload needed

Estimate cards per week from reading pace and unknown-word density.

Translate extraction policy into new cards per study day.

See whether your filtering rules produce a light deck or a future burden.

Calculator panel

Inputs update the result instantly.

Live estimate

Pages per week

Use the reading volume you can actually sustain.Unknown words per page

A rough average from a representative sample page.Keep rate after filtering

What percentage of unknown words become actual cards.Duplicate reduction

Estimated overlap removed through deduplication and repeated vocabulary.Study days per week

Needed to convert weekly extraction into a daily intake.Average seconds per review

sec

Use your normal review speed, not your rushed speed.Deck intensityChoose how aggressively you expect to learn and retain each new card.

At this reading pace, your extraction policy points to about 81 cards per week, or 14 new cards per study day.

Raw unknown words per week

360

Before filtering, deduplication, or card triage.

Estimated cards per week

After keep-rate and duplicate reduction are applied.

New cards per study day

6 study days each week.

Estimated review burden

16 min / Comfortable

106 reviews per study day at your current review speed.

Operator notes

This is workable, but only if your filtering stays disciplined. A small increase in keep-rate can make the deck much heavier.

Your keep-rate is reasonably selective. If the result still feels heavy, the problem is likely text difficulty or reading volume rather than filtering discipline.

At this pace, the review layer alone lands around 1.6 h per week. Judge the extraction policy by weekly time, not just card count.

How to interpret this tool

Most deck problems begin upstream. The issue is often not Anki itself, but the extraction policy you chose before the first card even existed.

This calculator turns reading volume, unknown-word density, and filtering discipline into a concrete card estimate so you can judge the deck before you generate it.

Usage notes

Use this for planning, not for pretending you can simulate every Anki scheduling edge case.

If the output looks mathematically fine but still feels emotionally heavy, trust the behavior change. That is often the earlier signal.

If one variable fixes the result, change that variable first. Do not redesign your whole workflow unless the simple fix fails.

FAQ

Why estimate cards before exporting the book?

Because the cheapest place to fix deck overload is before the deck exists. Once the cards are generated, most users keep too many of them.

What does duplicate reduction mean here?

It represents overlap, repeated lemmas, and words you would not keep twice after filtering. Real books repeat vocabulary more than raw extraction lists suggest.