Skip to content
TrademarkTrademark
Docs
Data

Choosing a chart

Updated: November 12, 2026
View on GitHub

Start from the question the reader brings, not from the data. "How did revenue move this year?" is a line. "Which team has the most open tickets?" is a bar. "What share of sessions came from search?" is a pie, if there are only a few parts. The same rows can answer all three, and each question wants a different chart.

By question

  • How did it change over time? LineChart. A line says the value moved continuously between readings.
  • Which is bigger? BarChart. Lengths from a shared baseline are the easiest thing to compare.
  • Which is bigger, with long names? BarChart orientation="horizontal". Category names read along the row instead of being cut under the bar.
  • What adds up to the total? BarChart stack or LineChart stack. Each part sits on the one before it, so the top is the total.
  • What is each part's share, over time? stack="percent". Every bar or column runs to 100%, so shares compare across rows.
  • What is each part's share, once? PieChart. Two to five slices. Past that, use a horizontal bar chart.
  • How do a budget and its spend compare? LineBarChart. A line for the target, bars for the actuals, on one scale.
  • How is it trending, in a tile or a table cell? Sparkline. The shape only: no axes, legend or card.
  • How close is it to a limit? RadialGauge or LinearGauge. One value against a range, such as a quota or a score.
  • What is each part's size and direction, with many parts? Treemap. Area for size, colour for up or down.
  • Which way did each item move? DivergingBars. Gains right, losses left, from one zero.
  • Where are the busy months, or hours? Heatmap. A grid of two periods, each cell's size in one hue.

By data shape

  • A date and one or more numbers per row: LineChart, or BarChart for a handful of periods.
  • A category and one number per row: BarChart, or PieChart for a few parts of a whole.
  • A category and several numbers per row: BarChart (grouped), or stack when the numbers add up.
  • A target and an actual per row: LineBarChart.
  • Readings at uneven intervals: LineChart xAxisType="number".
  • A plain array of numbers: Sparkline.
  • One number: a gauge, or a stat tile with a Sparkline.

Every chart but Sparkline and the gauges takes the same data and series, so moving between LineChart, BarChart and LineBarChart is a change of the tag name. See Data and series for the shape.

Things to avoid

  • A pie with many slices. Past five, the small slices are slivers nobody can compare. Keep the top four and group the rest as "Other", or use a horizontal bar chart. The recipe is in Recipes.
  • A smooth line through jumps. The default curve="natural" claims the value moved between readings. A price tier or a seat count changed in steps: use curve="step".
  • Two scales on one axis. LineBarChart has one y axis. A rate (4%) next to a count (8,000) sits flat on the baseline. Use two charts.
  • Stacking things that don't add up. Stack revenue by channel, not revenue and margin. The top of a stack should mean "total".
  • A bar chart for a long time series. Fifty bars become a comb. Use a line, or barWidth="fill" if it has to be bars.
  • Colour that only decorates. A single series doesn't need a hue per bar. Give it the brand (color: "brand") and let the length do the work.

One example, three charts

The same rows, asked three questions.

How did it move?
How did it move?: data
monthWebStore
Jan12488
Feb13191
Mar15886
Apr17294
May19599
FebMarAprMay
Which is bigger?
Which is bigger?: data
monthWebStore
Jan12488
Feb13191
Mar15886
Apr17294
May19599
JanFebMarAprMay
What is the total?
What is the total?: data
monthWebStore
Jan12488
Feb13191
Mar15886
Apr17294
May19599
JanFebMarAprMay
Edit this page on GitHub