Wanilog for wkstats users, page by page
Somewhere in your first months on WaniKani, your hand learned a route: wkstats.com, Progress, Level-up, the bar chart that says whether this level is going faster than the last. The community has read its progress through those pages since March 2016, when rfindley opened the [STATS] Statistics site thread on the forum. wkstats defined what WaniKani stats look like, and Wanilog keeps that shape: paste your APIv2 key, get your progress charted.
So the only thing you have to migrate is muscle memory. Every row below points at the Wanilog page that answers the same question. One click each.
The page map
| On wkstats | On Wanilog |
|---|---|
| Progress > Dashboard | DashboardLevel, time on level, items learned - the same at-a-glance readout once your key is in. |
| Progress > Level-up | Level-upThe per-level duration chart. Both sites show the median and mark resets. |
| Progress > Projections | Projection ·calculator (no key)A statistical forecast with a p25-p75 band; the no-key calculator carries the fastest-possible-path math. More below. |
| Items > Wanikani | ItemsThe same level 1-60 grid. Where wkstats has the Open Config panel, ours has inline search and SRS-stage grouping. |
| Items > JLPT / Joyo / Frequency | JLPT ·Joyo ·FrequencyPer-list coverage with the same item drill-down. Key-gated on both sites. |
| Charts > JLPT / Joyo / Frequency | JLPT lists ·Joyo by grade ·frequencyPublic pages, no key required - the same role the wkstats chart links play. |
| Charts > Reading | Reading coveragewkstats charts Aozora, NHK Easy, news, Twitter, and Wikipedia per level; ours scores your kanji against live NHK headlines, and needs your key. |
| Accuracy (a section on the Dashboard) | AccuracyThe meaning/reading split gets its own page here, plus a per-level chart and a leech list. |
One definition transfers untouched. The wkstats dashboard counts items learned at Guru and above, and every Wanilog surface draws the learned line at the same stage. The totals you are used to will match here.
The projections row deserves a longer note
On wkstats.com today, Progress > Projections shows a single sentence: "Sorry, this page is still under construction." The community filled the gap: in January 2022, UInt2048 published the WKStats Projections Page userscript, which adds a provisional projections page on top of the site. If your finish-date habit runs through that script, the native counterpart here is /projection.
There is no median-versus-average argument to have here. wkstats' own level-up page prints both the average and the median, and marks resets right on the chart; its dashboard's typical level-up figure is the median too. The sites agree on the statistics. What Wanilog adds is the forecast on top: it takes the median of your completed levels, projects that pace across the levels you have left, and frames the finish as a p25-p75 range. The page says "somewhere between" two dates rather than committing to one your next slow month would invalidate.
Rows with no left-hand column
A few Wanilog pages have no wkstats counterpart. The accuracy page grows a leech list and a trainer that drills your worst items without touching their SRS state. There is a review forecast, and a goal level with a date attached, if you want one. And the whole app installs: add it to your home screen as a PWA and the last-synced dashboard opens offline, on the train, where review ambitions go to die.
None of it is required on day one. The map above covers everything a wkstats habit will reach for.
You can run both
Both sites read from the same WaniKani APIv2 key: the wkstats login asks for exactly the token Wanilog does. Neither one writes to your WaniKani account. The cost of keeping wkstats in one tab and Wanilog in another is the second tab.
If you would rather look around before pasting anything, the landing page has a Try the demo button that loads a seeded account, no key involved. When you do sign in, the first sync pulls your full history and every row on the map fills in with your own numbers. Key handling is on the FAQ.