Compare Libraries

TanStack Charts is currently an unpublished 0.0.0 product proof, not a production replacement for the established releases below. This comparison records the architectural differences and evidence available today without turning untested behavior into a checkmark.

Tested versions#

These are exact repository pins, not the latest versions inferred at page render time.

Capability matrix#

• ✅ First-party path in the pinned package
• 🟡 Requires application or host composition, or an explicit lifecycle step
• 🔴 No first-party path in the pinned package

A checkmark means the named path exists; it does not claim identical defaults, accessibility, output, or performance.

The standard suite exercises axes, guides, tooltips, legends, and multi-series composition. Selection, animation, and resize paths are recorded but excluded from timing. Renderer and framework rows follow each package's documented output model.

Bundle snapshot#

Baseline date: 2026-07-29.

Each range covers 12 independently built, minified browser consumers: line, bar, area, and scatter at basic, interactive, and advanced tiers. Full size is a cold-page bundle. Only Recharts has a separate incremental result because that lane externalizes React and React DOM.

The tracked baseline records the package versions and complete chart/tier matrix; the deterministic bundle gate rejects either kind of drift.

The range is not an install size or a runtime-speed ranking. The comparison builds the current TanStack workspace source and the pinned competitor packages. Browser timing is meaningful only within one machine and browser run, so this page does not publish a cross-machine timing leaderboard.

Broader conformance#

The catalog corpus contains 100 TanStack/reference pairs: 68 sourced from Observable Plot, 21 from Recharts, and 11 from Apache ECharts. Sixteen pairs carry executable interaction scenarios. Those counts describe selected reference coverage, not each library's feature ceiling or a list of built-in TanStack chart types. Chart.js participates in the standard and stress suites, not the catalog corpus.

The catalog displays each renderer entry and its case-local data or transform dependencies. Its report counts the complete transitive authored source and publishes the source-line ratio for every pair; moving transforms into data.ts does not remove it from the comparison.

TanStack deliberately keeps several responsibilities outside the default runtime:

Choose Chart.js when Canvas-first standard charts and its plugin ecosystem fit the application. Choose Apache ECharts for a broad built-in controller and chart catalog with Canvas or SVG output. Choose Recharts for a React-native SVG component model. Choose Observable Plot for concise exploratory marks and transforms. Choose TanStack Charts when one typed, framework-independent definition must grow from standard charts into application-specific SVG or Canvas composition while keeping D3 and state ownership explicit.

Evidence and reproduction#

• Standard comparison protocol
• Tracked bundle baseline
• Stress protocol
• Catalog conformance protocol

pnpm benchmark:size
pnpm benchmark:check
pnpm benchmark:stress:quick
pnpm conformance:quick

The browser-backed commands require the pinned Playwright browser. Read the bundle and performance guide before interpreting results, and use the migration guide to establish application-specific parity before replacing an existing library.