> For the complete documentation index, see [llms.txt](https://support.audacityteam.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.audacityteam.org/new-in-audacity-4/changing-clip-color.md).
# Changing clip color
{% hint style="info" %}
Note: This feature is only available if you have **colorful clips** enabled in **Preferences -> Appearance -> Clip style**
{% endhint %}
## Changing color per clip
To change clip color, click on the 3-dot menu on the top right of the clip and select **Clip color**. You then are given the choice between several colors.
## Changing color for an entire track
To change the color for all clips on a track, click on the 3-dot menu on the track header and select **Track color**. You then are given the choice between several colors.
{% hint style="info" %}
Note: Changing track color only changes the color for clips which follow the track color. If you have changed the clip color for individual clips, they won't change color if you change track color.
{% endhint %}
---
# 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://support.audacityteam.org/new-in-audacity-4/changing-clip-color.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.
