> 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/text-styles-and-properties.md).
# Text styles and properties
## Overview
Layout and formatting concepts, and methods to re-use settings are covered in the [Layout and formatting](/3/formatting/layout-and-formatting.md) chapter. With regard to *Text objects* on a score file,
* Overview of settings,
* *Properties* of each individual Text object includes,
* Settings on individual character,
* Settings on object.
* *Global settings* includes,
* "**style for type** of object" under **Format → Style → \[item]**, and
* "**Text Style**" or "**style for text** inside type of object" under **Format → Style → Text Styles → \[item]**. ("Text Style" is the wording displayed inside musescore 3. To avoid confusions such as "Staff Text Style" and "Staff Text Text Style", the handbook uses wording "Style for text inside \[item]" whenever necessary.)
* Formatting can be assigned to individual character. To edit or clear settings on all characters, see [Text editing: Text edit mode](/3/text/text-editing.md#enterexit-text-edit-mode) chapter. Characters do not have any specific formatting initially. When formatting are added to them, they will always be used.
* A Text object itself does not have any specific *properties* initially. When properties are assigned in the Inspector, they will always be used, except for characters that already have formatting setting. To remove item properties, or set a property as global (move to style), see the [Inspector](/3/basics/inspector.md) chapter.
* User can edit values of ["**style for type** of object"](#the-style-for-type-of-object) and ["**style for text** inside type of object"](#text-style-or-style-for-text-inside-type-of-object).
* User can [apply "**style for text** inside type of object"](#applying-to-score-object) onto Text objects on a score.
* User can utilize [custom "**style for text** inside type of object"](#editing-and-applying-custom-profile) section.
* The "**style for text** inside **Staff Text**" is special. In addition to its original role for [Staff Text](/3/text/staff-text-and-system-text.md), it also serves as the master fallback profile of all Text objects. All Text objects on a score use its values unless overridden by other more speific settings.
* A subset of characters are treated specially. They always use font settings in **Format → Style → Score : Musical symbol font**. This includes musical glyphs such as Segno, Coda, ottavas, dynamics **glyphs** such as ***mf*** and some [Symbols and special characters](/3/text/text-editing.md#symbols-and-special-characters). See [Fonts](/3/advanced-topics/fonts.md) chapter.
## Text properties
* See [the Inspector](/3/basics/inspector.md) and [Text basics](/3/text/text-basics.md) chapter.
## The "**style for type** of object"
* Edit settings under **Format → Style → \[item]**. Settings are explained in ['Style' window](/3/formatting/layout-and-formatting.md#style-window) chapter.
## "**Text Style**" or "**style for text** inside type of object"
To edit style for text (profile), either:
* Edit settings under the **Format → Style → Text Styles → \[item]**, or
* Edit properties in the [Inspector](/3/basics/inspector.md), and click the **Set as style**.
Contains these options
* **Name** : Editable in User-1 to User-12 only.
* **Font** and **Size**: The name of the font (e.g. *Times New Roman*, *Arial* etc.) and its size in points, also see [Fonts](/3/advanced-topics/fonts.md).
* **Line Spacing**
* **Follow staff size**: determines whether text size changes proportionally, see [Layout and formatting](/3/formatting/layout-and-formatting.md) chapter.
* **Font style**: The font style to use, e.g. Italic, Bold or Underline.
* **Align**: Horizontal (left, center, right) and Vertical.
* **Color**: Color and **opacity** of the text. Opacity is set by the parameter "Alpha channel" in the "Select Color" dialog: a value between 0, transparent, and 255, opaque.
* **Offset** **X**/**Y**: Horizontal and vertical offsets in sp. units.
* **Frame**: Choose to have a circular or square frame around the text.
* **Border**: Color and **opacity** of the frame border.
* **Highlight**: Color of the background within the frame.
* **Thickness**: Thickness of the line of the frame in space units.
* **Margin**: Inner frame margin in space units.
* **Corner radius**: For box frame, radius of rounded corner.
### Applying to score object
* Change score object's **Style** property in [the Inspector](/3/basics/inspector.md).
### Editing and applying custom profile
\\
1. Edit custom style under **Format → Style → Text Styles → User-1" to "User-12**.
2. Change score object's **Style** property in [the Inspector](/3/basics/inspector.md).
## Workaround for lack of inspector and text editing mode
Edit using internal xml-like code when the interface is not available. See reference 1.
Applicable to,
* Instrument names (Long and short name). Main chapter [Staff / Part properties](/3/advanced-topics/staff--part-properties.md).
* Header and Footer. Main chapter [Score properties](/3/advanced-topics/score-properties.md#headerfooter).
Syntax ptions are,
* Set font size: `text`. Exactly one blank space. Nesting is mandatory.
* Set font family: `text`. Exactly one blank space. Nesting is mandatory.
* Set bold: `text`.
* Set italic: `text`.
* Set underline: `text`.
* Set subscript: `text`.
* Set superscript: `text`.
* Add symbol: `internalname`. See reference 2.
The [TUTORIAL: How to use ANY font for Instrument Names (and Chords) and still have a cool Flat sign](https://musescore.org/en/node/358259) is written for Musescore 4, it also works on Musescore 3.6.2.
## See also
* [Text editing](/3/text/text-editing.md)
* [Fonts](/3/advanced-topics/fonts.md)
* [Header/Footer](/3/advanced-topics/score-properties.md#headerfooter)
* [Behavior of applied text and lines](/3/basics/palettes.md#behavior-of-applied-text-and-lines)
## External
* Reference 1 [textbase.cpp sourcecode bookmark](https://github.com/fp22june/MuseScoreTag362/blob/master/libmscore/textbase.cpp#L1678)
* Reference 2 [sym.h sourcecode bookmark](https://github.com/fp22june/MuseScoreTag362/blob/master/libmscore/sym.h#L45)
---
# 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/text-styles-and-properties.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.