Table vs Chart
COMPAREBefore you pick which chart, decide whether you need a chart at all. Sometimes a plain table is the better answer.
A table presents data as exact numbers arranged in rows and columns, so readers can look up precise values. A chart encodes the same numbers as visual marks — bars, lines, slices or dots — so readers see patterns, trends and comparisons at a glance. Use a table to read values, a chart to see shape.
It is tempting to chart everything, but the most basic data-visualization decision comes one step earlier: table or chart? A table shows exact values you can read and look up. A chart turns those same values into shapes — bars, lines, dots — you take in at a glance. They serve opposite reading modes: a table is for reading numbers, a chart is for seeing a pattern. Match the format to what the reader actually needs to do.
Use a table for exact lookup, a small handful of numbers, or data that mixes different units and scales. Use a chart when the goal is to reveal a pattern, trend, or comparison that would be slow to spot in rows of figures. If the reader needs the precise number, lean table; if they need the shape of the data, lean chart.
The core difference
A table preserves every value exactly as it is. Nothing is rounded into a bar length or smoothed into a line, so a reader can find a specific cell and read its precise figure. That makes tables unbeatable for reference and lookup — but it also means the reader has to do the work of spotting any pattern themselves, scanning row by row.
A chart trades some of that precision for instant pattern recognition. By encoding numbers as position and length, it lets the eye see in a fraction of a second which value is biggest, whether a trend is rising, or how two groups compare — things that would take real effort to extract from a table. The cost is that you generally cannot read an exact figure off a chart; you read the shape, not the number.
Side-by-side comparison
| Table | Chart | |
|---|---|---|
| Best for | Exact lookup | Patterns & trends |
| Precision | Full — exact values | Approximate (reads the shape) |
| Speed to a pattern | Slow — scan manually | Instant |
| Mixed units | Handles them easily | Awkward — needs shared scale |
| Few numbers | Perfectly fine | Often overkill |
| Many data points | Overwhelming | Where charts shine |
| Reader does | Reads numbers | Sees a shape |
Worked example: cancelled vs confirmed tickets
Suppose a booking system reports, for one month, 1,840 confirmed and 160 cancelled tickets out of 2,000. Which visualization shows the percentage of cancelled vs confirmed tickets best — a pie chart, a line chart, a table, or a scatter plot?
- Pie (or donut) chart — best fit for the share. Confirmed and cancelled are two parts of one whole, so a two-slice pie showing 92% and 8% makes the split obvious instantly. With only two categories, the usual weakness of pies (comparing many similar slices) does not apply. A single 100% stacked bar works just as well.
- Table — best fit for the exact counts. If the reader needs to know it was precisely 160 cancellations, or you are reporting several statuses with counts and percentages side by side, a small table is clearer than any chart.
- Line chart — only for change over time. If you have the cancellation rate for each month and the question is "is it rising?", plot the monthly percentage as a line. For a single month it has nothing to show.
- Scatter plot — wrong tool. A scatter plot shows the relationship between two numeric variables, such as lead time versus cancellation rate across many events. It cannot show a share of a total.
The general lesson: decide what the reader must take away first. "8% were cancelled" is a pattern-level message, so chart it. "Exactly 160 of 2,000" is a lookup message, so tabulate it — or simply write it in a sentence.
When the table wins
Keep it a table when precision and reference matter more than visual punch:
- Readers need exact figures. Anything where the precise number is the answer — a price list, a specification, a reference of values to look up.
- There are only a few numbers. Three or four values do not need a chart; a short table or even a sentence reads faster.
- The data mixes units and scales. A count, a percentage, and a dollar figure do not belong on a shared axis, but they sit comfortably in adjacent columns.
When the chart wins
Switch to a chart when the goal is comprehension at a glance:
- You want a pattern to jump out. A trend over time, a ranking, or a relationship is far quicker to see as a shape than to reconstruct from rows.
- There are many data points. Dozens or hundreds of values overwhelm a table but become a clean, readable picture in a chart.
- Comparison is the point. Which is biggest, which is growing, how groups differ — these read instantly from length and position.
Charting a tiny set of numbers — say, three values — purely for decoration. A chart with so little data adds visual clutter without revealing anything a quick table or a single sentence would not say more precisely. The reverse error is dumping hundreds of rows into a table and expecting readers to spot the trend themselves; that is exactly the job a chart should do.
Tufte's data-ink ratio, applied to tables and charts
Edward Tufte, in The Visual Display of Quantitative Information, introduced the data-ink ratio: the share of a graphic's ink that actually shows data, as opposed to borders, backgrounds, heavy gridlines and decoration (which he called "chartjunk"). His advice is to maximise data-ink within reason — show the data, and erase non-data ink that does not help the reader. He also argued that for small data sets a well-made table usually beats a graphic.
The principle applies to tables just as much as to charts. A table designed with data-ink in mind:
- Drops most vertical rules and heavy borders. Light horizontal lines, or just white space, are usually enough to guide the eye along a row.
- Right-aligns numbers and uses consistent decimals, so digits line up by place value and comparing down a column is easy.
- Puts units in the column header instead of repeating "$" or "%" in every cell.
- Sorts rows meaningfully — by value, by time or alphabetically — rather than in whatever order the data arrived.
- Avoids zebra stripes, shading and bold except where they mark something specific, such as a total row.
For charts the same idea means removing 3-D effects, background fills, redundant legends and dense gridlines, and labelling data directly where possible. Tufte's guidance is a direction, not a rule to apply blindly: a few light gridlines or clear axis labels are non-data ink that still earns its place.
Use both together
Reports often work best with a chart and a table side by side: the chart delivers the headline pattern, the table carries the exact figures for anyone who wants to check. A dashboard might show a line chart of monthly revenue with a compact table of the last three months beneath it. If you do this, make sure the two agree exactly — same periods, same rounding, same units.
The decision rule
Ask what the reader must do with the numbers. If they need to look up or compare exact values, or the data is sparse or mixes units, use a table. If they need to see a pattern, trend, or comparison across many values, use a chart. And nothing stops you from using both — a chart to show the shape, with a table beneath it for the precise figures.
Frequently asked questions
What is the difference between a table and a chart?
A table presents exact values as text in rows and columns, so it is best for precise lookup. A chart turns those values into visual shapes such as bars or lines, so it is best for revealing patterns, trends and comparisons at a glance.
When should I use a table instead of a chart?
Use a table when readers need to look up exact values, when there are only a handful of numbers, or when the data mixes different units and scales that would not share an axis. Tables preserve precision that a chart rounds away.
Are charts always better than tables?
No. Charts win when the goal is to see a pattern or compare quickly, but tables win when readers need exact figures, the dataset is tiny, or the values use mixed units. The right choice depends on whether the reader needs to read numbers or see a shape.
Which visualization shows the percentage of cancelled vs confirmed tickets: a pie chart, line chart, table or scatter plot?
A pie or donut chart, because cancelled and confirmed are two parts of one whole. Use a table if readers need the exact counts, a line chart only if you are tracking the cancellation rate over time, and never a scatter plot, which shows relationships between two numeric variables.
What is Tufte's data-ink ratio?
The data-ink ratio, introduced by Edward Tufte, is the proportion of a graphic's ink devoted to showing data rather than decoration. Maximising it means showing as much data as possible with as little non-data ink as possible, for example by removing heavy borders, 3-D effects and unnecessary gridlines.
Make the right one
Once you have decided a chart is the answer, the next question is which one. The chart maker runs in your browser and exports PNG or SVG with no signup, the chart types guide has a quick-pick table, and the chart-chooser guide walks you through matching your data to the right type.