> 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/text/staff-text-and-system-text.md).

# Staff Text and System Text

## Overview

**Staff Text object** and **System Text object** are used for,

* Adding capo playback for guitarists (**Staff Text** only),
* Applying swing and straight time,
* Changing playback sound sample usage inside Musescore (see below and the [Mid-staff sound change](/3/sound-and-playback/mixer.md#mid-staff-sound-channel-change-pizz-con-sordino-etc) chapter), and
* Adding general purpose text not covered by other [Text types](/3/text/text-types.md). For example,
  * Adding musical expressions and performance indications not supported or not found inside Musescore (eg **a2**); and
  * Adding score and movement titles.
  * General purpose text are also commonly added with a frame with text. See [Frames](/3/formatting/frames.md) chapter.

Their main difference is related to anchor as covered in details in the [Text types](/3/text/text-types.md) chapter. Also, **Staff Text** affects the playback of staff / voice of the note it anchored to; **System Text** affects all staves.

The *Expression* button on the *Text Palette* is a styled **Staff Text**. It has its own "Text Style" profile. See ["Style" section below](#style) and the [Palette](/3/basics/palettes.md) chapter.

## Adding to a score

To add one onto a score:

1. Do either one of:
   * Select a note or rest; then for **Staff Text**, press <kbd>Ctrl</kbd>+<kbd>T</kbd>; or for **System Text**, press <kbd>Shift</kbd>+<kbd>Ctrl</kbd>+<kbd>T</kbd>, or
   * Select a note or rest; then select the desired option from **Add -> Text**, or
   * Select a note or rest, then click the desired text from [Palettes](/3/basics/palettes.md) (double-click in versions prior to 3.4), or
   * Drag the desired text from a palette onto a note or rest.
2. Start [entering text](/3/text/text-editing.md).
3. Press <kbd>Esc</kbd> or click on an empty space outside of the box to exit.

## Repeating System Text on other staves

New **System Text** is positioned above the top staff of each [system (layout concept)](https://musescore.org/en/handbook/4/page-layout-concepts). If you need a similar indication on a lower staff, add it to that staff using [Staff Text](#add-staff-text).

## Properties

Fomatting of a Staff Text object or System Text object on a score is edited in the [Inspector](/3/basics/inspector.md), covered in [Text basics](/3/text/text-basics.md) chapter.

The playback settings are edited in "Staff Text properties" and "System Text properties" window

Staff Text contains settings that affect playback. **Only the section after the attached note or rest is affect**. When a Staff Text is duplicated, or reused through [customized palette](/3/basics/palettes.md), the playback settings are reused.

## "Staff Text properties" window

The playback settings can be accessed in two ways:

* Select the Staff Text, and click on "Properties" in the "Staff Text" section of the Inspector.
* Right-click on the text and choose "Staff Text Properties," then click on the relevant tab.

The four tabs on top are:

* Change Channel : Change the channel used by [each Musescore Voices](/3/basics/working-with-multiple-voices.md) independently, understand channel by reading [Mixer](/3/sound-and-playback/mixer.md) chapter first. This only works with Musescore Instrument that has more than one channel.
* Swing Settings: Use "straight" or "swing" rhythm. To change rthythm of **this instrument everywhere in the score** or **all instruments**, see [Swing: global](/3/sound-and-playback/swing.md#apply-swing-globally) chapter for more info.
* Capo Settings: For stringed instruments you can apply a "capo", transposing the playback up by a number of frets/halftone steps. See [Capo playback](/3/sound-and-playback/capo-playback.md) chapter for more info.
* MIDI Action: For advanced users only, send a MIDI Continuous Controller / Control Change (MIDI CC) Message. You must [setup a custom instrument using a instruments.xml](https://musescore.org/en/handbook/developers-handbook/references/instrumentsxml-documentation) and declare MIDI Actions for of its channel first. You cannot edit instruments.xml inside Musescore. More info see [https://github.com/lminiero/musescore-vpo-midi-actions#musescore-tool-t…](https://github.com/lminiero/musescore-vpo-midi-actions#musescore-tool-to-add-midi-actions).

## "System Text properties" window

Works like ["Staff Text properties"](#staff-text-properties-window), but only has "Capo Settings" and "MIDI Action" tabs.

## Style

*See main chapters* [*Layout and formatting*](/3/formatting/layout-and-formatting.md) *and* [*Text styles and properties*](/3/text/text-styles-and-properties.md)*.*

* **Format → Style → Staff Text**.
* **Format → Style → Text Styles → Staff Text**.
* **Format → Style → Text Styles → Expression**.
* **Format → Style → Text Styles → System**.

## See also

* [Mid-staff sound change](/3/sound-and-playback/mixer.md#mid-staff-sound-channel-change-pizz-con-sordino-etc)

## External links

* [How to change instrument sound (e.g. pizz., con sordino) midway through score](https://musescore.org/en/node/50196) (MuseScore HowTo)


---

# 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/text/staff-text-and-system-text.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.