A common frustration: you finish an Anki session, and an hour later you cannot write the kanji you just reviewed. People ask why kanji is not sticking on Anki, or why they forget stroke order so fast. The honest answer is that Anki, by default, is testing the wrong thing for handwriting.
What Anki is great at
Anki is one of the best spaced-repetition tools ever made, and it is free and endlessly customizable. For vocabulary, readings, and recognition, it is genuinely hard to beat, and most serious learners use it for good reason. The issue is not the engine and it is not your discipline. It is the task you are pointing the engine at.
Why kanji does not stick from a flashcard
A standard Anki card shows you a character or a word and asks whether you knew it. You judge yourself good or again and move on. That trains recognition: matching a shape to a meaning. It never asks you to produce the character from a blank space, so your writing recall gets no practice at all. This is the core reason recognition is not recall, covered in recognition versus recall, and it is why you can clear a deck cleanly and still freeze with a pen an hour later.
People sometimes try to patch this by writing the character on a scratchpad before flipping the card. That genuinely helps, and it is better than nothing. But judging your own scribble good or bad on a generic card is awkward, stroke order is not built in, and the friction means most people stop doing it.
What Anki does well, and what writing adds
The two are complementary, not competing, once you see what each trains:
| Anki flashcards | Writing practice | |
|---|---|---|
| Trains | Recognition and reading | Production and handwriting |
| Your action | Reveal, then self-rate | Write the character from memory |
| Stroke order | Not really | Central |
| Best kept for | Vocabulary and readings | Turning recognition into recall |
Keep Anki for the left column, where it is excellent, and add a writing task for the right.
The fix: change the task, not the app
The lever almost no one pulls is the task. A spaced-repetition system does not care whether you review by recognizing or by producing. Point it at producing:
- See the meaning and reading. Keep the character hidden.
- Write it from memory, in stroke order, before checking anything.
- Reveal a guide only if you stall, then write it once more without it.
- Grade honestly, and let the misses return sooner.
That honest self-grade is the whole game, because writing does not let you fool yourself the way recognition does. The page is either right or it is not, which makes the signal feeding the schedule far more accurate. The same spacing that makes Anki work, the spacing effect, now builds writing instead of reading. We go deeper in spaced repetition for kanji writing.
Keep Anki, add writing
You do not need to abandon your deck, and you should not. Keep Anki for vocabulary and reading, where it shines, and add a writing-first app for production. The two cover the whole skill instead of half of it, and they reinforce each other: writing a character also sharpens the recognition Anki built. Kanji Write Practice is made for this pairing, free in early access. If you are weighing other tools, see our free Skritter alternative guide, and if you are prepping a test, JLPT N5 kanji writing practice.
A note on volume: adding writing does not double your workload. Spacing keeps the daily count small, and one writing rep is worth more than several recognitions, the testing effect again, so a few minutes a day is enough.
On the Anki writing add-on route
If you would rather stay entirely inside Anki, there are community add-ons and note types that show a meaning and reading and ask you to write the answer on a scratchpad before revealing it. They are a real option, and for a committed Anki user they can work. Be honest with yourself about two things, though. First, you still grade your own handwriting, so the discipline to mark a sloppy or wrong-order attempt as a fail is entirely on you. Second, stroke-order guidance is not built in, so when you blank completely you have nowhere to look. A purpose-built writing app removes both frictions: it gives you a guide to reveal when stuck, and the writing-and-review loop is the default rather than something you assemble and maintain. Neither path is wrong. The add-on route keeps everything in one app at the cost of some friction; a dedicated writing app trades the single-app tidiness for a smoother loop. If you have tried the scratchpad route before and quietly stopped doing it, that friction is usually the reason.
