Radar chart templates put several numeric attributes on their own spoke around a central point, then connect the values into a closed shape: one polygon per item you're comparing. It's the standard layout for a player's stats in a sports game, a product scorecard across five judging criteria, or a skill profile across ten competencies, because every attribute gets equal visual weight radiating outward from the center. PlotSet has two templates in this family: the classic radar chart, which plots a value as a point on each axis and connects them, and the polar area chart, which turns each category into a wedge instead.
The two aren't interchangeable. A radar chart is built to compare two or more items across the same set of attributes (this player against that one, this quarter against last quarter) using overlapping outlines so you can spot where one item pulls ahead and where it falls behind. The polar area chart is built for a single series split into categories: every wedge keeps the same angle, but its radius grows with the value, so it reads more like a bar chart bent into a circle than a head-to-head comparison tool.
Both formats carry a real weakness worth knowing before you publish either one. A wedge's visible area grows with the square of its radius, so a polar area chart can make a value that's twice as large look four times as big to the eye. Readers judge area, not radius. Radar charts have their own trap: reorder the axes and the polygon's shape changes even though the underlying numbers haven't moved, so two people can make the same dataset look completely different depending on which attribute sits at the top. If you're only comparing one or two attributes, or exact values matter more than overall shape, a plain bar chart will serve your readers better than either template here.