A capacity-based way to set a sustainable review workload, diagnose overload, and reduce daily cards without throwing away useful scheduling history.
Disclosure: I build AnkiQuiz, the changed-prompt quiz tool discussed below. AnkiQuiz is not affiliated with Anki, AnKing, AnkiHub, UWorld, AMBOSS, the NBME, or USMLE. It does not replace coursework, supervised clinical training, a validated question bank, or official assessments. AI-generated questions can contain errors.
There is no universal number of Anki reviews that is “too many” for a medical student. Two hundred short, focused cards may take one person 25 minutes and another person more than an hour. Five hundred reviews may be a temporary exam-week peak, a large overdue backlog, or the predictable result of an unsustainable new-card rate.
The useful limit is not a card count copied from someone else. You have too many reviews when their honest time cost repeatedly displaces required learning, representative question or skill practice, clinical duties, sleep, or recovery.
This guide shows you how to find that limit from a normal week, identify why the queue is large, and reduce future reviews in the right order. It complements the daily medical-school Anki workflow and the guide to how many new Anki cards to do per day.
The short answer
- Reserve time for fixed course or clinical duties, sleep, and representative practice.
- Give Anki a repeatable time budget, not an aspirational card target.
- Measure seven ordinary days of review count, minutes, new cards, and lapses.
- Convert the time budget into a personal card range using your median seconds per review.
- Treat repeated overflow, rising overdue cards, rushed grading, or displaced priorities as overload.
- Lower or pause new-card intake before changing scheduling settings.
- Narrow active scope and repair leeches, duplicates, and slow cards.
- Use FSRS workload estimates to evaluate retention tradeoffs instead of copying a preset.
Anki's manual notes that consistently learning 20 new cards a day can produce roughly 200 daily reviews, but this is an illustration—not a medical-school prescription. Card difficulty, review history, desired retention, lapses, and active deck size all change the result.
Why a universal review number fails
Cards are not equal units of work
A one-word cloze, a multi-step mechanism, an ECG rule, and an overloaded treatment table may all count as one review. Their time and cognitive demands are different. A raw count hides whether you are retrieving one clear target or learning a paragraph during the answer screen.
Training stages have different constraints
A preclinical student may have predictable lecture blocks but a large volume of new material. A student in dedicated study needs protected question blocks and review time. A clerk may have an early round, an unpredictable shift, patient tasks, and limited evening energy. The same queue can fit one stage and crowd out essential work in another.
A peak is different from a pattern
One unusually high day after travel, illness, or a deck import does not define your sustainable workload. A queue that exceeds capacity most days for two weeks is a system problem. Judge the pattern across representative weekdays and weekends rather than reacting to the largest number on the deck screen.
Fast is not automatically sustainable
Cards per minute can improve when prompts are focused and recall is fluent. It can also improve because you read only part of the prompt, reveal early, accept vague answers, or press Hard after forgetting. A faster session is useful only if grading remains honest and knowledge transfers to the tasks that matter.
Find your personal daily review capacity
Step 1: set the time boundary first
Start with the real day. Block patient care, mandatory sessions, first-pass learning, meals, sleep, and the question, visual, laboratory, or performance practice your course requires. The remaining repeatable block is your Anki capacity.
Do not use the most generous day of the week. Use an amount that can survive a representative week. You may set separate expectations for a normal preclinical day, a call day, and a weekend, but each should protect the work that flashcards cannot replace.
Step 2: measure seven ordinary days
Record:
- total review cards completed;
- total review minutes;
- median or average answer time;
- new cards introduced;
- Again presses or lapses;
- overdue cards remaining at the end of the planned block;
- important work, sleep, or recovery displaced by the queue.
Exclude days when you left Anki open while doing something else. Note unusual events instead of forcing them into the baseline. The goal is not a perfect productivity dashboard; it is a realistic denominator for decisions.
Step 3: translate time into a range
Use this planning estimate:
daily review capacity ≈ available review seconds ÷ median seconds per review
If you have 45 minutes and your recent median is 9 seconds, the rough capacity is 300 reviews. Add a buffer for relearning steps, difficult topics, interruptions, and natural variation. Treat the result as a range, not a quota you must fill.
The equation works in the other direction too. If 450 due reviews usually take 75 minutes but your repeatable limit is 45 minutes, motivation is not the missing variable. Intake, active scope, card quality, lapses, or settings must change.
Step 4: test the boundary across two weeks
A sustainable review load should usually fit without rushed grading or repeated sacrifice of higher-value work. If it fits only by borrowing from sleep, skipping questions, or ignoring clinical preparation, it does not fit.
Use the review-speed diagnostic if time per card is the main problem. Use the backlog recovery plan if overdue cards already span several days.
Seven signs your daily reviews are too high
- The queue regularly exceeds its planned time block. One peak is normal; repeated overflow means demand exceeds capacity.
- Overdue cards grow while new cards continue. New intake is adding future work faster than you can service the existing queue.
- You reveal answers before making a retrieval attempt. The session has shifted from recall to counter clearing.
- You grade forgotten cards Hard to avoid seeing them again. Under FSRS, Hard means successful but difficult recall; forgotten information should be graded Again.
- Questions, images, calculations, practical skills, or clinical preparation disappear. Anki retention is consuming the practice needed for transfer.
- Sleep and recovery become the adjustable part of the schedule. The deck has become larger than the life it must fit inside.
- Most effort goes to low-priority or repeatedly broken cards. The problem is scope or card design, not insufficient endurance.
Diagnose why the count is high
Too many recent new cards
New cards create learning steps and future reviews. A large batch can feel affordable on the day it is introduced and become expensive over the following days and weeks. Compare the review rise with recent intake before changing anything else.
Too much active scope
A comprehensive deck is not a mandate to keep every card active. Old low-priority details, material outside the current curriculum, and duplicate cards can consume the same scheduling attention as current objectives. Preview before unsuspending and suspend AnKing cards deliberately.
Repeated lapses and leeches
A small group of cards may create disproportionate work. The prompt may be ambiguous, the answer too large, the prerequisite missing, or similar facts interfering. Diagnose and repair Anki leeches instead of repeatedly pressing Again on an unchanged card.
Slow or overloaded prompts
If counts are moderate but minutes are excessive, inspect cards that take the longest. Break apart multi-target prompts, remove irrelevant fields, make the required answer explicit, and move first-pass learning outside review. Do not shorten a card so aggressively that the remaining cue gives away the answer.
A backlog rather than a normal workload
Overdue cards from missed days should not be mistaken for the stable daily count the deck will produce forever. Pause new cards, preserve current due work, and process the older backlog in bounded blocks. Avoid resetting the whole deck; resetting discards useful scheduling progress without fixing the cause.
A costly retention target or unnecessary limits
With FSRS, higher desired retention generally produces shorter intervals and more reviews. Use Anki's workload graph or simulator with your own collection and history before changing it. Do not copy a setting because it worked for a different student, and do not push desired retention below Anki's minimum recommendation merely to shrink the queue.
How to reduce reviews in the right order
1. Lower new cards now
This is the fastest way to stop creating additional review debt. Reduce the daily limit or use a temporary zero-new-card period. The due count may not fall immediately, because recent cards still need early reviews, but future pressure will start to ease.
The reviews-before-new-cards guide provides a study order for days when both categories do not fit.
2. Remove low-value active scope
Suspend cards that no longer serve a current objective, but make the decision by deck, tag, resource, or topic rather than randomly hiding today's inconvenient cards. Keep cards connected to current course work, repeated knowledge gaps, or durable clinical foundations.
3. Repair expensive cards after the review block
Flag slow, ambiguous, duplicate, and repeatedly failed cards while reviewing. Repair a small batch afterward so editing does not derail the session. Delete true duplicates, split overloaded prompts, add the minimum missing context, and relearn the underlying concept when needed.
4. Check answer-button habits
Use Again when you failed to recall the target, Hard when recall succeeded with substantial difficulty, Good for correct recall with normal effort, and Easy for genuinely easy recall. Honest grading may feel slower today, but gaming the buttons corrupts the evidence the scheduler needs. See the Again-vs-Hard grading guide for partial answers and common edge cases.
5. Evaluate settings with your data
FSRS can estimate reviews or minutes per day using your cards, memory states, parameters, and desired retention. Compare workload scenarios before committing. Changing desired retention is a tradeoff between workload and recall, not an emergency lever for one difficult afternoon.
Should maximum reviews per day be 9999?
The Maximum reviews/day setting controls how many review cards Anki will show. A high limit is commonly used to make all due reviews visible. That prevents a cap from silently hiding due work, but it does not mean every visible card outranks sleep, patient care, scheduled learning, or representative practice.
A lower cap can smooth an occasional peak or create a bounded backlog-recovery plan. The tradeoff is that cards beyond the cap remain due. Watch the hidden-review message and overdue trend rather than treating the smaller displayed number as completed work.
By default, Anki's review limit also constrains new cards. The official Anki deck-options guide recommends stopping new cards when a backlog exists. Enabling “New cards ignore review limit” can keep adding new material while reviews are hidden, so use it only when that is a deliberate priority decision.
What review capacity can look like at each stage
Preclinical courses
Anchor cards to current learning objectives and protect time to understand mechanisms, interpret images, use laboratory material, and answer legitimate questions. A lower intake early in a block is easier to raise than a review wave that peaks just before the exam.
Step dedicated study
Protect scheduled question blocks, careful review, and validated self-assessments. Keep cards that repair recurring knowledge gaps or preserve high-value material. If broad legacy reviews consume the question-first plan, narrow the active set rather than measuring success by a zero counter.
Clerkships
Build capacity around the busiest realistic clinical days, not only weekends. Patient responsibilities, preparation, feedback, sleep, and shelf-style practice come first. A smaller rotation-specific set completed consistently is usually more workable than carrying every historical card unchanged.
Where AnkiQuiz fits—and where it does not
AnkiQuiz can turn selected Anki text fields into single-choice, multiple-choice, fill-in-the-blank, and true/false questions. After the normal queue and essential work fit, a quiz from 10–20 important cards can check whether recall survives changed wording.
Use that check occasionally:
- choose one current topic and a small set of permitted text cards;
- remove private fields, patient data, clinical notes, and protected question-bank content;
- generate a short quiz and answer without opening the original card;
- reject ambiguous or unsupported questions;
- repair only reusable knowledge or cue problems the sample reveals.
AnkiQuiz does not read your due count, estimate review capacity, change FSRS settings, schedule or edit cards, clear a backlog, validate medical accuracy, or predict exam performance. If reviews are already excessive, do not turn generated quizzes into a second daily queue. The card-to-quiz tutorial explains setup and field selection.
Questions medical students commonly ask
How many Anki reviews per day is too many?
There is no universal count. Reviews are too many when their honest time cost repeatedly displaces required learning, representative practice, clinical duties, sleep, or recovery. Measure your own week and set a time boundary first.
Is 500 Anki reviews a day too many?
It depends on the cards, pace, and available time. If 500 focused reviews fit temporarily without rushed grading or displaced priorities, the number alone is not proof of overload. If they regularly exceed the planned block, reduce intake and scope.
How long should Anki reviews take?
Use the repeatable time left after fixed responsibilities and higher-priority learning tasks. The right duration is one you can sustain across ordinary busy days, not the longest session you can survive once.
Should maximum reviews per day be set to 9999?
A high limit reveals all due work but does not require completing it at any cost. A lower limit can bound peaks, but it hides cards that remain due. Choose deliberately and monitor the backlog.
How do I reduce daily Anki reviews?
Lower new-card intake first, narrow low-priority active scope, repair leeches and slow cards, remove duplicates, and model FSRS changes with your own data. Preserve scheduling history rather than resetting the deck.
Can AnkiQuiz reduce the review count?
No. It does not change the Anki queue or scheduler. It can provide an occasional changed-prompt check only after the primary workload is sustainable.
Set a limit your real week can keep
The right number of daily Anki reviews is the number that fits honest retrieval inside a balanced medical-school plan. Measure minutes, not social-media card counts. Protect the tasks Anki cannot perform. Then control new-card intake, active scope, card quality, and retention tradeoffs until the queue fits the life and training it is meant to support.