Basic radar chart example
radar-beta
title Editor comparison
axis speed["Speed"], ai["AI features"], export["Export"], share["Sharing"], price["Price"]
curve a["MermaidViewer"]{5, 5, 5, 4, 5}
curve b["Typical editor"]{3, 2, 3, 3, 4}
max 5
min 0Radar charts (also called spider charts) compare several items across the same set of dimensions. Each axis is a dimension, and each item is drawn as a polygon.
They're popular for skill matrices, product comparisons and performance reviews where the overall shape tells the story.
When to use a radar chart
- Team skill matrices
- Product and competitor comparisons
- Game character stats
- Self-assessments
Radar Chart syntax reference
| Syntax | What it does |
|---|---|
radar-beta | Start a radar chart. |
axis id["Label"], … | Define the axes (dimensions). |
curve id["Label"]{1, 2, 3} | A data series; one value per axis. |
max 5 / min 0 | Scale limits. |
graticule polygon | Use polygon grid lines instead of circles. |
Radar Chart examples
The same axes, one polygon per subject, are the comparison. A mermaid radar chart shows a few scores across the same dimensions, which is why people call it a spider chart. It's a bad place for a time series and a bad place for twenty skills. The shape is the argument.
Axes and curves
radar-beta opens the chart. title names the comparison. axis A, B, C lists the dimensions in order around the figure. curve me{1, 2, 3} is one subject. The numbers follow the axis order. The first number is A, the second is B, the third is C.
A second curve uses the same axes. curve you{3, 1, 2} doesn't get its own axis list. If you reorder the axes, you reorder every curve. That's the edit to do in one pass.
The numbers need a shared scale. If one axis is a 1-to-5 skill and another is a salary, the polygon is meaningless. Rescale before you paste, or pick axes that already share a scale. The simple form plots the values you type. It won't normalize them for you.
Two or three curves are readable. A fourth starts to cover the first. If the chart is a hiring loop, plot the finalists, not the whole pipeline. Order the axes so related dimensions sit next to each other. A, then B, then C is also the order a reader meets them clockwise. Put the controversial axis where you're willing to talk about it first, or last, on purpose.
Worked example
Two people, three skills. The axes are plain letters here so the values are easy to check. In a real chart you would spell the skills.
radar-beta
title Skills
axis A, B, C
curve me{1, 2, 3}
curve you{3, 1, 2}me is weak on A, middling on B, and strong on C. you is the opposite on A and C. The polygons cross. That crossing is the point of a radar chart. A table would list the same six numbers and hide the tradeoff. The chart shows that neither person dominates every axis.
If A is "communication" and you meant me to be the strong communicator, the 1 is in the wrong slot. Count positions against the axis list before you share the figure. There's no label inside the braces to save you.
Replace A, B, C with short names when you publish. Very long names collide around the rim. "Customer communication" can become "Comms" with a gloss under the chart. Keep the order stable once a team has learned it, because a swapped axis looks like a changed person. If a score can be zero, write 0 in the braces so the polygon touches the middle on purpose, instead of leaving the slot out.
When this is the wrong diagram
A quadrant chart is the better picture when you only have two scores and you want four labeled decisions. An XY chart is the better picture when one axis is time. Use a radar chart when every subject is scored on the same three or more dimensions.
Common mistakes
- A curve with fewer numbers than axes. Put one value per axis, in the same order, and write
0when the score is actually zero. - Reordering
axisand forgetting to reorder everycurve. Values are positional. The first number always belongs to the first axis. - Mixing scales, such as a 1-to-5 rating beside a dollar amount. Rescale so every axis shares a meaning, or split the chart.
- Five curves on one figure. The polygons paint over each other. Keep two or three subjects.
Where to go next
The AI radar generator will sketch axes from a comparison you describe. Count the numbers in the editor against the axis list, and the cheat sheet has the curve line. The skills radar template uses real skill names if letters are too abstract to copy.
Same scale on every axis
A radar chart compares subjects across the same axes. If one axis is a 1-to-5 skill and another is a dollar amount, the polygon is meaningless. Rescale every axis to the same range before you add a second curve, and write that range in the sentence under the figure so the reader knows what a peak means.
The order of numbers in curve is the order of axis lines. Adding an axis at the bottom of the file and a number at the front of the curve swaps two skills without looking wrong until someone who has the scores reads it. Count them. Two or three curves are enough. A fourth curve usually hides the first.
The skills radar template uses names instead of letters. The AI radar generator can draft axes from a comparison, and you still check that each curve has one number per axis.
If two subjects tie on every axis, drop one curve. The chart is not adding a comparison.
Tips and best practices
- Use the same scale for every axis.
- Compare at most three or four curves at once.
- Order axes so related dimensions sit next to each other.
Generate a radar chart with AI
Not sure where to start? Describe what you need and the AI radar chart generator writes the Mermaid code for you. Try prompts like:
- “Skills comparison of three job candidates”
- “Smartphone comparison across camera, battery, price, display and performance”
- “Personal wellbeing wheel”
Radar Chart templates
Radar Chart FAQ
How many values does each radar curve need?
One value per axis, in the same order the axes are declared.