Excel Radar Chart With Different Scales: What Works

Charts & pivot tables · Updated November 19, 2026

No: an Excel radar chart uses one shared value scale for every series and spoke, so you cannot assign a different scale to each metric or data series. To compare measures with different units, convert them to a meaningful common score before charting, or use separate charts or another chart type.

How scales work in an Excel radar chart

A radar chart places categories around a circle and plots each series as a connected shape. The category names sit at the ends of the spokes; values are measured outward from the center using circular gridlines. Excel applies the same value-axis scale to all those spokes. If the axis runs from 0 to 100, every plotted value is positioned against that range, regardless of whether a category represents dollars, minutes, or a rating.

That shared scale is important because it makes the shape comparable across categories. It also means values with very different magnitudes can become hard to see together. For instance, if one metric ranges from 0 to 10,000 and another from 0 to 10, the smaller values may sit close to the center when both are charted as raw numbers. Changing the chart’s maximum affects the whole chart; it does not give each spoke its own maximum.

Excel’s radar chart types—Radar, Radar with Markers, and Filled Radar—change how the data is drawn, not how its scales work. You can adjust the shared value-axis bounds and units, but Excel does not provide independent value axes for individual categories or series in a radar chart.

When different scales cause a problem

A radar chart can still be appropriate when the categories measure different things, provided the values have first been converted to a comparable score. For example, a team might compare departments on customer satisfaction, delivery reliability, and training completion. Those measures use different units, but each could be represented as a percentage of an agreed target. The chart would then show target attainment, not the original measurements.

Without that conversion, the shape can suggest a misleading comparison. A value of 8 on a 0–10 rating is not inherently equivalent to a value of 8,000 dollars. Nor does a larger raw number mean better performance if one category is a cost, error rate, or response time where lower is preferable. Decide what a plotted score means before choosing a chart.

Keep the raw values available in the worksheet or alongside the visualization. A normalized chart is useful for comparing patterns, but it hides units and can conceal practical differences. A reader should be able to find both the score and the underlying measurement.

Normalize values against a target

For many dashboards, target attainment is an understandable way to put unlike measures on a common scale. Set a target for each metric, then express each observation as a percentage of its target. This is suitable when higher values are better and the targets are meaningful and comparable as performance goals. A result of 100 means the target was met; 80 means the observation reached 80 percent of the target.

For example, suppose a table has metrics in B1:E1, one employee’s actual values in B2:E2, and the corresponding targets in B6:E6. The actual values are 80, 4, 12, and 90; the targets are 100, 5, 15, and 100. With the formula below entered in B8 and filled right, the normalized scores are 80, 80, 80, and 90. Copying it down for other people works if their actual values occupy the following rows.

With actual values in B2:E2 and targets in B6:E6, enter this formula in B8, then fill right and down through the normalized results table: =B2/B$6*100. For the example values, the results are 80/100 × 100 = 80, 4/5 × 100 = 80, 12/15 × 100 = 80, and 90/100 × 100 = 90.

This simple calculation needs a little care. It assumes the target is nonzero and that exceeding the target should produce a score above 100. If your policy caps scores at 100, or treats overachievement differently, define that rule explicitly before charting. Likewise, do not use this formula unchanged for measures where lower is better: a smaller response time, defect count, or cost should not automatically receive a smaller performance score.

Prepare and insert the chart

Build a separate table for the normalized values rather than replacing the original measurements. Put the category names in the first row and each person, product, or other series in its own row, with a label in the first column. Check that the numbers are stored as numbers and that every series uses the same category order. Clear labels make it easier to spot an accidental mismatch.

  1. Select the normalized table, including its row and column labels.
  2. On the ribbon, choose Insert > Insert Waterfall, Funnel, Stock, Surface or Radar Chart > Radar. Choose Radar with Markers if individual category points should be visible.
  3. If Excel plots categories and series in the wrong direction, select the chart and choose Chart Design > Switch Row/Column.
  4. Give the chart a descriptive title, and use the legend to identify each series. Keep the source values in the worksheet for reference.

These ribbon paths apply to Excel for Microsoft 365 on Windows. On Mac, the Insert tab also contains radar chart options, though the chart gallery layout can differ. In Excel for the web, available chart-formatting controls can vary; if a particular axis option is missing, open the workbook in the desktop app.

Set the shared value-axis bounds

To change the range shown by the radar chart, right-click a value-axis label or gridline and choose Format Axis. In the Format Axis pane, use Axis Options to set the shared Minimum and Maximum bounds and, where available, the major unit. For normalized scores that should run from 0 to 100, a minimum of 0 and maximum of 100 can make the scale easy to interpret. Values above 100 will then extend beyond the chosen maximum or may not display as intended, so decide how to treat over-target results first.

