How to Create an Animated Waterfall Chart

A total moved and someone wants to know why. Revenue went from $2.1M to $2.6M, and "we grew 24%" is true but useless, because it does not say what added the half-million or what quietly took some of it back. The answer is usually a mix: new business brought in a lot, expansion added more, churn gave some of it back, and the net of those forces is the number everyone is looking at. A single figure hides that arithmetic. A list of the pluses and minuses shows it, but only to a reader willing to track a running total down a column, and most readers will not.

A waterfall chart is built for exactly this question. It starts at one total, steps up and down through each driver that moved it, and lands on the final total, so the reader sees not just that the number changed but which forces changed it and by how much. This is a guide to building one that reads cleanly, with attention to the decisions that decide whether it works: where to anchor the start and end, how to order the steps, how to handle the mix of increases and decreases, and how to export a version that plays the change out one step at a time.

In this article

1. What a waterfall chart shows
2. When a waterfall is the right chart
3. Step 1: Anchor the start and end totals
4. Step 2: Order the steps so the logic reads
5. Step 3: Handle increases, decreases, and subtotals
6. Step 4: Build it and export the animated version
7. The mistakes that make a waterfall hard to read
8. A few waterfalls worth copying
9. The two-minute version

What a waterfall chart shows

A waterfall chart breaks a change between two totals into the sequence of increases and decreases that produced it. The first bar sits at the starting value, each following bar floats at the height where the previous one left off and moves up or down by the size of its driver, and the last bar returns to the axis to show the ending value. The floating middle bars are the point: they turn a column of adjustments into a connected path you can follow from the old number to the new one.

The three kinds of bar carry the whole design. The two anchor bars, start and end, rest on the baseline and represent absolute totals. The step bars in between represent changes, not totals, and float to show how each one moves the running figure. Colour usually separates the three: one for the anchors, one for increases, one for decreases. Once a reader learns that increases go up in one colour and decreases drop in another, the chart reads almost without labels.

The reason to use it rather than a bar chart or a table is that a waterfall shows causation, or at least contribution. A bar chart of "new business, expansion, churn" as three separate bars tells you their sizes but not how they combine. A waterfall connects them into a running total, so the reader sees each driver acting on the number in turn and understands how the parts produced the whole.

When a waterfall is the right chart

Reach for a waterfall when your subject is the bridge between two numbers and the interesting part is the composition of the gap. Last year's revenue to this year's. Gross revenue to net after deductions. Opening headcount to closing headcount through hires and departures. Budgeted cost to actual cost through each variance. In each case the two endpoints are known and the question is what happened in between.

It is the wrong chart when the endpoints are not really totals, or when the steps do not share a unit. A waterfall needs every step to add to or subtract from the same running quantity in the same unit, dollars, people, units shipped. If your "steps" are a percentage here and a count there, they do not belong on one running total. For a straight comparison of a few discrete values with no running total between them, a bar chart is clearer. For a change across many time periods rather than across a handful of drivers, a line chart fits the continuous axis better, a distinction the bar-versus-line guide works through in detail.

Step 1: Anchor the start and end totals

The two totals are the spine of the chart, and getting them right before anything else keeps the middle honest.

Pick the two numbers you are bridging and confirm they are genuine totals sitting on the same basis. Starting revenue and ending revenue should both be the same metric, measured the same way, over comparable periods. If the start is annual recurring revenue and the end is total revenue including one-off services, the steps between them will never reconcile, and a waterfall that does not reconcile is worse than no chart, because it looks precise while being wrong.

Set the start bar and the end bar to rest on the baseline as absolute values, and make sure the sum of the start plus every step equals the end. This is the arithmetic the chart is promising the reader, and it is worth checking with a calculator before you build, because an audience that spots the columns not adding up will distrust the entire story. When the numbers reconcile, the chart earns the authority that makes a waterfall worth using in an investor update or a board deck.

Step 2: Order the steps so the logic reads

The sequence of the middle steps is a real choice, and different orders tell different stories from the same figures.

Two orderings work well, and which one fits depends on your message. The first groups all the increases together and then all the decreases, so the chart rises to a peak and then settles back to the ending total. This suits a story about a strong period partly given back: everything you gained, then everything that pulled against it. The second follows the real sequence of events or the standard structure of the metric, gross to net through each deduction in the order they apply, for instance, which suits a story where the order itself carries meaning.

Avoid ordering the steps purely to flatter, dropping an awkward decrease into a spot where a later increase hides it. A reader following the running total will feel when the sequence has been arranged to obscure something, even if they cannot say what. Pick an order that reflects either the true chronology or the natural structure of the number, and keep it consistent if you build more than one of these.

Step 3: Handle increases, decreases, and subtotals

The middle of a waterfall is where clarity is won or lost, and three details do most of the work.

