> 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-basics.md).
# Text basics
This chapter describes **Musescore Text**. See also the [Notation types](/3/notation/notation-types.md) chapter and the [Text types](/3/text/text-types.md) chapters.
## Adding a text
To add a Musescore Text, either use,
* **Keyboard shortcut**: For example, press Ctrl+Tto enter [Staff text ](/3/text/staff-text-and-system-text.md), Ctrl+L to enter [Lyrics](/3/text/lyrics.md), and so on.
* [**Palette**](/3/basics/palettes.md) **(Workspace)**:
* Select a note and click an icon in one of the palettes (double-click in versions prior to 3.4); or,
* Drag a symbol from a palette onto the staff. E.g. [Swing text](/3/sound-and-playback/swing.md), [Tempo text](/3/sound-and-playback/tempo.md) etc.
* **Menu command**: **Add -> Text**, or
* **Plugin**: such as [Expression Dictionary](https://musescore.org/en/project/expression-dictionary)
## Basic formatting
*See also the* [*Text styles and properties*](/3/text/text-styles-and-properties.md) *chapter.*\
\&#xNAN;*As of Musescore 3.6.2, the inspector interface is not available for editing 1. Instrument names (Long and short name) and 2. Header and Footer. See workaround on the* [*Text styles and properties*](/3/text/text-styles-and-properties.md) *chapter.*
\ The basic formatting options recommended \_for beginners\_ are:
* edit *object properties* with the [Inspector](/3/basics/inspector.md#inspector-categories), and
* edit *individual character's formatting* with Text Toolbar, see [Text editing](/3/text/text-editing.md) chapter.
Options in the Inspector:
* **Font**: The name of the font (e.g. *Times New Roman*, *Arial* etc.), also see [Fonts](/3/advanced-topics/fonts.md).
* **Size** and **Font style** icons: Font style includes e.g. Italic, Bold or Underline.
* **Line Spacing** and **Follow staff size**: "Follow staff size" option determines whether text size changes proportionally, see [Layout and formatting](/3/formatting/layout-and-formatting.md) chapter.
* Alignment icons: Horizontal (left, center, right) and Vertical.
* **Frame**: Choose to have a circular or square frame around the text.
* **Remove Custom Formatting**: Removes all individual characters' formatting previously applied with [Text toolbar](/3/text/text-editing.md), see level of formatting in [Text styles and properties](/3/text/text-styles-and-properties.md) chapter.
To revert changes press the "Reset to style default" (the circular shape) button on the right.
## Adjust position of text objects
To position a text object, use any of the following methods:
* Drag the object.
* Select the object and adjust the X or Y offset values in the [Inspector](/3/basics/inspector.md#inspector-categories).
* Select the object and apply any of the following keyboard shortcuts:
* Left: Move text left 0.1 [staff space](/3/appendix/glossary.md#spatium).
* Right: Move text right 0.1 staff space.
* Up: Move text up 0.1 staff space.
* Down: Move text down 0.1 staff space.
* Ctrl+Left (Mac: Cmd+Left): Move text left one staff space.
* Ctrl+Right (Mac: Cmd+Right): Move text right one staff space.
* Ctrl+Up (Mac: Cmd+Up): Move text up one staff space.
* Ctrl+Down (Mac: Cmd+Down): Moves text down one staff space.
---
# 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-basics.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.