Problem
People need to see a total and how its parts contribute to changes in that total.
Solution
Stack categories using a common measure, keeping their order and colors stable. Label the total and make individual values available.
Use ordinary stacking to show both total quantity and composition. Use 100% stacking only when the question is about shares, and show the total separately if it still matters.
Place the category needing the closest comparison against the baseline. Use another chart when precise comparison among all categories is the main task.
Use when
The categories add up to a meaningful whole and both the total and its composition matter.
Don’t use when
The viewer needs to compare middle series against each other, or the categories don’t actually sum—stacking overlapping or double-counted quantities produces a total that means nothing. Above roughly six or seven categories, bands become slivers and the chart is a colour test.
Trade-offs
Middle bands are harder to compare because their baselines move. Changes below a band can make it appear to rise even when its own value is stable. A 100% chart hides changes in total volume.
Checklist
- Do these parts genuinely sum to the whole, with no overlap or double counting?
- Which series is at the bottom, and is it the one that most needs accurate reading?
- Is category order stable between refreshes and between viewers?
- How many categories, and is the thinnest band still visible?
- Is there an “other” bucket, and does it carry a count?
- Normal or 100%, and does the choice match the question being asked?
- If 100%, is the total available anywhere on the page?
- Do colours stay assigned to the same category across every panel?
- Could a viewer mistake a rising baseline for a growing band?
- Would small multiples let them compare the middle series properly?
Compare
Grafana offers stacking as Off, Normal and 100% across its time series, bar chart and histogram panels, which keeps the vocabulary consistent and makes the 100% mode easy to reach without its caveat attached. Datadog defaults many of its resource breakdowns to stacked areas, which suits infrastructure spend where the parts genuinely conserve and totals matter. Netdata stacks per-dimension charts heavily by default, which works because the dimensions are usually a true decomposition of a bounded resource. Amplitude leans on 100% stacking for composition over time, which is the honest use of that mode and still routinely gets screenshotted without the total anywhere in frame. Cloudflare Radar defuses the 100% caveat by printing every segment’s figure above the bar, so the chart can lose the total without the reader losing it. The bar ends up nearly redundant, which is a fair trade when the numbers were the point and the picture was only ever the index to them.
Related
Time series provides the time axis for stacked areas. Ranked list makes dominant parts easier to compare. Ratio and rate explains percentage shares.
Categorical series palette distinguishes categories. Small multiples gives each part its own baseline.