Give increases and decreases distinct, consistent colours, and keep those colours meaning the same thing across every waterfall you make, so a reader who has seen one of your charts already knows the code. Label each step with its own value, the size of that driver, not the running total, because the step's contribution is what the reader is there to learn. The running total is shown by the height; the label carries the magnitude of the individual force.

Add a subtotal bar when the running figure passes a meaningful checkpoint. A revenue bridge that runs from gross through several deductions to net often benefits from a subtotal at "net revenue" before continuing, resting on the baseline like the anchors so the reader gets a stable reference partway through. Subtotals are useful when the change has natural phases; skip them when the bridge is short enough to read in one pass, since an unnecessary subtotal just adds a bar to decode.

Step 4: Build it and export the animated version

With the totals anchored, the steps ordered, and the increases and decreases sorted, building is fast.

1. Open the waterfall chart generator and enter your start total, each step with its signed value, and your end total.
2. Set the colours for anchors, increases, and decreases, and turn on per-step labels so each driver shows its own contribution.
3. Add subtotal bars at any checkpoint the reader needs, and title the chart with the two totals it bridges and the period, for example "FY24 to FY25 revenue bridge."
4. Watch the preview build step by step, confirm it reconciles from start to end, then export for its destination.

The destination sets the format:

• A live presentation or board deck: an MP4 that plays each step in as you talk lets you walk the room through the reasoning one driver at a time, rather than showing the whole bridge and fielding questions about a step you have not reached yet. A static PNG is the right pick for a deck that will be read on paper.
• A social feed such as LinkedIn or X: a native MP4 where the steps build in sequence holds attention while the caption explains the drivers. The LinkedIn chart generator sizes it for the mobile feed, and the guide to animated charts for LinkedIn covers aspect ratio and length.
• A message in Slack or email: a GIF loops without anyone pressing play.
• A page, doc, or dashboard: an SVG stays sharp at any size.

Building the steps in one at a time is what a waterfall gains most from motion, because the chart is an argument about cause and effect, and revealing each step in turn lets the audience follow that argument at the pace you set instead of reading the conclusion first.

The mistakes that make a waterfall hard to read

A waterfall fails in a few recognisable ways, most of them about arithmetic or overload rather than looks.

• Steps that do not reconcile. If the start plus the steps does not equal the end, the chart is wrong, and a numerate audience will catch it. Check the sum before you build.
• Mixed units on the steps. A running total works only if every step moves the same quantity. Percentages and counts cannot share one bridge.
• Too many steps. Fifteen tiny floating bars turn the path into visual static and no single driver stands out. Group the small drivers into an "other" step and show the handful that move the number most.
• Labelling steps with the running total instead of their own value. The reader wants to know how big each driver is; the height already shows the running figure.
• Colour that does not distinguish direction. If increases and decreases look the same, the reader loses the one cue that makes a waterfall readable. Keep the two directions clearly apart.
• A static export when the story is a sequence. A frozen bridge makes the reader find the path themselves. If the point is how the number got from A to B, let it build.

A few waterfalls worth copying

Take these structures and drop in your own figures. The numbers here are illustrative.

The revenue bridge

The most common waterfall in a business setting. Start at last period's revenue, step up with new business and expansion, step down with churn and contraction, and land on this period's revenue. Label each driver with its own value and let the ending total rest back on the baseline. It answers the question a board actually asks, not "did revenue grow" but "what grew it and what worked against it," which is why it belongs in an investor update or a quarterly review.

The gross-to-net bridge

When the story is how a headline figure shrinks to a real one, gross revenue down through discounts, refunds, and fees to net revenue, a waterfall lays out each deduction in order. A subtotal at net before any further adjustments gives the reader a stable checkpoint. This structure suits any number that starts large and is reduced by a known set of subtractions.

The headcount bridge

The same shape works for people. Opening headcount, plus hires, minus departures, minus transfers out, plus transfers in, to closing headcount. It turns a set of HR figures into a clear account of how a team changed size over a period, and it reads at a glance in a planning meeting where a table of the same numbers would not.

The budget variance bridge

Budgeted cost to actual cost, stepping through each category that came in over or under. Increases and decreases here are overspend and underspend against plan, and the ending total is the actual figure. It shows not just that a budget was missed or beaten but which lines drove the gap, which is the version of the story a finance review needs.

The two-minute version

The whole method, condensed:

1. Anchor the two totals you are bridging, and confirm they sit on the same basis and reconcile.
2. Order the middle steps by real chronology or the natural structure of the metric, not to flatter.
3. Colour increases and decreases distinctly, label each step with its own value, and add subtotals only where a checkpoint helps.
4. Confirm the start plus the steps equals the end before you commit.
5. Build it, then export the animated version, an MP4 for decks and feeds, a GIF for quick shares, an SVG for pages.
6. Let each step build in turn so the audience follows the cause and effect instead of reading the ending first.

A waterfall is the clearest way to answer "why did this number change." Anchor the totals, order the drivers honestly, make the arithmetic reconcile, and let the chart step from the old number to the new one so the reason is something the reader watches rather than works out.