How Do You Insert a Treemap Chart in Excel?

How Do You Insert a Treemap Chart in Excel?

A treemap is the chart that turns a long list of categories into a mosaic of nested rectangles, each one sized by its share of the total.

It is genuinely useful for the thing it is built for, and Microsoft's own documentation is unusually candid about the thing it is not built for. That second half is the part almost no tutorial mentions, and it is the difference between a chart that earns its place on a dashboard and one that gets replaced three weeks later.

The insertion itself takes two clicks. The decision about whether to insert it at all takes a little more thought, so this guide covers both.

How Do You Insert a Treemap Chart in Excel? The Short Answer

Select your data, then go to the Insert tab, click Insert Hierarchy Chart, and choose Treemap. That is the whole procedure, and it is exactly how Microsoft words it on its own support page: "Go to the Insert tab > Insert Hierarchy Chart > Treemap."

There is a second route if you cannot find the hierarchy button.

Microsoft notes you "can also use Recommended Charts to create a treemap chart by going to Insert > Recommended Charts > All Charts." The All Charts tab lists every type Excel offers in one alphabetical panel, which is often faster than hunting for the right icon in the ribbon.

The feature is not new and it is not going anywhere. Microsoft lists the treemap as applying to Excel for Microsoft 365, Excel 2024 and Excel 2021, in both the Windows and Mac editions, and its own page metadata describes the chart as having been introduced in Office 2016 for Windows. There is no deprecation notice anywhere on the page.

One small thing that trips people up: the Chart Design and Format tabs that let you restyle the result are contextual. Microsoft's tip is that if you do not see them, you should "click anywhere in the treemap chart to add the Chart Tools to the ribbon." The tabs are not missing; the chart simply is not selected.

Not sure which of your pages are actually pulling in traffic worth charting? Get a free audit and see where your numbers are coming from.

What Does a Treemap Actually Show?

Rectangles Inside Rectangles

Microsoft's definition is worth reading closely, because every design decision in the chart follows from it: "A treemap chart provides a hierarchical view of your data and makes it easy to spot patterns, such as which items are a store's best sellers."

The mechanics are equally plain. "The tree branches are represented by rectangles and each sub-branch is shown as a smaller rectangle." A top-level category becomes a large block, and the items inside it become smaller blocks packed into that block's area. Nothing is plotted against an axis, because there is no axis. Area is the only encoding.

That single fact explains why treemaps look so different from everything else in the chart menu. A bar chart compares values by length along a shared baseline. A treemap compares them by how much of the rectangle each one eats.

Color and Proximity Do the Grouping

The second half of Microsoft's description covers how the grouping reads: "The treemap chart displays categories by color and proximity and can easily show lots of data which would be difficult with other chart types."

Excel handles the color assignment for you. The page states that "Excel automatically uses a different color for each of the top level or parent categories," so your parent groups arrive visually separated without any formatting work. Proximity does the rest: items in the same parent are packed together, so the eye reads the clusters before it reads any individual box.

The "lots of data" claim is the real argument for the chart type. Thirty categories in a bar chart is a wall of thin stripes with unreadable labels. Thirty categories in a treemap is a mosaic where the five that matter are immediately obvious because they are the five biggest shapes.

What Microsoft Does Not Tell You About the Data

Here is a genuine gap worth knowing about before you start. Microsoft's treemap page says only "Select your data" and shows a sample range as a picture. It never states which columns should hold what.

The arrangement the chart expects is the ordinary hierarchy layout: one column per level of category, running left to right from the broadest grouping to the narrowest, with the numeric values in the final column.

One row per leaf item. If your sheet has categories in the rightmost column and numbers on the left, the chart will not read your intent, and no error message will tell you why.

The blank-cell rule is documented, but on a different page. Microsoft's "Available chart types in Office" reference notes that a treemap "can be plotted when empty (blank) cells exist within the hierarchical structure," which means you do not have to repeat a parent category on every single row.

Leave the parent cell blank on continuation rows and Excel still groups them correctly. That permission is genuinely useful and it is nowhere on the how-to page.

How Do You Build One, Step by Step?

1. Lay the data out as a hierarchy. Put the broadest category in the leftmost column, any sub-category in the next column, and the numeric value in the last column. One row per item.
2. Leave the parent cell blank on repeat rows rather than copying the parent name down. Excel reads the blanks as "same parent as above."
3. Select the whole range, including the header row.
4. Go to Insert, click Insert Hierarchy Chart, and pick Treemap. The chart appears on the sheet immediately.
5. Click once inside the chart to bring the Chart Design and Format tabs onto the ribbon.
6. Fix the labels. Right-click any rectangle, choose Format Data Series, open Series Options, and set the label display under Label Options. This is where you decide whether parent category names appear as a banner across the top of each group or are suppressed in favor of the item names.
7. Give it a real title. The default is the name of your value column, which tells a reader nothing.

Step six is the one that decides whether the chart is legible. With banners on, every parent group gets a named strip and the hierarchy is obvious at a glance; with them off, you recover that space for the item labels inside the boxes.

On a chart with four or five parents, the banners are worth the space. On a chart with fifteen, they are not.

Charting the wrong numbers is a faster way to lose a morning than any formatting problem. Request a free audit and start from the ones that matter.

When Is a Treemap the Right Choice?

