Wanilog, modern WaniKani stats

[ricardo1]

Wanilog, modern WaniKani stats (wanilog.com)

Hey all! First time posting on the forum (been lurking for a while).

Built this after years of using wkstats and wishing it worked better on mobile. Wanilog is installable, offline, and has a few things I’ve always wanted in a stats dashboard.

Want to try Wanilog without using your API key? Hit Try the demo on the login page

Features

• Kanji Odyssey - a ~25-second cinematic replay of your journey, milestone kanji reveals, and a shareable stat card at the end.

• Share card - Spotify-Wrapped-style image of your SRS distribution, item counts, accuracy, and estimated JLPT level. Download as PNG or copy to clipboard, with toggles for hiding your username or days-in-WK. Launch it from the Home dashboard.

• Can I Read This? - paste any Japanese text and see which kanji you already know, with unknown ones highlighted and clickable for Jisho.

• Projection - finish-date forecast from your real median level time, with a what-if pace slider and per-level outlier exclusion.

• Reading coverage - JLPT, Joyo, and top-2,500 tracking with sample NHK articles filtered to your level.

• Leech list - your weakest items, ranked Anki-style (wrong ÷ √total) so chronic problems beat one-off slips. Page through in batches of 20.

• Accuracy breakdown - per type and SRS stage, including an effective pass rate (meaning × reading).

• Items browser - group by level or SRS stage, live-search by kanji, kana, romaji, or meaning.

Plus: rich hover tooltips on every kanji / vocab / radical (on’yomi, kun’yomi, meaning, review history, audio pronunciation, jisho + wanikani.com links), critical-kanji blockers on the Level-up page, SRS distribution donut, level-up history chart, command palette (⌘K) for quick nav.

Settings worth knowing

• Goal date - the hero turns green or red based on your pace

• Kanji outside WaniKani - paste kanji you’ve learned elsewhere and they count as known across the coverage pages and Can I Read This

• Japanese font picker - four options including a handwriting-style rounded font

• Audio voice preference, auto-refresh cadence, compact density, celebration toggles, JSON stats export

Privacy promise. Your API key stays in your browser. No backend, no server of mine ever sees your key - it goes straight from your device to the WaniKani API, and your sync data lives in your own IndexedDB. Free, no ads, no account.

Install it like an app

It’s a real PWA. Head to Settings → Install app and you’ll get step-by-step instructions tailored to your exact browser - iOS Safari, Android (Chrome or Firefox), desktop Chromium, or Safari on macOS Sonoma+. Once installed it launches from its own icon and works offline after the first sync.

---

Side project I built for myself. Especially keen on feedback from higher-level users - I’m only L5 so my own testing has gaps. Thanks all!

[Taniotoshi]

Nicely put together. I will use for a while and see what I get out of it.

In WKstats each kanji or item has a mouseover and link to the wk reference information. That’s the only area I felt this was lacking.

[ricardo1]

Thank you for the feedback! I’ve just added the mouseover now

[equant]

I’ll try it for a while, but right away it seems nice. First thing I thing I’d like to see changed would be the “What if you were faster?” …. It has me averaging 21 days per level. Lately I’ve been slower than that. It would be nice to see what 25 days per level looks like. I’m definitely more likely to ponder going slower than faster at this point.

[ricardo1]

@equant

I’ll try it for a while, but right away it seems nice. First thing I thing I’d like to see changed would be the “What if you were faster?” …. It has me averaging 21 days per level. Lately I’ve been slower than that. It would be nice to see what 25 days per level looks like. I’m definitely more likely to ponder going slower than faster at this point.

Thank you, I’ve just pushed an update that allows the slider to go up much more (+ renamed it to “What if your pace changed?”)

[BlueWisteria]

@ricardo1

https://wanilog.com

I like it so far, just wish the burn vs not learned on the kanji map were easier to tell apart. Since both are grey, it’s a little confusing. I liked the yellow that wkstats uses.

[ricardo1]

@BlueWisteria

I like it so far, just wish the burn vs not learned on the kanji map were easier to tell apart. Since both are grey, it’s a little confusing. I liked the yellow that wkstats uses.

You’re right - I’ve also made this yellow now so it’s clearer!

[equant]

Cool… Thanks for the changes.

I discovered the “Reading coverage” page which is pretty interesting. For NHK Easy news it shows a bunch of 100% coverage headlines that are all quite old. I’d love a way to see the best articles (for me) over the last n weeks.

[BlueWisteria]

Thank you! I also noticed when I was looking at the kanji map for jlpt, that the last couple hundred n1 kanji there is no more referencing to Wanikani. Are those kanji not on Wanikani? Would it be possible to put those separated like wkstats does? It’s a little abrupt for the kanji to suddenly not say anything or link to anywhere.

[KitsuFuwa]

I just tried it on Desktop, not yet on mobile, but it looks very cool! Really clean and modern UI. I’ll give it a try on Android later on.

I wasn’t using much WaniKani stats because of the UI for a start, but with Wanilog I may keep going back to it, especially with the PWA on the phone.

Thank you for this nice tool

[ricardo1]

No worries. Unfortunately the NHK Easy website has no reliable way to get the latest articles, so I decided to just remove this for now. I’ve added some new options to the regular NHK - you can now filter by “Best coverage / Best for learning / Most recent”. Hope that helps

[ricardo1]

These have been separated out now!

[_Michael]

Looks nice and polished. One thought: in my opinion the accuracy should not be the mean of meaning and reading, but the product. So basically:

meaning accuracy 90% and reading accuracy 70% should not be 80%, but 63% total accuracy.

[ricardo1]

Thank you! That’s true, I’ve just added an “effective accuracy” column.

[ricardo1]

Hey everyone, I have added a new sharing feature - you can now make a copyable “Spotify Wrapped” esque card which you can share with others. Example below:

[DuoLingo]

@_Michael

meaning accuracy 90% and reading accuracy 70% should not be 80%, but 63% total accuracy.

I disagree. Accuracy in our srs reviews simply reflect what % of questions were answered correctly. So, if we were tested on 10 meanings and 10 readings and we got 9 meanings correct and 7 readings correct, we get 90% for meanings and 70% for readings. And, in total we got 16 items correct out of 20 items for an accuracy of 80%.

Multiplying the 90% and 70% figures to get “total” or “effective” accuracy occurs in the realm of probabilities where the outcome of the subsequent event is dependent on the outcome of the first event which isn’t the case in our srs reviews.

Please return your accuracy calculations as you had it before.

[_Michael]

My interpretation is different, since I consider one kanji (or one vocabulary item) as a unity of meaning AND reading(s). So in your example: If we tested 10 meanings and 10 readings it is still only 10 items that got tested.

Or in other terms: Only when I can recall the meaning AND reading of an item, I consider it as learned. It is indeed similar like probabilities: Accuracy is the probability that I can remember the meaning AND reading of a kanji/vocab.

[ricardo1]

There are two columns - the default accuracy and the effective accuracy (combined meaning + reading)

[DuoLingo]

That works!

[princejuice]

This is real cool stuff ngl!