PDF to flashcards

How to turn a PDF into flashcards you'll actually review

Turning a PDF into flashcards is a two-stage job, and almost everyone skips the second one. Stage one is extraction — pull every testable claim out of the document, which any decent tool does in under a minute. Stage two is culling — delete the two thirds that are unanswerable, trivially obvious, or duplicated, because a review queue full of junk cards is abandoned within a fortnight and takes the habit with it. This is how to do both, and what makes a card survive the cull.

9 min readAI and learning

Why the raw output is never the deck

Ask any generator for flashcards from a 40-page PDF and you'll get several hundred. They will include: definitions worth knowing, the same definition three times in different words, questions about the document rather than the subject ("What does Figure 3 show?"), and cards whose answer is a paragraph. The first category is your deck. The rest is what turns a review queue into a chore.

The cost of a bad card is not zero, it is compounding. A card you can't answer gets marked wrong, so the scheduler shows it more often, so the queue grows, so you skip a day, so the queue grows further. Decks die from junk cards, not from difficulty. This is the failure mode described in AI flashcard quality.

The five-test cull

Run every generated card past these. It takes about four seconds per card and it is the difference between a deck you keep and one you abandon.

TestDelete the card if…
One answerThe question has more than one defensible answer, or the answer is longer than about fifteen words.
StandaloneIt only makes sense with the PDF open — "According to the text…", "In this chapter…", any reference to a figure number.
Not freeYou can answer it without knowing anything, by grammar or elimination.
Not a duplicateAnother card already tests the same fact from the same direction.
Worth the intervalYou would not care if you forgot it. Ruthlessness here is what keeps the queue small enough to clear daily.

Splitting the fat cards instead of deleting them

The most common bad card is one whose answer is a list: "What are the causes of X?" with six bullets. It fails the one-answer test, but the content is genuinely examinable. Don't delete it — split it.

  • Turn the list into cloze cards: "The causes of X are A, B, C, D, E and ___" — one card per hidden item, each with a single answer.
  • Add a count card: "How many recognised causes of X are there?" This is the one that saves you in the exam when you've listed four and can't remember whether there were five.
  • Keep one whole-list card for the week before the exam if the exam genuinely asks you to produce the whole list — but tag it so it isn't in your daily queue.

The full workflow

  1. 1

    Check the PDF is actually text, not pictures of text

    A scanned handout or a photographed page is an image. If you can't select the words in a PDF reader, no extractor can read them either without OCR. Tools differ sharply here — some silently produce nothing useful, which looks like a bad tool and is actually a bad input.

  2. 2

    Cut the PDF down before you generate

    Drop the title page, the reading list, the acknowledgements and the appendices you were never assigned. Every page you leave in produces cards you'll have to delete. Ten seconds here saves ten minutes of culling.

  3. 3

    Generate, then walk the list once with a delete key

    First pass is deletion only — don't edit, don't improve, just delete anything failing the five tests. Expect to remove half to two thirds. If you're deleting fewer than a third, you're being too kind.

  4. 4

    Second pass: split the list-shaped survivors

    Any card whose answer has commas in it. Turn it into clozes as above. This is where the deck goes from mediocre to good.

  5. 5

    Third pass: add the questions the PDF didn't ask

    The document explains; the exam applies. Add three or four "why" and "what would happen if" cards per topic yourself. These are always the highest-yield cards in the deck and no extractor generates them well.

  6. 6

    Put it on a real scheduler and review daily

    A deck reviewed on a proper interval algorithm costs a few minutes a day and holds for months. A deck reviewed by flipping through the whole stack costs an hour and holds for a week.

Textbook chapters versus lecture slides versus papers

SourceCards per 10 pagesThe trap
Lecture slides25–40 — dense, already distilledBullet fragments make questions with no single answer. Expect heavy splitting.
Textbook chapter15–25 after cullingEnormous volume of context prose that generates trivia. Cull hardest here.
Journal paper5–10, mostly method and conclusionAlmost all of a paper is not examinable. Cards about the specific study rarely earn their place.
Your own handwritten notes20–30Needs handwriting recognition first; abbreviations you invented won't be understood.

When not to bother

Flashcards are for facts you must produce from memory, quickly, without reasoning. They are a poor fit for material where the exam asks for an argument, a derivation or a judgement. A law student's case-name-to-principle cards are excellent; "cards" summarising an essay's structure are wasted effort that would be better spent writing the essay.

If the PDF is a reading you need to *understand* rather than *know*, summarise and self-explain instead — self-explanation buys more per minute on that kind of material than any deck will.

Common questions

How do I turn a PDF into flashcards automatically?

Upload the PDF to a flashcard generator, generate a first draft, then cull it hard — expect to delete half to two thirds. The generation is the easy part and takes a minute; the culling is what determines whether you still review the deck in three weeks.

Are AI-generated flashcards any good?

The good ones are as good as yours and arrive a hundred times faster; the bad ones are unanswerable, duplicated or subtly wrong. The deciding factor is whether you review the output. A generated deck accepted wholesale is usually worse than thirty cards you wrote yourself; a generated deck culled to a third is usually better.

How many flashcards should I make from one lecture?

Twenty to forty from a typical slide deck, after culling. If you're ending up with over a hundred from one lecture you're carding context rather than testable facts, and the queue will become unclearable within a fortnight.

Why won't my PDF generate any flashcards?

It's almost always a scanned or photographed document — an image of text rather than text. If you can't select and copy the words in a PDF reader, the extractor can't read them either. Run it through OCR first, or use a tool that handles handwriting and scans directly.

Should I use cloze deletion or question-and-answer cards?

Cloze for lists, sequences and anything where the whole answer is long — it splits one bad card into several good ones. Question-and-answer for definitions, mechanisms and relationships. Most decks want both, and list-shaped material converted to Q&A is the commonest source of cards nobody can answer.

Can I check whether a generated card is correct?

Only if the tool cites where it came from. Page-level citations turn verification into a four-second check; without them you have to trust the model or re-read the document, and in practice people trust it. Insist on citations for any material you'll be examined on.

Try it on your own material

Upload your notes, slides or lecture recordings and get a tutor that answers only from them — and says so when they don't cover it.

$12/month, or $8/month billed yearly · cancel in two clicks