Microsoft's own recommendation is narrow and specific: "Treemap charts are good for comparing proportions within the hierarchy."

That is the test. If the sentence you want the reader to arrive at is "this slice is about a third of that group, and that group is about half the business," a treemap says it faster than anything else in Excel.

Revenue by region and then by product inside each region. Spend by department and then by vendor. Traffic by channel and then by landing page.

It is also the right pick when the category count is too high for a bar chart but the structure is too shallow for anything more elaborate. Two levels and forty leaves is squarely treemap territory.

There are three situations where it is the wrong pick, and they are worth naming:

• Change over time. A treemap is a snapshot. There is no time axis and no way to add one, so anything that happens across months belongs in a line chart.
• Precise comparison. People read area badly. Two rectangles of similar size are effectively indistinguishable, so if the exact gap between two values is the point, use a bar.
• Values that are not parts of a whole. The chart's entire logic is share of total. Averages, rates, scores and indexes are not shares of anything, and packing them into rectangles implies an arithmetic that is not there.

Want to know which channels are actually worth a slice of your reporting? Request a free audit.

What Are the Real Limitations?

The most important limitation is the one Microsoft volunteers about its own chart, in the same breath as the recommendation. The full sentence reads: "Treemap charts are good for comparing proportions within the hierarchy, however, treemap charts aren't great at showing hierarchical levels between the largest categories and each data point."

Read that again, because it is a real constraint and not a hedge. The chart is weak at showing the relationship between the top of the hierarchy and the bottom of it. You can see that one rectangle is bigger than another.

What you cannot easily see is the chain of parentage connecting a small box back up to the group it belongs to, especially once the boxes get small enough that their labels drop out.

Microsoft then names the replacement outright: a sunburst chart "is a much better visual chart for showing that." It is unusual for a vendor's own how-to page to point you at a different chart halfway through, and it is the single most useful sentence on the page.

A second limitation is structural. Microsoft's chart-type reference states flatly that "there are no chart sub-types for treemap charts." Most Excel chart families offer variants — stacked, clustered, 100 percent, three-dimensional.

The treemap offers exactly one layout. You can restyle the colors and the labels, but you cannot change how the rectangles are packed, and you cannot switch to a different arrangement of the same data within the chart type.

The third is label survival. Because every box is sized by value, small values get small boxes, and a small box cannot hold text. On a long tail of categories the labels simply vanish, which means the chart stops being self-explanatory for exactly the items a reader is most likely to need help identifying.

The practical fix is to group the tail into an "Other" row in the source data before charting, rather than hoping the rendering copes.

Finally, nothing in Microsoft's documentation addresses negative values on either page — not the how-to and not the chart-type reference. Given that the chart encodes magnitude as area, a negative number has no sensible rectangle, so treat negatives as something to resolve in the data before you chart it rather than something the chart will handle for you.

How Does It Compare to the Alternatives?

Against a pie chart, the treemap wins on category count and loses on familiarity. A pie falls apart past six or seven slices; a treemap is comfortable with forty. But every audience already knows how to read a pie, and some will need a sentence of orientation for a treemap.

Against a sunburst chart, the choice is the one Microsoft itself frames. Both are hierarchical and both live under the same Insert Hierarchy Chart button. The sunburst draws each level of the hierarchy as a concentric ring, so the parent-to-child relationship is drawn explicitly rather than implied by packing.

Use the treemap when proportions matter most, and the sunburst when the structure matters most. For data with three or more levels, the sunburst is almost always the better read.

Against a stacked bar chart, the treemap wins when you have one total to break down and loses when you have several to compare. A row of stacked bars lets a reader compare composition across regions or quarters side by side. A treemap shows one composition beautifully and cannot show two next to each other at all.

Against a bubble chart, these are not really competitors, though they look similar at a glance because both encode size. A bubble chart plots position on two axes and uses size as a third dimension, so it answers questions about correlation.

A treemap has no axes and answers questions about share. If the question involves two variables moving together, the bubble chart is the tool.

Curious how your own numbers would break down if someone actually charted them? Start with a free audit and find out what is worth reporting.

Final Thoughts

Inserting a treemap in Excel is a two-click job, and the version shipping in Excel for Microsoft 365, Excel 2024 and Excel 2021 is the same one that arrived in Office 2016. The procedure is not the hard part.

The hard part is the sentence Microsoft puts in the middle of its own instructions, where it tells you the chart "aren't great at showing hierarchical levels between the largest categories and each data point" and recommends a sunburst for that job instead.

Take that at face value. It is the clearest guidance available about where the chart's usefulness ends, and it comes from the people who built it.

Use a treemap when your question is about proportion inside a shallow hierarchy and your category count is too high for a bar chart.

Lay the data out with categories on the left and values on the right, lean on the blank-cell behavior rather than repeating parent names, fix the label display before you show anyone, and group the long tail into an "Other" row so the small boxes do not turn into unlabeled noise.

If you are weighing it against the other size-based option in the chart menu, our guide to the bubble chart in Excel covers the comparison in more depth, including why position-based charts answer a different kind of question entirely.

One last practical note: Microsoft's pages do describe both Windows and Mac behavior, but the step-by-step wording and the screenshots are Windows-first. If you are on a Mac and the ribbon does not look like the picture, the chart type is still there under the same hierarchy grouping. Verified against Microsoft's published documentation as of November 13, 2026.