> 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/notation/rhythm-meter-and-measures/stems-and-flags.md).

# Stems and flags

## Stem direction

### Default stem direction

MuseScore aligns the stems of [voice](/basics/working-with-multiple-voices.md) 1 notes according to the conventions of music theory. By contrast, voice 2 and voice 4 stems point *downwards* by default, while voice 3 stems point *upwards*. Voice 1 stems automatically flip upwards in the presence of voice 2 or 4 notes.

### Flipping stem direction

1. Select either the notehead, stem or attached beam (if any)
2. Use any of the following methods:
   * Press <kbd>X</kbd>
   * Click on the "Flip direction" icon in the **Note input** toolbar
   * Select a stem direction from the **Stem** tab in the **Properties** panel

This action will flip any attached beam as well.

## Changing stem length

1. Select the stem
2. Use one of the following methods:
   * Press <kbd>Up</kbd> or <kbd>Down</kbd> to extend or shorten the stem
   * Change **Length** in the **Properties** panel

## Creating stemless notes

To hide the stems of individual notes:

1. Select one or more noteheads
2. Go to the [Properties](/basics/properties-panel.md) panel
3. Select the **Stem** tab
4. Select the checkbox next to **Stemless**

To hide all stems in an instrument part:

1. Right-click on the staff and select **Staff/Part properties**
2. Click on **Advanced style properties**
3. Select the checkbox next to **Stemless**

## Stem and flag properties

Properties specific to stems and flags can be edited from the **Stem** tab in the **Note** section of the [Properties](/basics/properties-panel.md) panel:

* **Stemless** removes the stem (and associated beams) from the selected note(s)
* **Stem direction**:
  * **Auto** determines the direction of the stem according to the voice of the selected note(s)
  * **Up** and **Down** override the default stem direction
* **Flag style** sets the appearance of flags for the entire score to either **traditional** (default) or **straight**
* **Thickness** determines the stem's width
* **Length** determines the stem's length
* **Stem offset** can be used to move the stem in a horizontal and/or vertical direction

## Stem and flag style

Global settings for **Stem thickness** and **Flag style** may also be set in **Format→Style→Notes**.

## See also

[Beams](/notation/rhythm-meter-and-measures/beams.md)


---

# 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://handbook.musescore.org/notation/rhythm-meter-and-measures/stems-and-flags.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.