> For the complete documentation index, see [llms.txt](https://handbook.musescore.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.musescore.org/3/sound-and-playback/capo-playback.md).

# Capo playback

MuseScore allows you to transpose the playback of a staff, without affecting the music notation. This simulates the effect of a [capo](https://en.wikipedia.org/wiki/Capo) (Wikipedia) on the instrument.

## Add capo to a single staff

1. [Add](/3/text/text-basics.md) [staff text](/3/text/staff-text-and-system-text.md) to the note/rest from which you want capo playback to start;
2. Click on "Properties" in the "Staff Text" section of the [Inspector](/3/basics/inspector.md), or right-click on the staff text and select **Staff Text Properties...**; then click on the **Capo Settings** tab;
3. Check the "Capo Settings" checkbox, and set **Capo fret** to the fret number you wish to apply the capo at (each fret increases the pitch by a semitone);
4. Click **Ok** to apply your changes;
5. [Edit](/3/text/text-editing.md) the wording of the text as desired.

## Add capo to linked staff/tablature

* Same method as above, but in step 1, add the staff text to the music staff only.

## Add capo to unlinked staff/tablature

* Same method as above, but apply the staff text to both staff and tablature.

**Note**: Capo playback will apply from the note that the staff text is attached to, until either the next staff text with "Capo Settings" enabled, or until the end of the score.

## Remove capo

To remove capo playback from a staff, returning the instrument to its normal tuning:

* Add staff text with a "Capo fret" setting of "No capo".


---

# 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://handbook.musescore.org/3/sound-and-playback/capo-playback.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.