> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/10.2-analytics/pentaho-dashboard-designer-cp/create-a-chart/chart-types/pie-charts.md).

# Pie charts

If you are comparing parts of a whole, consider using a pie chart, which gives dashboard consumers an immediate visual clue of the relative sizes of the shares of a whole. Key words associated with charts include, portion, share, and percentage. For example, if you want to demonstrate the proportion of the company's budget spent on health insurance, use a pie chart. Categories are represented by individual slices. To make the chart easier to read, limit the number of slices to five. The size of the slice in a pie chart is determined by the value as shown in the following example:

![Pie chart](/files/Rd5vX2KGbSF8dSlviqe1)

You can animate a pie chart if you want its pieces to be exploded, which means that the individual slices of the pie can be pulled away from the rest of the pie.

![Exploded pie chart](/files/NisF40lAZNotQCkB3g1c)

To animate a pie, enable **Animated** check box in the Chart Designer.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pba/10.2-analytics/pentaho-dashboard-designer-cp/create-a-chart/chart-types/pie-charts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.