> 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/notation/notation-types.md). # Notation types Musescore handle score items differently based on their types. Type of a single selected score item is displayed on the status bar.
Checktype
## Basics Beginners can make better decision on choosing the correct type by skiming through the handbook, reading the [*MuseScore 3 Handbook*](/3/readme.md), the [*Text types*](/3/text/text-types.md), and the [*Lines*](/3/notation/lines.md) chapters. Different types serve distinct purposes. For example, a [Text types](/3/text/text-types.md) cannot change a note's pitch. That is, if changing a note's pitch is the purpose, it is *wrong* to add [a Staff Text](/3/text/staff-text-and-system-text.md) (a subtype of Musescore Text) and *manually enter* a sharp or hash (#) symbol into it. Different types anchor differently, which may have impact on program features such as playback or [Musescore Part](/3/advanced-topics/parts.md). A score item's type *cannot be changed after it is added* onto a score. ## Advanced Advanced users may benefit from knowing that there are two distinct groups, **Functional** text and symbols are created when the user performs actions such as [Keyboard shortcuts](/3/appendix/keyboard-shortcuts.md), [clicking a toolbar button](/3/basics/viewing-and-navigation.md#toolbars), or [adding an item from the palette](/3/basics/palettes.md). They affect the score semantically in a way that is most useful or makes most sense (check out GitHub and Discord discussions). The [Synthesizer](/3/sound-and-playback/synthesizer.md) creates playback for them. Appropiate [Layout and formatting](/3/formatting/layout-and-formatting.md) are automatically applied. They are also replaced whenever appropiate, for example adding an accidental sharp **#** removes the existing flat **b** . **Non-functional** ones are found under the **Symbols** category in the [Master palette](/3/advanced-topics/master-palette.md). Most features of functional ones listed above are not applicable to them. They are not removed from the score unless the user deliberately do so. There are *non-functional versions of most functional items*. Some notation are non-functional *by design* because there is no consensus on musical interpretation yet. Also, the task of implementating every notations' function inside Musescore is impractical due to the fact that some digital resource are not created or maintained by Musescore dev team. This includes historical clefs in the [Bravura](https://github.com/steinbergmedia/bravura) font by Steinberg and the [SMuFL](https://w3c.github.io/smufl/latest/index.html) codepoint - glyph definitions, etc. ## External links [Discussion on symbol usage](https://musescore.org/en/node/104266)\ [SMuFL](https://w3c.github.io/smufl/latest/index.html)\ [Bravura](https://github.com/steinbergmedia/bravura) --- # 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/notation/notation-types.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.