> 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/score-properties.md).
# Score properties
## Overview
This page describes
* the [**Score Properties** dialog](#score-properties-window); and
* the [**Header and Footer** feature](#headerfooter) that automatically add text to the top and the bottom area of *each page* respectively. To add text to *certain page(s)* only, use frame and text block. See [Frames](/3/formatting/frames.md) chapter.
## Score Properties window
The **Score Properties** dialog contains [metadata tags](https://w.wiki/CqB$), editable descriptive digital data of the file. To open it,
1. Open the "Full Score" or a Musescore Part. See [Parts](/3/advanced-topics/parts.md) chapter;
2. Open **File → Score Properties**.
Every score created with Musescore 3 contains the following predefined metadata tags. Some of them are empty initially, some are automatically assigned with information provided in the **New Score** dialog. See [Create a new score](/3/basics/create-a-new-score.md) chapter.
**NOTE**: Score created from a template may generate a top vertical frame with text inside *on the first page*. These frame text are also automatically assigned with information provided, but they *are not linked to and thus not automatically updated with changes made to metadata tags*. See [Frames](/3/formatting/frames.md) chapter.
* **File Path**: The score file's location on user's computer.
* **MuseScore Version**: The version of MuseScore the score was last saved with.
* **Revision**: The revision of MuseScore the score was last saved with.
* **API-Level**: The file format version.
* **arranger**: (empty)
* **composer**: This is initially set to the same text as "Composer" on the first page of the [New Score Wizard](/3/basics/create-a-new-score.md#create-new-score).
* **copyright**: This is initially set to the same text as "Copyright" on the first page of the [New Score Wizard](/3/basics/create-a-new-score.md#create-new-score) (if you need a copyright symbols, copy/paste this: ©).
* **creationDate**: Date of the score creation. This could be empty, if the score was saved in test mode (see [Command line options](/3/appendix/command-line-options.md)).
* **lyricist**: This is initially set to the same text as "Lyricist" on the first page of the [New Score Wizard](/3/basics/create-a-new-score.md#create-new-score).
* **originalFormat**: This tag exists only if the score is imported (see [file formats](/3/advanced-topics/file-formats.md)).
* **platform**: The computing platform the score was created on. This might be empty if the score was saved in test mode.
* **poet**: (empty)
* **source**: May contain a URL if the score was downloaded from or [saved to MuseScore.com](/3/basics/share-scores-online.md).
* **translator**: (empty)
* **workNumber** is the number of the larger work (e.g. 8—for "The Four Seasons," Op. 8, by Vivaldi). *Not* automatically filled in on a new score.
* **workTitle** is the title of the larger work (e.g "The Four Seasons,"). Automatically filled with the "Title" entered in the **New Score** dialog. Some users may find it more appropriate to input the "Title" into **movementTitle** instead.
* **movementNumber** is the number of the movement in the larger work (e.g. 3 for Autumn). *Not* automatically filled in on a new score.
* **movementTitle** is the title of the movement in the larger work (e.g.“Autumn”). *Not* automatically filled in on a new score.
Each Musescore Part, *but not the "Full Score"* (See [Part](/3/advanced-topics/parts.md) chapter) has an additional tag,
* **partName**: The name of the part as given on part creation (which is also used to fill the corresponding part name text in the top vertical frame—*be aware that later changes to one are not reflected in the other*).
### Editing metadata tags
1. Open the "Full Score" or a Musescore Part. See [Parts](/3/advanced-topics/parts.md) chapter;
2. Open **File → Score Properties**;
3. Edit the text of the various metadata tags as required.
There is no way to enter *line breaks* directly when editing metadata tag inside Musescore 3. To display multiline text in a header or footer (as a result of using metadata tags), use an external text editor program (e.g. Notepad for Windows, TextEdit for Mac, Nano for Linux) to create a desired text and copy it into MuseScore. An example of multiline text (feel free to copy and modify).
`Words: © 2000 The Archbishops' Council. Used with permission. Music: © 2006, 2021 The Royal School of Church Music. All Rights Reserved.`
### Adding new metadata tags
1. Open the "Full Score" or a Musescore Part. See [Parts](/3/advanced-topics/parts.md) chapter;
2. Open **File → Score Properties**;
3. Press **New** button, enter name and text;
4. Press **OK**;
### Accessing metadata tags in a score
The only place to add score properties (metadata tags) on to a score is by referring them in header or footer, see Header and footer section below.
## Header/Footer
Use **Header and Footer** feature to automatically add text to the top and the bottom area of *each page* respectively. To add text to *certain page(s)* only, use frame and text block. See [Frames](/3/formatting/frames.md) chapter.
### Adding a header or footer
1. Open the "Full Score" or a Musescore Part. See [Parts](/3/advanced-topics/parts.md) chapter;
2. Open **Format → Style → Header, Footer**;
3. Check the **Header Text** and **Footer Text** boxes as required.
### Entering information
Open **Format → Style → Header, Footer**,
* The area on the top is for headers, area below it is for footers.
* Both of them are divided into two rows, labelled Odd, and Even, for content on odd and even pages respectively.
* They are also divided into three columns, labelled Left, Middle, and Right, representing the corresponding areas.
There are three kinds of valid input,
* plain text,
* placeholder text, or special symbols, that converts into information automatically, they include
* *read-only* information such as the current page number, and
* *editable* metadata, see ["Using metadata"](#using-metadata) section.
Placeholder text or special symbols are case-sensitive, they must be entered letter-for-letter with the correct case. For example,
* $d converts into current date
* $D converts into creation date
* $:movementNumber: converts into "Moverment number" metadata
* $:movementnumber: is invalid because of the wrong lower case 'n'
Musescore version and revision last saved $v and $r are only available in MuseScore 3.6 and after.
The part name placeholder text, $I, $i, or $:partName: , is only available in a Musescore Part, *but not the "Full Score"* (See [Part](/3/advanced-topics/parts.md) chapter).
To see a list of available placeholder text or special symbols, hover the mouse cursor over any text input area and wait for a popup box to appear. Shown below is the list for Musescore 3.\\
### Using metadata
Metadata are digital information, or tags, assigned in **File→Score properties**, use $:\[metadata tag]: syntax to add them to header and footer. See the example in ["Entering information"](#entering-information) section, and the [Score Properties](#score-properties-window) section above.
### Editing text formatting
Format the header or footer item itself with **Format → Style → Text Styles → Header** and **Footer**. Format individual characters with workaround on the [Text styles and properties](/3/text/text-styles-and-properties.md#workaround-for-lack-of-inspector-and-text-editing-mode) chapter.
## See also
* [Layout and formatting: Header and footer](/3/formatting/layout-and-formatting.md#header-footer)
* [Frames](/3/formatting/frames.md)
* [Command line options: Test mode](/3/appendix/command-line-options.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 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/score-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.