This entry is part of the Chart Index, the reference library for the Chart Design Field Guide.

The area chart is a line chart with the region beneath filled. That single change shifts the message: a line says here is the trajectory; an area says here is the volume. The filled region accumulates visual weight, which is appropriate when the underlying quantity is itself cumulative or volumetric — and misleading when it is not.

Area charts are the form most commonly misused in business reporting. Two overlapping translucent areas, three stacked series with no zero baseline, gradient fills that hide the data — these are the standard pathologies. The fix is almost always the same: ask whether the area is meaningful, or whether a line would say it better.

What it is

An area chart maps a continuous variable to one axis and a quantitative variable to the other, joining the points with line segments and filling the region between the line and a baseline. The fill is the encoding: its vertical extent at each x-position represents the value, and the total area under the curve has a literal volumetric meaning when the quantity is a rate.

Cumulative API calls · 14-day window2026-05-15 → 2026-05-28 · billions

A cumulative metric is the canonical case: the fill makes the running total perceptually obvious. The line's slope shows the rate; the area shows what has been accumulated.

When to use it

Area charts are appropriate when:

  • The y-value is a cumulative quantity — running totals, integrals, anything where the area under the curve has literal meaning.
  • The reader's question is "how much, in total?" rather than "how fast?"
  • You have one dominant series to show, or stacked compositions of a small number of series (3–5 max).
  • The data is non-negative and continuous — area charts with negative values require careful baselining and usually a different form.
  • You want visual weight to emphasise volume — a line of the same data feels lighter and more analytical.

When not to use it

  • Multiple overlapping series. Two translucent areas overlapping create a third colour where they intersect; the eye cannot disentangle which series owns which value. Use lines.
  • Sparse data. An area chart with five data points connected by straight lines is mostly empty fill. The form needs density to feel like a continuous quantity.
  • Negative values. Area charts read most naturally with a zero baseline and positive values. Negative regions require careful design and are usually better as a bar or line chart with reference lines.
  • Comparing rates of change. The fill obscures slope; for "how fast is this growing?", a clean line is clearer.

Design principles

Anchor at zero

Unlike line charts, where a non-zero baseline is often appropriate, area charts almost always require a zero baseline. The fill is the encoding — if the baseline floats, the area no longer represents the quantity, only the change.

Keep fills quiet

The fill should be lighter than the line that bounds it. A typical setting: line at full saturation, fill at 8–15% opacity. The reader perceives the boundary first, then the volume. A heavy fill drowns the line and makes the data harder to read.

Use a single colour family

When multiple series stack, stay within one hue family or use a low-chroma categorical palette. Stacked areas in saturated rainbow colours read as decorative; in muted, related tones they read as analytical.

Area chart fill weights
OPACITY 0.05 — FILL DISAPPEARSOPACITY 0.12 — BALANCEDOPACITY 0.35 — TOO HEAVY
The same series rendered at three opacities. The middle weight reads as the data series; the heavy weight competes with the line; the light weight nearly vanishes.

Show the boundary line clearly

The line where fill meets the air is what the eye reads as the data. Make it 1.5–2px and full-saturation; the fill underneath supports it. A common mistake is to use a thin line with a heavy fill — the eye reads the top of the fill, but it is fuzzy, and the precise value becomes hard to pick up.

Avoid gradient fills

Gradients fade the value at the bottom of the chart into the background and add visual noise that means nothing. A flat fill at a single opacity is more truthful and more legible. Gradient charts are decoration borrowed from data-art; they have no place in analysis.

Mark the area, not the boundary, when the volume is the story

If the reader's question is "how much was processed?", annotate the area itself with a numeric callout near the centre of the filled region. If the question is "when did it peak?", annotate the boundary. Place the label where the eye lands when it asks the question.

Break the line for missing data

As with line charts, never interpolate through gaps silently. If a day is missing, drop the fill to zero or break the path entirely. A smooth fill through missing data implies values that were never recorded.

Anatomy

The Composition of an Area Chart
403020100JanFebMarAprMayJunfill (volume)boundary linezero baseline (required)
An anatomical guide

The area chart has one structural requirement the line chart does not: the zero baseline. Everything else — boundary line weight, fill opacity, axis treatment — follows from the same Tufte/Few principles that govern any continuous-axis form.

  • Line chart — for the same data when slope and rate are the message rather than volume.
  • Stacked area — for compositional change over time. Covered in a separate entry.
  • Stream graph — stacked areas with a flowing central baseline. Decorative but powerful for shifting compositions.
  • Horizon chart — area chart folded into bands for dense small-multiple displays. Covered in a separate entry.
  • Histogram — looks similar but encodes a distribution over bins, not a quantity over time.

Reading list

  • Tufte, E. (2001). The Visual Display of Quantitative Information. On data-ink ratio and chartjunk.
  • Few, S. (2012). Show Me the Numbers. On when area charts help and when they harm.
  • Byron, L. & Wattenberg, M. (2008). Stacked Graphs — Geometry & Aesthetics. The formal treatment of area-stacking layouts.