> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/showmemore/features/small-multiple-charts/labels.md).
# Labels
Control how labels are displayed across panels, including visibility, formatting, and content. Labels help highlight key values without overwhelming the visual.
#### **Show labels**
Toggle whether labels are displayed on the chart.
* **On** – Displays values within each panel
* **Off** – Hides labels for a cleaner view
***
#### **Font size – measure**
Adjust the size of value labels.
Larger sizes improve visibility, while smaller sizes keep the chart compact.
***
#### **Font size – dimension**
Adjust the size of panel titles or category labels.
***
#### **Font family**
The chart uses the font defined in your Tableau workbook.
To update:
* Go to **Format → Workbook**
* Change the font settings
* Reload the extension
***
#### **End value label**
Control whether the last value in each panel is shown.
* **On** – Highlights the most recent value
* **Off** – Hides end labels
***
#### **Label position**
Define where labels appear within each panel.
Positioning options help balance readability and clutter depending on chart density.
***
#### **Number formatting**
Control how values are displayed (e.g. decimals, abbreviations like K/M).
***
#### **Notes**
* Use labels sparingly when many panels are displayed
* Enable **End value label** for trend-focused charts
* Keep font sizes consistent across panels
* Use formatting to improve readability without clutter
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.infotopics.com/showmemore/features/small-multiple-charts/labels.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
