You can have the cleanest Airtable base in the world and your stakeholders still won't open it — because tables aren't how people read data. They read charts. This guide covers how to create charts and graphs in Airtable: every supported type, where to build them, and the rules for picking the right shape for the question you're trying to answer.
We'll cover both Airtable charting surfaces — the Charts extension that lives inside a base, and the chart element inside Interface Designer. They share most of the same engine, but they're used differently and most teams need both.
Charts Extension vs Interface Designer: Pick Once
| Feature | Charts Extension | Interface Designer Charts |
|---|---|---|
| Where the chart lives | A base's Extensions panel | An Interface Designer page |
| Best audience | People editing the base | Read-only stakeholders, clients |
| Filter controls | Per-extension settings only | Page-level + element-level filters |
| Public sharing | Embed URL (free on all paid plans) | Public link (Business + Enterprise) |
| Click-through to record | No | Yes — opens record detail page |
| Number of charts | One per extension instance | Many per dashboard page |
Rule of thumb: the Charts extension is for ad-hoc analysis next to your data. Interface Designer is for finished dashboards delivered to an audience. Most production bases use both — extensions for the ops team working in the base, interfaces for executives reading the output.
The Six Chart Types Airtable Supports
Airtable's chart engine produces six visualisations. Picking the right one is half the work of making a chart that reads at a glance.
Vertical Bar Chart
The default. Use it when comparing a numeric value across discrete categories: revenue by region, tickets by status, headcount by team. Best when you have between 3 and 15 categories. Above 15, switch to horizontal bars so the labels don't crowd.
Horizontal Bar Chart
Same chart, rotated. Use it when category names are long ("North America Enterprise" doesn't fit under a vertical bar) or when there are many categories you want to sort descending. The buyer's "items below reorder point" list reads best as horizontal bars sorted shortest-cover-first.
Stacked Bar Chart
Bar chart where each bar is broken down into sub-categories. Use it when you want to show both totals and the mix inside each total: deals by stage stacked by owner, traffic by source stacked by device, revenue by month stacked by product line.
A stacked bar with more than four stacks becomes a mess. If you have more, group the smaller categories into "Other."
Line Chart
Use it for trends over time. Revenue by month, signups by week, response time by day. The x-axis should be a date field; the y-axis a number. Anything other than time goes on a bar chart, not a line — connecting non-time categories with a line implies a sequence that doesn't exist.
You can plot multiple lines on the same chart by selecting a secondary grouping field — useful for "MRR by month, one line per plan tier."
Pie / Donut Chart
The single most overused chart in business reporting. Use it when you have 2 to 5 categories that sum to a meaningful 100% — share of revenue by product, percentage of tickets by priority. Stop using it as soon as you have 6+ slices; bar charts beat pie charts at every count above five.
Scatter Plot
Two-variable relationship. Deal size vs sales cycle, customer age vs lifetime value, project hours vs revenue. The pattern shows the correlation. Airtable supports optional grouping that colors the dots by a third field — useful for "deal size vs cycle length, colored by industry."
Building a Chart in the Charts Extension
The Charts extension is the fastest way to get a chart on screen.
- Open the base. Click Extensions in the top right.
- Click Add an extension. Search for Charts. Click Add.
- In the extension panel, click Create chart.
- Pick the Table and (optionally) View the chart should read from.
- Pick the Chart type from the six above.
- Set the X-axis field (categories or time).
- Set the Y-axis field and aggregation (SUM, COUNT, AVERAGE).
- Optionally pick a Group by field for stacking or coloring.
The chart renders live and updates as records change. To share it, click the share icon in the extension header — Airtable produces a public embed URL that anyone can open.
For the official documentation on extensions, see Airtable's extensions overview.
Building a Chart in Interface Designer
Interface Designer charts share the same engine but live inside a dashboard page.
- Open Interfaces in the top toolbar. Click Start building (or open an existing interface).
- Pick the Dashboard layout if creating a new page.
- From the left element palette, drag a Chart element onto the canvas.
- In the right configuration panel, pick Source table, Source view, Chart type, X-axis, and Y-axis aggregation.
- Resize and reposition the chart on the page.
- Click Publish when the page is ready.
The two big advantages over the extension: you can put many charts on one page, and you can add page-level filters that update every chart simultaneously. See our full Interface Designer guide for the rest of the element types.
Picking the Right Chart: A Decision Tree
Most chart mistakes come from picking the wrong type. Here's the rule we apply on every client build.
| What you're showing | Use this chart |
|---|---|
| A value over time | Line chart, date on x-axis |
| A value compared across few categories (≤15) | Vertical bar chart |
| A value compared across many categories (16+) | Horizontal bar chart, sorted descending |
| Totals broken down into 2–4 sub-categories | Stacked bar chart |
| Share of a 100% whole, 2–5 categories | Pie or donut chart |
| Share of a 100% whole, 6+ categories | Horizontal bar chart with values as % of total |
| Relationship between two numeric variables | Scatter plot |
| A single KPI versus a target | Number element or Gauge (Interface only) |
If you're tempted to use a pie chart and you have more than 5 slices, write the percentages next to a horizontal bar instead. Stakeholders read horizontal bars 40% faster than donut charts, per common BI usability research — and they spot rank order immediately, which is what they were going to do with the data anyway.
Pivot-Style Summaries in Airtable
Airtable doesn't have a "pivot chart" type but it has two ways to get the same shape.
Pivot Table extension. A separate extension from Charts. Add it the same way: Extensions → Add → Pivot Table. Pick rows, columns, values, and aggregation. The result is a familiar Excel-style cross-tabulation. Use it when you want the numbers, not a visualisation.
Stacked bar in Interface Designer. Drag a Chart element. Pick stacked bar. Set x-axis to your row field, y-axis to your value field with the aggregation, and "Group by" to your column field. This is a pivot chart in everything but name.
For most reporting we lean on the stacked bar because it shows mix and totals together; the Pivot Table extension is better when the user wants to read exact numbers off a grid.
Five Practical Examples
Sales pipeline by stage. Stacked vertical bar. X = Stage. Y = SUM(Amount). Group by = Owner. Shows both pipeline value per stage and who owns it.
MRR trend by plan. Line chart with multiple series. X = Month (formula field). Y = SUM(MRR). Group by = Plan Tier. One line per plan, all on the same chart.
Tickets by priority. Horizontal bar chart. X = Priority. Y = COUNT(records). Sort descending. Better than a pie because the priorities have a natural order (P0, P1, P2, P3) and bars preserve it.
Inventory by warehouse. Horizontal bar. X = Warehouse. Y = SUM(Stock Value). Sort descending. The biggest warehouses always appear at the top.
Deal size vs sales cycle. Scatter plot. X = Days to Close. Y = Amount. Group by = Segment. Shows whether big deals take longer to close — and whether that pattern differs by segment.
Common Mistakes
Charting a text field that looks like a number. Airtable treats single-line-text "$1,200" as a string. Convert to a Number or Currency field before charting.
Lookup fields exploding into multiple data points. A lookup that returns three values shows up as three rows in the chart. If you want one value per record, wrap it in a rollup with an aggregation (SUM for numbers, ARRAYJOIN for text).
Pie charts with more than five slices. Switch to a horizontal bar. Always. We have never seen a 7-slice pie outperform a 7-bar chart for comprehension.
Forgetting the source view filter. Test data, archived records, and draft records sneak into charts when they read from the whole table. Always point a chart at a curated view, even if the view is "Everything except archived."
Choosing line charts for non-time x-axes. A line implies sequence. Salesperson names on the x-axis connected by a line implies Alice → Bob → Carol is a sequence; it's not. Use bars.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Chart shows no data | Source view has zero matching records | Open the source view; widen its filter |
| Totals look inflated | Y-axis is reading a lookup with multiple values | Replace lookup with a numeric rollup |
| Bars are out of order | No sort applied at the source view | Sort the source view by the value or category field |
| Pie chart has a giant "Other" slice | Too many small categories grouped | Filter the source view to top N categories or switch to a bar |
| Chart updates feel slow | Source table is very large and unfiltered | Add a view filter that limits to the rows the chart needs |
Where to Go Next
Charts are most useful as part of a complete reporting surface — the how to build an Airtable dashboard guide walks through the full Interface Designer dashboard build. For the chart engine's underlying field requirements, the linked records explained tutorial covers rollups, which are what most "value" fields in a real chart actually are.
When Airtable's six chart types run out — multi-axis charts, geographic maps, statistical visualisations — that's the prompt to connect Airtable to a dedicated BI tool. Our Airtable to Power BI guide covers the path. Airtable's official Charts extension documentation covers a few edge cases on date binning and number formatting that we didn't have space for here.
