Chart maker · Radar
Radar chart maker
The profile chart: five or six dimensions, one or two contenders, and the shape of each option visible at a glance. Paste the scores, edit the chart natively.
Paste, pick, download
Rows as dimensions (same scale — say 1 to 10), one score column per contender. With three or more shared dimensions, the radar appears in the recommendations. The export is a native, editable chart in PowerPoint and WPS. Free, no sign-up, no watermark.
When a radar wins
- The choice is a profile, not a number. Vendor A vs B, candidate X vs Y — "stronger overall" is vague, "stronger here and here" is a shape.
- You are conceding points on purpose. Showing where your option is weaker buys credibility for where it wins. Procurement respects the honest polygon.
- Three to six shared dimensions. Enough axes to form a character, few enough to read it.
When it lets you down
- Exact values matter. Radars trade precision for profile; if "by how much" is the question, use bars.
- Three-plus contenders. Overlapping polygons become camouflage. Two entities maximum — three only if one is clearly the hero.
- The scales differ per axis. Dollars next to percentages next to counts corrupts the shape. Normalize first, and say so.
Try it with this data
| Dimension | Vendor A | Vendor B |
|---|---|---|
| Price | 8 | 6 |
| Features | 6 | 9 |
| Support | 7 | 5 |
| Security | 9 | 7 |
| Integrations | 5 | 8 |
Field notes on radars
- Same scale on every axis. All 1–10 or all percentages — the polygon is only honest when the axes are.
- Two shapes, one hero. Your recommendation in full color, the alternative muted — the shapes argue, the colors decide.
- Name the trade-off in the title. "A is cheaper and safer; B is richer" — the chart proves the sentence, the sentence sells the meeting.
- Keep it to one claim per page. A radar is already dense; pair it with a single sentence, per field note #2.
A scores table from your last evaluation?
Paste it, see the shapes →Other chart makers
From the field notes
One page, one claim — the discipline that keeps a radar readable is in field note #2.
ChartThat — data in, charts out. · [email protected]