> For the complete documentation index, see [llms.txt](https://help.chartplugin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.chartplugin.com/manage-charts-style/with-manual-settings.md).

# With manual styles

The Style tab gives you full control over how your chart looks. It’s broken into logical panels so you can move from broad styling to fine details.

If you need something beyond what’s available here — pixel-perfect, 1:1 with your design — we’ve got you covered. With **Custom charts**, our team can add any chart exactly as in your mockups to your Chart account. Just **send us your Figma file at <hello@chartplugin.com>** and we’ll take care of the rest.

<figure><img src="/files/Xc16AcYGJdrdALpBkv89" alt=""><figcaption></figcaption></figure>

### Layout

1. **Palette & series colours** — set individual series colours, gradients, and opacity.
2. **Typography** — adjust font family, weight, size, and colour for titles, labels, and tooltips.
3. **Grid** — change gridline styles.
4. **Data label controls** — toggle labels, set formats.

### Working with series colours

* Click a swatch to open the colour picker; use HEX.
* Reorder series to match your legend order.

### Typography tips

* Match your product’s type ramp by using your primary brand font.
* Use upper/lowercase intentionally—chart labels inherit exactly what you type.
* Set subtitles to a smaller point size to create hierarchy.

### Grids

* Use subtle gridlines (light grey or low opacity) to avoid visual noise.
* Add padding via the Settings tab to create breathing room for titles.

### Data labels

* Enable labels sparingly—too many labels can clutter the chart.
* Use number formatters (Settings) to keep labels consistent (e.g. $1.2K, 12.3%).
* For pie charts, combine labels with contrasting colours to maintain readability.


---

# 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://help.chartplugin.com/manage-charts-style/with-manual-settings.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.
