> 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/advanced-topics/staff-type-change.md).
# Staff Type Change
You can change the appearance of a staff mid-score by adding a **Staff type change** element to a measure, and adjusting its properties in the [Inspector](/3/basics/inspector.md).
## Add a Staff Type Change
1. Select a measure in the score and, in the "Text" [palette](/3/basics/palettes.md), click (double-click prior to version 3.4) the "Staff type change" symbol,
; alternatively, drag the "Staff type change" icon onto a measure;
2. Select the symbol, and adjust its properties (see below) in the [Inspector](/3/basics/inspector.md) as required.
## Staff type change properties
When you alter a **Staff type change** property in the Inspector, the new value takes precedence over the value shown in the global [Staff properties](/3/advanced-topics/staff--part-properties.md#staff--part-properties-common-to-all-four-staff-types) dialog. Only those property values in "Staff Properties" that cannot be changed in the "Staff type change" dialog will be valid throughout the score.
The properties that can be altered in the **Staff type change** dialog in the Inspector are:
**Offset**\
How far the changed staff shall be moved up or down: measured in *spaces (abbr.:* [*sp*](/3/appendix/glossary.md#spatium)*)* .
**Small**\
Tick the box to create a reduced-size staff.
**Scale**\
Changes the size of the staff and all associated elements, as a percentage.
**Lines**\
The number of lines making up the staff.
**Line distance**\
The distance between two staff lines, measured in *spaces (abbr.:* [*sp*](/3/appendix/glossary.md#spatium)*)*.
**Step offset**\
How many steps up or down the notes in the staff are offset.
**Show barlines**\
Whether the staff barlines will be shown.
**Show ledger lines**\
Whether ledger lines will be shown for notes above/below the staff lines.
**Slash style**\
Whether the notes shall be shown in standard or slash style.
**Notehead scheme**\
Allows selection of how noteheads are displayed.
**Generate clefs**\
Whether the staff clef will be shown.
**Generate time signatures**\
Whether the staff time signature(s) will be shown or not.
**Generate key signatures**\
Whether the staff key signatures will be shown or not.
## Example
To illustrate the use of **Staff type change**, the staff shown below was created using the following steps:
1. Add a Staff type change to measure 2.
2. Set size to "Small".
3. Set "Lines" to 4.
4. Add a second Staff Type Change to measure 3.
5. Change "Lines" to 7,
Afterwards the global Staff Properties are changed using [Staff properties](/3/advanced-topics/staff--part-properties.md):
1 Set "Lines" to 2.\
2\. Change "Staff Line Color".
As can be seen, the change in "Lines" is only effective up to the first staff type change, whereas the change to "Staff Line Color" is effective throughout the score.
---
# 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/advanced-topics/staff-type-change.md?ask=&goal=
```
`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.