> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-user-manual/settings/customizations/configuring-custom-color-palettes.md).

# Configuring custom color palettes

Admins can define **custom color palettes** for [styling maps in Builder](/carto-user-manual/maps/layers.md#fill-color). This feature allows organizations to set up their own predefined color schemes, removing the need to manually add custom colors in each new map.

Custom color palettes can range from **3 to 20 steps** and can be of any type: diverging, sequential, qualitative or singlehue.

## Managing custom color palettes

To create a custom color palette, head to the *Customizations* section of the Settings, where you will find the custom color palette editor:

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-dc1d1e6f6ba6e86a2d6bcf86f563f910d9bdc297%2FScreenshot%202024-11-11%20at%2015.51.25.png?alt=media" alt=""><figcaption><p>Custom color palette editor in the Settings</p></figcaption></figure>

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-2cf14b2756585d09bb4c9725d69d39f348ef1329%2FScreenshot%202024-11-11%20at%2015.56.45.png?alt=media" alt=""><figcaption><p>Detailed view of a custom palette</p></figcaption></figure>

Custom color palettes **can't be modified**, but they can be duplicated and deleted. If a custom palette is deleted, the maps where it is applied will not be altered, but users will not be able to apply the palette again.

## Applying custom color palettes

Once created, custom palettes can be used in Builder if the required palette **type** matches and the number of color **steps** is less than or equal to the number of steps in the saved custom palette.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-dc393dadd768feb4abfe5858c7b8f1ee9f5ff933%2FScreenshot%202024-11-11%20at%2015.37.27.png?alt=media" alt=""><figcaption><p>Applying a custom palette in Builder</p></figcaption></figure>


---

# 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.carto.com/carto-user-manual/settings/customizations/configuring-custom-color-palettes.md?ask=<question>&goal=<user_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.