> 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/sound-and-playback/tempo.md).

# Tempo

This page provides information on [tempo markings](#tempo-marking), [fermata symbols](#fermata), their playback details, [changing monitoring playback tempo](#changing-monitoring-playback-tempo-in-play-panel) and [adding metronome tick sound](#metronome). To add markings such as `♬ = ♪ 𝅘𝅥𝅯` see [Swing](/3/sound-and-playback/swing.md) chapter.

## Tempo marking

## Overview

The musical terminology tempo means the speed or pace of a composition. The following **Tempo** [Text](/3/text/text-types.md) can change playback tempo inside Musescore,

* **Metronome marks**: Consists of a note, an equals sign, and a whole number. For example (crotchet) `♩ = 80`
* **Verbal tempo indications**: Andante, Allegro etc.
* **Metric modulations**: `♩ = ♪` (crotchet = quaver)

Musescore's synthesizer paces based on two settings,

* The real, written tempo of score. It is only determined by tempo markings on the score. *Section breaks and barlines do not reset anything.* If no tempo marking is present on a score, it plays as if `♩ = 120` is used (120 crotchets or quarter notes in one minute), and
* The [control slider that change pace temporarily, intended for monitoring](#changing-monitoring-playback-tempo-in-play-panel).

Musicians use tempo markings to help indicate the value of one beat, but Musescore does not - beat information is obtained from [Time signatures](/3/notation/time-signatures.md) only, and is referred to in other functions such as navigation, [metronome tick sound](#metronome) etc.

[Inspector's Tempo field](#changing-playback) uses a special unit "BPM". "BPM" is the amount of *quarter notes would have been* within one minute in decimal number. It is not related to the musical beat. It is not the whole number used in metronome marks conventionally, or on the score. This unit is also used in [Play panel](/3/sound-and-playback/play-mode.md#play-panel).

Playback of **Metronome marks** and **Metric modulations** follows [written numerical content](#changing-appearance) (by default, [can be overridden](#changing-playback)) but ignores accompanying text. Musescore does not understand the content of **Verbal tempo indications**, they have *pre-defined tempo settings* that [are editable](#changing-playback).

## Adding tempo marking

All markings are found in the **Tempo** [palette](/3/basics/palettes.md). New tempo markings are positioned at the top of system (a layout term. See the [Layout and formatting](/3/formatting/layout-and-formatting.md#page) and the [Text type](/3/text/text-types.md) chapters).

To add a **Metronome mark, Verbal tempo indication, or Metric modulation**, either

* Select a note/rest and click a palette item (double-click in Musescore version 3.3.4 and before),
* Drag a palette item onto a note/rest,
* Click **Add → Text → Tempo marking**, or
* Use plugins such as [Tap tempo](https://musescore.org/en/project/tap-tempo).

To add a **Metronome mark** that use a suitable note value that matches the beat information from the time signature,

* Select a note/rest and press the keyboard shortcut <kbd>Alt</kbd>+<kbd>Shift</kbd>+<kbd>T</kbd>.

## Changing appearance

Playback can be configured to follow written content of **Metronome mark and Metric modulation**, provided that the note symbol and augmentation dot are *special characters*. The augmentation dot is not a full stop or period. The equal sign and numbers are *plain characters*. Formatting options are covered in the ["Properties and global settings"](#properties-and-global-settings) section.

### Adding plain characters

1. Select an object.
2. Enter [edit mode](/3/basics/edit-mode.md#edit-mode) (double click)
3. Type text.

### Adding special characters

1. Select an object.
2. Enter [edit mode](/3/basics/edit-mode.md#edit-mode) (double click).
3. Use **Special characters window: Common symbols tab**, one way to open the window is <kbd>F2</kbd>

## Changing playback

To assign a manual overriding tempo setting,

1. Select object(s).
2. Uncheck [Inspector](/3/basics/inspector.md) → "Tempo text" : **Follow text**.
3. Enter a value in **Tempo**, this value use the special BPM unit, which is not related to musical beat. See [Overview](#overview).

## Repeating tempo markings on other staves

Tempo markings [anchor and thus are displayed](/3/text/text-types.md) like **System Text**. To duplicate markings onto multiple staves, see [Staff Text and System Text: Repeating System Text on other staves](/3/text/staff-text-and-system-text.md#repeating-system-text-on-other-staves) chapter.

## Properties and global settings

<figure><img src="/files/jBVksy8wRtpOUu87JZlX" alt="Inspector: Tempo Text"><figcaption></figcaption></figure>

[Selected](/3/basics/selecting-elements.md) tempo markings(s) on a score can be edited with [Inspector](/3/basics/inspector.md),

Under the "Text" section,

* **Fontface**: Affects [plain characters](#changing-appearance). Ignored by [special characters](#changing-appearance), which always use fontface selected under **Format → Style → Score : Musical text font**.
* **Remove Custom Formatting**: Very rarely used. Removes \<sym> internal codings and makes special characters inside incompatible with the "Musical text" global styling functionality. See the [Fonts](/3/advanced-topics/fonts.md) chapter.
* See also the [Text basics](/3/text/text-basics.md) chapter.

Under the "Tempo text" section,

* **Follow text**: Toggle Musescore's metronome marking interpretation function.
* **Tempo**: [Manual overriding tempo](#changing-playback) used when **Follow text** is unchecked.
* **Style**: "Text Style" profile applied. See the [Text styles and properties](/3/text/text-styles-and-properties.md) chapter.
* **Placement**: Position, above or below staff.

Global settings are covered in the [Layout and formatting](/3/formatting/layout-and-formatting.md) chapter.

## Creating ritardando and accelerando

Musescore does not understand and does not create playback for any *tempo expression text*, including **ritardando** ("*rit.*") and **accelerando** ("*accel.*"), and thus cannot create correct playback for these.

To create **ritardando** ("*rit.*") and **accelerando** ("*accel.*") marking and proper playback:

1. Add multiple tempo markings for playback. [Make tempo markings invisible](/3/basics/inspector.md) as required, visibility does not affect playback. Use the [*TempoChanges*](https://musescore.org/project/tempochanges) plugin to automate this process.
2. Add [Staff/System Text](/3/text/staff-text-and-system-text.md) for printing and reading.

In the example illustrated below, the tempo was originally 110 crotchets per minute. At the ritardando, the value decreases by 10 on the first note of each measure. Each tempo change is made invisible by unchecking the **Visible** checkbox in the [Inspector](/3/basics/inspector.md) (Keyboard Shortcut V), so that only the ritardando shows on the printed score:

<figure><img src="/files/QWzcCFNVpBsxDwOyKUa8" alt="Ritardando"><figcaption></figcaption></figure>

## Changing monitoring playback tempo in Play Panel

<figure><img src="/files/tIEhXozvwXy4CrDkcd6h" alt="Play panel"><figcaption></figcaption></figure>

Use [Play Panel](/3/sound-and-playback/play-mode.md#play-panel) to change playback tempo temporarily:

1. Display the play panel: **View→Play Panel** or <kbd>F11</kbd> (Mac: <kbd>Fn</kbd>+<kbd>F11</kbd>):
2. Move the tempo slider up or down as required. Double-click the tempo slider to reset it. BPM is a special unit used by Musescore, which is not related to musical beat. See [overview](#overview).

## Fermata

Fermata are available in the [Articulations and Ornaments](/3/notation/articulations-and-ornaments.md) palette.\
In playback on a score with multiple instruments, if a note or rest of one instrument is extended with a fermata symbol, every notes sounding the same moment as that note will continue to sound until the extended note ends. [Fermatas applied to barlines has no effect](/3/notation/articulations-and-ornaments.md#add-fermata-to-a-barline)

## Inspector properties

Select a Fermata symbol, edit its property in **Fermata** in the [Inspector](/3/basics/inspector.md):

**Placement**: Above or below note\
**Time stretch**: Multiplication of normal time duration to play back the current element. Value 1.00 is meaningless as it means no time extension.

## Metronome

Musescore can automatically add metronome ticks sound to playback if desired, use the Playback toolbar or Play Panel, see the [Play mode](/3/sound-and-playback/play-mode.md#play-panel) chapter.

How many ticks are added onto each measure is determined by the time signature and tempo. It does *not* depend on the note value (duration) used on metronome markings (both crotchet `♩ = 60` and quaver `♪ = 120` markings create identical result).

There are two tick sound clips, strong ticks and weak ticks. Which one is added is determined by the beat and written tempo (not affected by the adjustment settings on the Play Panel, but see comments on a related feature request [#304412](https://musescore.org/en/node/304412)). Beat is dictated by the time signature only, but *not* affected by the beaming style, or the note value (duration) used on metronome markings.

* For simple meters, the top number of the time signature is the number of beats in each measure. 2 = duple, 3 = triple, 4 = quadruple. Strong ticks are created on each beat. No weak ticks are created.
* For compound meters (6/8, 9/8, etc), the top number of the time signature divided by three, is the number of beats in each measure. 6 = duple, 9 = triple, 12 = quadruple. Strong ticks are created on each beat. Weak ticks (two weaks following one strong) are created only if it is below 60 beats per minute. For example, onto measure using 6/8, both dotted crotchet `♩ . = 59` and quaver `♪ = 179` markings create the result of two strong ticks and four weak ticks in each measure.

These ticks are not added to any [exported audio files](/3/basics/opensaveexportprint.md). If you want to include these ticks to exported audio, try these:

* Add a percussion staff, fill the first measure with the desired rhythm and the rest with measure repeats, then hide that staff, [source](https://musescore.org/en/node/154666?page=1),
* [Metronome SoundFont (CC0)](https://musescore.org/en/node/320431) provided by mirabilos,
* [Add metronome part](https://musescore.org/en/project/add-metronome-part) plugin by sal.vador.

## See also

* [Text types](/3/text/text-types.md)
* [Fonts](/3/advanced-topics/fonts.md)
* [Play mode](/3/sound-and-playback/play-mode.md)
* [Time signature](/3/notation/time-signatures.md)

## External links

* [How to create a visual swing marking](https://musescore.org/en/node/266325) (MuseScore HowTo)
* [Metrico: a font to create metronome marks, metric modulations and swing indications for music notation.](https://github.com/fkretlow/metrico)


---

# 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/sound-and-playback/tempo.md?ask=<question>&goal=<endgoal>
```

`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.
