A budget or spend breakdown with one or two levels
Department totals split into line items, or revenue split into product lines. A treemap shows which pieces are big and which are rounding errors faster than a table of numbers can.
Three ways to show nested part-to-whole data: treemap, sunburst and marimekko, for budgets, org spend and category trees. Pick the layout that matches how many levels you actually need to show.
Una vista rápida de lo que hay aquí, haz clic en cualquiera para abrirla.
Hierarchy chart templates are for data that nests: a total split into categories, and those categories split again into subcategories. A company budget broken into departments and then line items is a hierarchy. So is website traffic broken into channel, then source, then campaign. Where a bar chart compares flat categories side by side, these three templates show the parent-child relationship itself: how a slice of the whole belongs to a bigger slice above it.
The three shapes encode that nesting differently, and the difference matters more than it looks. A treemap uses rectangle area (bigger box, bigger value) nested inside each other, so the two or three items that dominate a budget jump out at a glance. The sunburst nests the same way but as rings radiating from a center, giving each level its own ring; it reads more like an org chart than a size comparison. A marimekko is the odd one out: bar width carries one variable, like market size, and internal stacking carries another, like share within it. Two dimensions at once, not just depth.
All three run into the same wall: readability past two or three levels. A treemap's inner boxes shrink to slivers once you nest a fourth level in; a sunburst's outer rings get thin enough that labels stop fitting. If your real hierarchy runs five levels deep, the fix isn't a fancier chart. It's picking the two levels that actually answer the question and aggregating the rest into an "other" bucket before you chart it.
Cada uno abre su propio generador gratuito con datos de ejemplo ya cargados.
Department totals split into line items, or revenue split into product lines. A treemap shows which pieces are big and which are rounding errors faster than a table of numbers can.
Site traffic by channel, then source, then campaign. A sunburst keeps each level visually separate as its own ring, which a treemap's nested boxes start to blur once you're past two levels.
Market share by segment, where each segment is also sized by revenue. A marimekko is built for exactly this: bar width for one variable, stacked height for the other. Neither a treemap nor a pie chart can carry both at once.
A long tail of minor cost centers next to two or three that dominate the total. Rectangle area in a treemap makes that imbalance obvious in a way a pie chart's thin slivers of slices can't.
De una hoja de cálculo a un gráfico publicado, paso a paso.
One or two levels and size is the point: treemap. Three-plus levels you need to keep visually distinct: sunburst. Two independent variables layered on top of each other: marimekko.
Each template linked below opens with sample data already bound in, so you can see the parent-child column layout it expects before touching your own file.
Structure your data as parent and child columns with a value per row, then import a CSV or Excel file, paste from a spreadsheet, or connect a Google Sheet.
Publish for an interactive embed where viewers can click into a segment to drill down, or export a static PNG, SVG or PDF for a deck or report.
Abre el editor y comienza desde cualquier plantilla en esta categoría: los datos de ejemplo ya están cargados.
Abre el editorUse a treemap when the point is comparing sizes, like which department or product line is biggest, since rectangle area reads faster than anything else. Use a sunburst when the point is the structure itself, like a three-level category tree, since each ring keeps a level visually distinct in a way nested boxes don't.
Gratis para empezar con 300+ plantillas. Sin tarjeta de crédito requerida.