ChartKit is 32,110 bytes, measured 2026-10-29. Nivo minimal line is 96,583 bytes, 2026-10-24.
Compare / Nivo
ChartKit vs Nivo
Feature-by-feature against Nivo 0.99.0, checked 2026-10-18. Rank order is native › partial › plugin › manual › none. Unknown is not a win.
ChartKit rechecked 2026-11-04 on 236653ac. Losses stay in the table. They are not the default tab.
Rows
Every scored feature, both answers.
ChartKit ahead is the default. Behind is one click away, in grey.
No features match.
Measured
Beyond the feature count.
Only figures this site already publishes. A missing panel means we do not have that number for Nivo.
Round 13 (2026-10-18, d8dcc5a). Not re-run on bb7c4b8996562106d7f74ae8d2db98f24f08f547. Server render, 100,000-point line: ChartKit 2.63 ms median, Nivo 9971.51 ms median. Browser millisecond rows are ChartKit vs uPlot only. ChartKit line gzip is 32,110 bytes (createRenderer of the line, bench/results/bundle.json, bb7c4b8996562106d7f74ae8d2db98f24f08f547, 2026-10-29). Nivo line gzip is 96,550 bytes with React external, 100,561 with React included (bench/results/bundle.json, 2026-10-29T19:08:35.474Z).
Switch
No Nivo converter yet. The spec is nine lines.
There is no paste converter for Nivo. This bar spec passes validate(). Open it in the playground, or pick a library that does convert.
{
"version": "1", "type": "bar",
"data": [
{ "region": "North", "sales": 40 }, { "region": "South", "sales": 55 },
{ "region": "East", "sales": 32 }, { "region": "West", "sales": 48 }
],
"encoding": { "x": "region", "y": "sales" },
"a11y": { "alt": "South has the highest sales across all regions." }
}