Changing bounds is not a substitute for normalizing the data. If one spoke represents values up to 10,000 and another up to 10, the axis still applies one range to both. A tighter maximum can make differences appear more prominent, but it can also exaggerate small gaps and obscure the full context. State a nonzero minimum clearly if you use one.

Axis formatting labels and gridlines also matter. Too many circular gridlines can make a chart busy, while too few make values difficult to estimate. Because radar charts are better at showing broad profiles than exact values, use data labels sparingly and keep a table or data labels nearby when precision is important.

Choose a normalization method that fits

Target attainment is not the only way to create comparable scores. The right method depends on what the chart is supposed to communicate. A common mistake is to normalize each metric simply because a chart needs it, without checking whether the resulting scores have a useful interpretation.

  • Percent of target: Useful when each measure has a defensible goal and the audience understands what meeting that goal means. It can produce scores above 100 unless you set a cap.
  • Min-to-max scaling: Maps values within a selected range to a shared interval such as 0–100. It can show relative position, but the result depends on the chosen minimum and maximum and may change when the data range changes.
  • Standardized scores: Useful for some analytical comparisons, but less intuitive for a general dashboard. A score of zero may mean an average rather than no performance, so a radar chart centered at zero may be a poor visual fit.
  • Ordinal ratings: A shared rating scale, such as 1–5, can work when categories are assessed using consistent criteria. Do not imply that subjective ratings are precise measurements.

For a measure where lower is better, decide how to translate the original values into a performance score. For example, a team may define a response-time goal and award full credit at or below that threshold. That scoring rule is a business decision, not an Excel chart setting. Document it so viewers do not mistake the plotted score for the original measurement.

Limits of radar charts and useful alternatives

Even after normalization, a radar chart is not ideal for every comparison. The area and outline of a shape can attract attention, but they are affected by category order and by how many categories are included. Two series may cross, making exact comparisons difficult, and a polygon can look impressive even when its individual values are close. With many series or spokes, labels and lines quickly become crowded.

Consider a different design when readers need to compare exact values, rank many items, or understand a time trend. A clustered bar chart is often clearer for comparing categories; small multiples can show one chart per measure; and a table with conditional formatting can preserve exact values while highlighting patterns. A line chart is generally a better choice for ordered time points. These alternatives do not eliminate the need to handle different units thoughtfully, but they can make comparisons easier to read.

If you keep the radar chart, limit the number of series and categories, use consistent category order across related charts, and explain what the common score represents. A small set of clearly defined target-attainment scores is usually easier to interpret than a large polygon built from unrelated raw measurements.

Common mistakes to avoid

  • Putting raw mixed-unit values on the chart: A single axis cannot make dollars, percentages, and minutes independently readable. Normalize deliberately or separate the measures.
  • Assuming every higher score is better: Invert or otherwise define a scoring approach for costs, delays, and error rates before plotting.
  • Changing the axis maximum to fix one spoke: Bounds apply across the chart, not to one category. Adjust the data or use a different visualization.
  • Using a target without explaining it: A percentage-of-target score only makes sense if viewers can understand the target and whether results may exceed it.
  • Comparing charts with different scoring rules: A 90 on one chart may not mean the same thing as a 90 on another if their transformations or target definitions differ.

Frequently Asked Questions

Can each axis in an Excel radar chart have a different scale?

No. Excel uses one shared value scale for all spokes and series in a radar chart. You can change the shared axis bounds, but you cannot set a separate minimum and maximum for each category.

Can I use a secondary axis for one radar-chart series?

A radar chart does not provide independent value axes for its series. To compare values with different units, make a separate normalized data table or use separate charts designed with clearly explained scales.

How do I compare percentages, ratings, and dollar values?

Choose a meaningful conversion, such as scoring each measure as a percentage of its target, then chart those scores. Keep the raw values visible and explain the scoring rules; a chart cannot make unlike units directly comparable by itself.

Can I set a radar chart scale from 0 to 100?

Yes, when the plotted values are appropriate for that range. Right-click the value axis, choose Format Axis, and set the shared bounds in Axis Options. This changes the whole chart and does not rescale individual metrics.

Why does my radar chart look different after I reorder the categories?

The values are connected in category order, so reordering spokes changes the polygon’s shape even if no values change. Keep category order consistent when comparing charts, and avoid interpreting the filled area as a precise measure of overall performance.

Related

Try it: the Percentage Formula Generator: percent of, percent change, increase and decrease, with the formula.

More in Charts & pivot tables

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.