> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/faq/theme-setup/how-do-i-change-button-colors-and-hover-style.md).

# How do I change button colors and hover style?

Button colors, hover state, and shape are controlled in Theme settings — here's where to find each setting.

Button colors are controlled globally in one place — the Colors settings panel.

Go to **Theme Editor → Theme settings → Colors → Buttons and links**.

Three settings control all buttons across your store:

| Setting    | What it controls                                                                              |
| ---------- | --------------------------------------------------------------------------------------------- |
| **Base**   | Text color on Solid buttons (typically white or dark neutral)                                 |
| **Accent** | Background of Solid buttons, outline and text of Outlined buttons, and links across the store |
| **Hover**  | The button appearance when a customer mouses over it                                          |

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FgH5pJD2gTASj95SVO62X%2FGroup%202%20(1).jpg?alt=media&amp;token=4fa382fb-b0e5-48a4-9caa-c2290b1bc144" alt=""><figcaption></figcaption></figure>

***

### Tips

A tight relationship between Accent and Hover — one shade darker or lighter — feels polished. A dramatic shift (e.g. black to brand red) creates high energy. Either works; the key is consistency.

{% hint style="warning" %}
**Star ratings are not part of this.** They have their own color in **Theme settings → Colors → Extra → Rating**, and changing Accent will not move them.
{% endhint %}

***

### Per-section button styles

Individual sections can override the global color scheme. If a specific section's buttons look different from the rest of the store:

1. Open the section in Theme Editor
2. Check if a **Color scheme** is set to a custom value
3. Switch it to **Base** to inherit the global Buttons and links colors

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FlD6Eo5ZNsSjbzldGnPtl%2FGroup%202%20(2).jpg?alt=media&amp;token=449ea71e-17d7-4934-84f7-eb9fd63a153d" alt=""><figcaption></figcaption></figure>

***

### Button shape (corner radius)

To change whether buttons are sharp, rounded, or pill-shaped:

Go to **Theme settings → Shapes → Buttons** and adjust the corner radius slider.

***

### Related

* [Colors](https://staylime.com/docs/avante-themes/theme-settings/colors.md) — full color system reference
* [Typography](https://staylime.com/docs/avante-themes/theme-settings/typography.md) — button label font is controlled under the Custom typography preset


---

# 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://staylime.com/docs/avante-themes/faq/theme-setup/how-do-i-change-button-colors-and-hover-style.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.
