How it works
The workflow, examples and limits behind every tool.
Card editor ↗
Each card has a front, back, optional tag and local review state. CSV import creates new cards with no review history.
Example: A CSV row containing “Capital of France?” and “Paris” creates one two-sided card.
Up to 200 cards; each side is plain text, up to 2,000 characters. No built-in copyrighted study decks or AI generation.
Practice ↗
A simple box schedule uses 1, 3, 7, 14 and 30 days. Again returns the card to box 0, due today; Good advances one box and Easy two.
Example: A new card marked Good is due tomorrow. The same card marked Good at its next review is due three days later.
This is a transparent practice schedule, not Anki, FSRS or a prediction of memory. The Again queue repeats only when you start another session.
Review plan ↗
Today includes all overdue cards. Future dates count cards by their stored due date; unreviewed cards are due today.
Example: Two overdue cards plus one card due today make three cards to review today.
Dates use your device’s local calendar. Changing the system date can change what appears due.
Deck backup ↗
JSON preserves IDs, boxes, due dates and review totals. CSV preserves the front, back and tag only.
Example: Use JSON when changing browsers to retain progress; use CSV when preparing cards in a spreadsheet.
Cards and progress stay in this browser. Export before clearing site data or changing devices.
Local work, explicit limits
Each workspace reports its input and file limits. Imports validate the supported format before asking to replace saved work. Plain text is displayed as text, never executed as markup. Both languages use the same tools; the root address always opens in English, with Chinese under /zh/.